wiki-page-writer
Write Evidence-Based Wiki Pages
Technical docs often drift from implementation details. This skill guides Claude, Codex, and Claude Code to write cited wiki pages with diagrams.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "wiki-page-writer" from https://skillstore.io/skills/sickn33-wiki-page-writer.md and its manifest at https://skillstore.io/api/skills/sickn33-wiki-page-writer/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 "wiki-page-writer". Document the payment service.
Expected outcome:
- A Markdown wiki page with VitePress frontmatter.
- Sections for overview, architecture, components, data flow, implementation, and references.
- At least two Mermaid diagrams and file-line citations.
Using "wiki-page-writer". Create onboarding documentation for authentication.
Expected outcome:
A structured page that explains the authentication flow, important classes, configuration tables, and cited implementation details.
Using "wiki-page-writer". Explain the event processing pipeline.
Expected outcome:
A technical deep dive with diagrams, component summaries, data movement notes, and references to relevant source files.
Security Audit
SafeAll static findings are false positives caused by Markdown fences, inline code formatting, Mermaid syntax, and documentation validation wording. I found no evidence of executable shell commands, network access, prompt injection, or malicious intent in SKILL.md. The skill asks agents to read repository files for documentation, so users should scope it to code they may summarize.
Risk Factors
⚙️ External commands (11)
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-wiki-page-writer/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-wiki-page-writer?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-wiki-page-writer?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-wiki-page-writer/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-wiki-page-writer.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). wiki-page-writer security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-wiki-page-writer/audits/5BibTeX citation
@techreport{sickn33-sickn33-wiki-page-writer-2026,
author = {sickn33},
title = {wiki-page-writer security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-wiki-page-writer/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: "wiki-page-writer security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/sickn33-wiki-page-writer/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-wiki-page-writer:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Document a component
Create a wiki page that explains a component, its purpose, and its implementation with source citations.
Map system architecture
Produce architecture notes with Mermaid diagrams, component summaries, data flow details, and references.
Prepare onboarding docs
Turn existing code into structured documentation that helps new contributors understand important paths and decisions.
Try These Prompts
Create a wiki page for [component]. Read the relevant files, cite evidence, and include Mermaid diagrams.
Write a VitePress wiki page for [feature]. Cover purpose, architecture, components, data flow, implementation details, and references.
Analyze [subsystem]. Trace the real code paths, cite at least five source files, and show the main interactions with diagrams.
Generate a deep technical wiki page for [system]. Separate facts from inference, explain design reasons, and flag missing evidence.
Best Practices
- Provide the repository area and audience before asking for a page.
- Ask the agent to verify citations against actual file paths.
- Review generated diagrams before publishing docs.
Avoid
- Do not request broad repository documentation without a scope.
- Do not publish pages with Unknown citations left unresolved.
- Do not use it for legal, policy, or marketing content without review.