skills/local/cali-product-workflow/skills-strategic-analysis/cali-product-discovery/SKILL.md
[Cali] Complete expert in the short-cycle product learning method, based on the e-book "Guide to Creating Products with Short Learning Cycles" by Cali (Renato Caliari). Use this skill whenever the user asks about: idea validation, customer discovery, product experimentation, jobs to be done, pricing strategies, business models, marketing channels, early adopters, MVP, product-market fit, pre-sales, launch strategies, product innovation, product lifecycle, building customer trust, marketplace, open source as strategy, or any concept related to creating and validating digital products with low risk and fast learning. This skill contains ALL the method details — do not skip any detail.
npx skillsauth add renatocaliari/agent-sync-public-skills cali-product-discoveryInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This guide is a method to replace speculation with evidence, step by step. Core principle: experiment before building. Reduce uncertainty with small, fast, and cheap experiments.
"Life is too short to build something that nobody wants." — Ash Maurya
The process has 8 stages (not necessarily linear):
→ Read reference files as needed:
references/01-experimentation-principles.md — criteria for reliable data + 6 principlesreferences/02-stages-1-to-3.md — audience, market, solutionsreferences/03-stages-4-to-6.md — offer, commitment, manual processreferences/04-stage-7.md — viable business, product-market fit, channelsreferences/05-stage-8-signals.md — pulse of the system, signals in tensionreferences/06-appendix-business-models.md — business models, open source, pricingreferences/07-appendix-strategies.md — marketplace, solutions, trust, bonuses, promotions, ads, lifecycle| User asks about... | Read... | |---|---| | How to validate an idea / experiment | 01, 02 | | Target audience, market, jobs to be done | 02 | | Solution, product, features | 02, 03 | | Offer, advertisement, early adopters | 03 | | Pre-sale, commitment, waitlist | 03 | | MVP, manual process, concierge, wizard of oz | 03 | | Product-market fit, channels, viable business | 04 | | Metrics, retention, growth | 04, 05 | | Pricing, pricing models | 06 | | Business models, revenue, costs | 06 | | Open source as strategy | 06 | | Marketplace, supply and demand | 07 | | Trust, guarantees, social proof | 07 | | Bonuses, launch promotions | 07 | | Online ads, stages of awareness | 07 | | Product lifecycle, innovation | 07 |
IMPORTANT: When the user needs to choose between predefined options, ALWAYS use the question tool (if available) with enumerated format:
label and descriptionWhen question tool is not available, use enumerated text in chat (A/B/C/D or 1/2/3).
Note for this skill: This is primarily a reference/exploratory skill. If the user wants to explore a specific concept, you may ask clarifying questions to understand context before recommending which references to read or which stage to focus on.
This skill is based on the e-book "Guia para criar produtos com aprendizado em ciclos curtos" (Guide to Creating Products with Short Learning Cycles) by Renato Caliari.
Author: Renato Caliari
Substack: Practical Guide to Validate Ideas
GitHub: @renatocaliari
This skill was translated and adapted by permission and attribution to the original author.
Original Repository: github.com/renatocaliari/my-opencode-config
For specialized analysis, these standalone skills are available at github.com/renatocaliari/agent-sync-public:
| Skill | Description | Lines |
|-------|-----------|--------|
| cali-product-health | Product health monitoring via signals in tension | ~100 |
| cali-product-pricing | Pricing strategy: Exchange Base, Consumption Control, Interest Alignment, Trust Pact | ~100 |
| cali-product-open-source | OSS as business strategy: Proprietary Problem, Org Structures, Competition Protection | ~60 |
| cali-product-trust-building | 10 pillars of trust, guarantees, perception, commitment | ~60 |
| cali-product-promotions | MAGIC framework, 4 launch strategies, bonuses | ~60 |
| cali-product-business-models | Cost reduction & revenue generation models | ~80 |
| cali-product-ads | 5 awareness stages, ad categories | ~50 |
Install (if you don't have it yet): ... Note: These are optional enhancements. The core method works without them — the references/ contain all the necessary content.
tools
Auto-initialize structured documentation for any project using lat.md (knowledge graph of markdown files with [[wiki links]], // @lat: code refs, and semantic search). Detects cali-product-workflow artifacts (spec-product.md, spec-tech.md, critiques) and uses them as seed material. Falls back to extracting business rules, architecture, and design decisions directly from the codebase. Use when a project lacks structured documentation or when lat.md/ is missing. After seeding, lat.md extension hooks keep documentation alive automatically.
testing
[Cali] Server security audit and hardening for private servers behind Tailscale. Use when: auditing server security, hardening SSH/firewall/Docker, checking for vulnerabilities, setting up fail2ban, reviewing port exposure, or responding to security alerts. Covers 6 layers: CloudFlare, UFW, Tailscale, SSH, Docker, Application. Triggers: "server security", "security audit", "harden server", "SSH hardening", "firewall rules", "UFW config", "fail2ban", "port security", "Docker security", "vulnerability check", "security review".
tools
Run supply chain security scans before installing packages or before releases. Triggers when: user installs a package (npm, pip, go get, brew), user asks to 'scan dependencies', 'check vulnerabilities', 'supply chain', 'security audit', 'run trivy', 'run socket', or before any release/deployment. Also triggers on mentions of: socket.dev, trivy, OSV-scanner, dotenvx, CVE, dependency audit. Covers all four tools with concrete commands.
tools
Create GitHub releases following project conventions. Triggers when: user says 'release', 'create release', 'push release', 'deploy to main', 'merge to main', user merges a PR to main, or when git push to main is detected. Also triggers on mentions of: gh release, semver, version bump, changelog, release-please. Covers: config-driven (read .release.yml and execute) and fallback (gh CLI) release flows, versioning rules, tag management, and the mandatory release-on-merge convention.