forensics-data-collector
Forensics Data Collector - Auto-activating skill for Security Advanced. Triggers on: forensics data collector, forensics data collector Part of the Security Advanced skill category.
33
0%
Does it follow best practices?
Impact
95%
1.07xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/04-security-advanced/forensics-data-collector/SKILL.mdQuality
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a placeholder with no substantive content. It fails to describe any concrete capabilities, lacks natural trigger terms users would employ, and provides no guidance on when the skill should be selected. It would be nearly impossible for Claude to correctly choose this skill from a pool of available options.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Collects forensic artifacts including memory dumps, disk images, network logs, and system event logs for incident response investigations.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user mentions forensic analysis, evidence collection, incident response, digital forensics, memory capture, disk imaging, or chain of custody.'
Remove the duplicate trigger term ('forensics data collector' is listed twice) and replace with varied natural language terms users would actually say, such as 'forensic investigation', 'collect evidence', 'security incident artifacts', 'DFIR'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only states it is a 'Forensics Data Collector' and an 'Auto-activating skill for Security Advanced' without describing what it actually does (e.g., collect logs, capture memory dumps, extract artifacts). | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no explanation of capabilities and no explicit 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('forensics data collector, forensics data collector'). There are no natural user keywords like 'incident response', 'evidence collection', 'disk image', 'memory dump', 'log collection', or 'digital forensics'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it could overlap with any security-related skill. 'Forensics Data Collector' as a label is somewhat specific, but without concrete actions or scope, it provides no clear niche to distinguish it from other security skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell with no actual content—it is entirely meta-description and boilerplate that tells Claude nothing about forensic data collection. There are no tools, commands, techniques, workflows, or examples that would enable Claude to assist with any forensics task. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable guidance: include specific forensic data collection tools (e.g., dd, dcfldd, volatility, FTK Imager) with actual command examples for disk imaging, memory acquisition, and log collection.
Define a clear multi-step workflow with validation checkpoints, e.g., 1) Identify evidence sources, 2) Create forensic image with hash verification, 3) Validate image integrity, 4) Extract artifacts, 5) Document chain of custody.
Remove all meta-description sections ('Purpose', 'When to Use', 'Example Triggers', 'Capabilities') that describe the skill rather than teaching the skill—these waste tokens and provide no actionable value.
Add references to supporting materials for advanced topics (e.g., memory forensics, network forensics, timeline analysis) using progressive disclosure with clearly signaled links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It explains what the skill does in abstract terms without providing any actual forensics data collection guidance, commands, or techniques. Every section restates the same vague concept. | 1 / 3 |
Actionability | There is zero concrete, executable guidance—no commands, no code, no specific tools, no procedures for forensic data collection. The content only describes itself rather than instructing Claude on how to perform any task. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or sequenced operations. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of boilerplate with no references to detailed materials, no links to supporting files, and no meaningful structural organization beyond generic headings. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
c8a915c
- 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.