skill-template

Template for creating new Agent Skills for context engineering. Use this template when adding new skills to the collection.

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./template/SKILL.md

Quality

Content

53%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 is a well-organized authoring template with clear sections, concrete good/avoid examples, and real one-level-deep reference files. Its scores are held at the mid-range anchors by over-explanation of section purposes, placeholder rather than fully realized executable content, and absence of explicit validation checkpoints.

Suggestions

Tighten the per-section narration: replace 'Describe specific situations...' preamble with a one-line purpose plus the good/avoid examples, letting examples carry the guidance.

Add an explicit validation checkpoint for skill authoring, e.g. a short checklist ('verify ownership boundary stated, triggers include a Do-not-activate block, references resolve to real files').

Move the longer instructional prose (e.g., freedom-level guidance, claims/metadata rules) into a reference file and keep SKILL.md as a lean overview pointing to it.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and the 'Default assumption: Claude is already very smart' guidance explicitly pushes against padding, but several sections over-explain what a heading should contain (e.g., narrating what 'When to Activate' or 'Gotchas' are), which keeps it at the mostly-efficient-but-could-be-tightened anchor rather than a 4.	3 / 5
Actionability	It gives concrete, actionable scaffolding including good/avoid third-person examples, an explicit input/output example block, and numbered gotcha/guideline formats, but as a template it stops at instructional guidance and placeholders rather than fully executable, copy-paste-ready content, matching the some-concrete-but-incomplete anchor.	3 / 5
Workflow Clarity	Section order provides a rough authoring sequence (When to Activate through References), but there are no explicit validation checkpoints or feedback loops for the skill-authoring process, so it sits at the steps-present-but-checkpoints-missing anchor; this is not a destructive/batch skill, so the 3-cap rule does not additionally bind it.	3 / 5
Progressive Disclosure	Structure is clear with well-signaled, one-level-deep references to real bundle files ('./references/topic-details.md' and './references/reference-file.md', both present), and the 500-line budget guidance pushes detail to references; it is not a 5 because the references are stubs and a few inline sections could themselves be deferred to reference files.	4 / 5
	Total	13 / 20 Passed

Description

62%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 third-person, includes an explicit 'Use this template when' trigger, and clearly states both what it is and when to apply it. Its main weakness is moderate keyword coverage and a 'when' clause that is somewhat generic, which keep it just below the top anchors.

Suggestions

Broaden trigger terms with natural synonyms a user would say, e.g. 'Use when creating, scaffolding, or authoring a new skill, or when starting from a skill template.'

Sharpen the 'when' clause with concrete signals, e.g. 'Use when the user asks to add a new skill to the collection or requests a starting template for a skill.'

Add one or two more concrete actions (e.g., 'scaffold structure, fill in sections, link reference files') to lift specificity toward the comprehensive-coverage anchor.

Dimension	Reasoning	Score
Specificity	Names the domain ('creating new Agent Skills for context engineering') and one to two concrete actions ('creating', 'adding new skills'), but does not list several specific actions, so it stops at the domain-plus-1-2-actions anchor rather than the comprehensive-coverage anchor above.	3 / 5
Completeness	Explicitly answers both what ('Template for creating new Agent Skills for context engineering') and when ('Use this template when adding new skills to the collection'); because a 'Use...when' clause is present it is not capped at 3, but the 'when' is fairly generic and could be more specific, so it sits at the both-present-but-could-be-sharper anchor rather than a 5.	4 / 5
Trigger Term Quality	Includes relevant natural phrases a user might say ('adding new skills', 'context engineering', 'new skills to the collection'), but misses common variations and synonyms (e.g., 'skill template', 'author a skill', 'scaffold a skill'), fitting the some-keywords-but-missing-variations anchor.	3 / 5
Distinctiveness Conflict Risk	It occupies a clear meta niche (skill authoring/template scaffolding) with distinct triggers, with only minor overlap risk against closely related skill-authoring skills; not a 5 because the trigger phrasing is broad enough that a generic 'help me write a skill' request could overlap.	4 / 5
	Total	14 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: muratcankoylan/Agent-Skills-for-Context-Engineering
Path: template/SKILL.md
Commit: 6dbe1a1

Reviewed: 19 days ago

Table of Contents

Discovery Implementation Validation

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.