domain-expertise-template
Template for creating domain expertise skills. Copy and customize for your specific domain.
Best use case
domain-expertise-template is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Template for creating domain expertise skills. Copy and customize for your specific domain.
Teams using domain-expertise-template should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/domain-expertise-template/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How domain-expertise-template Compares
| Feature / Agent | domain-expertise-template | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Template for creating domain expertise skills. Copy and customize for your specific domain.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Domain Expertise Template Copy this template to create your own domain expertise skill. ## Instructions 1. Copy this file to `~/.claude/skills/your-domain/SKILL.md` 2. Replace all `[PLACEHOLDER]` text with your content 3. Customize sections as needed 4. Test and iterate --- ```markdown --- name: [your-skill-name] description: Use when [trigger conditions]. Applies [your methodology/framework] for [outcome]. --- <framework_overview> ## What This Is [One paragraph describing what this expertise covers and why it matters] ## When to Use - [Trigger situation 1] - [Trigger situation 2] - [Trigger situation 3] ## Key Terms | Term | Definition | |------|------------| | [Term 1] | [Definition] | | [Term 2] | [Definition] | </framework_overview> <principles> ## Core Philosophy ### 1. [PRINCIPLE NAME IN CAPS] [2-3 sentences explaining this principle and why it matters] Example: - Good: [example of applying this principle well] - Bad: [example of violating this principle] ### 2. [PRINCIPLE NAME IN CAPS] [2-3 sentences explaining this principle and why it matters] Example: - Good: [example] - Bad: [example] ### 3. [PRINCIPLE NAME IN CAPS] [2-3 sentences explaining this principle and why it matters] Example: - Good: [example] - Bad: [example] </principles> <process> ## The Process ### Step 1: [Name] **Purpose**: [Why this step matters] **Actions**: - [Action 1] - [Action 2] **Output**: [What this step produces] ### Step 2: [Name] **Purpose**: [Why this step matters] **Actions**: - [Action 1] - [Action 2] **Output**: [What this step produces] ### Step 3: [Name] **Purpose**: [Why this step matters] **Actions**: - [Action 1] - [Action 2] **Output**: [What this step produces] </process> <templates> ## Output Templates ### [Template Name 1] ```markdown # [Document Title] ## Section 1 [What goes here] ## Section 2 [What goes here] ## Section 3 [What goes here] ``` ### [Template Name 2] [Another template if needed] </templates> <anti-patterns> ## Common Mistakes ### 1. [ANTI-PATTERN NAME] **What it looks like**: [Description of the mistake] **Why it's wrong**: [Consequences] **Instead**: [Correct approach] ### 2. [ANTI-PATTERN NAME] **What it looks like**: [Description] **Why it's wrong**: [Consequences] **Instead**: [Correct approach] ### 3. [ANTI-PATTERN NAME] **What it looks like**: [Description] **Why it's wrong**: [Consequences] **Instead**: [Correct approach] </anti-patterns> <intake> Before I help with [domain], I need to understand: 1. **[Question about scope]** - [Option A] - [Option B] - [Option C] 2. **[Question about context]** [Open-ended question] 3. **[Question about constraints]** [Open-ended question] 4. **Any specific concerns or requirements?** **I'll wait for your answers before proceeding.** </intake> ``` --- ## Customization Checklist - [ ] Updated skill name and description - [ ] Added 3+ principles with examples - [ ] Added 3+ process steps - [ ] Created output templates - [ ] Added 2+ anti-patterns - [ ] Created intake questions - [ ] Tested skill triggers correctly
Related Skills
cloudformation-template-creator
Cloudformation Template Creator - Auto-activating skill for AWS Skills. Triggers on: cloudformation template creator, cloudformation template creator Part of the AWS Skills skill category.
recipe-create-doc-from-template
Copy a Google Docs template, fill in content, and share with collaborators.
gws-modelarmor-create-template
Google Model Armor: Create a new Model Armor template.
make-skill-template
Create new Agent Skills for GitHub Copilot from prompts or by duplicating this template. Use when asked to "create a skill", "make a new skill", "scaffold a skill", or when building specialized AI capabilities with bundled resources. Generates SKILL.md files with proper frontmatter, directory structure, and optional scripts/references/assets folders.
template-skill
Replace with description of the skill and when Claude should use it.
../../../engineering-team/email-template-builder/SKILL.md
No description provided.
../../../project-management/atlassian-templates/SKILL.md
No description provided.
templates
Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.
obsidian-clipper-template-creator
Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.
notion-template-business
Expert in building and selling Notion templates as a business - not just making templates, but building a sustainable digital product business. Covers template design, pricing, marketplaces, marketing, and scaling to real revenue. Use when: notion template, sell templates, digital product, notion business, gumroad.
incident-runbook-templates
Create structured incident response runbooks with step-by-step procedures, escalation paths, and recovery actions. Use when building runbooks, responding to incidents, or establishing incident response procedures.
github-actions-templates
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.