documentation
Create Clear, Structured Documentation
Unstructured documents make important information difficult to find and use. This skill organizes Markdown content with clear sections, concise prose, suitable formatting, and optional diagrams.
This skill is part of a pack
Install the whole pack to get every skill the task needs, in one command.
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/bfdcampos-documentation.md and its manifest at https://skillstore.io/api/skills/bfdcampos-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". Create a README for a command-line backup tool.
Expected outcome:
- Project overview explaining the backup tool and its purpose.
- Installation and usage sections with clearly formatted commands.
- Configuration, limitations, and troubleshooting sections.
Using "documentation". Turn meeting notes into an implementation plan.
Expected outcome:
A structured plan containing objectives, scope, concrete tasks, dependencies, risks, owners, and next steps.
Using "documentation". Document the data flow between an application and its services.
Expected outcome:
An architecture document describing components, interfaces, data movement, decisions, and a Mermaid flow diagram.
Security Audit
SafeAll three static findings are false positives caused by Markdown inline-code formatting and ordinary writing guidance. SKILL.md contains no shell execution, system reconnaissance, prompt injection, network access, or other harmful intent.
Risk Factors
⚙️ External commands (2)
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/bfdcampos-documentation/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/bfdcampos-documentation?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/bfdcampos-documentation?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/bfdcampos-documentation/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/bfdcampos-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
BfdCampos. (2026). documentation security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/bfdcampos-documentation/audits/9BibTeX citation
@techreport{bfdcampos-bfdcampos-documentation-2026,
author = {BfdCampos},
title = {documentation security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/bfdcampos-documentation/audits/9},
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 9)"
version: "unspecified"
type: report
authors:
- name: "BfdCampos"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/bfdcampos-documentation/audits/9"
identifiers:
- type: other
value: "skillstore:bfdcampos-documentation:audit:9"
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
Prepare Project Documentation
Create readable READMEs, setup guides, and technical notes for software projects.
Structure Plans and Proposals
Turn objectives, constraints, and decisions into actionable plans or persuasive proposals.
Develop Technical Guides
Organize complex source material into clear guides, specifications, and design documents.
Try These Prompts
Create a Markdown note about [topic]. Use clear headers, short paragraphs, and bullet points. Save it with a sensible filename.
Write a README for [project]. Include an overview, installation, usage, configuration, and limitations. Format commands and configurations in code blocks.
Create a proposal for [decision]. Explain the problem, options, recommendation, benefits, risks, and next steps. Keep the argument persuasive and honest.
Create an architecture specification for [system] using [source material]. Cover context, components, data flows, decisions, risks, and unresolved questions. Add a Mermaid diagram when relationships need visualization. Distinguish confirmed facts from assumptions.
Best Practices
- Provide the audience, purpose, source material, and required sections before generation.
- Review factual claims, commands, and configuration details before publishing.
- Use diagrams only when they clarify relationships that prose cannot explain efficiently.
Avoid
- Do not request a document without supplying available facts or context.
- Do not use excessive formatting, emojis, or diagrams in formal technical documents.
- Do not treat generated content as verified evidence or approved policy.