Results for “claim-validation”

Enforces a verification gate before any completion claim, requiring fresh command output as evidence.

Find sources for every numerical claim in the draft, add inline hyperlinks, and add internal links to brand-reference articles. Triggered after /draft.

Enforces running verification commands and confirming output before claiming work is complete, fixed, or passing, ensuring evidence precedes any success claims.

Find outdated stats and assertions in an extracted article. For each, check freshness and propose a replacement with a current source.

Validate user claims against codebase and git history, trace to root cause, and propose a fix

Verify that a change really works before you claim completion

Enforces running verification commands and confirming output before claiming work is complete, fixed, or passing, to prevent false success claims.

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Schema validation for notes. Checks against domain-specific templates. Validates required fields, enum values, description quality, and link health. Non-blocking — warns but doesn't prevent capture. Triggers on "/validate", "/validate [note]", "check schema", "validate note", "validate all".

Centralized JSON validation for AGENT_SUCCESS_CRITERIA with defensive parsing and injection attack prevention (CVSS 8.2)

Runs bottom-up type-chain validation across database, hooks, and UI layers, then fixes errors at the failing layer for project health checks before large changes.

Validate schema validator operations. Auto-activating skill for Data Pipelines. Triggers on: schema validator, schema validator Part of the Data Pipelines skill category. Use when working with schema validator functionality. Trigger with phrases like "schema validator", "schema validator", "schema".

Validate backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to ensure backups are reliable for disaster recovery and ransomware response scenarios.

Validate Pleasur.ai Stage 01 blog-keyword candidates with the Business potential, Intent, and Difficulty method using current Ahrefs evidence. Use before AIO vetting and prioritization to reject poor business fits, mismatched search intent, and SERPs the brand cannot realistically win.

Validate whether an OSS tool is worth building through staged namespace, existing-solution, and feasibility review

Use before claiming work is complete, fixed, or passing, and before committing or opening a PR - run the actual verification command and read its output before making any success claim.

Require fresh evidence before claiming an implementation, fix, build, or test is complete.

Algebra Based Validation Skill