Packages Documentation
CheckedGenerates clear, concise documentation for software packages, including installation instructions and usage examples.
Install on your platform
packages-documentation. SKILL.md is marked internal, so the skills CLI hides it.We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-10-21. We don't show a command we know will fail.
What we know about this skill
Publisher
reactive
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned reactive/data-client at 4ae608081e.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 4ae608081e
- Scanned
- 1 file, 98 lines
About this skill
What it does
This skill generates documentation for software packages. It can analyze package files and produce formatted documentation, including descriptions of functions, classes, and modules. The generated documentation aims to be clear, concise, and easily understandable by developers.
When to use it
- Creating API references: Generate comprehensive documentation for a library or framework's public API.
- Onboarding new team members: Quickly create documentation to help new developers understand the codebase.
- Automating documentation updates: Keep documentation synchronized with code changes through automated generation.
- Generating user guides: Produce user-friendly guides explaining how to use a software package.
Key capabilities
- Package file analysis
- Formatted documentation generation
- Description of functions, classes and modules
- Clear and concise writing style
Example prompts
- "Generate documentation for the 'my-package' library."
- "Create API reference documentation for all public functions in this code."
- “Can you document the ‘data-client’ package?”
Tips & gotchas
The quality of the generated documentation depends heavily on the clarity and structure of the original package files. Ensure your code includes sufficient comments to facilitate accurate documentation generation.