Meta skill for creating new SDD experts from domain documentation. Provide a markdown file path with domain knowledge + optional steering context. Automatically synthesizes references, generates signal scripts, validates, and registers in experts.md/signals.md catalogs. Single-prompt creation with follow-up tweaks. Triggers - create expert, new expert, make expert, expert for, domain expert, add expert (project)
67
81%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
The canonical home for this skill is expert-sdd-creator in tdg-ninja/context-specs-factory-ai
Create SDD experts from domain documentation in a single prompt.
Example prompt:
Create an expert for my custom testing framework.
Docs: /path/to/custom-docs.md
Focus on: component testing, live dependency testing, Cucumber BDD patternsRead the markdown file and steering context to determine:
expert-)Create directory at .claude/skills/expert-{name}/ (sibling to this skill's directory):
expert-{name}/
├── SKILL.md # Frontmatter + Expert Mode + Signal Mode
├── references/
│ ├── {topic-1}.md # Synthesized from input docs
│ ├── {topic-N}.md
│ └── signal-workflow.md # How signal validates behavior
└── scripts/
├── run_signal.sh # Main signal execution
└── {helper}.sh # Additional helpers as neededFrom the input markdown:
signal-workflow.md describing validation approachAnalyze domain to determine appropriate signal approach:
| Domain Type | Signal Approach |
|---|---|
| Testing (Cucumber, JUnit) | Run tests, parse results |
| API/Service (REST, GraphQL) | Call endpoints, check responses |
| Build/Deploy (Maven, Gradle) | Run build, check artifacts |
| Config/Data (YAML, JSON) | Validate syntax, check schema |
| CLI tools (flyway, kubectl) | Run commands, parse output |
Generate run_signal.sh with domain-specific checks and TODOs for customization.
Structure the expert's SKILL.md:
---
name: expert-{name}
description: {domain} expertise with signal capability. {what it provides}. Triggers: {trigger-list} (project)
---Body includes:
Run validation:
scripts/validate_expert.sh /path/to/expert-{name}If valid, register:
scripts/register_expert.sh /path/to/expert-{name}Output to user:
Every expert must have:
SKILL.md with valid YAML frontmatter:
name: expert-{name} formatdescription: includes triggers and "(project)" suffixreferences/ directory with:
signal-workflow.md describing validation approachscripts/ directory with:
run_signal.sh (executable)→ See references/expert-structure.md for detailed patterns
Validate and register created experts.
| Action | Command |
|---|---|
| Validate | scripts/validate_expert.sh <expert-dir> |
| Register | scripts/register_expert.sh <expert-dir> |
→ See references/catalog-formats.md for entry formats
→ See references/signal-patterns.md for signal script patterns
3a7a725
Canonical home
since Aug 20, 2026
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.