CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

synthetic-skill

Synthetic fixture used only to test portable SDK contracts.

Quality

51%

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 ./tests/fixtures/synthetic-skill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

45%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 a flawlessly lean, well-organized declaration that serves its stated purpose as a synthetic test fixture, but as skill content it instructs nothing: no actions, no workflow, no executable guidance. Conciseness and structure are perfect; actionability and workflow clarity are absent by design.

Suggestions

State at least one concrete action to perform when the skill is invoked (e.g., a specific command or verification step) so the body instructs rather than only describes.

If any process is intended when this fixture is used, sequence it explicitly — even a single unambiguous step would let the simple-skill exception apply to workflow clarity.

DimensionReasoningScore

Conciseness

The two-sentence body ('This fixture contains no runtime, provider, distribution, or publication state.') is maximally lean — no padding, no explanations of concepts Claude already knows, every token earning its place — which matches anchor 5 ('Lean and efficient; assumes Claude's competence').

5 / 5

Actionability

The body 'only describes rather than instructs': it declares fixture properties but provides no concrete code, commands, or steps to execute, exactly matching anchor 1. Anchor 2 is not met because even high-level hints toward a task are absent.

1 / 5

Workflow Clarity

No steps, sequence, or action of any kind is stated, so anchor 1 ('Steps missing or incoherent; no sequence') is the literal match. The simple-skill exception does not apply because no unambiguous single action for Claude to perform is stated anywhere in the body.

1 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references (no references/, scripts/, or assets/ bundles exist), and its single heading plus one clear statement is well-organized, satisfying the simple-skill provision ('progressive disclosure can score 5 with just well-organized sections').

5 / 5

Total

12

/

20

Passed

Description

33%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 clearly states what the artifact is — a synthetic test fixture — but reads as pipeline metadata rather than a user-facing skill description: it has no 'when to use' guidance, no natural trigger terms, and only one generic action verb. It is distinctive within its niche but would never surface for a real user need.

Suggestions

Add an explicit trigger clause (e.g., 'Use when validating portable SDK contract compliance...') so both 'what' and 'when' are answered.

Include natural keywords a user would actually say (e.g., 'SDK contract', 'portability check', 'contract validation') rather than only internal jargon like 'synthetic fixture'.

Name the concrete actions the skill performs (e.g., 'validates frontmatter fields', 'checks contract portability') instead of the single generic verb 'test'.

DimensionReasoningScore

Specificity

The description names its domain ('Synthetic fixture used only to test portable SDK contracts') but provides only a single generic action verb ('test'), matching anchor 2 ('Names the domain but actions are minimal or generic'). Anchor 3 is not met because there is no list of 1-2 concrete capability actions.

2 / 5

Completeness

A clear 'what' is present ('Synthetic fixture used only to test portable SDK contracts') but no 'Use when...' clause or equivalent trigger guidance exists, capping completeness at 3 per the judging guidelines. It is not anchor 2 because the 'what' is not vague; it is not anchor 4 because no 'when' is present at all.

3 / 5

Trigger Term Quality

Phrases like 'Synthetic fixture' and 'portable SDK contracts' are internal technical jargon that no user would naturally say when needing this skill; there are no natural keywords at all, matching anchor 1 ('only technical jargon or entirely generic language'). Anchor 2 is not met because even one or two generic user-facing keywords are absent.

1 / 5

Distinctiveness Conflict Risk

The scoping 'used only to test portable SDK contracts' carves out a narrow niche with minimal overlap risk, though the generic term 'test' could superficially collide with testing-related skills, matching anchor 4 ('mostly distinct; minor overlap risk'). Anchor 5's 'distinct triggers' is not met because the description contains no trigger phrases.

4 / 5

Total

10

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

jscraik/skills-sdk

Path

tests/fixtures/synthetic-skill/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.