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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill forensics-data-collectorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely lacking in all key areas. It provides no information about what the skill actually does, contains no natural trigger terms users would say, and reads more like auto-generated metadata than a useful skill description. The only slight positive is that 'forensics' provides some domain specificity.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Collects memory dumps, disk images, network logs, and system artifacts for security incident investigation.'
Include a 'Use when...' clause with natural trigger terms like 'incident response', 'collect evidence', 'security breach', 'malware analysis', 'memory forensics'.
Remove the redundant trigger term and replace with varied natural language users would actually say when needing forensic data collection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Forensics Data Collector' is just a name, and 'Auto-activating skill for Security Advanced' describes metadata, not capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no actions described) and 'when should Claude use it' (no explicit use-case guidance beyond the skill name as a trigger). | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'forensics data collector' repeated twice. This is the skill name itself, not natural user language. Missing terms like 'collect evidence', 'incident response', 'memory dump', 'disk image', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'forensics data collector' is somewhat specific to a security/forensics domain, which provides some distinctiveness. However, without describing actual capabilities, it could still conflict with other security-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially an empty placeholder with no actual content. It describes what a forensics data collector skill might do but provides absolutely no actionable guidance, code, commands, or specific techniques. For a security-critical domain like digital forensics, this complete lack of substance is particularly problematic.
Suggestions
Add concrete forensics data collection procedures with specific commands (e.g., memory acquisition with tools like volatility, disk imaging with dd/dcfldd, network capture with tcpdump)
Include a clear workflow with validation checkpoints for evidence integrity (hash verification, chain of custody documentation, write-blocking procedures)
Provide executable code examples for common forensics tasks like log collection, artifact extraction, and timeline generation
Reference detailed guides for specific forensics scenarios (incident response, malware analysis, network forensics) with clear navigation structure
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actionable information. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific steps, no actual forensics data collection techniques. The entire skill describes what it claims to do rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined whatsoever. For a forensics data collection skill, there should be clear steps for evidence preservation, chain of custody, data acquisition methods, and validation - none of which are present. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, no links to specific techniques, tools, or examples that would be essential for forensics work. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
- 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.