docs-agent
Maintain Unite-Hub Documentation
Documentation drifts when code, APIs, and agents change. This skill guides Claude, Codex, and Claude Code through focused updates for README, API, architecture, and changelog files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "docs-agent" from https://skillstore.io/skills/cleanexpo-docs-agent.md and its manifest at https://skillstore.io/api/skills/cleanexpo-docs-agent/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 "docs-agent". A new contacts bulk update endpoint was added.
Expected outcome:
Adds an API documentation section that explains the endpoint purpose, authentication, inputs, success result, error cases, and usage guidance.
Using "docs-agent". The dashboard gained a new analytics page.
Expected outcome:
Updates the README feature list, expands the architecture overview, and adds a changelog entry under Added.
Using "docs-agent". Agent definitions changed after a workflow refactor.
Expected outcome:
Refreshes the Claude agent file with updated roles, invocation rules, tool notes, and integration expectations.
Security Audit
SafeAll static findings are false positives from Markdown backticks, fenced examples, inline paths, relative fetch examples, HTTP status codes, and Mermaid documentation. No evidence found of command execution, external data exfiltration, prompt injection, or malicious instructions in SKILL.md.
Risk Factors
⚙️ External commands (87)
🌐 Network access (1)
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/cleanexpo-docs-agent/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/cleanexpo-docs-agent?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/cleanexpo-docs-agent?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/cleanexpo-docs-agent/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/cleanexpo-docs-agent.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
CleanExpo. (2026). docs-agent security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/cleanexpo-docs-agent/audits/8BibTeX citation
@techreport{cleanexpo-cleanexpo-docs-agent-2026,
author = {CleanExpo},
title = {docs-agent security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/cleanexpo-docs-agent/audits/8},
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: "docs-agent security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "CleanExpo"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/cleanexpo-docs-agent/audits/8"
identifiers:
- type: other
value: "skillstore:cleanexpo-docs-agent:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Refresh README after a release
Update feature lists, setup steps, usage notes, deployment details, and links after a product release.
Document new API endpoints
Create endpoint references that cover purpose, authentication, request fields, response shape, errors, and usage notes.
Keep architecture docs aligned
Revise system diagrams, component summaries, data flows, and integration notes after refactors or new services.
Try These Prompts
Update the README for this feature change: [describe change]. Preserve the existing structure and mark any missing details.
Document the new endpoint at [route path]. Include purpose, authentication, request fields, response summary, errors, and a short usage note.
Review the recent changes and update README, API documentation, architecture notes, and the changelog where needed. List assumptions before editing.
Compare the current documentation with the implemented code paths, agents, and integrations. Report stale sections and propose precise edits.
Best Practices
- Provide the code change summary and affected files before asking for documentation updates.
- Ask the skill to preserve existing headings, tone, and project-specific naming.
- Review generated examples for accuracy before publishing documentation.
Avoid
- Do not ask for broad documentation rewrites without describing what changed.
- Do not accept placeholder endpoint details when the route behavior is available.
- Do not publish generated examples before checking that names, routes, and versions are current.