CtrlK
BlogDocsLog inGet started
Tessl Logo

generate-prompt

Generates reusable Prompt Template files (.github/prompts/*.prompt.md) with variable substitution for ad-hoc, high-frequency tasks. Use when the user needs quick, repeatable prompts for common operations (explain code, fix bug, add tests, refactor, document). Creates templates with handlebars variables, optimized context structure, and strict output constraints. Not for complex workflows (use skills) or persistent roles (use agents).

84

2.10x
Quality

77%

Does it follow best practices?

Impact

97%

2.10x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/generate-prompt/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 a well-structured, actionable walkthrough with clear references and a validation step. Its main weakness is conciseness: it repeats examples and inlines catalog/detail that partly duplicate the bundle files. Workflow and progressive disclosure are strong, with explicit loading commands and a final checklist.

Suggestions

Trim repeated example sets (e.g. the Explain/Fix/Add-tests examples recur across Steps 2-5); rely on the reference files for exhaustive lists and keep one canonical example per step.

Replace the placeholder `head -10 .github/prompts/{{prompt-name}}.prompt.md` guidance with a concrete validation step or note that the name must be substituted, so the validation commands are copy-paste runnable.

Consider moving the 'Common Prompt Templates' catalog (lines 338-358) into a reference file so the overview stays lean and points to it, improving both conciseness and progressive disclosure.

DimensionReasoningScore

Conciseness

The body is thorough and well-organized but lengthy, repeating example sets across steps and including guidance (e.g. repeated Good/Bad structure examples, full template-library catalog) that Claude could infer from the references; it earns its place only partly.

3 / 5

Actionability

Provides concrete, executable guidance (bash `cat` commands to load each reference, a template file, grep/head validation commands, a final checklist) with only minor gaps such as the `head -10 .github/prompts/{{prompt-name}}.prompt.md` placeholder not being literally runnable until a name is substituted.

4 / 5

Workflow Clarity

A clearly sequenced 7-step process with an explicit validation checkpoint and final checklist in Step 7, falling just short of a 5 because the validation is manual/guidance-style rather than a strict validate-fix-retry loop with failure handling.

4 / 5

Progressive Disclosure

SKILL.md acts as an overview with clearly signaled, one-level-deep references (three references plus one asset, each loaded via an explicit `cat` command and summarized in the Resources section); the file listing is confirmed real, with only minor inlining of detail that could live in references.

4 / 5

Total

15

/

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 the concrete output and mechanism, gives explicit 'Use when' triggers with natural example phrases, and sharply differentiates the skill from skills/agents/instructions. It is slightly under-comprehensive on action listing and synonym coverage but otherwise excellent.

DimensionReasoningScore

Specificity

Names the concrete output (Prompt Template files at a specific path) plus specific mechanisms (handlebars variables, variable substitution, optimized context structure, strict output constraints), with only minor coverage gaps relative to the 'several specific actions' anchor.

4 / 5

Completeness

Explicitly answers what ('Generates reusable Prompt Template files... with variable substitution') and when ('Use when the user needs quick, repeatable prompts for common operations') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user phrases ('explain code, fix bug, add tests, refactor, document') plus the file extension pattern, though it is missing some synonyms and variations users might naturally say.

4 / 5

Distinctiveness Conflict Risk

Defines a clear niche and explicitly distinguishes it from adjacent artifacts ('Not for complex workflows (use skills) or persistent roles (use agents)'), minimizing wrong-skill triggering.

5 / 5

Total

18

/

20

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
canonical/copilot-collections
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.