CtrlK
BlogDocsLog inGet started
Tessl Logo

make-instructions

Create VS Code file-based instructions (.instructions.md files). Use when asked to create, scaffold, or add file-based instructions for Copilot. Generates .instructions.md with YAML frontmatter and background knowledge content.

68

Quality

81%

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

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 content is well-structured, actionable, and concise, with a clear five-step workflow culminating in a validation checklist. It consistently sits at the strong-but-not-exemplary tier across dimensions, mainly lacking an explicit error-recovery loop and finer trimming.

Suggestions

Add an explicit error-recovery feedback loop in Step 5 (e.g., 'If the YAML is invalid, fix and re-validate before proceeding') to push workflow_clarity toward 5.

Tighten the meta-guidance bullets in Step 4 and the Recommended sections list to reduce minor verbosity and lift conciseness.

Include one short inline do/don't code example for the body content (mirroring the applyTo pitfall example) to make actionability fully copy-paste ready.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence without explaining basic concepts, but a few list items and the meta-guidance bullets could be trimmed further, placing it just below the fully lean 5 anchor.

4 / 5

Actionability

Provides concrete, copy-paste-ready guidance (YAML frontmatter template, file-path patterns, applyTo globs, a do/don't pitfall example), with only minor gaps relative to the fully executable 5 anchor.

4 / 5

Workflow Clarity

Steps 1–5 are clearly sequenced and Step 5 provides an explicit validation checklist, but there is no error-recovery/retry feedback loop, which keeps it below the 5 anchor.

4 / 5

Progressive Disclosure

A single well-organized file with clear sections and no need for external references (none exist), with only minor organization gaps versus the ideal one-level-deep reference structure.

4 / 5

Total

16

/

20

Passed

Description

87%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 strong: it states concrete capabilities, provides an explicit 'Use when' trigger clause, and occupies a distinct niche. It falls just short of top marks on specificity and trigger-term coverage where a few additional synonyms/actions would make it comprehensive.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Create', 'scaffold, or add', 'Generates .instructions.md with YAML frontmatter and background knowledge content') with only minor coverage gaps, fitting the 'several specific actions' anchor rather than the comprehensive 5.

4 / 5

Completeness

Explicitly answers both 'what' (create/generate .instructions.md with frontmatter and background content) and 'when' ('Use when asked to create, scaffold, or add file-based instructions for Copilot') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases users would say ('create, scaffold, or add file-based instructions for Copilot', '.instructions.md', 'VS Code') give good keyword coverage, though a few synonyms are missing relative to the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (VS Code file-based instructions for Copilot) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

18

/

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