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.

80

Quality

100%

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

100%

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

The SKILL.md body is a high-quality, self-contained procedural guide: concise, actionable, with a well-sequenced workflow and an explicit validation step. It appropriately assumes Claude's competence while supplying the product-specific details (paths, frontmatter, globs) that Claude would not already know.

DimensionReasoningScore

Conciseness

The body is lean and action-oriented — concrete frontmatter template, applyTo globs, checklists, and a pitfalls table — with only a brief product-specific orientation paragraph; every section earns its place rather than explaining concepts Claude already knows. Not a 2 because there is no meaningful padding or redundant explanation.

3 / 3

Actionability

Provides concrete, copy-paste-ready guidance: the exact file path template `.github/instructions/<topic>.instructions.md`, a full YAML frontmatter block, specific applyTo patterns, and a validation checklist. As an instruction-only skill, the absence of executable code is not penalized because the guidance itself is actionable.

3 / 3

Workflow Clarity

A clearly sequenced five-step workflow (Investigate → Choose location → Generate → Write body → Validate) culminates in an explicit Step 5 validation checklist; the task is non-destructive file creation, so the absence of an explicit retry loop does not cap the score. Not a 2 because checkpoints are explicit rather than implicit or missing.

3 / 3

Progressive Disclosure

Self-contained single-purpose skill with well-organized sections (overview, When Not to Use, Workflow, Common Pitfalls) and no need for external references; structure is clear and easy to navigate. Not a 2 because content is appropriately sectioned with nothing that should be split out into separate files.

3 / 3

Total

12

/

12

Passed

Description

100%

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 specific, trigger-rich, and complete: it states concrete capabilities, gives an explicit "Use when..." clause with natural user verbs, and occupies a distinct niche. It is a strong activation description with no notable gaps.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Create VS Code file-based instructions", "create, scaffold, or add", and "Generates .instructions.md with YAML frontmatter and background knowledge content" — matching the anchor for listing multiple specific concrete actions; not a 2 because it goes beyond naming a domain plus a few actions.

3 / 3

Completeness

Explicitly answers what ("Create... Generates .instructions.md with YAML frontmatter and background knowledge content") and when ("Use when asked to create, scaffold, or add file-based instructions for Copilot"), satisfying the both-what-and-when anchor with an explicit trigger clause.

3 / 3

Trigger Term Quality

Natural user-facing terms appear in "Use when asked to create, scaffold, or add file-based instructions for Copilot", covering the verbs a user would actually say; not a 2 because common variations (create/scaffold/add) are present rather than a single keyword.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche — VS Code Copilot .instructions.md files — with distinct triggers unlikely to fire for unrelated skills; not a 2 because the scope is specific rather than a generic document/file domain.

3 / 3

Total

12

/

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