CtrlK
BlogDocsLog inGet started
Tessl Logo

disable-model-invocation

A skill that cannot be invoked by the model.

53

Quality

58%

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 ./legacy_pi_mono_code/pi-mono/packages/coding-agent/test/fixtures/skills/disable-model-invocation/SKILL.md

The canonical home for this skill is disable-model-invocation in Kiz8-Team/pi-cwl

SKILL.md
Quality
Evals
Security

Quality

Content

96%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 lean, executable, and unambiguous for a trivial single-purpose manual-only skill, scoring near the top of the rubric. The only minor weakness is progressive disclosure, since there is barely any structure to organize — appropriate for this skill but not a showcase of sectioning. No changes are strictly required.

DimensionReasoningScore

Conciseness

The body is two short lines that state exactly the invocation constraint with no padding or explanation of concepts Claude already knows, matching 'Lean and efficient; every token earns its place.' There is nothing to trim, so it does not drop to 4.

5 / 5

Actionability

It gives the exact, copy-paste-ready command '/skill:disable-model-invocation' as the sole action, matching 'Fully executable; copy-paste ready commands'. It is not a 4 because there are no gaps in the single action being conveyed.

5 / 5

Workflow Clarity

This is a simple single-purpose skill with one unambiguous action (manual invocation), which the simple-skill exception allows to score 5. There are no destructive or batch operations requiring validation checkpoints, so no cap applies.

5 / 5

Progressive Disclosure

The content is appropriately minimal for a trivial skill with no need for external references, but it consists of a single heading and one sentence, so 'well-organized sections' is only weakly demonstrated. It is not a 5 because there is essentially no section structure to navigate, and not a 3 because nothing is inlined that belongs elsewhere.

4 / 5

Total

19

/

20

Passed

Description

21%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 terse meta-statement about a property of the skill rather than a capability-and-trigger description. It lacks natural trigger terms and any 'when to use' guidance, which limits its usefulness for routing. Rewriting it to state the manual-only behavior as an explicit capability with trigger phrasing would substantially improve it.

Suggestions

Add an explicit 'Use when...' or equivalent trigger clause (e.g., 'Use when a skill must only be invoked manually by the user and never auto-triggered by the model') to address the missing 'when' dimension.

Include natural user-facing terms such as 'manual-only skill', 'disable auto-invocation', or '/skill invocation' rather than pure meta-jargon.

Reframe the description as a concrete capability/action statement in third person (e.g., 'Prevents model-initiated invocation; restricts triggering to explicit /skill commands.') to raise specificity.

DimensionReasoningScore

Specificity

The phrase "A skill that cannot be invoked by the model" names the meta-domain of skill invocation but describes a property rather than listing concrete actions, matching the anchor 'Names the domain but actions are minimal or generic.' It does not reach 3 because no concrete capability actions are enumerated.

2 / 5

Completeness

There is only a vague 'what' (a property of the skill) and no 'when'/trigger clause at all, matching 'Has a vague what and no when'. It is not a 1 because a discernible statement exists, and not a 3 because no usable 'when' guidance is implied.

2 / 5

Trigger Term Quality

The text offers only technical jargon ("skill", "invoked by the model") with no natural phrases a user would actually say when needing this skill, matching the 'No natural keywords; only technical jargon' anchor. It does not reach 2 because there are not even generic user-facing keywords present.

1 / 5

Distinctiveness Conflict Risk

The manual-only concept is somewhat specific, but the description conveys no clear triggers, so it could overlap conceptually with other meta-skills. It is not a 4 because no distinct trigger phrases are given, and not a 2 because the manual-invocation notion is narrower than fully generic language.

3 / 5

Total

8

/

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
Dicklesworthstone/pi_agent_rust
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.