rootnode-skills MCP — 사용 사례, 설치 & 라이브 데모

왜 쓰나요

핵심 기능

Four-stage prompt compilation (Parse / Select / Construct / Validate)
Six-dimension Project audit with action plans
Detects seven structural anti-patterns that make Claude ignore instructions
Context budget analysis with per-file evaluation
Behavioral tuning against eight documented Claude tendencies

라이브 데모

실제 사용 모습

rootnode-skill.replay ▶ 준비됨

0/0

설치

클라이언트 선택

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "rootnode-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/drayline/rootnode-skills",
        "~/.claude/skills/rootnode-skills"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop → Settings → Developer → Edit Config 열기. 저장 후 앱 재시작.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "rootnode-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/drayline/rootnode-skills",
        "~/.claude/skills/rootnode-skills"
      ],
      "_inferred": true
    }
  }
}

Cursor는 Claude Desktop과 동일한 mcpServers 스키마 사용. 프로젝트 설정이 전역보다 우선.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "rootnode-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/drayline/rootnode-skills",
        "~/.claude/skills/rootnode-skills"
      ],
      "_inferred": true
    }
  }
}

Cline 사이드바의 MCP Servers 아이콘 클릭 후 "Edit Configuration" 선택.

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "rootnode-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/drayline/rootnode-skills",
        "~/.claude/skills/rootnode-skills"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop과 같은 형식. Windsurf 재시작 후 적용.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "rootnode-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/drayline/rootnode-skills",
        "~/.claude/skills/rootnode-skills"
      ]
    }
  ]
}

Continue는 맵이 아닌 서버 오브젝트 배열 사용.

~/.config/zed/settings.json

{
  "context_servers": {
    "rootnode-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/drayline/rootnode-skills",
          "~/.claude/skills/rootnode-skills"
        ]
      }
    }
  }
}

context_servers에 추가. 저장 시 Zed가 핫 리로드.

claude mcp add rootnode-skill -- git clone https://github.com/drayline/rootnode-skills ~/.claude/skills/rootnode-skills

한 줄 명령. claude mcp list로 확인, claude mcp remove로 제거.

사용 사례

실전 활용법: rootnode-skills

Diagnose why a Claude Project stopped following instructions

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

언제 쓸까: Your Project worked, you added stuff, now it ignores key rules.

사전 조건

Skill cloned — git clone https://github.com/drayline/rootnode-skills ~/.claude/skills/rootnode-skills

흐름

Run the project audit

Use rootnode-project-audit on my Project system prompt + instructions.✓ 복사됨

→ Six-dimension scorecard with specific failures called out
Check for anti-patterns

Now rootnode-anti-pattern-detection — which of the 7 patterns do I have?✓ 복사됨

→ Named patterns (e.g. 'conflicting directives', 'buried critical instruction')
Rebalance memory

Apply rootnode-memory-optimization — where should each rule actually live?✓ 복사됨

→ Recommendation on what belongs in system prompt vs project docs vs user memory

결과: A diagnosed Project with a concrete fix list.

함정

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

언제 쓸까: You have goals, constraints, and examples — but not yet a prompt.

흐름

Run prompt-compilation

rootnode-prompt-compilation — here's my intent, constraints, and 3 examples. Parse / Select / Construct / Validate.✓ 복사됨

→ Structured system prompt following the four stages
Validate

Now rootnode-prompt-validation — score it across the six dimensions.✓ 복사됨

→ Scorecard with specific weaknesses
Apply behavioral tuning

rootnode-behavioral-tuning — which of my instructions will Claude drift from?✓ 복사됨

→ Countermeasures inserted at the right places

결과: A well-engineered Project prompt on day one.

조합

다른 MCP와 조합해 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.✓ 복사됨

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.✓ 복사됨

도구

이 MCP가 노출하는 것

도구	입력	언제 호출
rootnode-prompt-compilation	intent + constraints + examples	Starting a new Project or major rewrite
rootnode-project-audit	existing Project prompt	Project behavior degraded
rootnode-anti-pattern-detection	prompt/instructions	When Claude ignores rules
rootnode-memory-optimization	all prompt + project files	Information is in the wrong place
rootnode-context-budget	project files list	Hitting context limits
rootnode-behavioral-tuning	instructions	You need reliable adherence

비용 및 제한

운영 비용

API 쿼터: None
호출당 토큰: Audits read whole prompts — can be large
금액: Free — skills are local files
팁: Run audit once per major revision, not per-message.

보안

권한, 시크릿, 파급범위

자격 증명 저장: No credentials — pure prompts

데이터 외부 송신: None

문제 해결

자주 발생하는 오류와 해결

Skill not invoked — Claude gives generic prompt advice instead of using the audit

Reference the specific sub-skill by name: 'rootnode-project-audit'.

확인: ls ~/.claude/skills/rootnode-skills/

SKILL.md frontmatter wrong in a sub-skill

Each sub-skill has its own SKILL.md — inspect the folder.

확인: head ~/.claude/skills/rootnode-skills/rootnode-project-audit/SKILL.md

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.

대안

rootnode-skills 다른 것과 비교

대안	언제 쓰나	단점/장점
skills-skill-8 (huangwb8)	You want skill-authoring tooling rather than Project-level engineering	Different layer — skill vs Project
Raw prompt iteration	Small Projects that don't need formal engineering	Lower overhead, higher drift risk

rootnode-skills