Skills update-docs
📦

update-docs

Content revision r1 Safe ⚙️ External commands

Update Project Documentation

Project documentation often falls behind implementation changes. This skill guides focused updates to specs, database notes, error lists, and README files.

Supports: Claude Codex Code(CC)
🥉 77 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "update-docs" from https://skillstore.io/skills/crearize-update-docs.md and its manifest at https://skillstore.io/api/skills/crearize-update-docs/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.

Markdown detail GET /skills/crearize-update-docs.md Signed manifest GET /api/skills/crearize-update-docs/manifest Signed lockfile GET /api/skills/crearize-update-docs/lockfile

Test it

Using "update-docs". Update the README with new installation steps and environment setup notes.

Expected outcome:

  • README selected as the target document.
  • Installation and environment sections updated while preserving the existing layout.
  • Completion report lists the updated path and summary of changes.

Using "update-docs". Update the database design document with a new audit log table.

Expected outcome:

  • Database design document selected as the target.
  • Audit log details added in the existing database documentation structure.
  • Completion report identifies the document path and the applied update.

Using "update-docs". Add a new validation error code to the error documentation.

Expected outcome:

  • Error code list selected as the target document.
  • New error information inserted with matching Markdown formatting.
  • Completion report summarizes the added error code entry.

Security Audit

Safe
v8 • 7/6/2026 Open versioned report

All eight static findings are false positives caused by Markdown inline code, fenced examples, and Japanese prose. The skill describes a documentation update workflow and shows no prompt injection, data exfiltration, obfuscation, or malicious intent.

1
Files scanned
61
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (7)
SKILL.md:17 SKILL.md:21 SKILL.md:25 SKILL.md:29 SKILL.md:33-36 SKILL.md:36-48 SKILL.md:48-60
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
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.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/crearize-update-docs/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/crearize-update-docs/security.svg)](https://skillstore.io/skills/crearize-update-docs?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/crearize-update-docs?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/crearize-update-docs/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/crearize-update-docs.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

Crearize. (2026). update-docs security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/crearize-update-docs/audits/8

BibTeX citation

@techreport{crearize-crearize-update-docs-2026, author = {Crearize}, title = {update-docs security audit report (audit version 8)}, institution = {Skillstore}, year = {2026}, number = {8}, url = {https://skillstore.io/skills/crearize-update-docs/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: "update-docs security audit report (audit version 8)" version: "unspecified" type: report authors: - name: "Crearize" date-released: "2026-07-06" url: "https://skillstore.io/skills/crearize-update-docs/audits/8" identifiers: - type: other value: "skillstore:crearize-update-docs:audit:8" description: "Skillstore immutable audit report identifier"

Compare variants

2 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Highest Skillstore Score
Cygnusfear Recommended

cygnusfear-update-docs

Skillstore Score 79
Evidence Confidence High
Skillstore usage 12
Updated

2026-08-21

Crearize Current

crearize-update-docs

Skillstore Score 77
Evidence Confidence High
Skillstore usage 29
Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
85
Content
70
Community
83
Spec Compliance

What You Can Build

Refresh Feature Specifications

Update a feature specification after behavior, requirements, or acceptance criteria change.

Maintain Database Design Notes

Keep database design documentation aligned with schema changes and new data relationships.

Revise README and Error Guides

Document new setup steps, usage notes, or error codes after a release.

Try These Prompts

Update a README 
Update the README documentation with these setup changes: [describe changes]. Keep the current structure and Markdown style.
Revise a Feature Spec 
Update the feature specification for [feature name]. Add these behavior changes and acceptance criteria: [details].
Synchronize Database Docs 
Update the database design document with these schema changes: [tables, fields, relationships]. Preserve existing section order.
Document a Release 
Update the relevant docs after this release: [release notes]. Cover feature specs, README changes, and error code updates as needed.

Best Practices

  • Provide the document type and the exact update scope.
  • Include source decisions, requirements, or release notes with the request.
  • Review the final Markdown diff before committing the change.

Avoid

  • Do not use it to update unrelated application code.
  • Do not provide vague update text without a target document.
  • Do not use it to read arbitrary files outside documented project paths.

Frequently Asked Questions

Which documents can this skill update?
It supports feature specifications, database design notes, error code lists, and README files.
Does it preserve existing Markdown structure?
Yes. The workflow asks the agent to keep the existing structure and Markdown format.
Can it create application code?
No. It is focused on documentation updates, not code implementation.
Does it validate Markdown rendering?
No. It asks for syntax review, but it does not define an external renderer or validator.
Can Claude Code or Codex use it?
Yes. The report lists Claude, Codex, and Claude Code as supported tools.
What should I include in a request?
Include the document type, target feature or area, and the exact content changes.

Developer Details

Author

Crearize

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Repository

https://github.com/Crearize/ProjectTemplate/tree/main/.claude/skills/update-docs

Ref

d11af420e07cd866fe39cfa937efef3223896c06

Maintenance freshness

7/18/2026

Usage

21 downloads · 218 views

File structure

📄 SKILL.md

More from Crearize

View all

Related Skills

View all