writing-wiki-pages

Enforces citation, attribution, and growth-log rules when editing product-wiki pages.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/missingbulb/GoogleCalendarEventCreator --skill writing-wiki-pages-missingbulb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-wiki-pages
Source: https://github.com/missingbulb/GoogleCalendarEventCreator/tree/main/.claudinite/shared/packs/product-wiki/skills/writing-wiki-pages
Command: npx skills add https://github.com/missingbulb/GoogleCalendarEventCreator --skill writing-wiki-pages-missingbulb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product research wikis degrade over time: claims get written without sources, figures get misattributed, corrections silently erase history, and automated passes fabricate growth. This Skill defines the editorial rules every edit under product-wiki/ must follow so the knowledge base stays cited, auditable, and honest. ## Core Features & Use Cases - Key insights header discipline: Leads each page with a few plain-language bullets carrying the research's actual conclusions, rewritten only when a pass changes the page's top-line understanding. - Citation and attribution rules: Requires every claim to be cited, corrects wrong claims with a noted reason instead of deletion, attributes recurring figures to their named origin, and counts independent voices rather than mentions. - Growth log and PR gating: Records every real change in the page's growth log, keeps product-requirements/ human-reviewed only, and lands all unattended growth as an unmerged PR. - Use Case: During a weekly wiki-growth pass, an agent researches a page's open questions, adds only newly citable findings with sources, updates the header and growth log, and opens a PR — or writes nothing when no citable material is found. ## Quick Start Ask the agent to grow the product wiki by researching the open questions on a product-wiki page and updating it under these writing rules.

Frequently Asked Questions about writing-wiki-pages

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

FAQPage Schema
How do I write a product wiki page with proper citations?▼

Read the target page end to end first, research what its Open questions section flags as open or dated, and write only claims backed by a citable source. Record every change in the page's growth log and update open questions in both directions.

How should I attribute a statistic found in multiple search results?▼

Recurring figures across search snippets are usually one source repeated, not independent confirmation. Attribute the figure to the publisher a source explicitly names as its origin, and when sources disagree about the origin, say so on the page.

What belongs in the Key insights header of a wiki page?▼

A few short bullets carrying the research's actual conclusions — the numbers, competitors, or findings that turned out false — written in plain words without citations or hedges. It is a current view, rewritten only when a pass changes the page's top-line understanding.

Can an automated pass edit product-requirements directly?▼

No. The product-requirements folder is human-reviewed only and never changes as a side effect of wiki work. A wiki finding that should move a requirement gets a growth-log note and a repo issue, then waits for a human.

What happens when a research pass finds nothing citable?▼

The pass writes nothing: no edit, no log entry, and no PR. Fabricated growth is explicitly prohibited, and most passes are expected to find little or nothing new.