cogni-claims

Manage claim verification lifecycle — submit, verify, review dashboard, inspect, resolve, and cobrowse claims

Verify claims against a single source URL and return deviation analysis as JSON.

Fetch a source URL via browser automation (browsermcp → claude-in-chrome fallback), locate the relevant passage, and capture a screenshot.

Cross-plugin data model for claim verification — defines ClaimRecord, DeviationRecord, and ResolutionRecord schemas, status transitions, deviation types, severity levels, and workspace layout. Use this skill whenever you need to understand claim data structures, create or validate claim records, check what fields a ClaimRecord has, understand deviation types or severity levels, or work with the cogni-claims directory layout. Any plugin that submits or consumes claims should consult this skill for the contract.

Manage claim verification lifecycle — submit, verify, review dashboard, inspect, resolve, and cobrowse claims. Use this skill whenever the user mentions claims, fact-checking, source verification, checking whether statements match their cited sources, reviewing deviations, or anything related to tracking the accuracy of sourced statements. Also use it when another plugin submits claims for verification (e.g., after a research or portfolio workflow produces sourced assertions). Even if the user doesn't say "claims" explicitly — if they're asking about verifying facts against sources, checking citations, finding outdated or mismatched data in cited references, reviewing what's been flagged, checking for stale sources, outdated data in references, or asking "which claims need attention" or "what did verification find", this skill handles it. Also trigger when the user wants to cobrowse unreachable sources together, recover unavailable claims interactively, open sources in their browser to help check them, or says things like "let's look at those sources together", "help me check these links", or "browse the unavailable sources".