home / skills / muratcankoylan / agent-skills-for-context-engineering / template

template skill

/template

This skill standardizes the creation of new Agent Skills for context engineering, ensuring consistent patterns, docs, and integration across teams.

npx playbooks add skill muratcankoylan/agent-skills-for-context-engineering --skill template

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
3.6 KB
---
name: skill-template
description: Template for creating new Agent Skills for context engineering. Use this template when adding new skills to the collection.
---

# Skill Name

Provide a clear, concise description of what this skill covers and when to use it. This description appears in skill discovery and should help agents (and humans) determine when this skill is relevant.

**Important**: Keep the total SKILL.md body under 500 lines for optimal performance. Move detailed reference material to separate files in the `references/` directory.

## When to Activate

Describe specific situations, tasks, or contexts where this skill should be activated. Include both direct triggers (specific keywords or task types) and indirect signals (broader patterns that indicate skill relevance).

Write in third person. The description is injected into the system prompt, and inconsistent point-of-view can cause discovery problems.

- Good: "Processes Excel files and generates reports"
- Avoid: "I can help you process Excel files"

## Core Concepts

Explain the fundamental concepts covered by this skill. These are the mental models, principles, or frameworks that the skill teaches.

Default assumption: Claude is already very smart. Only add context Claude does not already have. Challenge each piece of information:
- "Does Claude really need this explanation?"
- "Can I assume Claude knows this?"
- "Does this paragraph justify its token cost?"

## Detailed Topics

### Topic 1

Provide detailed explanation of the first major topic. Include specific techniques, patterns, or approaches. Use examples to illustrate concepts.

### Topic 2

Provide detailed explanation of the second major topic. Continue with additional topics as needed.

For longer topics, consider moving content to `references/` and linking:
- See [detailed reference](./references/topic-details.md) for complete implementation

## Practical Guidance

Provide actionable guidance for applying the skill. Include common patterns, anti-patterns to avoid, and decision frameworks for choosing between approaches.

Match the level of specificity to the task's fragility:
- **High freedom**: Multiple approaches are valid, decisions depend on context
- **Medium freedom**: Preferred pattern exists, some variation acceptable
- **Low freedom**: Operations are fragile, specific sequence must be followed

## Examples

Provide concrete examples that illustrate skill application. Examples should show before/after comparisons, demonstrate correct usage, or show how to handle edge cases.

Use input/output pairs for clarity:

**Example:**
```
Input: [describe input]
Output: [show expected output]
```

## Guidelines

List specific guidelines to follow when applying this skill. These should be actionable rules that can be checked or verified.

1. Guideline one with specific, verifiable criteria
2. Guideline two with clear success conditions
3. Continue as needed

## Integration

Explain how this skill integrates with other skills in the collection. List related skills as plain text (not links) to avoid cross-directory reference issues:

- skill-name-one - Brief description of relationship
- skill-name-two - Brief description of relationship

## References

Internal reference (use relative path to skill's own reference files):
- [Reference Name](./references/reference-file.md) - Description

Related skills in this collection:
- skill-name - Relationship description

External resources:
- Research papers, documentation, or guides

---

## Skill Metadata

**Created**: [Date]
**Last Updated**: [Date]
**Author**: [Author or Attribution]
**Version**: [Version number]

Overview

This skill is a reusable template for creating new agent skills focused on context engineering. It provides a concise structure, activation signals, core concepts, practical guidance, and example patterns to accelerate adding consistent, discoverable skills to an agent collection. Use it to standardize skill authoring and ensure reliable integration with multi-agent systems.

How this skill works

The template defines what to include when authoring a skill: activation triggers, core concepts, detailed topics, practical guidance, examples, and integration notes. It inspects tasks and metadata to recommend when the skill should be invoked, and prescribes concise inputs/outputs and verification guidelines to reduce ambiguity. Authors follow the template to produce consistent skill artifacts that agents can discover and use reliably.

When to use it

  • Adding a new capability to the agent collection and needing a standard format
  • Documenting activation triggers and context cues for skill dispatchers
  • Creating teachable guidance for context engineering patterns
  • Refactoring an existing skill to improve discoverability and maintainability
  • Onboarding new contributors who will author or review agent skills

Best practices

  • Keep descriptions short and task-focused; limit background to what the agent truly needs
  • Define explicit activation signals: keywords, task types, and indirect patterns
  • Provide concrete examples with input/output pairs to show expected behavior
  • Separate long reference material into dedicated reference files to keep the main skill concise
  • List integration points and related skills in plain text to clarify relationships
  • Include verifiable guidelines and success criteria for automated checks

Example use cases

  • Create a skill for processing structured inputs (CSV, JSON) with explicit activation keywords and example IO
  • Document a multi-agent coordination pattern and its triggers so dispatchers can route tasks correctly
  • Refactor a brittle skill by adding clear success checks and moving long explanations to references
  • Author a new retrieval-augmented generation skill with activation signals and sample prompts
  • Add a debugging skill that detects common context overflow patterns and suggests remediation

FAQ

How long should the main skill document be?

Keep the main skill concise — aim for under a few hundred lines; move detailed references to separate files.

Which perspective should the skill use?

Write the activation and discovery text in third person; other sections can be authored in a neutral, instructional tone.