$ loading_
Write and maintain technical docs, from READMEs to API and runbook guides.
This skill is essentially an open-source prompt-only documentation writing skill with no required secrets, no declared network endpoints, and no local execution or data access capabilities, so overall risk is low. It comes from a GitHub repository, but adoption and maintenance signals are limited, so basic supply-chain awareness is still advisable.
The materials explicitly state that no API keys or environment variables are required; as a prompt-only skill, it does not introduce a credential injection, storage, or abuse path.
No remote endpoints or network behavior are declared, and the README only describes documentation structures and principles, with no indication that user data is sent to third parties.
The system flags it as prompt-only; the documentation shows no ability to start local processes, run scripts, or invoke system capabilities.
The materials declare no access to filesystems, databases, or external resources; its role is limited to generating/maintaining documentation prompts and does not show local or remote data read/write capability.
The source is an open-source GitHub repository, making it auditable and significantly lowering supply-chain risk; although the license is unspecified, it has 0 stars, and maintenance is unknown, there are no concrete high-risk red flags given that this is a non-executing prompt-only skill.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "documentation" skill from askskill: 1. Download https://raw.githubusercontent.com/anthropics/knowledge-work-plugins/main/engineering/skills/documentation/SKILL.md 2. Save it as ~/.claude/skills/documentation/SKILL.md 3. Reload skills and tell me it's ready
Based on this project's code structure and feature overview, write a complete README including introduction, installation steps, usage examples, configuration notes, and FAQ.
A well-structured project README suitable for open-source or internal team use.
Write API documentation for the following endpoints, including paths, parameter descriptions, sample requests, sample responses, error codes, and authentication details, in a format suitable for frontend-backend collaboration.
A standardized API document set that supports development, integration, and maintenance.
Create an operations runbook for this production service, covering common alerts, troubleshooting steps, recovery actions, rollback plans, and escalation contacts for on-call engineers.
An actionable incident runbook that helps on-call staff diagnose issues and restore service quickly.
Write clear, maintainable technical documentation for different audiences and purposes.
Embed Zoom Virtual Agent chat on web with secure controls and context updates.
Quickly add Zoom’s prebuilt React video UI to web workflows.
Create stakeholder updates tailored to audience, cadence, and communication goals.
Review an analysis for methodology, accuracy, bias, and evidence support.
Generate people analytics reports on headcount, attrition, diversity, and org health.
Identify, categorize, and prioritize technical debt for smarter refactoring decisions.
Guide users to co-author docs, proposals, and specs through iterative refinement.
Create and review technical docs and agent instruction files in repositories.
Create or update repeatable operational runbooks and incident response procedures.
Analyze Python codebases and generate README, API docs, and setup guides.
Generate, search, and maintain codebase documentation for faster team development.
Read, edit, and write Feishu documents for faster cloud collaboration.