certisyn-independent-verification
From the author
Independent, third-party verification of what a counterparty claims about itself, established BEFORE an agent commits funds, signs, delegates authority, or admits that counterparty to a deal. Declared coverage today is verification by physical law - vehicle telemetry and orbital node claims - where a finding is arithmetic that can be re-derived rather than an opinion that must be weighed. Use for any reliance on a counterparty assertion, when drafting the verification clause of an agreement, and when assembling or assessing a dispute filing. Returns one of four outcomes, always names what it could not determine, and states the conditions under which its own evidence should be ruled out.
Install
npx skills add internet-court/internet-court-skill --skill certisyn-independent-verification -a claude-code
Installs to .claude/skills/certisyn-independent-verification/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 91
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- validatehashgraph-online/awesome-codex-pluginsFreshly judge whether a finished change and its claims meet original acceptance: PASS, FAIL or NOT_PROVEN. Use when: asked for a go/no-go, sign-off or independent verdict.Other★ 1.4K
- verify-before-claimMark393295827/third-brain-v7-skillsUse when an agent is about to claim completion, correctness, safety, publication, deployment, or any consequential external fact.DevOps★ 141
- completion-verificationcbrock84/headcountVerifies that work is actually complete before it is claimed to be — running the checks, reading the output, and confirming the original request was satisfied rather than approximated. Use this before saying something is done, fixed, or passing; before committing or opening a pull request; and whenever a claim of success has not been backed by command output.Engineering★ 2.1K
- verification-before-completionforyourhealth111-pixel/Vibe-SkillsCompletion-evidence route used before claiming work is complete, fixed, passing, committed, or PR-ready. Requires fresh verification output before success claims. Do not use for root-cause debugging, TDD implementation, test-report packaging, or review-feedback triage.Testing★ 3.8K
- api-contract-verificationnahid-sparktales/agent-dispatcherProve an API integration actually works by executing it — success path, documented failure paths, auth failure — and leave behind a contract test that catches the next break. Use before reporting any endpoint, client or third-party integration as working, when asked whether an integration is verified, or when checking someone else's integration work. Not for load or performance testing, not for rendered UI verification, and not a substitute for reading the provider's own documentation.Legal★ 59
- kiro-verify-completiongotalab/cc-sddVerify completion and success claims with fresh evidence. Use before claiming a task is complete, a fix works, tests pass, or a feature is ready for GO.Testing★ 3.7K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in