From karmaiq-firefighter
Walk upstream root-cause candidates for a specific karmaIQ interface ID or service. Manual slash invocation when the user already has a resolved interface_id or knows the target service. Ranks predecessors by error rate over the active time window.
How this skill is triggered — by the user, by Claude, or both
Slash command
/karmaiq-firefighter:rca <interface-id-or-service-name><interface-id-or-service-name>This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Walk upstream from `$ARGUMENTS`, ranking predecessors by error rate.
Walk upstream from $ARGUMENTS, ranking predecessors by error rate.
$ARGUMENTS does not contain :: (so it's likely a service or API name, not a full node_id), call search_catalog(catalog="graph", query="$ARGUMENTS") to resolve. Take the top match if unambiguous; otherwise list options and ask the user.get_time_intervals(duration_minutes=720, num_windows=1).${CLAUDE_PLUGIN_DATA}/../karmaiq-core/domain.txt.root_cause_candidates(node_id="<resolved>", metric="errors", depth=3, top_k=10, epochStartTime=..., epochEndTime=..., domain="<active>").get_api_deep_dive on the worst candidate)karmaiq-firefighter:fire <candidate> for a deeper end-to-end runIf $ARGUMENTS contains a route path, preserve it byte-for-byte — never rewrite ([^/]+) to {id}.
npx claudepluginhub codekarma-tech-public/codekarma-mcp-plugin --plugin karmaiq-firefighterProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.