
Skill Developer
Plan advanced skill-system features—hot-reload rules, skill dependencies, and environment-based enforcement—for maintainers extending agent routing beyond static SKILL.md files.
Overview
Skill Developer is an agent skill most often used in Build agent-tooling (also Ship review, Operate iterate) that outlines advanced skill-system enhancements like dependencies, hot-reload rules, and conditional enforceme
Install
npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill skill-developerWhat is this skill?
- Hot-reload skill-rules.json without restarting Claude Code (future enhancement)
- Skill dependency chains via dependsOn for progressive disclosure
- Conditional enforcement: suggest vs block by production, development, or CI context
- Independent skills today; composition and load order as explicit config
- Targets faster iteration for skill repo maintainers
Adoption & trust: 588 installs on skills.sh; 40.1k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your growing skill repo needs ordered prerequisites and stricter gates in CI, but skills are independent and rule changes require restarting the agent.
Who is it for?
Maintainers of multi-skill repos with skill-rules.json or similar routing who plan CI blocking and skill chains.
Skip if: Builders who only need a single short SKILL.md with no shared rule file or enforcement policy.
When should I use this skill?
Designing or extending skill-rules.json, skill dependency graphs, or environment-based enforcement beyond independent skills.
What do I get? / Deliverables
You get concrete configuration sketches for dependsOn, environment-aware enforcement, and hot-reload behavior to implement or prioritize on your skill platform.
- Dependency and enforcement config sketches
- Hot-reload implementation backlog
- Documented tradeoffs for suggest vs block modes
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Skill-system architecture and rule configuration live in agent-tooling when you scale beyond a handful of skills. skill-rules.json, dependency graphs, and enforcement modes are developer-facing extensions to the agent toolchain.
Where it fits
Model dependsOn so an advanced deploy skill always loads a base git skill first.
Set enforcement to block in CI while keeping suggest locally for faster iteration.
Plan file watchers on skill-rules.json to avoid restart friction during skill development.
How it compares
Architecture notes for skill orchestration, not a substitute for official Claude Code skill runtime APIs.
Common Questions / FAQ
Who is skill-developer for?
Indie maintainers and small teams extending antigravity-style skill rule systems beyond static, independent skills.
When should I use skill-developer?
During Build when designing skill-rules.json; at Ship security/review when defining CI block vs suggest; and at Operate when iterating on reload and dependency behavior without full restarts.
Is skill-developer safe to install?
It discusses config patterns only—review the Security Audits panel on this page and treat production block enforcement as something you implement and test yourself.
Workflow Chain
Requires first: writing skills
SKILL.md
READMESKILL.md - Skill Developer
# Advanced Topics & Future Enhancements Ideas and concepts for future improvements to the skill system. --- ## Dynamic Rule Updates **Current State:** Requires Claude Code restart to pick up changes to skill-rules.json **Future Enhancement:** Hot-reload configuration without restart **Implementation Ideas:** - Watch skill-rules.json for changes - Reload on file modification - Invalidate cached compiled regexes - Notify user of reload **Benefits:** - Faster iteration during skill development - No need to restart Claude Code - Better developer experience --- ## Skill Dependencies **Current State:** Skills are independent **Future Enhancement:** Specify skill dependencies and load order **Configuration Idea:** ```json { "my-advanced-skill": { "dependsOn": ["prerequisite-skill", "base-skill"], "type": "domain", ... } } ``` **Use Cases:** - Advanced skill builds on base skill knowledge - Ensure foundational skills loaded first - Chain skills for complex workflows **Benefits:** - Better skill composition - Clearer skill relationships - Progressive disclosure --- ## Conditional Enforcement **Current State:** Enforcement level is static **Future Enhancement:** Enforce based on context or environment **Configuration Idea:** ```json { "enforcement": { "default": "suggest", "when": { "production": "block", "development": "suggest", "ci": "block" } } } ``` **Use Cases:** - Stricter enforcement in production - Relaxed rules during development - CI/CD pipeline requirements **Benefits:** - Environment-appropriate enforcement - Flexible rule application - Context-aware guardrails --- ## Skill Analytics **Current State:** No usage tracking **Future Enhancement:** Track skill usage patterns and effectiveness **Metrics to Collect:** - Skill trigger frequency - False positive rate - False negative rate - Time to skill usage after suggestion - User override rate (skip markers, env vars) - Performance metrics (execution time) **Dashbord Ideas:** - Most/least used skills - Skills with highest false positive rate - Performance bottlenecks - Skill effectiveness scores **Benefits:** - Data-driven skill improvement - Identify problems early - Optimize patterns based on real usage --- ## Skill Versioning **Current State:** No version tracking **Future Enhancement:** Version skills and track compatibility **Configuration Idea:** ```json { "my-skill": { "version": "2.1.0", "minClaudeVersion": "1.5.0", "changelog": "Added support for new workflow patterns", ... } } ``` **Benefits:** - Track skill evolution - Ensure compatibility - Document changes - Support migration paths --- ## Multi-Language Support **Current State:** English only **Future Enhancement:** Support multiple languages for skill content **Implementation Ideas:** - Language-specific SKILL.md variants - Automatic language detection - Fallback to English **Use Cases:** - International teams - Localized documentation - Multi-language projects --- ## Skill Testing Framework **Current State:** Manual testing with npx tsx commands **Future Enhancement:** Automated skill testing **Features:** - Test cases for trigger patterns - Assertion framework - CI/CD integration - Coverage reports **Example Test:** ```typescript describe('database-verification', () => { it('triggers on Prisma imports', () => { const result = testSkill({ prompt: "add user tracking", file: "services/user.ts", content: "import { PrismaService } from './prisma'" }); expect(result.triggered).toBe(true); expect(result.skill).toBe('database-verification'); }); }); ``` **Benefits:** - Prevent regressions - Validate patterns before deployment - Confidence in changes --- ## Related Files - [SKILL.md](SKILL.md) - Main skill guide - [TROUBLESHOOTING.md](TROUBLESHOOTING.md) - Current debugging guide - [HOOK_MECHANISMS.md](HOOK_MECHANISMS.md) - How hooks work today # Hook Mechanisms -