CtrlK
BlogDocsLog inGet started
Tessl Logo

creating-skills

Use when you need to create a new custom skill for a profile - guides through gathering requirements, creating directory structure, writing SKILL.md, and optionally adding bundled scripts

57

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.agency/plugins/nori/skills/creating-skills/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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.

A compact, well-organized instructional skill body with genuinely useful concrete templates and contrastive examples. Its weaknesses are the absence of any validation checkpoint in the workflow and incomplete executable specifics for the core deliverable (directory path, frontmatter format).

Suggestions

Add a validation checkpoint to the required steps, e.g., "Verify the new SKILL.md frontmatter parses and the skill is discoverable in the profile directory".

Include a concrete frontmatter and directory example (actual path pattern plus a minimal valid SKILL.md) so the core deliverable is copy-paste ready.

Move the good/bad example gallery into a references/ file (one level deep) and keep only a pointer plus one exemplar inline.

DimensionReasoningScore

Conciseness

The body is lean and instructional throughout, with only minor trimmable lines like "Scripts are simple code cli tools that do various things deterministically"; it explains nothing Claude already knows.

4 / 5

Actionability

Provides a copy-paste <required> block template, a step-with-guidelines example, and concrete good/bad example pairs, but omits key executable details such as the profile directory path, a SKILL.md frontmatter example, and the command to create the skill directory.

3 / 5

Workflow Clarity

The required checklist gives a coherent ordered 6-step sequence ending with instructing the user to run /nori-switch-profile, but no validation checkpoints exist (e.g., verifying the written SKILL.md parses or the skill loads).

3 / 5

Progressive Disclosure

Sections (Overview, Writing Skills, Writing scripts, Tools and Code) are well organized and the referenced example URLs are one level deep and clearly signaled; however, the body exceeds the simple-skill threshold and the good/bad example gallery is inlined content that could live in a references file.

4 / 5

Total

14

/

20

Passed

Description

70%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.

A clear, well-structured description that names the domain and four concrete actions with an explicit trigger clause. Its main deductions are second-person voice (mandated specificity penalty) and limited trigger-phrase coverage.

Suggestions

Rewrite in third person (e.g., "Guides through gathering requirements... Use when the user asks to create, make, or add a custom skill") to avoid the voice penalty.

Broaden trigger coverage with natural variations users would say: "new skill", "make a skill", "add a skill to my profile", "SKILL.md".

Mention the full lifecycle (e.g., verifying the created skill or switching profiles) to close the completeness gap.

DimensionReasoningScore

Specificity

Lists four concrete actions ("gathering requirements, creating directory structure, writing SKILL.md, and optionally adding bundled scripts"), a baseline 4 for several specific actions with minor gaps, but reduced by 1 per the guideline because the description uses second-person voice ("Use when you need to...").

3 / 5

Completeness

Both a clear what ("guides through gathering requirements, creating directory structure, writing SKILL.md, and optionally adding bundled scripts") and an explicit when ("Use when you need to create a new custom skill for a profile") are present; the when clause relies on a single trigger phrase and could be more specific.

4 / 5

Trigger Term Quality

"create a new custom skill", "SKILL.md", and "bundled scripts" are natural terms users would say, but common variations like "make a skill", "add a skill", or "new skill" are missing.

4 / 5

Distinctiveness Conflict Risk

"custom skill for a profile", "SKILL.md", and "bundled scripts" form a distinct authoring niche with low conflict risk, though it could overlap with skill-editing or profile-management requests.

4 / 5

Total

15

/

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