skill-maker
Skill Maker
Overview
Creating skills IS Test-Driven Development applied to process documentation.
Write test cases (pressure scenarios with subagents), watch them fail (baseline behavior), write the skill (documentation), watch tests pass (agents comply), and refactor (close loopholes).
Core principle: If you didn't watch an agent fail without the skill, you don't know if the skill teaches the right thing.
What is a Skill?
Skills are modular packages that extend Claude's capabilities with specialized knowledge, workflows, and tools — like "onboarding guides" for specific domains.
Skills provide: Specialized workflows, tool integrations, domain expertise, bundled resources (scripts, references, assets)
Skills are: Reusable techniques, patterns, tools, reference guides
Skills are NOT: Narratives, one-off solutions, or project-specific conventions (use CLAUDE.md for those)
More from xbklairith/kisune
market-analysis
Use when analyzing markets or interpreting charts - applies technical indicators (RSI, MACD, Moving Averages), identifies support/resistance, analyzes multi-timeframe trends, checks fundamentals and sentiment. Activates when user says "analyze BTC", "what's the trend", "check this chart", mentions ticker symbols, or uses /trading:analyze command.
444spec-driven-planning
MANDATORY planning — creates specs in docx/features/ with EARS requirements and technical design. MUST activate instead of ad-hoc planning for any new feature.
33strategy-research
Use when developing or documenting trading strategies - guides edge hypothesis formation, validates statistical significance, documents strategy rules systematically (entry, exit, risk management). Activates when user says "research this strategy", "document my approach", "test this idea", mentions "trading strategy", "edge", or uses /trading:research command.
24pattern-recognition
Use when identifying chart patterns or setups - recognizes candlestick patterns (head and shoulders, double top/bottom, triangles), documents pattern library with entry/exit criteria. Activates when user says "what pattern is this", "is this a flag", "document this setup", mentions pattern names, or uses /trading:pattern command.
23spec-driven-implementation
MANDATORY implementation — breaks design into TDD tasks in docx/features/ tasks.md with Red-Green-Refactor. MUST activate after spec-driven-planning.
21pattern
Chart pattern identification — head and shoulders, double tops, triangles, flags. Documents pattern library with entry/exit criteria.
21