CtrlK
BlogDocsLog inGet started
Tessl Logo

pwn-chain

从逆向走到可用利用 (Working Exploit) 的全链路工程化方法。 适用场景:拿到了二进制 + 漏洞点 + 目标环境,需要写出一个能稳定打通的 exploit(不是只能本地复现一下、远程一打就崩的脚本)。 覆盖三大方向:栈溢出 / 堆利用 / 内核 pwn。强调"CTF 本地通 → 真实远程稳定打通"的工程差距:libc 版本错配、堆喷射时序、SMEP/SMAP/KASLR、栈对齐、远程缓冲。 核心工具链:pwntools + GEF/pwndbg + ROPgadget/Ropper + one_gadget + libc-database + qemu-system 内核调试。 触发关键词:pwn、栈溢出、堆溢出、ROP、ret2libc、ret2csu、one_gadget、libc-database、堆利用、tcache、fastbin、unsorted bin、kernel pwn、kROP、SMEP、SMAP、KASLR、modprobe_path、pwntools、GEF、pwndbg。

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a dense, actionable reference with a clear sequenced workflow, explicit validation checkpoints, and well-organized one-level-deep references to files that exist. Its main weakness is moderate redundancy between the caveats and routing sections.

Suggestions

Deduplicate caveats: the '注意事项' section re-states 栈对齐 and libc 版本 points already covered in Step 6 — fold only the unique items (glibc version sensitivity, KASLR leak once) into the workflow steps and drop the repeats.

Consolidate routing: '与其他 skill 的分工' and '路由上下文' list overlapping upstream/downstream skills — merge them into a single routing block.

Pick one navigation pattern: '子模块导航' re-links stack-pwn.md and kernel-pwn.md already linked inline in the scenarios — keep '子模块导航' as the single index and drop the inline '完整模板参见' lines (or vice versa).

DimensionReasoningScore

Conciseness

Mostly dense and assumes competence (no beginner explanations of ROP/movaps/tcache), but the '注意事项' section re-states caveats already in Step 6 ('栈对齐', 'libc 版本必须确认') and the '与其他 skill 的分工' table overlaps the '路由上下文' routing block, so not every token earns its place. Not a 1 because the bulk is lean and technical, not padded with concepts Claude already knows.

2 / 3

Actionability

Provides concrete executable commands ('checksec ./vuln', "libc-database ./find puts 0x6f0", 'ROPgadget --binary … --only "pop|ret"', 'one_gadget ./libc.so.6'), a copy-paste bootstrap bash script, and pwntools template snippets whose '…' placeholders are justified by deferral to references/.

3 / 3

Workflow Clarity

Six-step sequence with explicit validation checkpoints ('验证成功率 ≥ 95%', a 4-item completion self-check) and feedback loops (auto-install fail 2× → output manual steps; local pass → remote stabilize). The remote/batch operations do have validation, so it is not capped at 2.

3 / 3

Progressive Disclosure

The overview in SKILL.md defers full templates to one-level-deep references (stack-pwn.md, heap-pwn.md, kernel-pwn.md), all of which exist, with clear navigation via inline '完整模板参见 references/…' pointers plus a '子模块导航' index section.

3 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, complete, and distinctive: it states what the skill does, when to use it, lists natural trigger keywords, and carves out a clear non-overlapping niche, all in third person with no vague fluff or over-claims.

DimensionReasoningScore

Specificity

Names concrete actions and concerns rather than vague language — '需要写出一个能稳定打通的 exploit' plus the engineering gaps 'libc 版本错配、堆喷射时序、SMEP/SMAP/KASLR、栈对齐、远程缓冲' across three directions (栈溢出/堆利用/内核 pwn) and a concrete tool chain. It is comprehensive and specific, not a 2, because it lists multiple concrete items rather than just naming the domain.

3 / 3

Completeness

Clearly answers both 'what' ('从逆向走到可用利用 (Working Exploit) 的全链路工程化方法') and 'when' ('适用场景:拿到了二进制 + 漏洞点 + 目标环境,需要写出…exploit') with an explicit trigger-keyword clause, so it is not capped at 2 for a missing 'Use when…' clause.

3 / 3

Trigger Term Quality

An explicit '触发关键词' line lists natural terms a user would actually say — 'pwn、栈溢出、堆溢出、ROP、ret2libc、ret2csu、one_gadget、libc-database、tcache、fastbin、kernel pwn、modprobe_path、pwntools、pwndbg' — with broad coverage, not just a subset.

3 / 3

Distinctiveness Conflict Risk

Carves a clear non-overlapping niche — explicitly '不负责发现漏洞…只负责…从漏洞点写出 exploit' — with pwn-specific triggers unlikely to fire for reverse-engineering or attack-chain skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
zhaoxuya520/reverse-skill
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.