wiki-verify

Marks wiki entries as verified by writing certifier, timestamp, and evidence to sidecar files.

Updated May 14, 2026
One-click install
npx skills add https://github.com/dadlabs-io/llm-wiki-bootstrap --skill wiki-verify-dadlabs-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wiki-verify
Source: https://github.com/dadlabs-io/llm-wiki-bootstrap/tree/main/bootstrap/skills/wiki-verify
Command: npx skills add https://github.com/dadlabs-io/llm-wiki-bootstrap --skill wiki-verify-dadlabs-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Wiki entries cannot certify their own claims, so every entry starts as unverified and needs a separate, auditable act of certification. This Skill flips an entry's truth-status from unverified to verified while recording who certified it, when, and on what evidence. ## Core Features & Use Cases - Auditable verification: Records the certifier role (--by human, --by agent, or --by tool), an ISO timestamp, and an optional one-line evidence note in a sidecar JSON file, keeping the entry's git history clean. - Lifecycle guardrails: Refuses to verify contradicted or rolled-back entries, treats already-verified entries as an idempotent no-op, and lists candidates when a slug is ambiguous. - Optional frontmatter mirroring: The --mirror flag syncs the verified field into entry frontmatter for downstream tools that cannot read sidecars, with a follow-up backlink integration step. - Use Case: After a sandbox tool confirms three proof-of-concepts in a security entry, run the skill with --by tool --evidence "Aardvark sandbox-verified 3 PoCs" to certify the entry and commit the sidecar update. ## Quick Start Verify the wiki entry with slug foo-2026 in the agentic-design topic as a human reviewer with a short evidence note describing what you checked.

Frequently Asked Questions about wiki-verify

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

FAQPage Schema
How do I verify a wiki entry with wiki-verify?▼

Run the wiki-verify.py script with the entry slug or path, the --topic notebook, and a --by role of human, agent, or tool. Add --evidence for a one-line note, --dry-run to preview, or --mirror to also update the entry frontmatter.

Why can't a wiki entry be verified when it is first written?▼

The icarus invariant forbids an entry from being both author and certifier of its own claims, so new entries start as unverified. A separate wiki-verify invocation is the only intended path to set verified: verified, keeping certification auditable.

Can I verify a contradicted or rolled-back wiki entry?▼

No, the script exits with an error for contradicted or rolled-back entries. The supported path is to review the conflict, write a new entry that revises the old one, and verify that new entry instead.

What happens if I verify an entry that is already verified?▼

Re-verifying an already-verified entry is an idempotent no-op: the script exits 0 with status no-op-already-verified and changes nothing. Ambiguous or missing slugs stop the run with the candidate entries listed.

Does wiki-verify modify the original entry file?▼

By default it writes only to the sidecar file _signals/<slug>.json, leaving the entry untouched and its git history clean. Passing --mirror also edits the entry frontmatter, after which the backlink integration script should be re-run.