Marketplace domain-expertise-template
Template for creating domain expertise skills. Copy and customize for your specific domain.
install
source · Clone the upstream repo
git clone https://github.com/aiskillstore/marketplace
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/aiskillstore/marketplace "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/chaiwithjai/domain-expertise-template" ~/.claude/skills/aiskillstore-marketplace-domain-expertise-template && rm -rf "$T"
manifest:
skills/chaiwithjai/domain-expertise-template/SKILL.mdsource content
Domain Expertise Template
Copy this template to create your own domain expertise skill.
Instructions
- Copy this file to
~/.claude/skills/your-domain/SKILL.md - Replace all
text with your content[PLACEHOLDER] - Customize sections as needed
- Test and iterate
--- 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 Mistakes1. [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:-
[Question about scope]
- [Option A]
- [Option B]
- [Option C]
-
[Question about context] [Open-ended question]
-
[Question about constraints] [Open-ended question]
-
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