CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

minimal-plugin-skill

Minimal plugin skill fixture. Use when a test needs a valid plugin skill.

Quality

71%

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/minimal-plugin/skills/minimal-plugin-skill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 lean and well-organized for a two-line fixture skill, scoring at the top of the rubric on conciseness and structure. Its one real weakness is actionability: the instruction names a goal ('verify plugin-level skill discovery') without any concrete step or expected outcome for carrying out the verification.

Suggestions

Add one concrete step or expected outcome for the verification (e.g., 'Invoke this skill and confirm it appears in the plugin's skill listing and executes without error').

Briefly define what 'verify' means here — the observable check that signals discovery worked — so the guidance is executable rather than a bare directive.

DimensionReasoningScore

Conciseness

The body is one heading plus a single instruction sentence ("Use this bundled skill to verify plugin-level skill discovery.") with zero padding and no explanation of concepts Claude already knows. Every token earns its place, matching the lean-and-efficient anchor exactly.

5 / 5

Actionability

"Use this bundled skill to verify plugin-level skill discovery" gives a high-level directive with no concrete steps, commands, or code for how the verification is performed or what success looks like. It instructs rather than merely describes (above anchor 1) but offers only minimal concrete guidance, matching anchor 2.

2 / 5

Workflow Clarity

This is a simple single-action skill, so the simple-skill exception applies: the single action (use the skill to verify plugin-level skill discovery) is stated and unambiguous in intent. It falls short of 5 because the sentence never specifies what 'verify' entails — no expected outcome or check is given, leaving a minor gap.

4 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references, and no bundle files (references/, scripts/, assets/) exist to structure. The heading plus one-line body is well-organized for a skill of this size, which per the rubric's simple-skill guidance earns the top score.

5 / 5

Total

16

/

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 has an explicit and reasonably concrete "Use when..." trigger and a distinct niche, but the capability half is nearly empty — it identifies the artifact as a fixture without stating any concrete actions or trigger synonyms. It is serviceable for its stated fixture purpose but scores in the middling range against the rubric.

Suggestions

State at least one concrete action in the 'what' half (e.g., 'Provides a minimal, valid plugin skill that loads and executes correctly') instead of only naming the artifact type.

Broaden trigger-term coverage with natural synonyms users would say, such as 'sample skill', 'example skill', 'dummy skill', or 'test fixture'.

Make the 'what' describe capabilities rather than the artifact's nature so the description fully answers both 'what does this do' and 'when should it be used'.

DimensionReasoningScore

Specificity

"Minimal plugin skill fixture" names the domain (plugin skill fixture for tests) but describes the artifact's nature rather than any capability action — no verbs describing what the skill does. It is not purely abstract language (anchor 1) since the domain is precisely identified, but it falls well short of anchor 3, which requires 1-2 concrete actions.

2 / 5

Completeness

Both halves are present: "what" via "Minimal plugin skill fixture" and an explicit "when" via "Use when a test needs a valid plugin skill" (so the ≤3 cap for a missing 'Use when' clause does not apply). Not anchor 5 because the "what" is thin — it describes what the artifact is rather than what it concretely does.

4 / 5

Trigger Term Quality

"Use when a test needs a valid plugin skill" supplies relevant keywords for the niche ("test", "valid plugin skill", "fixture") but misses natural variations and synonyms such as "sample skill", "example skill", or "dummy skill". This matches the anchor-3 pattern of relevant-but-incomplete keyword coverage rather than the comprehensive coverage of anchor 4.

3 / 5

Distinctiveness Conflict Risk

"plugin-level skill discovery" and "valid plugin skill" carve out a clear, narrow niche with a distinct trigger, giving minimal conflict risk with unrelated skills. Generic terms like "test" and "skill" leave minor overlap risk with other test- or plugin-related skills, keeping it below anchor 5.

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/minimal-plugin/skills/minimal-plugin-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.