CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

contract-skill

Hermetic Agent Plugins lifecycle contract

Quality

43%

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/agent_plugins/portable/skills/contract-skill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

30%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 placeholder stub: a single heading and the line 'Initial fixture bytes.' with no instructions, examples, or workflow. While it wastes almost no tokens, it provides zero actionable guidance. The entire body needs to be replaced with the skill's actual instructions.

Suggestions

Replace 'Initial fixture bytes.' with the actual task instructions — concrete commands or code showing how the lifecycle contract is validated/enforced.

If the lifecycle involves multiple steps (e.g. install → validate → activate), list them as an ordered sequence with an explicit validation checkpoint before any state transition.

Move any lengthy contract rules or reference tables into a references/ file and link to it from a concise overview section in SKILL.md.

DimensionReasoningScore

Conciseness

The body ("# Contract skill\n\nInitial fixture bytes.") is maximally lean with no over-explanation, but the placeholder line 'Initial fixture bytes.' is a token that earns nothing — efficient with one minor instance of waste, so anchor 4 rather than 5.

4 / 5

Actionability

The body contains no code, commands, or instructions of any kind — 'Initial fixture bytes.' doesn't even describe a task, matching the anchor for entirely vague content with no concrete guidance.

1 / 5

Workflow Clarity

No steps or sequence are present anywhere in the body. The simple-skill exception cannot apply because there is no single unambiguous action stated — there is no action at all, matching the 'steps missing or incoherent' anchor.

1 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files, so the simple-skill exception is available, but the body offers only a single heading over placeholder text — nominal structure with nothing organized or navigable, which is below the 'well-organized sections' needed for a 5.

3 / 5

Total

9

/

20

Passed

Description

28%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 is a bare noun phrase that names a niche domain but states no concrete actions and provides no 'use when' trigger guidance. It is more specific than pure fluff like 'Helps with documents', but fails on completeness and trigger-term quality. It needs concrete verbs describing what the skill does and an explicit trigger clause.

Suggestions

Replace the noun phrase with third-person action verbs, e.g. 'Validates and enforces the Hermetic Agent Plugins lifecycle contract: install, enable, disable, and remove plugin lifecycle states'.

Add an explicit trigger clause: 'Use when the user mentions agent plugins, plugin installation, plugin lifecycle states, or contract compliance'.

Include natural synonyms and file/keyword variants users would actually type (e.g. 'plugin lifecycle', 'hermetic contract', 'plugin validation').

DimensionReasoningScore

Specificity

The description names a domain ("Agent Plugins lifecycle contract") but contains no action verbs whatsoever — no concrete capability is stated, matching the anchor for minimal/generic actions rather than the 1-2 concrete actions needed for a 3.

2 / 5

Completeness

"Hermetic Agent Plugins lifecycle contract" is a vague noun-phrase 'what' with no 'when to use' clause at all — the explicit trigger guidance guideline caps it here, and it lacks the clear what-with-actions needed for a 3.

2 / 5

Trigger Term Quality

"Hermetic", "lifecycle", and "contract" are technical jargon users would rarely say; only "Agent Plugins" is a plausibly natural term, so it sits between 'only technical jargon' (1) and 'some relevant keywords' (3), closer to one generic keyword with natural phrases missing.

2 / 5

Distinctiveness Conflict Risk

The niche jargon ("Hermetic Agent Plugins") gives it a somewhat distinct surface, but with no stated action it could still overlap with any other plugin-lifecycle or contract-related skill — somewhat specific but not clearly distinct enough for a 4.

3 / 5

Total

9

/

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

microsoft/apm

Path

tests/fixtures/agent_plugins/portable/skills/contract-skill/SKILL.md

Revision

2920043

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill