skills.rest
Elijah-J
Elijah-JCOMMUNITY
Explore all skills by this author →
GitHub

write-wiki-page

Draft, revise, or audit technical wiki pages under output/wiki using local corpus docs.

Updated Aug 27, 2026
Search Tags:#workflow#templates#documentation#evidence#wiki#corpus
One-click install
npx skills add https://github.com/Elijah-J/InfoScraper --skill write-wiki-page
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-wiki-page
Source: https://github.com/Elijah-J/InfoScraper/tree/main/.agents/skills/write-wiki-page
Command: npx skills add https://github.com/Elijah-J/InfoScraper --skill write-wiki-page

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Draft, revise, or audit technical wiki pages under output/wiki/ using local corpus docs. This skill standardizes structure, sources, and tone to ensure accurate, consistent wiki content across projects.

Core Features & Use Cases

  • Template-driven drafting: enforce a canonical page structure with consistent sections and references.
  • Corpus-backed evidence: pull and cite information from local docs and repo notes to support claims.
  • Revision workflow: support corpus-only drafts, repo-substantiated pages, and accuracy audits with consistent voice.

Quick Start

Provide a topic or existing wiki page title to start drafting or auditing a wiki page under output/wiki/ using the standard templates.

Frequently Asked Questions about write-wiki-page

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I draft technical wiki pages using local corpus documents?▼

Draft technical wiki pages using local corpus documents by applying a template-driven structure that enforces canonical sections and references. The workflow separates public guidance from repository-specific notes to ensure consistent content.

What is the best way to audit wiki pages for accuracy against repository notes?▼

The best way to audit wiki pages for accuracy is to cross-reference claims against local corpus docs and repository notes. This enforces a frontmatter-driven revision workflow to verify evidence and maintain a consistent voice.

Can I generate corpus-only explainers without direct repository substantiation?▼

Yes, you can generate corpus-only explainers without direct repository substantiation. The drafting workflow supports corpus-only drafts alongside repo-substantiated pages, enforcing frontmatter metadata to track source evidence levels.

How do you structure documentation to separate public guidance from repository notes?▼

Structure documentation to separate public guidance from repository notes by applying a template-driven page format. This canonical structure uses frontmatter to enforce consistent sections, ensuring public content remains distinct from internal technical details.

Does the wiki drafting workflow require external dependencies or tools?▼

The wiki drafting workflow does not require external dependencies or tools. It operates entirely locally, using your existing corpus documents and a frontmatter-driven template to standardize page structure and source citations.

Related Skills

Explore More Content & Communication Skills→
hiivmindhiivmind

hiivmind-corpus-add-source

Add documentation sources to a corpus via CLI-guided prompts and config.yaml updates.

Official
Advanced
zzafergokzzafergok
1

markdown-to-html-skill

Convert Markdown documents to HTML using marked.js, pandoc, gomarkdown, or static site generators.

Community
Intermediate
xbklairithxbklairith
2

documentation

Generate code docstrings, API references, READMEs, and Mermaid architecture diagrams.

Community
Intermediate
KirKruglovKirKruglov
5

generate-charter

Generate a formal project charter from briefs, stakeholder answers, and constraints.

Community
Intermediate