CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

spec-to-code-compliance

Verifies code implements exactly what documentation specifies for blockchain audits. Use when comparing code against whitepapers, finding gaps between specs and implementation, or performing compliance checks for protocol implementations.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/spec-to-code-compliance/SKILL.md

The canonical home for this skill is spec-to-code-compliance in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

56%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 lays out a well-sequenced 7-phase workflow with useful anti-shortcut and anti-hallucination guardrails, but its progressive disclosure strategy is broken: every detailed reference points to a file that does not exist in the bundle, leaving key executable details (IR formats, quality thresholds, checklists) unavailable. Repetitive cross-references and overlapping discovery lists also add avoidable tokens.

Suggestions

Ship the referenced bundle files (IR_EXAMPLES.md, OUTPUT_REQUIREMENTS.md, COMPLETENESS_CHECKLIST.md) or remove the references and inline the essential content — currently every detailed reference in the body dangles.

Deduplicate the repeated "See IR_EXAMPLES.md for detailed examples" mentions (appears after Phases 2, 3, 4 and again in Resources) into a single Resources section, and merge the overlapping Phase 0 documentation-discovery and Phase 1 normalization lists.

Inline the critical quality thresholds (minimum Spec-IR item counts, confidence floor of 0.8, IR record format) from the missing OUTPUT_REQUIREMENTS.md so the workflow is executable even without the bundle files.

DimensionReasoningScore

Conciseness

The body is dense and non-pedagogical (no explanations of concepts Claude already knows), but contains real repetition: "See IR_EXAMPLES.md for detailed examples" appears after Phases 2, 3, and 4 and again in the Resources section, and the Phase 0/1 discovery lists overlap. Mostly efficient but could be tightened, matching the 3 anchor rather than 4.

3 / 5

Actionability

Concrete taxonomy is inline (match_type enum, CRITICAL/HIGH/MEDIUM/LOW severity levels, 16-section report structure, confidence ≥ 0.8 threshold), but the key executable details — IR format examples, quality thresholds, and completeness checklists — are all deferred to bundle files (IR_EXAMPLES.md, OUTPUT_REQUIREMENTS.md, COMPLETENESS_CHECKLIST.md) that do not exist in the bundle. Some concrete guidance but incomplete with missing key details, fitting the 3 anchor; not 2 because what is inline is specific and structured rather than high-level hints.

3 / 5

Workflow Clarity

Phases 0–6 are clearly sequenced with explicit feedback loops ("Investigate until full_match or mismatch", "Investigate until confidence ≥ 0.8 or classify as AMBIGUOUS") and a pre-finalization completeness verification step. Not 5 because that verification step points to a missing COMPLETENESS_CHECKLIST.md, so it cannot actually be executed as written — a minor validation gap. This is a read-only analysis skill, so the destructive/batch cap does not apply.

4 / 5

Progressive Disclosure

References are clearly signaled and one level deep, and the body itself is well-sectioned by phase, but scored against the actual bundle structure all three referenced files (IR_EXAMPLES.md, OUTPUT_REQUIREMENTS.md, COMPLETENESS_CHECKLIST.md) are absent — the promised disclosure structure is broken and every reference dangles. Structure is present and references are signaled (not buried or inlined), fitting the 3 anchor rather than 2, but the missing files prevent a higher score.

3 / 5

Total

13

/

20

Passed

Description

87%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.

A strong description: concrete, third-person, with an explicit "Use when..." trigger clause and a well-scoped blockchain-audit niche. Minor room for improvement only in keyword synonym coverage and distinguishing the listed actions from one another.

DimensionReasoningScore

Specificity

Lists several concrete actions — "verifies code implements exactly what documentation specifies", "comparing code against whitepapers", "finding gaps between specs and implementation", "performing compliance checks for protocol implementations" — but they are closely related variations of one verification task rather than comprehensive distinct capabilities, so it falls between the 3 and 5 anchors rather than clearly at 5.

4 / 5

Completeness

Clearly answers "what" ("Verifies code implements exactly what documentation specifies for blockchain audits") and "when" with an explicit "Use when..." clause containing concrete trigger phrases; uses third-person voice throughout, matching the top anchor example pattern.

5 / 5

Trigger Term Quality

Natural trigger phrases like "comparing code against whitepapers", "finding gaps between specs and implementation", and "compliance checks for protocol implementations" match what an auditor would actually say, but common variations such as "design docs", "documentation", or "spec alignment" are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche — blockchain spec-to-code compliance auditing — with distinct triggers (whitepapers, spec/implementation gaps, protocol compliance) that are unlikely to fire for unrelated skills; the domain scoping keeps overlap risk minimal.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/spec-to-code-compliance/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.