suggest-docs-skills-to-write
by balukosuri
Use this skill when a technical writer wants a concrete, prioritized list of new skills worth writing for their documentation work — not a generic skill catalog, but suggestions grounded in their real repo and how they actually work. Triggers on requests like "what skills should I write for this docs repo," "suggest skills I should add to my stack," "what Cursor skills would help my team," "audit my repo and tell me what to automate with skills," "which skills am I missing," or "help me decide what skills to author next." The default deliverable is a justified slate of skills to write (name, purpose, triggers, why it fits them). Optional follow-up only if they explicitly ask — draft one or more SKILL.md files to a path they choose. Flow — (1) mechanical scan plus reading real documentation pages (prose, not just git history), (2) short adaptive interview ("Plan Mode") shaped by what the repo and content showed, (3) recommend which skills to write and in what order, (4) only on opt-in, generate SKILL.md drafts. Always consider this skill when the goal is deciding what to build, not polishing a single doc page — including indirect phrasings like "where should I invest in automation," "what should I script next for docs," or "I want more leverage from AI on this repo." Do not use this skill for one-off doc edits, single-topic copy audits, or "write me a random skill" with no repo and no sense of their workflow.