documentation
Build Complete Technical Documentation
Software documentation often becomes fragmented across formats and project stages. This skill provides a phased workflow for planning, creating, publishing, and maintaining it.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "documentation" from https://skillstore.io/skills/sickn33-documentation.md and its manifest at https://skillstore.io/api/skills/sickn33-documentation/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "documentation". Plan documentation for a new payment API used by external developers.
Expected outcome:
- Planning: define audiences, terminology, ownership, and publication structure.
- API reference: document authentication, endpoints, schemas, errors, and complete requests.
- Guides: add setup, first transaction, testing, troubleshooting, and migration topics.
- Quality gates: validate examples, links, API coverage, and release ownership.
Using "documentation". Create an architecture documentation plan for a distributed order system.
Expected outcome:
- Start with system context and external dependencies.
- Describe services, data stores, queues, and deployment boundaries.
- Add component, sequence, data flow, and failure recovery views.
- Review diagrams whenever interfaces or deployment topology change.
Using "documentation". Improve an outdated internal engineering wiki.
Expected outcome:
The plan inventories pages, assigns owners, restructures navigation, updates onboarding content, repairs links, and schedules recurring reviews.
Security Audit
SafeAll 63 static findings were reviewed against SKILL.md. The 61 execution alerts are Markdown syntax, while both reconnaissance alerts are ordinary documentation text without executable behavior or malicious intent.
Risk Factors
⚙️ External commands (50)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-documentation/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-documentation?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-documentation?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-documentation/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-documentation.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). documentation security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-documentation/audits/5BibTeX citation
@techreport{sickn33-sickn33-documentation-2026,
author = {sickn33},
title = {documentation security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-documentation/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "documentation security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/sickn33-documentation/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-documentation:audit:5"
description: "Skillstore immutable audit report identifier"
Compare variants
5 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
89jobrien-documentation
2026-08-21
sickn33-documentation
2026-08-21
bfdcampos-documentation
2026-08-21
crazyswami-documentation
2026-08-21
daothihuong2111-documentation
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Document a new service
Plan a README, API reference, setup guide, and examples for a software service.
Describe system architecture
Coordinate context, container, component, sequence, data flow, and deployment documentation.
Maintain a documentation portal
Structure wiki pages, onboarding guides, release notes, references, and recurring quality reviews.
Try These Prompts
Create a documentation plan for [project], including its audience, README sections, setup guide, usage examples, and review checklist.
Plan API documentation for [service] from [source], covering endpoints, schemas, authentication, examples, OpenAPI output, and validation.
Design a C4 documentation set for [system], including context, containers, components, data flows, sequences, deployment, and Mermaid diagrams.
Build a phased documentation program for [product], assigning deliverables, specialist skills, dependencies, quality gates, owners, and maintenance intervals.
Best Practices
- Define audiences, scope, owners, and quality criteria before generating content.
- Validate every example, link, diagram, and API statement against the current system.
- Update documentation with code, interface, deployment, and release changes.
Avoid
- Do not invoke every listed specialist skill when the task needs only one document.
- Do not publish generated technical claims without review by a responsible subject expert.
- Do not create duplicate references when an authoritative source already exists.