From karmaiq-architect
Top CPU-consuming methods in a karmaIQ service. Manual slash invocation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/karmaiq-architect:hot <service-name><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
1. Read active domain from `${CLAUDE_PLUGIN_DATA}/../karmaiq-core/domain.txt`. If unset → stop.
$ARGUMENTS${CLAUDE_PLUGIN_DATA}/../karmaiq-core/domain.txt. If unset → stop.analyze_codebase_methods(service_name="$ARGUMENTS", strategy="hot", top_k=20, cpu_threshold=1.0, domain="<active>").## Hot methods in <service>
| method (Class.method) | CPU % | calls/min | category |
|---|---|---|---|
<top 20, ordered by CPU>
End with: "For deeper analysis of any flow these methods participate in, look up the method's flow via mcp__karma-iq__search_catalog(catalog="method", query="<method>", service_name="$ARGUMENTS") and run mcp__karma-iq__analyze_flow on the returned flow_id."
If the service is not instrumented at method level, say so explicitly — do not report "no hot methods".
npx claudepluginhub codekarma-tech-public/codekarma-mcp-plugin --plugin karmaiq-architectCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.