CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

memory-forensics

Master memory forensics techniques including memory acquisition, process analysis, and artifact extraction using Volatility and related tools. Use when analyzing memory dumps, investigating incidents, or performing malware analysis from RAM captures.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/reverse-engineering/skills/memory-forensics/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%Weight 40%Scale 1-5

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 largely actionable, command-first reference with a sensible split that offloads the Volatility plugin catalog to references/details.md. Its weaknesses are padded sections covering Windows internals and injection techniques Claude already knows, workflows that list steps without inline validation or decision checkpoints, and a meta-commentary placeholder where a clean reference pointer should be.

Suggestions

Remove or move the 'Data Structures' section (EPROCESS/PEB/VAD C definitions) to a reference file — it restates Windows internals Claude already knows and consumes ~50 lines of context without adding operational guidance.

Replace the 'Detailed section: Volatility 3 Framework' meta-commentary ('Originally a 2680-byte section... Codex's 8 KB skill body cap') with a clean, linked pointer such as 'See [references/details.md](references/details.md) for Volatility 3 installation, plugin reference, and Linux/macOS analysis.'

Add validation checkpoints inside the workflows, e.g., verify dump size/hash and symbol-table load before plugin runs, and define what flags a process as suspicious before step 4 ('Analyze suspicious processes') so the dump step has a decision gate.

Show the prerequisite commands instead of commenting on them — e.g., include the hivelist invocation before windows.hashdump, and name the actual tools for 'Mimikatz-style extraction' or drop the line.

DimensionReasoningScore

Conciseness

Most of the body is lean, annotated command lists, but ~70 lines restate knowledge Claude already has: the C definitions of EPROCESS/PEB/MMVAD ('Windows Process Structures', 'VAD'), a catalog of textbook injection techniques (Classic DLL Injection, Process Hollowing, APC Injection), and meta-commentary about "Codex's 8 KB skill body cap" and a "2680-byte section" that earns no tokens. This sits at anchor 3 ('mostly efficient but includes some unnecessary explanation') rather than 4, where such trimming would already be done.

3 / 5

Actionability

Nearly all Volatility/strings/YARA commands are copy-paste ready with sensible placeholders (e.g., 'vol -f memory.raw windows.malfind', 'windows.pslist --pid <PID> --dump'), and the YARA rules are valid. Minor gaps keep it from 5: 'windows.hashdump' is shown with only a comment that it "requires hivelist first" without the command, "Mimikatz-style extraction — Requires specific plugins/tools" names nothing, and the Belkasoft/Magnet entries are bare comments with no invocation.

4 / 5

Workflow Clarity

The Malware Analysis and Incident Response workflows give a clear numbered sequence with per-step purpose comments, but checkpoints are missing or implicit within the workflows themselves — there is no step to verify the dump (size/hash/symbols loaded) before analysis, no decision point for what qualifies a process as "suspicious" before dumping it, and no verify-findings loop. Verification guidance exists only outside the workflows in Best Practices ('Validate results', 'Cross-reference'), which fits anchor 3 ('sequence present but checkpoints missing or implicit') better than anchor 4 ('most checkpoints present').

3 / 5

Progressive Disclosure

The bundle structure is sound: the bulky Volatility 3 plugin reference genuinely lives in references/details.md, is one level deep, is real and well-organized, and the body points to it. Anchor 5 is blocked by the awkward pointer (the reference is announced via meta-commentary about byte caps rather than a clean 'See references/details.md' link) and by inlined content (the C data-structures section) that arguably belongs in a reference file. This places it at anchor 4 ('good structure; references mostly clear; minor organization gaps').

4 / 5

Total

14

/

20

Passed

Description

83%Weight 40%Scale 1-5

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

A strong description that pairs a concrete capability list with an explicit, well-scoped 'Use when...' trigger clause in third-person voice. It would benefit from a couple more natural trigger synonyms (e.g., 'RAM dump', 'memory image') to round out coverage.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "memory acquisition, process analysis, and artifact extraction using Volatility and related tools" — but coverage has minor gaps (e.g., credential recovery and rootkit detection covered in the body are absent), and "Master memory forensics techniques" is a slightly generic frame. This fits anchor 4 ('several specific actions; minor gaps') better than anchor 5, whose example shows a fuller, more comprehensive action list.

4 / 5

Completeness

It explicitly answers both what ("memory acquisition, process analysis, and artifact extraction using Volatility and related tools") and when ("Use when analyzing memory dumps, investigating incidents, or performing malware analysis from RAM captures") with concrete trigger phrases, mirroring the anchor-5 good example structure. Not 4, because the 'when' clause is already explicit and specific rather than merely present.

5 / 5

Trigger Term Quality

Natural terms include "memory dumps", "investigating incidents", "malware analysis", "RAM captures", and the tool name "Volatility" — good coverage a user would plausibly say. A few common variations are missing ("RAM dump", "memory capture", "memory image", ".raw/.lime/.vmem files"), so it does not reach anchor 5's comprehensive synonym/extension coverage.

4 / 5

Distinctiveness Conflict Risk

A clear niche (memory/RAM forensics with Volatility) with largely distinct triggers, but "investigating incidents" and "malware analysis" are broad enough to overlap with general incident-response or malware-analysis skills unless the RAM-capture qualifier is honored. Mostly distinct with minor overlap risk matches anchor 4 rather than anchor 5's minimal-conflict profile.

4 / 5

Total

17

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

wshobson/agents

Path

plugins/reverse-engineering/skills/memory-forensics/SKILL.md

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.