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 extremely weak across all dimensions. It reads as auto-generated boilerplate with no actual content describing capabilities, use cases, or meaningful trigger terms. The skill name is simply repeated as the trigger term, and there is zero information about what the skill actually does or when it should be selected.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Collects and preserves digital forensic evidence including disk images, memory dumps, network captures, and system 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 investigation, memory forensics, disk imaging, or chain of custody.'
Remove the duplicated trigger term ('forensics data collector' is listed twice) and replace with diverse, natural keywords users would actually say when needing this skill.
| 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 | The description fails to answer both 'what does this do' and 'when should Claude use it'. 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 | While 'forensics data collector' is a somewhat specific domain term, the description is so vague that it's unclear what distinguishes this from any other security-related skill. The lack of concrete actions or scope makes it impossible to differentiate from overlapping 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 essentially a placeholder or template with no substantive content. It contains no actionable forensics data collection procedures, no concrete commands or tools (e.g., dd, volatility, tcpdump, FTK), no workflow for evidence preservation or chain of custody, and no references to supporting materials. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable forensic data collection procedures—e.g., memory acquisition with `volatility`, disk imaging with `dd` or `dc3dd`, network capture with `tcpdump`, with exact command-line examples.
Define a clear multi-step workflow with validation checkpoints: identify volatile data → capture memory → image disks → collect logs → verify hashes → document chain of custody.
Remove all generic filler ('Provides step-by-step guidance', 'Follows industry best practices') and replace with actual domain-specific instructions and tool configurations.
Add references to supporting files for detailed topics like specific compliance frameworks (SOC2, GDPR evidence requirements), tool-specific guides, or evidence handling checklists.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic filler that tells Claude nothing useful. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are vague platitudes. The entire file explains what the skill is rather than providing any actual forensics data collection knowledge. | 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 the skill abstractly without instructing Claude on how to actually perform any forensics task. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. Forensic data collection is inherently a multi-step, order-sensitive process (e.g., chain of custody, volatile data first) and none of this is addressed. No validation checkpoints exist. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to supporting files, no structured sections with real content, and no navigation to deeper material. There are no bundle files to support it either. | 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
13d35b8
- 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.