CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

beta

Beta fixture skill. Use when plugin-eval tests need the second bundled skill.

Quality

69%

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/plugin-eval/fixtures/multi-skill-plugin/skills/beta/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 maximally token-efficient and appropriately avoids any progressive-disclosure overhead for a fixture of this size. Its weakness is actionability and workflow clarity: the single directive does not concretely state what 'using' the fixture involves, leaving an executor to infer behavior. As a test fixture this is tolerable, but as instructional content it is thin.

Suggestions

State concretely what invoking the skill does (e.g., 'No action required; this fixture exists solely so plugin-eval sees a second bundled skill') so the directive is unambiguous.

If any behavior is expected when the skill runs, add the one or two specific steps or commands involved.

Clarify the relationship to the other bundled fixture skill (ordering, naming expectations) so the 'second bundled' role is operationally clear.

DimensionReasoningScore

Conciseness

The body is a single heading plus one sentence ("Use this fixture skill as the second bundled plugin skill.") with no padding, no explanations of concepts Claude already knows, and nothing to trim — matching "Lean and efficient; every token earns its place". It cannot score higher than the top anchor and is clearly not level 4, where some over-explanation would exist.

5 / 5

Actionability

The only guidance is the high-level directive "Use this fixture skill as the second bundled plugin skill", which gives no concrete steps, commands, or examples of what using it entails — matching "Minimal concrete guidance; high-level hints but missing the specific steps to execute". It is above level 1 because it instructs rather than merely describes, but below level 3 because no concrete detail accompanies the instruction.

2 / 5

Workflow Clarity

As a trivial single-purpose skill the body presents one action, but that action ("use as the second bundled plugin skill") is not unambiguously defined — nothing states what happens when the skill is invoked — so the simple-skill exception to score 5 does not fully apply. It sits between level 2 (rough sequence, poorly defined steps) and level 4 (clear, mostly checkpointed sequence), landing at 3; no validation is required since no destructive or batch operations are involved.

3 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references, and the single heading plus one line is appropriately organized with nothing inlined that belongs in a separate file, matching the simple-skill exception ("can score 5 with just well-organized sections"). No bundle files exist, so there are no buried or nested references to penalize.

5 / 5

Total

15

/

20

Passed

Description

57%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 follows good structural form: explicit "Use when" trigger guidance, third-person voice, and a clearly delimited niche, which keeps conflict risk low. However, it names no concrete capabilities and its trigger vocabulary is narrow internal jargon ("plugin-eval") with no natural user phrasings or synonyms. It is serviceable for a test fixture but would under-perform as a real skill description.

Suggestions

Add 1–2 concrete actions the skill performs (or explicitly state it is a passive fixture with no runtime behavior) so specificity rises above 'names the domain only'.

Broaden trigger terms with natural variations a user would actually say (e.g., 'plugin evaluation', 'bundled plugin skills', 'second skill fixture') instead of only the internal term 'plugin-eval'.

Make the 'what' more informative — 'Beta fixture skill' conveys identity but not what the skill does when invoked.

DimensionReasoningScore

Specificity

The description names its domain ("Beta fixture skill") but lists zero concrete actions or capabilities — it only states what the skill is, matching "Names the domain but actions are minimal or generic". It does not reach level 3, which requires 1–2 concrete actions, and is not level 1 since a specific domain is explicitly named.

2 / 5

Completeness

Both parts are explicitly present: the "what" ("Beta fixture skill") and an explicit "Use when plugin-eval tests need the second bundled skill" trigger clause, matching "Has both 'what' and 'when'". It is not level 5 because the "what" is thin and lacks concrete trigger phrases beyond the single narrow condition, and not level 3 because the "when" is explicit rather than weakly implied.

4 / 5

Trigger Term Quality

Relevant keywords are present ("plugin-eval tests", "second bundled skill", "beta") but they are narrow jargon with no common variations or synonyms, matching "Some relevant keywords but missing common variations or synonyms". It falls short of level 4's "good keyword coverage" and above level 2 because the terms are domain-relevant rather than fully generic like "Works with files".

3 / 5

Distinctiveness Conflict Risk

The niche is clear and unlikely to trigger for unrelated work ("Use when plugin-eval tests need the second bundled skill"), with only minor overlap risk against closely related sibling fixture skills, matching "Mostly distinct; minor overlap risk with closely related skills". It is not level 5 since the trigger could collide with a near-identical first/alpha fixture description, and not level 3 because the domain is quite narrow.

4 / 5

Total

13

/

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

openai/plugins

Path

plugins/plugin-eval/fixtures/multi-skill-plugin/skills/beta/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.