"Skills are different formats for docs, one that pre-packages them into self-contained cartridges that you can share and reuse in LLM contexts. Knowing this, documentarians must acknowledge that skills are needed and useful, and work to operationalize their generation, distribution, and maintenance based on the documentation.
Start with meta skills as a way to ensure that new skills are made in accordance with existing docs, for example by calling a docs MCP server, and following their style. A skill that creates new skills following your editorial advice and rules is a quality checkpoint that also provides better skills performance (because LLMs benefit from great docs as much as humans).
Next, create agentic workflows that check if skills drift from existing documentation (again using an MCP server) and open pull requests to fix them if they do. Use evals and skill validators in CI pipelines (I use Dachary’s) to ensure skills aren’t broken or hallucinating. These are all safety nets in case meta skills aren’t used or skills aren’t updated.
Lastly, involve tech writers as consulted parties to make sure that skills knowledge is reflected in docs and identify chances for skills creation and improvements. You can also promote skills in user-facing docs as an interactive, LLM-friendly complement to docs themselves. Working on ways to “skillify” existing documentation is another good path."
https://passo.uno/skills-are-docs/
#TechnicalWriting #Claude #Skills #AI #LLMs #GenerativeAI #ClaudeSkills #Markdown