checking-owasp-compliance
This skill uses the owasp-compliance-checker plugin to automatically identify potential security vulnerabilities based on the OWASP Top 10 (2021) list. It helps ensure your application adheres to industry-standard security practices by providing a detailed analysis of compliance gaps and offering remediation guidance. Use this skill when you need to audit your code for OWASP compliance, identify and fix vulnerabilities, or generate a compliance report. Trigger this skill by asking to "check OWASP compliance", "scan for OWASP vulnerabilities", or using the `/owasp` shortcut.
89
53%
Does it follow best practices?
Impact
97%
1.07xAverage score across 9 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./backups/skill-structure-cleanup-20251108-073936/plugins/security/owasp-compliance-checker/skills/owasp-compliance-checker/SKILL.mdQuality
Discovery
100%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 skill description that clearly articulates what the skill does (OWASP Top 10 vulnerability identification, compliance gap analysis, remediation guidance), when to use it (auditing, fixing vulnerabilities, generating reports), and how to trigger it (specific phrases and shortcut). The only minor issue is the use of second person ('your application', 'your code'), which slightly deviates from the preferred third-person voice, but the overall quality is high.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: identify security vulnerabilities, analyze compliance gaps, provide remediation guidance, audit code, fix vulnerabilities, and generate compliance reports. These are specific and actionable. | 3 / 3 |
Completeness | Clearly answers both 'what' (identify vulnerabilities based on OWASP Top 10, analyze compliance gaps, offer remediation guidance) and 'when' ('Use this skill when you need to audit your code for OWASP compliance, identify and fix vulnerabilities, or generate a compliance report'). Explicit trigger guidance is also provided. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'check OWASP compliance', 'scan for OWASP vulnerabilities', '/owasp' shortcut, 'audit your code', 'compliance report', 'OWASP Top 10'. These cover natural user phrasings well. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: OWASP Top 10 compliance checking via a specific plugin. The domain (OWASP security compliance) and specific triggers ('/owasp', 'OWASP compliance') make it unlikely to conflict with general security or code review skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is largely descriptive rather than instructive. It explains what the skill does in abstract terms but provides no concrete commands, configuration details, sample outputs, or executable examples. The content is padded with generic advice and repeated information that Claude already knows, making it both verbose and unactionable.
Suggestions
Add concrete, executable examples showing exact plugin invocation syntax (e.g., the actual command or API call to run the owasp-compliance-checker) and sample output/report format.
Remove the 'When to Use This Skill', 'Best Practices', and 'Integration' sections entirely — they add no actionable information and repeat what's in the description or state obvious advice.
Include a real example showing a scan result with specific vulnerability findings and the exact remediation steps, so Claude knows what output to produce and how to guide the user.
Add validation/error handling steps: what to do if the plugin is not installed, if the scan fails, or if the report contains false positives.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and padded with information Claude already knows. Sections like 'When to Use This Skill' repeat the description, 'Best Practices' offers generic advice (regular scanning, stay updated), and the 'How It Works' section explains obvious plugin behavior. The 'Integration' section is vague filler. | 1 / 3 |
Actionability | There are no concrete commands, code snippets, API calls, or executable examples. The 'examples' merely describe what the skill 'will do' in abstract terms without showing actual plugin invocation syntax, configuration, command-line usage, or sample output. Nothing is copy-paste ready. | 1 / 3 |
Workflow Clarity | The workflow steps are superficial ('activate plugin', 'scan codebase', 'generate report') with no actual commands, no validation checkpoints, no error handling, and no feedback loops. There is no guidance on what to do if the scan fails or how to interpret results. | 1 / 3 |
Progressive Disclosure | The content is organized into sections with headers, which provides some structure. However, there are no references to external files, no bundle files to support deeper content, and inline content that could be trimmed doesn't justify its length. It's not a monolithic wall of text but also not well-structured for progressive disclosure. | 2 / 3 |
Total | 5 / 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
18c44a8
- 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.