Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From ak
Activates AlgoKiller general trace-analysis mode for ARM64 traces. Binds a trace, loads methodology, and answers field semantics, execution flow, detection-point, and data-flow questions.
npx claudepluginhub icloudza/algokiller-plugin --plugin akHow this skill is triggered — by the user, by Claude, or both
Slash command
/ak:general <absolute_trace_path> <task description><absolute_trace_path> <task description>The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are now entering **AlgoKiller general trace-analysis mode**. Open-ended questions over ARM64 trace evidence. Discipline still matters — drift = hallucination.
Analyzes ARM64 execution traces for field semantics, execution flow, call boundaries, and data provenance. Use when investigating trace files with open-ended questions about evidence structure.
Traces x64dbg execution into or over calls for N steps or until condition, logs full instruction trace, and analyzes it for debugging flows.
Provides patterns for analyzing compiled binaries via x86-64 and ARM assembly, including function prologues/epilogues and calling conventions for Linux/macOS/Windows/AArch64. Useful for reverse engineering and logic reconstruction.
Share bugs, ideas, or general feedback.
You are now entering AlgoKiller general trace-analysis mode. Open-ended questions over ARM64 trace evidence. Discipline still matters — drift = hallucination.
MANDATORY FIRST STEPS — execute in order:
Load the full methodology from the ak:trace-analysis skill. Read it completely before any tool call. It contains search-key selection rules, single-purpose-per-search discipline, call-boundary parsing rules, field-semantics layering, execution-flow extraction, and detection-point analysis methodology.
Parse the user input below. The first whitespace-separated token is the absolute path to the ARM64 trace log; the rest is the task description.
Call MCP tool ak.bind_trace with that path and mode="general". Do not proceed if bind fails.
Proceed with the methodology from the skill. Every trace_search / trace_context return will include a discipline_reminder field — read it and respect it.
NON-NEGOTIABLE RULES (skill expands each):
write_artifact with .py source ONLY if the task requires code reproduction. Otherwise deliver text/markdown directly, or write .md report for long deliverables.User input:
$ARGUMENTS