analyzing-windows-lnk-files-for-artifacts
Parse Windows LNK shortcut files to extract target paths, timestamps, volume information, and machine identifiers for forensic timeline reconstruction.
69
62%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/analyzing-windows-lnk-files-for-artifacts/SKILL.mdQuality
Discovery
82%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 is a strong, specific description that clearly identifies a narrow forensic analysis domain with concrete actions and excellent trigger terms. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know precisely when to select this skill. Adding that clause would make this description excellent.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about analyzing Windows shortcut (.lnk) files, forensic artifact extraction, or building forensic timelines from LNK metadata.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: parse LNK files, extract target paths, timestamps, volume information, machine identifiers, and forensic timeline reconstruction. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (parse LNK files, extract various metadata for forensic timeline reconstruction), but lacks an explicit 'Use when...' clause specifying when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords a forensic analyst would use: 'Windows LNK', 'shortcut files', 'target paths', 'timestamps', 'volume information', 'machine identifiers', 'forensic timeline reconstruction'. These are terms users in this domain would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche targeting Windows LNK shortcut file forensics specifically. Very unlikely to conflict with other skills given the narrow domain of LNK parsing and forensic timeline reconstruction. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill excels at actionability with complete, executable code examples for LNK file forensic analysis. However, it is significantly over-engineered for a SKILL.md file — it's a monolithic document that includes extensive reference material (concept tables, tool lists, narrative scenarios) that should either be in separate files or removed entirely. The lack of validation checkpoints in a forensic workflow and the absence of progressive disclosure significantly weaken the overall quality.
Suggestions
Cut the Key Concepts table, Tools & Systems table, and Common Scenarios section — move them to separate reference files (e.g., REFERENCE.md, SCENARIOS.md) and link from the main skill, or remove entirely since Claude knows these concepts.
Add validation checkpoints: verify LNK files were collected (check count/hashes), verify CSV output was written correctly, and validate parsed data before analysis.
Remove redundancy between Step 2 (LECmd) and Step 3 (Python) — pick one as the primary approach and reference the other as an alternative, or clearly indicate when to use which.
Trim the Prerequisites and When to Use sections to 2-3 bullet points each — Claude doesn't need five bullets explaining when LNK analysis is relevant.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~250+ lines. It includes extensive prerequisite lists, a large key concepts table explaining things Claude already knows (what a .lnk file is, what Jump Lists are), a full tools table with obvious descriptions, four detailed scenario descriptions that are purely narrative without actionable steps, and an output format section that's a lengthy example. Much of this could be cut in half or more. | 1 / 3 |
Actionability | The skill provides fully executable bash commands and Python scripts that are copy-paste ready. The LECmd commands, the LnkParse3 Python script, and the analysis scripts are all concrete and complete with specific file paths, proper imports, and real output handling. | 3 / 3 |
Workflow Clarity | The four steps are clearly sequenced (collect → parse with LECmd → parse with Python → analyze), but there are no validation checkpoints. No step verifies that LNK files were successfully collected, that parsing produced valid output, or that the CSV was correctly written. For forensic operations where evidence integrity matters, this is a significant gap. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of content with no references to external files. The entire Python parsing script, analysis script, key concepts table, tools table, four scenario descriptions, and output format are all inline. The scenarios and tools tables could easily be separate reference files, and the two parsing approaches (LECmd vs Python) could be split out. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- mukul975/Anthropic-Cybersecurity-Skills
- Commit
888bbe4
- 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.