skills/renatocaliari/pi-product-workflow/cali-product-workflow/skills-domain-libraries/cali-product-promotions/SKILL.md
Launch promotion strategies using the MAGIC framework. Covers Loss Leader, Gift Card Sale, Limited High-Value Package, and Irresistible Freebie strategies with tactical examples.
npx skillsauth add renatocaliari/agent-sync-public-skills cali-product-promotionsInstall 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.
A simple offer, but communicated unequivocally, tends to work better than a brilliant offer that nobody understands.
M (Magnet → Reason): what is the magnetic reason for this offer to exist now? (discount, special launch condition, seasonal offer) Creates the context.
A (Avatar → Avatar): who is this offer for? Naming the audience helps the person immediately identify. (small business owners? writers? those seeking a healthy lifestyle?)
G (Goal → Purpose): what is the desired outcome the person can achieve? It's not a guarantee, but the direction, the purpose. (clarity in business? launching a product?)
I (Interval → Timeframe): in how much time or for how long? Defines a temporal horizon that makes the promise more concrete. (30 days? 6 weeks? a single meeting?)
C (Container → Packaging): what is the "packaging" of the offer? A word that gives shape to the experience and helps make it tangible. (a program, a blueprint, a workshop, a mentoring, a consulting)
Drastically reduce the entry barrier so a new customer can experience your work. You offer an initial product or service with a calculated loss, knowing that a portion of these customers will purchase higher-value solutions in the future.
Tactical Examples:
Allows generating upfront revenue and turning current customers into an acquisition channel. The person buys a service (for themselves or to gift) with perceived value much higher than the amount paid.
Tactical Examples:
Instead of offering a discount to everyone, create an exclusive and premium offer for the most engaged audience. Scarcity is not in the price, but in access.
Tactical Examples:
Instead of giving a price discount, you add more value to the original offer. The perception of getting something valuable for free can be psychologically more attractive than a simple discount.
Tactical Examples:
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.