content-grounding

Verify content claims via web research before writing or editing.

3|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/Muvon/octomind-tap --skill content-grounding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: content-grounding
Source: https://github.com/Muvon/octomind-tap/tree/main/skills/content-grounding
Command: npx skills add https://github.com/Muvon/octomind-tap --skill content-grounding

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents content hallucinations by forcing confidence triage, triggering live research when needed, and escalating to the user when verification fails.

Core Features & Use Cases

  • Confidence triage before claims: classifies each claim into common knowledge, familiar specifics, unfamiliar entities, time-sensitive items, or speculation to decide whether to write, research, or escalate.
  • Mandatory research triggers: blocks writing without verification for versions, pricing, stats, quotes, people, URLs, endpoints, commands, and any unfamiliar or niche subjects.
  • Source-verifying output rules: requires inline attribution or opinion markers, flags unverifiable facts with [needs verification], and includes a grounding report when research occurs.
  • Safe editing protocol: preserves existing factual claims in user drafts, verifies unfamiliar entities before changing them, and edits only non-factual aspects when sources are missing.
  • Live verification capabilities: runs with websearch and webfetch to confirm details from primary sources.

Quick Start

Use the content-grounding skill to draft or edit a factual article while automatically researching and verifying any uncertain product, feature, version, pricing, or quote claims.

Frequently Asked Questions about content-grounding

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

FAQPage Schema
How do I prevent AI content hallucinations when writing factual articles?

Preventing content hallucinations requires confidence triage to classify claims before writing. You must trigger live websearch and webfetch to verify unfamiliar specifics like pricing or versions, and flag unverifiable facts with a needs verification tag.

How do I verify product pricing and software versions before publishing a blog post?

Verifying product pricing and software versions requires mandatory research triggers that block writing until live websearch retrieves primary sources. You then cross-reference facts, annotate citations, and generate a grounding report for the blog post.

Can I edit existing draft articles without losing accurate source verification?

Editing existing drafts safely requires a safe editing protocol that preserves existing factual claims. You verify unfamiliar entities before changing them, and edit only non-factual aspects when authoritative webfetch sources are missing.

What happens to unverifiable statistics or quotes when live research fails?

When live websearch fails to verify statistics or quotes, the content is flagged with a needs verification marker. The workflow escalates with a single targeted question to the user instead of asserting the unverified claim.

Does content grounding work without websearch and webfetch dependencies?

Content grounding does not work without websearch and webfetch dependencies. These capabilities are required to retrieve primary sources, cross-reference facts, and confirm time-sensitive items or niche subjects during the writing workflow.