cogni-claims

Manage claim verification lifecycle — submit, verify, review dashboard, inspect, and resolve 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, or reviewing what's been flagged, this skill handles it.

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.

This skill should be used when any plugin or agent needs to understand the ClaimEntity schema, "claim data model", "claim schema", "ClaimRecord fields", "DeviationRecord structure", "claim contract", "deviation types", "deviation severity levels", "resolution actions", "claim status transitions", "claim lifecycle states", or "workspace claims directory layout". Internal contract definition — provides the cross-plugin data model and record type specifications for claim lifecycle management in the cogni-claims verification system.

This skill should be used when the user asks to "verify claims", "check claims against sources", "claims dashboard", "show claims", "resolve claim", "submit claim", "claim verification", "fact-check claims", "re-verify claims", "review deviations", "inspect claim", "what claims are pending", or when any plugin needs to submit claims for source verification. Orchestrates the full claim verification lifecycle: ingestion, source-based verification, deviation detection, dashboard presentation, and user-guided resolution.