documentation
Maintain Project Documentation
Project documentation becomes hard to find when files grow, duplicate, or use different structures. This skill gives Claude Code, Claude, and Codex a consistent workflow for writing, updating, and organizing markdown documentation.
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/daothihuong2111-documentation.md and its manifest at https://skillstore.io/api/skills/daothihuong2111-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 docs for the Settings screen.
Expected outcome:
- Found no existing Settings screen documentation.
- Created a screen overview with purpose, navigation, features, and related links.
- Created technical notes with component references, state flow, and integration points.
Using "documentation". Update the authentication guide with the new login flow.
Expected outcome:
- Located the current authentication guide and listed its sections.
- Updated only the login flow section.
- Kept existing headings, links, and document scope intact.
Using "documentation". Check whether we have duplicate onboarding docs.
Expected outcome:
- Identified overlapping onboarding content in two guide files.
- Recommended one source document and one redirecting reference.
- Listed sections that should be merged before deletion.
Security Audit
Medium RiskMost static findings are false positives caused by markdown fences, inline-code backticks, placeholder relative links, Mermaid diagrams, and documented example paths. The real security-relevant surface is the bundled Bash helper scripts, which can execute locally and modify caller-supplied documentation files; no prompt injection attempt or malicious intent was found.
Confirmed security concerns (1)
Capability review items (8)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚙️ External commands (50)
📁 Filesystem access (34)
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/daothihuong2111-documentation/audits/10?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/daothihuong2111-documentation?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/daothihuong2111-documentation?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/daothihuong2111-documentation/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/daothihuong2111-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
DaoThiHuong2111. (2026). documentation security audit report (audit version 10) [Author version unspecified]. Skillstore. https://skillstore.io/skills/daothihuong2111-documentation/audits/10BibTeX citation
@techreport{daothihuong2111-daothihuong2111-documentation-2026,
author = {DaoThiHuong2111},
title = {documentation security audit report (audit version 10)},
institution = {Skillstore},
year = {2026},
number = {10},
url = {https://skillstore.io/skills/daothihuong2111-documentation/audits/10},
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 10)"
version: "unspecified"
type: report
authors:
- name: "DaoThiHuong2111"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/daothihuong2111-documentation/audits/10"
identifiers:
- type: other
value: "skillstore:daothihuong2111-documentation:audit:10"
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
Create screen documentation
Generate a screen README and technical notes that follow the project template and required sections.
Update existing developer docs
Find the right document section, update only the relevant content, and preserve the existing file structure.
Reduce documentation drift
Find duplicate or oversized documentation and guide consolidation into focused markdown files.
Try These Prompts
Use the documentation skill to find existing docs about this feature before creating anything new: [feature or topic].
Create screen documentation for [screen name]. Follow the screen README and technical templates, and ask before creating duplicate files.
Update the [section name] section in [document path] to reflect these changes: [change summary]. Keep the file under the documentation rules.
Audit docs for duplicate coverage of [topic]. Recommend what to merge, what to delete, and which file should become the source of truth.
Best Practices
- Search existing documentation before creating new files.
- Keep each markdown file focused and below the documented size limit.
- Include traceable code references when documentation describes implementation details.
Avoid
- Creating a new document when an existing section should be updated.
- Copying the same explanation into several files.
- Adding untested examples or links without validation.
Frequently Asked Questions
What type of documentation does this skill create?
Does it work with Claude Code?
Will it create files automatically?
How does it prevent duplicate documentation?
Does it validate links and examples?
Is this skill project-specific?
Developer Details
Author
DaoThiHuong2111License
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
7db9b9f06e0ab79c575b58bc48c4d8dc9849f424
Maintenance freshness
7/18/2026
Usage
231 downloads · 367 views