vulnerability-report-generator
Vulnerability Report Generator - Auto-activating skill for Security Advanced. Triggers on: vulnerability report generator, vulnerability report generator Part of the Security Advanced skill category.
34
0%
Does it follow best practices?
Impact
100%
1.01xAverage 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/vulnerability-report-generator/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 that restates the skill name without providing any meaningful information about capabilities, use cases, or trigger conditions. It lacks concrete actions, natural trigger terms, explicit 'when to use' guidance, and distinctiveness from other security-related skills. It scores at the lowest level across all dimensions.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates structured vulnerability reports from scan results, including severity ratings, CVSS scores, remediation recommendations, and executive summaries.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a vulnerability report, security assessment, CVE summary, pentest findings document, or needs to format scan output into a professional report.'
Remove the redundant duplicate trigger term and replace with diverse natural language variations users would actually say, such as 'security report', 'vuln report', 'penetration test report', 'security findings', 'CVE documentation'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the skill ('Vulnerability Report Generator') but provides no concrete actions. There is no mention of what the skill actually does—no specific capabilities like scanning, analyzing, formatting reports, or any other actionable detail. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond restating the skill name, and the 'when' clause is just a redundant repetition of the skill name rather than meaningful trigger guidance. There is no explicit 'Use when...' clause with real context. | 1 / 3 |
Trigger Term Quality | The only trigger term listed is 'vulnerability report generator' repeated twice. It lacks natural variations users might say such as 'security scan', 'CVE report', 'vulnerability assessment', 'security audit', 'pentest report', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic within the security domain. 'Security Advanced skill category' and 'vulnerability report generator' provide minimal differentiation from other security-related skills. It would easily conflict with any other security reporting or vulnerability analysis skill. | 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 substantive content. It consists entirely of auto-generated boilerplate that repeats the skill name without providing any actual instructions, code, templates, or guidance for generating vulnerability reports. It fails on every dimension of the rubric.
Suggestions
Add a concrete vulnerability report template with sections (Executive Summary, Findings, Risk Ratings, Remediation) and example content for each section.
Include executable code or commands for common vulnerability scanning tools (e.g., nmap, nikto, OWASP ZAP) with examples of how to parse their output into report format.
Define a clear workflow: 1) Scan/enumerate → 2) Classify findings by severity (CVSS) → 3) Generate report → 4) Validate completeness, with explicit validation checkpoints.
Remove all boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill meta-information rather than providing actionable instructions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats the phrase 'vulnerability report generator' excessively, and provides zero substantive information about how to actually generate vulnerability reports. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no code, no commands, no templates, no report structure, no examples of vulnerability report output. Every section is vague and abstract, describing what the skill supposedly does rather than instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps. There are no sequences, no validation checkpoints, and no process for generating a vulnerability report. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of placeholder text with no meaningful structure. There are no references to detailed materials, no linked resources, and the section headers contain only generic boilerplate rather than organized, navigable content. | 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
3076d78
- 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.