원클릭으로 Manus에서 모든 스킬 실행

general

스타76

포크23

업데이트2026년 5월 12일 19:53

Strong activation entry for AlgoKiller general trace-analysis mode. Bind an ARM64 trace, force-load the trace-analysis methodology, and answer field semantics / execution flow / detection-point / data-flow questions.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

icloudza

icloudza/algokiller-plugin

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

관련 직업SOC

SOC 직업 분류 기준

기타 컴퓨터 관련 직업컴퓨터 및 수학직·SOC 15-1299

SKILL.md

readonly

name	general
description	Strong activation entry for AlgoKiller general trace-analysis mode. Bind an ARM64 trace, force-load the trace-analysis methodology, and answer field semantics / execution flow / detection-point / data-flow questions.
argument-hint	<absolute_trace_path> <task description>
disable-model-invocation	true

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):

Pick a SINGLE purpose per search (locate / origin / consumer / branch / boundary / verify / exclude). Do not reuse one result for multiple roles.
Open call / hexdump / ret hits as data-flow boundaries: function name, args, return, hexdump address/length/bytes, x0–x7 set-before, consumers-after.
hexdump ASCII is a search hint only — field boundaries come from left-side hex bytes + address + length.
Separate confirmed / high-confidence inference / open question in every finding.
Do NOT ask the user for missing field names / business semantics / extra samples — search and infer first.
Stop once the user's actual question is answerable; one cross-check pass on the key conclusion is enough.
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

이 저장소의 다른 Skills

같은 저장소

ciphertext-recovery

icloudza/algokiller-plugin

ARM64 trace 密文还原方法论。当用户给出一段 ARM64 执行 trace 文件并要求从某段密文/header/token/加密结果反向还原加密、签名或编码算法时使用。提供候选算法穷举、key schedule 提取、轮函数提取、魔改检测、表查找证据、闭环验证的完整方法论。激活此 skill 前应已通过 ak MCP 的 bind_trace 工具绑定 trace 文件并选择 mode=ciphertext。

2026-05-1476

trace-analysis

icloudza/algokiller-plugin

ARM64 trace 通用证据分析方法论。当用户给出一段 ARM64 执行 trace 文件并询问字段含义、执行流、检测点、数据来源、call 边界、buffer 生命周期等开放问题（不属于纯密文还原）时使用。提供搜索键选择、单一目的搜索纪律、call 边界解析、字段语义分层、执行流抽取与检测点分析的完整方法论。激活此 skill 前应已通过 ak MCP 的 bind_trace 工具绑定 trace 文件并选择 mode=general。

2026-05-1476

ciphertext

icloudza/algokiller-plugin

Strong activation entry for AlgoKiller ciphertext-recovery mode. Bind an ARM64 trace, force-load the ciphertext-recovery methodology, and start cipher / algorithm recovery from a target ciphertext.

2026-05-1276

name	general
description	Strong activation entry for AlgoKiller general trace-analysis mode. Bind an ARM64 trace, force-load the trace-analysis methodology, and answer field semantics / execution flow / detection-point / data-flow questions.
argument-hint	<absolute_trace_path> <task description>
disable-model-invocation	true

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):

Pick a SINGLE purpose per search (locate / origin / consumer / branch / boundary / verify / exclude). Do not reuse one result for multiple roles.
Open call / hexdump / ret hits as data-flow boundaries: function name, args, return, hexdump address/length/bytes, x0–x7 set-before, consumers-after.
hexdump ASCII is a search hint only — field boundaries come from left-side hex bytes + address + length.
Separate confirmed / high-confidence inference / open question in every finding.
Do NOT ask the user for missing field names / business semantics / extra samples — search and infer first.
Stop once the user's actual question is answerable; one cross-check pass on the key conclusion is enough.
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