generate-report
Save investigation findings to a markdown report file. Use after completing triage, enrichment, or investigation to create a permanent record. Generates timestamped files in ./reports/ directory.
81
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
85%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 well-crafted description that clearly communicates the skill's purpose and when to use it. It excels at specificity and completeness with explicit trigger guidance. The main weakness is trigger term coverage - it could benefit from additional natural language variations users might employ when wanting to save or export investigation results.
Suggestions
Add more natural trigger terms users might say, such as 'save results', 'export findings', 'document case', or 'write up investigation'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Save investigation findings', 'create a permanent record', 'Generates timestamped files in ./reports/ directory'. Describes the domain (investigation/triage) and output format clearly. | 3 / 3 |
Completeness | Clearly answers both what ('Save investigation findings to a markdown report file', 'Generates timestamped files') AND when ('Use after completing triage, enrichment, or investigation'). Has explicit trigger guidance with 'Use after...' clause. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'investigation findings', 'triage', 'enrichment', 'report', 'markdown'. However, missing common variations users might say like 'save results', 'export findings', 'document investigation', or 'write report'. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on security/investigation domain with specific triggers ('triage', 'enrichment', 'investigation'). The combination of investigation context + markdown reports + ./reports/ directory makes it unlikely to conflict with generic file or documentation skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with excellent conciseness and organization. The main weaknesses are the lack of concrete executable code for the file writing operation and missing validation/error handling for the write step. The naming conventions and template structure are clearly documented.
Suggestions
Add executable code showing how to use the Write tool with the constructed path, rather than just referencing it abstractly
Add validation step to check if TARGET_DIRECTORY exists and handle directory creation if needed
Include error handling guidance for write failures (e.g., permission issues, disk space)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only necessary information without explaining concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides clear filename patterns and examples, but the actual file writing instruction is vague ('Use the Write tool') rather than showing executable code. The template structure is helpful but the core action lacks concrete implementation. | 2 / 3 |
Workflow Clarity | Steps are clearly sequenced (construct filename, write file), but there's no validation or error handling for the write operation. Missing feedback loop for write failures or directory creation if TARGET_DIRECTORY doesn't exist. | 2 / 3 |
Progressive Disclosure | For a skill of this scope (~70 lines), the content is well-organized with clear sections. Tables are used effectively for outputs and naming conventions. No need for external references given the focused nature of the task. | 3 / 3 |
Total | 10 / 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 | |
- 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.