/ Verzeichnis / Playground / rootnode-skills
● Community drayline ⚡ Sofort

rootnode-skills

von 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).

Warum nutzen

Hauptfunktionen

Live-Demo

In der Praxis

rootnode-skill.replay ▶ bereit
0/0

Installation

Repository des Autors · Offizielle Dokumentation zu Claude Skills

Anwendungsfälle

Praxisnahe Nutzung: rootnode-skills

Diagnose why a Claude Project stopped following instructions

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

Wann einsetzen: Your Project worked, you added stuff, now it ignores key rules.

Ablauf
  1. Run the project audit
    Use rootnode-project-audit on my Project system prompt + instructions.✓ Kopiert
    → 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?✓ Kopiert
    → Named patterns (e.g. 'conflicting directives', 'buried critical instruction')
  3. Rebalance memory
    Apply rootnode-memory-optimization — where should each rule actually live?✓ Kopiert
    → Recommendation on what belongs in system prompt vs project docs vs user memory

Ergebnis: A diagnosed Project with a concrete fix list.

Fallstricke
  • 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

Wann einsetzen: You have goals, constraints, and examples — but not yet a prompt.

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

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

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

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.✓ Kopiert
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.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

WerkzeugEingabenWann aufrufenKosten
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

Kosten & Limits

Was der Betrieb kostet

API-Kontingent
None
Tokens pro Aufruf
Audits read whole prompts — can be large
Kosten in €
Free — skills are local files
Tipp
Run audit once per major revision, not per-message.

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: No credentials — pure prompts
Datenabfluss: None

Fehlerbehebung

Häufige Fehler und Lösungen

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.

Alternativen

rootnode-skills vs. andere

AlternativeWann stattdessenKompromiss
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

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen