security-benchmark-runner
Security Benchmark Runner - Auto-activating skill for Security Advanced. Triggers on: security benchmark runner, security benchmark runner Part of the Security Advanced skill category.
33
0%
Does it follow best practices?
Impact
94%
1.02xAverage 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/security-benchmark-runner/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 what the skill does or when it should be used. It lacks concrete actions, natural trigger terms, explicit usage guidance, and any distinguishing details that would help Claude select it appropriately from a list of skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Runs CIS benchmarks against system configurations, evaluates security compliance posture, generates remediation reports.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about security benchmarks, compliance scanning, CIS hardening checks, vulnerability assessments, or security posture evaluation.'
Remove the redundant duplicate trigger term ('security benchmark runner' listed twice) and replace with varied natural language terms users would actually say, such as 'security scan', 'compliance check', 'hardening audit', 'benchmark test'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only states it is a 'Security Benchmark Runner' without describing what it actually does—no verbs like 'scans', 'evaluates', 'reports', or any specific capabilities are mentioned. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no 'Use when...' clause, and the description only restates the skill name and category without explaining functionality or trigger conditions. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'security benchmark runner' repeated twice, which is the skill's own name rather than natural keywords a user would say. Missing terms like 'vulnerability scan', 'security audit', 'compliance check', 'CIS benchmark', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic within the security domain. 'Security Benchmark Runner' could overlap with any security-related skill, and the lack of specific actions or scope makes it indistinguishable from other security tools. | 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 a hollow template with no actual content. It repeatedly references 'security benchmark runner' without ever defining what a security benchmark runner is, how to use one, or providing any executable guidance. It fails on every dimension because it contains no actionable information whatsoever.
Suggestions
Add concrete, executable examples of running security benchmarks (e.g., specific commands for tools like CIS-CAT, OpenSCAP, or Lynis with expected output formats)
Define a clear workflow with steps: select benchmark profile → configure target → run scan → validate results → generate report, with validation checkpoints at each stage
Remove all meta-description sections ('When to Use', 'Capabilities', 'Example Triggers') and replace with actual technical content such as configuration templates, CLI commands, and output parsing instructions
Add references to specific benchmark frameworks (CIS, NIST, DISA STIGs) with links to detailed guides for each if needed
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It repeats 'security benchmark runner' numerous times without providing any actual instructions, commands, or technical content. Every section describes what the skill could do rather than doing it. | 1 / 3 |
Actionability | There is zero concrete, executable guidance. No code, no commands, no specific steps, no configurations. The content is entirely abstract descriptions like 'Provides step-by-step guidance' without actually providing any such guidance. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequences, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | While there are section headers, the content under each is vacuous. There are no references to detailed files, no examples, and no meaningful content organization. The structure exists but serves no purpose since there's nothing of substance to organize. | 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
c8a915c
- 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.