Track 4 — Build & monetise 构建与变现 · M19 · 25 min · Live today
Best practices and anti-patterns
What separates a skill people trust from one they uninstall: narrow scope, deterministic rules, real evidence on the Decision Card, budgets, versioning, and an honest failure path.
Prerequisites: M16 · Create your first twin in 30 minutes
After this module you can…
- Review a skill against a checklist before publishing it.
- Name the four anti-patterns that most often break trust.
Key points
- One skill, one job. A skill that does five things cannot be scoped or priced.
- Rules must be checkable by a reviewer who never reads the prompt.
- A Decision Card with no evidence panel is just a confirm dialog.
- Version every change; never silently mutate a skill buyers already installed.
- Anti-patterns: vague rules, hidden side effects, unbounded runs, simulated success.
Hands-on exercise: Review someone else's skill
- Open a skill you did not write and read only its manifest.
- Predict its risk tier and side effects, then check the derived contract.
- Write one concrete improvement.
Evidence of success: A written review naming one anti-pattern.
Knowledge check
Getting it wrong is fine — the explanation tells you why.
1. A skill's rules say "handle refunds sensibly". What is wrong?
2. You improve an installed skill. What must you do?
Module 19 of 20 · progress is stored on this device.