CtrlK
BlogDocsLog inGet started
Tessl Logo

using-skills

Describes how to use abilities. Read before any conversation.

44

Quality

44%

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 ./.agency/plugins/nori/skills/using-skills/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body delivers concrete, copy-paste-ready instruction (exact templates and tool calls) in a well-organized single file, though it carries some redundant anti-pattern examples. The core workflow is clearly sequenced but embeds its validation checkpoints only implicitly via examples rather than as explicit numbered steps.

DimensionReasoningScore

Conciseness

The body is mostly efficient and avoids explaining concepts Claude already knows, but repeated bad-example variants (e.g., four near-identical TodoWrite anti-patterns) could be tightened, matching 'mostly efficient but includes some unnecessary content'; not 1 because no padded concept explanations are present.

2 / 3

Actionability

Guidance is concrete and copy-paste ready with exact announcement templates, explicit 'Use Read tool', and literal TodoWrite() call syntax, matching the 'fully executable... specific examples' anchor; absence of code is not penalized for an instruction-only skill per the code_vs_instruction_skills note.

3 / 3

Workflow Clarity

The required workflow is clearly sequenced (read, announce, create todos) but validation checkpoints are only implicit — confirming relevance before announcing appears in examples, not as an explicit numbered step — matching 'steps listed but validation gaps'; not 1 because the sequence is clear.

2 / 3

Progressive Disclosure

A single self-contained file with no nested references and clearly organized sections (required, failure modes, announcing, how to read), which the simple_skills note permits to score 3 when well-organized without external references; no bundle files exist to layer.

3 / 3

Total

10

/

12

Passed

Description

17%

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 too generic and abstract to function as a reliable skill trigger, naming only a vague meta-domain without concrete capabilities or natural user-facing keywords. While it states both a weak 'what' and an unconditional 'when', it lacks the explicit contextual triggers needed to distinguish it from other skills.

Suggestions

Replace 'Describes how to use abilities' with concrete actions, e.g. 'Reads skill files, announces skill usage, and tracks checklist steps via TodoWrite.'

Add a natural-language trigger clause such as 'Use whenever you are about to invoke a skill or follow a multi-step checklist.'

Tighten distinctiveness by referencing the specific behaviors (TodoWrite checklists, skill announcements) that separate this meta-skill from domain skills.

DimensionReasoningScore

Specificity

The phrase 'Describes how to use abilities' names only a vague meta-domain with no concrete actions enumerated, matching the 'vague or no actions; abstract language' anchor rather than score 2 which requires named actions.

1 / 3

Completeness

A weak 'what' (describes how to use abilities) and an explicit but unconditional 'when' ('Read before any conversation') are both present, landing on 'has what, but when is... only implied'; it falls short of 3 due to the absence of explicit contextual triggers.

2 / 3

Trigger Term Quality

No natural keywords a user would say to invoke this; 'abilities' and 'Read before any conversation' are generic internal jargon with no relevant trigger variations, matching the lowest anchor.

1 / 3

Distinctiveness Conflict Risk

'How to use abilities' is maximally generic meta-guidance that would overlap with virtually every other skill, matching the 'very generic; would conflict with many skills' anchor.

1 / 3

Total

5

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
microsoft/FluidFramework
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.