artifact-validate-claim-create-footnotes

Verify claims against sources and generate standardized footnotes with absolute paths.

Updated Aug 27, 2026

Search Tags:#documentation #ontology #evidence #mapping #claims #source-verification #footnotes

Ready to run

npx skills add https://github.com/WesleyMFrederick/cc-workflows-plugin --skill artifact-validate-claim-create-footnotes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: artifact-validate-claim-create-footnotes
Source: https://github.com/WesleyMFrederick/cc-workflows-plugin/tree/main/src-claude/skills/artifact-validate-claim-create-footnotes
Command: npx skills add https://github.com/WesleyMFrederick/cc-workflows-plugin --skill artifact-validate-claim-create-footnotes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restructures evidence tags so source details live in footnotes, ensuring every claim is verified against its source before a footnote is written.

Core Features & Use Cases

Source-verified footnotes: Move source details out of inline claims into formal footnotes with absolute paths.
Content mapping: Map every claim fragment to a specific source line to support traceability.
Ontology-ready: Supports OBS, F-LK, M, and all ontology tag types for consistent documentation.

Quick Start

Run artifact-validate-claim-create-footnotes on your whiteboard documents to generate verified footnotes with absolute source paths.

Frequently Asked Questions about artifact-validate-claim-create-footnotes

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

FAQPage Schema

How do I automatically generate footnotes with absolute source paths for document claims?▼

The Skill verifies each claim against its source line before generating standardized footnotes with absolute paths. This content-mapping workflow ensures every claim fragment is traceable to a specific source location and assigned a verifiable footnote ID.

How do I map claim fragments to specific source lines for traceability?▼

You enforce a content-mapping workflow that links every claim fragment to a specific source line and assigns a verifiable footnote ID. This process restructures evidence tags so source details live in formal footnotes with absolute paths.

Does this footnote generation tool support indexed ontology tags like OBS, F-LK, and M?▼

Yes, the source verification process fully supports OBS, F-LK, M, and all ontology tag types. Applying it to whiteboard documents ensures consistent referencing and standardized documentation across your indexed ontology tags.

What is the best way to move inline source details out of claims and into formal footnotes?▼

Restructuring evidence tags moves source details out of inline claims into formal footnotes with absolute paths. This approach verifies claims against their sources before writing footnotes, ensuring source details are consistently relocated and standardized.

Why should I verify claims against sources before writing footnotes?▼

Verifying claims against sources before writing footnotes prevents unverified information from being formally referenced. The workflow restructures evidence tags so source details live in footnotes, ensuring every claim is checked against its source line before documentation.