CtrlK
BlogDocsLog inGet started
Tessl Logo

generate-agent-skills

Architects, generates, and validates Agent Skills. Enforces specification and best practices. Used any time an agent skill must be created or updated.

82

1.25x
Quality

74%

Does it follow best practices?

Impact

100%

1.25x

Average score across 3 eval scenarios

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/generate-agent-skills/SKILL.md

The canonical home for this skill is generate-agent-skills in canonical/copilot-collections

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 body delivers an exemplary 6-step workflow: concrete commands, mandatory validation with feedback loops, checkpoints, and a well-signaled one-level reference layer. Its one real weakness is token economy — the scaffold mandate is repeated four times with heavy emphasis decoration that adds tokens without adding information.

Suggestions

State the scaffolding/script mandate once in the critical-requirements block and reference it by pointer elsewhere; drop the duplicate MANDATORY banners, checklist items, and STOP CONDITION repetition to reclaim tokens.

Move the Step 2 script-vs-checklist decision guidance and the Step 6 iteration patterns into references/BEST_PRACTICES.md and workflows.md respectively, keeping only one-line pointers in SKILL.md.

DimensionReasoningScore

Conciseness

The body is instructional rather than explanatory, but the scaffolding mandate is repeated four times (the CRITICAL WORKFLOW REQUIREMENTS block, the Step 3 MANDATORY banner, the post-validation checklist, and the STOP CONDITION) alongside heavy emoji emphasis blocks, so it could be noticeably tightened.

3 / 5

Actionability

Fully executable, copy-paste-ready commands are given throughout: the scaffold invocation with documented --name/--simple options, a worked validate example ("python3 scripts/validate_skill.py --path .github/skills/diagnose-ci-failure"), an ls verification checkpoint with expected output, and the inline naming regex.

5 / 5

Workflow Clarity

A clear 6-step sequence with explicit mandatory validation steps, verification checkpoints, error-recovery feedback loops ("If validation fails: Read the error output carefully, Fix critical violations immediately"), a post-validation checklist, and explicit stop conditions.

5 / 5

Progressive Disclosure

The Knowledge Retrieval section clearly maps each question type to one-level-deep reference files (all of which exist in the bundle), but inline content such as the script-vs-checklist decision guidance and the iteration patterns duplicates material that belongs in references — minor organization gaps.

4 / 5

Total

17

/

20

Passed

Description

67%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 well-formed third-person prose that answers both what the skill does and when to use it, scoring near the top of the scale. Its weaknesses are the abstract "enforces specification and best practices" filler phrase and a trigger vocabulary limited to "agent skill / created or updated" without the synonyms users would naturally say.

Suggestions

Replace "Enforces specification and best practices" with a concrete action (e.g., "validates SKILL.md frontmatter, naming conventions, and bundle structure against the specification") to lift specificity to the comprehensive anchor.

Expand the when-clause with concrete trigger phrases and synonyms, e.g., "Use when the user asks to create, author, build, or update an Agent Skill, or when editing SKILL.md frontmatter or a skill's bundle files."

Add file-extension/format keywords such as "SKILL.md" so queries mentioning the file itself naturally match.

DimensionReasoningScore

Specificity

"Architects, generates, and validates Agent Skills" lists several concrete third-person actions, but "Enforces specification and best practices" is abstract padding, leaving minor gaps in coverage short of the comprehensive anchor 5.

4 / 5

Completeness

Both a clear "what" (architects, generates, validates) and an explicit "when" ("Used any time an agent skill must be created or updated") are present, but the when-clause lacks the concrete trigger phrases of the anchor-5 example.

4 / 5

Trigger Term Quality

"agent skill" and "created or updated" are natural terms a user might say, but common variations and synonyms ("skill authoring", "build a skill", "SKILL.md", "edit/modify a skill") are missing, matching the some-keywords-missing-synonyms anchor.

3 / 5

Distinctiveness Conflict Risk

The "Agent Skills" niche is mostly distinct with clear dedicated triggers; only minor overlap risk with general code-generation or workflow-design skills.

4 / 5

Total

15

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 7 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.