skills/renatocaliari/pi-product-workflow/cali-product-workflow/skills-domain-libraries/cali-product-trust-building/SKILL.md
Building trust through perception and guarantee mechanisms. Covers ten pillars to materialize trust, guarantee types from unconditional to anti-guarantees, and strategic approaches for different contexts.
npx skillsauth add renatocaliari/agent-sync-public-skills cali-product-trust-buildingInstall 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.
When someone seeks us out, they carry the weight of past experiences, skepticism, and the fear of making the wrong decision once again. The person is not just asking themselves "does this work?", but rather "will this work for me?".
Trust manifests here in a deeper way: not in more gain promises, but in the removal of loss risk. Subtracting fear becomes more powerful than adding one more benefit.
The most radical form of removing friction. The message: "I'm not asking you to say yes or no today, but to make an informed decision. Both choices are risk-free, but only one of them can help you reach your purpose." The responsibility for risk is fully absorbed by whoever offers the help.
Co-responsibility approach. Must be "better than money back" — because the person's time and energy are also valuable. Aligns commitment: "If you do your part, I guarantee mine."
Explicitly state the minimum requirements that the person must fulfill to access the guarantee (e.g., having used the product with a minimum of Y people for so long; having participated for at least X days of training; etc.)
Examples of super guarantee after passing minimum requirements:
In contexts of high demand or rare opportunities, the absence of a guarantee can, paradoxically, signal value. The "all sales are final" policy works best for high-value services or explosive situations, where the opportunity itself is the great attraction.
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.