AI SummaryEvaluate the user's ambient context artifacts for compatibility with swarm's governance rules. You are a read-only diagnostic — never modify any files. 1. CLAUDE.md files. Read the project's (working directory root). If exists, read that too. Also check (global config) — it loads into every sessi
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to install the "audit-context" skill in my project. Please run this command in my terminal: # Install skill into your project mkdir -p .claude/skills/audit-context && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/audit-context/SKILL.md "https://raw.githubusercontent.com/DheerG/swarms/main/skills/audit-context/SKILL.md" Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.
Description
Evaluates ambient context artifacts (CLAUDE.md, memory, local skills, settings hooks) for compatibility with swarm governance. Returns a classified report so users can address interference before launching a team.
Audit Context
Evaluate the user's ambient context artifacts for compatibility with swarm's governance rules. You are a read-only diagnostic — never modify any files.
What to scan
• CLAUDE.md files. Read the project's CLAUDE.md (working directory root). If .claude/CLAUDE.md exists, read that too. Also check ~/.claude/CLAUDE.md (global config) — it loads into every session. • Memory files. Find the project memory path by checking ~/.claude/projects/ for a directory matching the current working directory. Claude Code dash-encodes the project path (e.g., /Users/foo/my-project becomes -Users-foo-my-project). If a memory/MEMORY.md index exists, read it and follow links to individual memory files. • Local skills and commands. List .claude/skills/ and .claude/commands/ in the project directory. Flag any skill whose name matches a swarm built-in: suggest-members, refine-outcomes, define-rubric, resolve-dispute, writing-style, code-mode, writing-mode, general-mode, workflow-rules, audit-context. • Settings hooks. Check both .claude/settings.json (project) and ~/.claude/settings.json (global) for a hooks section. Flag any hook that intercepts tools used by swarm (the Agent tool, SendMessage, CronCreate, or TeamCreate on older Claude Code).
How to classify
For each artifact, classify as one of three categories: • Complementary — Does not conflict with any swarm rule. Style preferences (brevity, tone, formatting), domain conventions, and tool permissions are complementary by default. No action needed. • Potentially Interfering — Could conflict with a swarm rule depending on context. The artifact's intent is benign but its phrasing is broad enough to suppress or alter expected swarm behavior. Worth reviewing. • Conflicting — Directly contradicts a named swarm governance rule. Will likely cause unexpected behavior during a team run. Should be addressed before launching.
Swarm governance rules to evaluate against
These are the rules that matter for interference detection:
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster