CtrlK
BlogDocsLog inGet started
Tessl Logo

create-skill

Create a reusable skill (SKILL.md) that packages a workflow.

52

Quality

57%

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 ./extensions/copilot/assets/prompts/skills/create-skill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The body is commendably concise and reasonably sequenced for a meta-skill, but its actionability is undercut by deferring the core template/principles to external files that are not bundled, and its references are not clearly signaled or backed by actual bundle files. Workflow steps lack explicit validation checkpoints.

Suggestions

Either inline a minimal SKILL.md template/structure checklist or add a bundled references/ file (e.g. references/skill-template.md) and link to it with a real markdown link so the substantive guidance is available, not just referenced.

Add explicit validation/completion checkpoints to the Iterate workflow, e.g. 'Verify the saved SKILL.md has name, description, and at least one actionable section before finalizing.'

Replace backtick/bold mentions of external resources with clear navigable links (e.g. [skills.md](skills.md)) and confirm each referenced file exists in the bundle.

DimensionReasoningScore

Conciseness

The ~28-line body is lean and sectioned (Extract / Clarify / Iterate) with no padding and no explanation of concepts Claude already knows, matching score 3 'Lean and efficient; assumes Claude's competence; every token earns its place'; it is not verbose enough to drop to 2.

3 / 3

Actionability

Concrete guidance exists ("Extract: step-by-step process, decision points, branching logic", specific clarifying questions, numbered iterate steps), but the substantive know-how — the SKILL.md template and principles — is deferred to unbundled external files ("Load and follow skills.md for template and principles"), leaving it incomplete per score 2 'Some concrete guidance but incomplete; missing key details'.

2 / 3

Workflow Clarity

A clear Extract → Clarify → Iterate sequence with a refinement loop ('Identify the most ambiguous or weak parts and ask about those') is present, but there are no explicit validation or completion checkpoints, matching score 2 'Steps listed but validation gaps; sequence present but checkpoints missing or implicit'; a 3 would require explicit verification steps.

2 / 3

Progressive Disclosure

The body is well-organized into sections but references external resources ("skills.md", "agent-customization") via backticks/bold rather than clear navigable links, and no bundle files (references/scripts/assets) exist to back those references, matching score 2 'references present but not clearly signaled'; it is not a monolithic wall (1) nor a clean one-level-deep reference set (3).

2 / 3

Total

9

/

12

Passed

Description

50%

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 cleanly states what the skill does and uses relevant natural terms, but it omits any explicit "when to use" trigger guidance and offers only a single concrete action. It is competent but generic, capped at level 2 across all dimensions.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user wants to create, save, or refactor a reusable SKILL.md from a conversation workflow.'

Broaden trigger terms with natural variations users would say: 'make a skill', 'write a skill', 'skill template', 'package a workflow as a skill'.

Add a second concrete action (e.g. 'extract, generalize, and save a workflow as a SKILL.md') to lift specificity from 2 to 3 and reduce overlap with agent-customization.

DimensionReasoningScore

Specificity

Quotes "Create a reusable skill (SKILL.md) that packages a workflow" name the domain and one concrete action (create/package), matching the score-2 anchor 'Names domain and some actions, but not comprehensive'; it does not list multiple distinct concrete actions required for a 3.

2 / 3

Completeness

It states WHAT ("Create a reusable skill... that packages a workflow") but provides no "Use when..." or equivalent trigger guidance, so per the guidelines completeness is capped at 2 ('Has what, but when is missing or only implied').

2 / 3

Trigger Term Quality

Natural terms like "skill", "SKILL.md", and "workflow" are present and would be said by a user, but coverage is thin with no common variations (e.g. "make a skill", "write a skill", "skill template"), matching score 2 'Some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

"Create a reusable skill (SKILL.md)" carves a niche, but it explicitly overlaps with the related `agent-customization` skill and lacks distinct trigger phrasing, matching score 2 'Somewhat specific but could still overlap with similar skills'; it is not generic enough for a 1 nor distinctive enough for a 3.

2 / 3

Total

8

/

12

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.

Validation15 / 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
posit-dev/positron
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.