CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

certisyn-independent-verification

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.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./vendored/certisyn/certisyn-independent-verification/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

52%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and encodes a clear, well-validated decision procedure with exhaustive failure handling, but it is packaged as a monolithic ~800-line document. Significant rhetorical and methodological essay content inflates token cost, and no progressive disclosure is used - API references, measurement records, and legal material are all inlined where separate reference files belong.

Suggestions

Move the endpoint API reference, the attestation measurement records ('What the register resolves', the GenLayer attestation log), and the license notice into separate files under references/ and link to them one level deep, keeping SKILL.md to the decision procedure, outcome table, and evidence grid.

Cut the rhetorical framing and methodology essays (metrology, psychophysics, clinical-trials prior art, 'Why a forum should prefer this evidence class') to a few sentences or a reference document; they explain context Claude does not need to execute the procedure.

Isolate time-sensitive values (detection-rate measurements, contract addresses, digests dated 15/17 September 2026) into a clearly dated reference file so the main procedure text stays stable, and instruct readers to pull live values from the capability endpoint as the file itself advises.

DimensionReasoningScore

Conciseness

The ~815-line body is noticeably verbose: rhetorical framing ('A system that must return a value will, under commercial pressure, eventually return a comfortable one'), extended essays on metrology, psychophysics and clinical-trials methodology, legal-philosophy sections, and inlined license text add hundreds of tokens without actionable value. Time-sensitive measurements ('measured 17 September 2026', contract addresses, digests) are embedded mid-flow rather than isolated in a dated section, which the guidelines penalize. This fits the anchor for several unnecessary padded sections rather than the anchor-3 case of only occasional slack.

2 / 5

Actionability

Concrete curl commands, complete endpoint tables, an exhaustive HTTP-error-to-outcome mapping, full JSON record shapes, and a runnable verification script ('node pt/verify.mjs') give mostly executable guidance. Some directives remain abstract ('route to intake', 'request access rather than inferring'), matching the anchor-4 case of concrete commands with minor gaps rather than the fully copy-paste-ready coverage of the 5 anchor.

4 / 5

Workflow Clarity

The six-step decision procedure is clearly sequenced and validated: the failure table defines explicit feedback loops (400/422 fix-and-resend, 429 exponential backoff with 3-attempt cap, 404 re-check after 60 seconds) and the guardrails act as checkpoints. Steps 5 and 6 are compressed into a single line and the sequence is repeatedly interrupted by digressions, so it sits at the anchor-4 level of most checkpoints present with minor gaps rather than the fully checkpointed anchor-5 workflow.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are all absent) and essentially all detail is inlined in one ~800-line file: the full endpoint API reference, attestation measurement records, the clause template, the 'For other verifiers' essay, and license text all clearly belong in separate reference files. Section headers do provide some structure (above the anchor-1 wall of text), but the volume of inlined reference material matches the anchor for content that clearly belongs in separate files.

2 / 5

Total

12

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, third-person, and explicitly states both capability and trigger conditions, with a clear 'Use for...' clause naming three concrete use cases. Trigger coverage is good but misses common synonyms like 'due diligence' or 'vetting'. Conflict risk is minimal given the well-defined niche.

DimensionReasoningScore

Specificity

The description lists multiple concrete capabilities - 'Independent, third-party verification of what a counterparty claims about itself', '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' - with a concrete coverage scope ('vehicle telemetry and orbital node claims'). This matches the anchor for comprehensive coverage of specific actions rather than the anchor-4 case of minor gaps.

5 / 5

Completeness

It explicitly answers both what the skill does (independent verification of counterparty self-claims before commitment, returning four outcomes) and when to use it, via an explicit 'Use for...' clause with three concrete triggers. Both halves are present and concrete, matching the anchor-5 example pattern; the 4 anchor requires a 'when' that could be more explicit, which does not apply here.

5 / 5

Trigger Term Quality

'Use for any reliance on a counterparty assertion, when drafting the verification clause of an agreement, and when assembling or assessing a dispute filing' provides several natural trigger phrases ('counterparty assertion', 'verification clause', 'dispute filing'), but common variations a user might actually say ('due diligence', 'vet a vendor', 'check credentials') are missing. Good keyword coverage with a few natural terms absent fits the 4 anchor, not the 5 anchor's synonym-complete coverage.

4 / 5

Distinctiveness Conflict Risk

The niche is clear and distinct - pre-commitment, third-party verification of counterparty self-claims in agent commerce - with triggers ('verification clause', 'dispute filing', 'reliance on a counterparty assertion') unlikely to fire for unrelated skills. It matches the clear-niche, minimal-conflict-risk anchor rather than the anchor-4 case of overlap with closely related skills.

5 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (832 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

internet-court/internet-court-skill

Path

vendored/certisyn/certisyn-independent-verification/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.