license-compliance-scanner
License Compliance Scanner - Auto-activating skill for Security Fundamentals. Triggers on: license compliance scanner, license compliance scanner Part of the Security Fundamentals skill category.
33
0%
Does it follow best practices?
Impact
96%
1.03xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/03-security-fundamentals/license-compliance-scanner/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 with no substantive content. It names the skill and its category but provides zero information about what it does, what actions it performs, or when it should be selected. It would be nearly impossible for Claude to correctly choose this skill from a pool of available skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Scans project dependencies for license compliance issues, identifies restrictive licenses (GPL, AGPL), and generates compliance reports.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about license compliance, open source licensing, dependency license checks, SPDX, or needs to audit licenses in a codebase.'
Remove the duplicate trigger term ('license compliance scanner' is listed twice) and expand with natural variations users would actually say, such as 'license audit', 'check licenses', 'OSS compliance', 'dependency licenses'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the skill ('License Compliance Scanner') but provides no concrete actions. There is no indication of what the skill actually does—no verbs like 'scans', 'detects', 'reports', or 'validates' are present. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'license compliance scanner' repeated twice. There are no natural user keywords like 'license check', 'open source licenses', 'dependency licensing', 'GPL', 'MIT', 'SPDX', or 'license audit' that a user would naturally say. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it could overlap with any security-related skill. 'Security Fundamentals' is a broad category, and without specific actions or triggers, it's indistinguishable from other security scanning or compliance skills. | 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 template/placeholder with no actual content. It repeatedly names 'license compliance scanner' without ever explaining what tools to use, how to scan dependencies, what license types to flag, or any concrete implementation details. It provides zero value beyond what the skill's title already conveys.
Suggestions
Add concrete, executable examples showing how to scan for license compliance (e.g., using tools like `license_finder`, `scancode-toolkit`, `fossa`, or `licensee` with actual CLI commands and expected output).
Define a clear workflow: 1) Scan dependencies, 2) Identify problematic licenses (list specific ones like GPL, AGPL, etc.), 3) Generate a compliance report, 4) Validate against an allow/deny list.
Remove all boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill meta-information rather than providing actionable guidance.
Include a concrete example showing input (e.g., a project with mixed licenses) and expected output (e.g., a compliance report format) so Claude knows exactly what to produce.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'license compliance scanner' excessively, and provides zero substantive information about how to actually scan for license compliance. | 1 / 3 |
Actionability | There are no concrete steps, no code, no commands, no specific tools, and no executable guidance whatsoever. Every section is vague and abstract, describing what the skill supposedly does rather than instructing how to do it. | 1 / 3 |
Workflow Clarity | There is no workflow, no sequence of steps, and no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of generic placeholder text with no references to detailed materials, no links to related files, and no meaningful structural organization beyond boilerplate headings. | 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
3e83543
- 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.