CtrlK
BlogDocsLog inGet started
Tessl Logo

action-skill-contracts

Author deterministic skills for operations that change state or invoke external tools

54

Quality

61%

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 ./.copilot/skills/action-skill-contracts/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%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 concise, well-structured, and gives concrete authoring directives with strong anti-pattern guidance. Its main gap is the absence of an explicitly sequenced authoring workflow with validation checkpoints.

DimensionReasoningScore

Conciseness

The body is lean and dense: each bullet earns its place with no padding or explanation of concepts Claude already knows, matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

Guidance is concrete and directive (e.g., 'Start with an explicit ## SCOPE: activation conditions, allowed targets, and exclusions'; 'Define STOP conditions for missing prerequisites...'), with only minor gaps versus literal templates.

4 / 5

Workflow Clarity

The Patterns bullets give a rough sequence (SCOPE → workflow → STOP → canonical ref → focus) but the authoring process itself has no explicit validation checkpoints or feedback loops.

3 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references and is organized into clear, well-signaled sections (Context, Patterns, Examples, Anti-Patterns), satisfying the simple-skill exception.

5 / 5

Total

17

/

20

Passed

Description

42%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 states a clear purpose but omits any explicit trigger ('Use when...') guidance and relies on technical phrasing rather than natural user keywords. It is distinguishable but not strongly niche-marked.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers (e.g., 'Use when authoring or revising a skill that mutates files, state, or repositories, or calls external tools').

Replace jargon like 'deterministic skills' with user-facing phrasing and include synonyms/file-type cues users would actually say.

List 1-2 more concrete capabilities to lift specificity beyond a single named action.

DimensionReasoningScore

Specificity

Names the domain ('operations that change state or invoke external tools') and one concrete action ('Author deterministic skills'), but lists no further concrete actions, matching the 'domain + 1-2 actions, not comprehensive' anchor.

3 / 5

Completeness

It clearly states the 'what' (author deterministic skills for state-changing operations) but provides no 'when'/'Use when' trigger guidance, so per the missing-trigger-clause rule it caps at 3.

3 / 5

Trigger Term Quality

Terms like 'deterministic skills', 'change state', and 'invoke external tools' are technical jargon rather than natural phrases a user would say; it lacks the natural trigger language users actually use.

2 / 5

Distinctiveness Conflict Risk

The state-mutation/external-tool niche is somewhat specific and distinguishable from informational skills, but it could still overlap with general skill-authoring skills.

3 / 5

Total

11

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
bradygaster/squad
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.