/ Directorio / Playground / rootnode-skills
● Comunidad drayline ⚡ Instantáneo

rootnode-skills

por drayline · drayline/rootnode-skills

19 skills for diagnosing, building, and optimizing Claude Projects — prompt compilation, anti-pattern detection, context budget analysis.

drayline/rootnode-skills is a suite for engineering quality Claude Projects. Build skills (prompt-compilation, skill-builder), Diagnose skills (project-audit, global-audit, anti-pattern-detection, prompt-validation), Optimize skills (behavioral-tuning, memory-optimization, context-budget), plus 4 block libraries (identity, reasoning, output formats) and 5 domain packs (strategy, SWE, content, research, agents).

Por qué usarlo

Características clave

Demo en vivo

Cómo se ve en la práctica

rootnode-skill.replay ▶ listo
0/0

Instalación

Repositorio del autor · Documentación oficial de Skills de Claude

Casos de uso

Usos del mundo real: rootnode-skills

Diagnose why a Claude Project stopped following instructions

👤 Claude.ai power users whose Project drifted ⏱ ~45 min intermediate

Cuándo usarlo: Your Project worked, you added stuff, now it ignores key rules.

Flujo
  1. Run the project audit
    Use rootnode-project-audit on my Project system prompt + instructions.✓ Copiado
    → Six-dimension scorecard with specific failures called out
  2. Check for anti-patterns
    Now rootnode-anti-pattern-detection — which of the 7 patterns do I have?✓ Copiado
    → Named patterns (e.g. 'conflicting directives', 'buried critical instruction')
  3. Rebalance memory
    Apply rootnode-memory-optimization — where should each rule actually live?✓ Copiado
    → Recommendation on what belongs in system prompt vs project docs vs user memory

Resultado: A diagnosed Project with a concrete fix list.

Errores comunes
  • Audit report is long; you only fix the easy ones — Start with anti-patterns flagged — those block the rest

Compile a new Claude Project system prompt from scratch

👤 Anyone building a Claude Project for the first time ⏱ ~60 min intermediate

Cuándo usarlo: You have goals, constraints, and examples — but not yet a prompt.

Flujo
  1. Run prompt-compilation
    rootnode-prompt-compilation — here's my intent, constraints, and 3 examples. Parse / Select / Construct / Validate.✓ Copiado
    → Structured system prompt following the four stages
  2. Validate
    Now rootnode-prompt-validation — score it across the six dimensions.✓ Copiado
    → Scorecard with specific weaknesses
  3. Apply behavioral tuning
    rootnode-behavioral-tuning — which of my instructions will Claude drift from?✓ Copiado
    → Countermeasures inserted at the right places

Resultado: A well-engineered Project prompt on day one.

Combinaciones

Combínalo con otros MCPs para multiplicar por 10

rootnode-skill + skillcheck-free-skill

Audit your Project prompt, then validate any skills it references against spec

Run rootnode-project-audit, then SkillCheck on each referenced SKILL.md.✓ Copiado
rootnode-skill + planning-with-files

Audit produces a long fix list — track progress on it across sessions

Use planning-with-files to track the rootnode audit fix list across this week.✓ Copiado

Herramientas

Lo que expone este MCP

HerramientaEntradasCuándo llamarCoste
rootnode-prompt-compilation intent + constraints + examples Starting a new Project or major rewrite 0
rootnode-project-audit existing Project prompt Project behavior degraded 0
rootnode-anti-pattern-detection prompt/instructions When Claude ignores rules 0
rootnode-memory-optimization all prompt + project files Information is in the wrong place 0
rootnode-context-budget project files list Hitting context limits 0
rootnode-behavioral-tuning instructions You need reliable adherence 0

Coste y límites

Lo que cuesta ejecutarlo

Cuota de API
None
Tokens por llamada
Audits read whole prompts — can be large
Monetario
Free — skills are local files
Consejo
Run audit once per major revision, not per-message.

Seguridad

Permisos, secretos, alcance

Almacenamiento de credenciales: No credentials — pure prompts
Salida de datos: None

Resolución de problemas

Errores comunes y soluciones

Wrong trigger keywords — wrong sub-skill activates

Sub-skill names are specific ('project-audit' vs 'global-audit' vs 'full-stack-audit'); use the right one.

Alternativas

rootnode-skills vs otros

AlternativaCuándo usarlaContrapartida
skills-skill-8 (huangwb8)You want skill-authoring tooling rather than Project-level engineeringDifferent layer — skill vs Project
Raw prompt iterationSmall Projects that don't need formal engineeringLower overhead, higher drift risk

Más

Recursos

📖 Lee el README oficial en GitHub

🐙 Ver issues abiertas

🔍 Ver todos los 400+ servidores MCP y Skills