Back to skills
SKILL.md
Domain Expertise Template
ASecurityTemplate for creating domain expertise skills. Copy and customize for your specific domain.
- 416 stars
- 0 votes
- 0 copies
- 3 views
- Added February 7, 2026
Security analysis
100/100Pro scans all 2 files and shows the line behind each finding
npx -y skills add aiskillstore/marketplace --skill domain-expertise-template --agent claude-codeAre you the author of Domain Expertise Template?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/aiskillstore-domain-expertise-template)---
name: domain-expertise-template
description: Template for creating domain expertise skills. Copy and customize for your specific domain.
---
# 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
Files in this skill
- SKILL.md
- skill-report.json
Attribution
Comments
Loading comments…