CtrlK
BlogDocsLog inGet started
Tessl Logo

using-skills

Describes how to use abilities. Read before any conversation.

48

Quality

50%

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

75%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 well-structured, mostly lean instruction skill with concrete directives and a clear sequenced procedure plus a failure-mode checklist. It is held back from top marks by minor redundancy and the absence of explicit validation/feedback loops.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence, using compact bad/good example pairs rather than explaining concepts Claude already knows; minor redundancy across failure-mode examples keeps it just below a 5.

4 / 5

Actionability

It gives concrete, executable directives ('Use Read tool to read the skill', 'announce you are using it', 'Create TodoWrite todos') with exact phrasings in good examples; as an instruction-only skill this is mostly actionable with only minor gaps.

4 / 5

Workflow Clarity

The <required> block lays out a clear three-step sequence and the failure-mode section acts as a checklist; the skill is non-destructive so the simple-skill exception applies, though no explicit validation/feedback loop is present to reach 5.

4 / 5

Progressive Disclosure

Content is well-organized into clearly headed sections (required block, failure modes, announcing usage, how to read) in a single self-contained file with no nested references; structure is good with only minor organization gaps.

4 / 5

Total

16

/

20

Passed

Description

25%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 too vague and generic: it names the domain but lists no concrete actions and lacks explicit trigger phrases, making it indistinct from many skills. Both the 'what' and 'when' are weakly specified.

Suggestions

Replace 'Describes how to use abilities' with concrete actions, e.g. 'Reads a skill with the Read tool, announces its usage, and creates TodoWrite checklists for its steps.'

Add an explicit trigger clause such as 'Use when the user invokes a skill, references a skill, or asks how to follow a skill's process.'

Add natural trigger terms users would say (e.g. 'use this skill', 'follow the workflow', 'skill checklist') to improve distinctiveness.

DimensionReasoningScore

Specificity

"Describes how to use abilities" names the domain but offers only a minimal, generic action, matching the 'Names the domain but actions are minimal or generic' anchor; it does not list concrete actions needed for a 3.

2 / 5

Completeness

The 'what' is vague ("use abilities") and the 'when' ("Read before any conversation") is only weakly implied rather than an explicit 'Use when...' trigger; per the guideline a missing explicit trigger caps completeness, and this falls at the vague-what/weak-when level.

2 / 5

Trigger Term Quality

Only generic terms like "abilities" and "conversation" appear, lacking the natural phrases a user would actually say; this fits 'One or two generic keywords; missing the natural phrases users say' rather than the broader coverage of 3.

2 / 5

Distinctiveness Conflict Risk

"Use abilities" before "any conversation" is extremely broad with high overlap risk against virtually any other skill, matching the 'Very broad; high overlap risk' anchor.

2 / 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.

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.