CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

sdk-scenario-generator

Create, review, and maintain gold-standard Skills SDK eval scenarios before internal evals, dry Tessl staging, or live private Tessl scoring. Use when creating or updating a skill, writing skill tests, adding eval cases, importing KnowledgeOS or Tessl suggestions, checking scenario drift, or hardening evals that are too easy.

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, token-efficient instruction skill: explicit gates, concrete validation commands, a failure-mode checklist, and a references section whose files all exist one level deep. The main gaps are redundancy across the Gotchas/Execution Boundaries/Validation lane-separation rules, policy statements mixed into the numbered workflow, and unlabeled reference entries that give no guidance on when to open each file.

Suggestions

Collapse the repeated lane-separation rule (Workflow step 12, Execution Boundaries, and the closing Validation paragraph) into a single stated-once rule to remove redundancy and earn a conciseness 5.

Add a one-phrase purpose label to each References entry (e.g., 'gold-scenario-contract.md — scenario authoring rules; tessl-tile-scenario-contract.md — Tessl tile asset format') so readers can route to the right file without opening all twelve.

Separate the 12-step Workflow into a strictly ordered gate sequence, moving authoring policies (steps 5–10) into a 'Authoring rules' subsection so the actual execution order is explicit.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — no known concepts are explained, and sections like Failure Mode and Validation are terse checklists. It is not 5 because the lane-separation rule is repeated nearly verbatim across Workflow step 12, Execution Boundaries, and the closing Validation paragraph, and Gotchas partially restate Execution Boundaries — trimming that redundancy would make every token earn its place.

4 / 5

Actionability

The Validation section gives eight copy-paste-ready commands with exact flags (e.g., `./bin/ask sdk eval scenario-quality <skill-path> --preview --json --robot`), and steps name exact artifacts (`instructions.json`, `scenario-N/{task.md,criteria.json,capability.txt}`). It is not 5 because several workflow steps are policy directives without an executable action (e.g., "Treat Tessl rejection as a pipeline defect…", "Feed repeat failures back to the start of the pipeline") — they say what to decide, not the command or edit to make.

4 / 5

Workflow Clarity

The 12-step workflow lays out an ordered pipeline with explicit validation gates ("Run package verify, scenario-quality, scorer-quality, and scorer-calibration before oss-local…"), a feedback loop (step 4), a Failure Mode stop-checklist, and a Validation section. It is not 5 because the numbered list interleaves sequencing with authoring policies (steps 5–10 are rules, not steps), so the true execution order is partly implicit and a reader must reconstruct when each policy applies.

4 / 5

Progressive Disclosure

The body is a concise overview with one-level-deep references, and every listed path (evals.yaml, contract.yaml, gold-scenario-contract.md, tessl-registry-boundaries.md, sdk-pipeline-setup.md, knowledgeos-handoff-conversion.md, etc.) exists in references/. It is not 5 because the References section is a bare unlabeled path list — no per-file purpose labels or routing guidance (e.g., which contract to read for Tessl tiles vs. eval repair), unlike the 5 anchor's '**Form filling**: See [FORMS.md](FORMS.md)' pattern.

4 / 5

Total

16

/

20

Passed

Description

83%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 with an explicit 'Use when…' clause, natural trigger phrases, and a clearly delimited niche around Skills SDK eval scenarios and Tessl staging. Third-person voice is used correctly. Its only weaknesses are the thin set of 'what' verbs (create/review/maintain) and some missing natural synonym variations.

DimensionReasoningScore

Specificity

Names concrete actions ("Create, review, and maintain gold-standard Skills SDK eval scenarios") and specific gate contexts ("internal evals, dry Tessl staging, or live private Tessl scoring"), matching the anchor for several specific actions with minor gaps. It falls short of 5 because the 'what' is carried by only three generic verbs plus the qualifier 'gold-standard', rather than a comprehensive list of concrete capabilities.

4 / 5

Completeness

Explicitly answers both questions: what it does ("Create, review, and maintain gold-standard Skills SDK eval scenarios before internal evals, dry Tessl staging, or live private Tessl scoring") and when to use it ("Use when creating or updating a skill, writing skill tests, adding eval cases..."). Both 'what' and 'when' are present with concrete trigger phrases, exactly matching the 5 anchor.

5 / 5

Trigger Term Quality

Includes natural phrases a user would say — "creating or updating a skill", "writing skill tests", "adding eval cases", "hardening evals that are too easy" — plus real product names (KnowledgeOS, Tessl). It is not 5 because common variations and synonyms (e.g., 'eval review', 'failing evals', 'test cases') are missing; it is above 3 because coverage goes beyond 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

The Tessl/SDK eval-scenario niche with distinct triggers ("dry Tessl staging", "KnowledgeOS or Tessl suggestions", "scenario drift") is clearly distinguishable. Minor overlap remains with general skill-authoring skills via "creating or updating a skill", matching 'mostly distinct; minor overlap risk' rather than the fully distinct 5 anchor.

4 / 5

Total

17

/

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

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository

jscraik/Agent-Skills

Path

Skills/agent-ops/sdk-scenario-generator/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.