Stats
Actions
Tags
From karmaiq-impact
Show all unique paths between two services in the karmaIQ graph. Manual slash invocation for understanding connectivity, finding hidden coupling, or planning a service rewire.
How this skill is triggered — by the user, by Claude, or both
Slash command
/karmaiq-impact:path <from-service> <to-service><from-service> <to-service>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
`$ARGUMENTS` should be `<from-service> <to-service>`. If only one token, ask for the missing one.
$ARGUMENTS$ARGUMENTS should be <from-service> <to-service>. If only one token, ask for the missing one.
${CLAUDE_PLUGIN_DATA}/../karmaiq-core/domain.txt. If unset → stop.search_catalog(catalog="graph", query="<from>") → from_id.search_catalog(catalog="graph", query="<to>") → to_id.find_path(strategy="shortest", from_id="<resolved>", to_id="<resolved>", max_paths=5).find_path(strategy="critical", from_id=..., to_id=..., metric="latency") if the user mentioned slowness, or metric="qpm" if they mentioned traffic.End with: "Want the critical path by latency? Re-run with metric=latency. Want the hottest-traffic path? metric=qpm."
npx claudepluginhub codekarma-tech-public/codekarma-mcp-plugin --plugin karmaiq-impactCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.