skill-template
Template for creating new Agent Skills for context engineering. Use this template when adding new skills to the collection.
Install with Tessl CLI
npx tessl i github:muratcankoylan/Agent-Skills-for-Context-Engineering --skill skill-template63
Quality
47%
Does it follow best practices?
Impact
91%
1.35xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./template/SKILL.mdDiscovery
67%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 adequately covers the what and when, earning full marks for completeness. However, it lacks specificity about what the template actually contains or produces, and the trigger terms rely on somewhat technical jargon ('context engineering') rather than natural user language. The description would benefit from more concrete actions and common user phrasings.
Suggestions
Add specific actions the template enables, e.g., 'Provides YAML frontmatter structure, description guidelines, and content sections for new skills'
Include more natural trigger terms users might say: 'create a skill', 'new SKILL.md', 'skill file', 'write a skill definition'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain ('Agent Skills for context engineering') and one action ('creating new'), but lacks concrete details about what the template contains or what specific actions it enables. | 2 / 3 |
Completeness | Explicitly answers both what ('Template for creating new Agent Skills') and when ('Use this template when adding new skills to the collection') with a clear trigger clause. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'template', 'new skills', and 'adding new skills', but 'context engineering' is jargon and misses natural variations users might say like 'skill file', 'SKILL.md', or 'write a skill'. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to skill creation but could overlap with other template-related skills or documentation skills; 'context engineering' helps narrow scope but the term is niche. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a meta-template for creating skills rather than an actual skill with actionable content. While it demonstrates good structural principles and progressive disclosure patterns, it fails on conciseness and actionability because it consists entirely of placeholder text and instructional commentary rather than concrete, executable guidance. As a template, it serves its purpose, but evaluated as skill content it lacks the substance needed for high scores.
Suggestions
If this is meant to be a skill about creating skills, replace placeholder sections with concrete examples of good vs bad skill content
Add executable code examples showing how to structure a real skill file programmatically
Remove meta-commentary like 'Provide detailed explanation of the first major topic' and replace with actual content or remove the template sections entirely
Consider whether this belongs as a SKILL.md or as documentation in a different format (e.g., CONTRIBUTING.md or a README)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | This is a meta-template with extensive explanatory text about how to write skills, not an actual skill. It explains concepts Claude already knows (like 'keep files under 500 lines', 'use examples') and includes verbose instructional commentary that wouldn't be needed in a real skill. | 1 / 3 |
Actionability | The content is entirely placeholder text with no concrete, executable guidance. Sections like 'Topic 1' and 'Topic 2' contain only meta-instructions about what to write, not actual actionable content. No real code, commands, or specific examples are provided. | 1 / 3 |
Workflow Clarity | The template does provide a clear structure and sequence of sections to follow when creating a skill, but as a template it lacks actual workflow steps with validation checkpoints. The guidance about 'high/medium/low freedom' is useful but abstract. | 2 / 3 |
Progressive Disclosure | The template demonstrates good progressive disclosure principles: it mentions keeping SKILL.md under 500 lines, references a `references/` directory for detailed content, and shows how to link to external files. The structure itself models appropriate content organization. | 3 / 3 |
Total | 7 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.