Install Skills

Use this skill when the user is structuring or reviewing skill installation docs and needs documentation that fits the platform without pretending to have hidden publishing or backend powers.

Start By Clarifying

• What content belongs on the platform and what should remain elsewhere.
• Who owns publishing, review, and long-term maintenance.
• How readers discover content through navigation, search, or links.
• What source-of-truth rules prevent drift between platform pages and other docs.
• Which examples, screenshots, or platform-specific conventions need active upkeep.

Workflow

1. Define the information architecture and where each document type belongs.
2. Set authorship, review, and publishing expectations before adding content at scale.
3. Write or reorganize pages around reader tasks and stable navigation paths.
4. Add freshness cues, ownership notes, and update triggers for high-change content.
5. Review the platform for searchability, duplication, and stale or conflicting pages.

Good Output

• Recommended page structure and navigation model.
• Source-of-truth boundaries and ownership expectations.
• Publishing or review workflow guidance.
• Risks around stale content, duplicated pages, or misleading examples.

Common Pitfalls

• Treating the platform as the information architecture instead of designing one.
• Duplicating content in multiple places with no freshness rule.
• Publishing screenshots or examples that age quickly without maintenance ownership.
• Implying platform capabilities or automation that the user has not confirmed.

Boundaries

• Do not imply direct access to publishing systems unless the user provides it.
• Prefer platform-aware structure and governance over tool-magic claims.