secret-scanner
Secret Scanner - Auto-activating skill for Security Fundamentals. Triggers on: secret scanner, secret scanner Part of the Security Fundamentals skill category.
34
0%
Does it follow best practices?
Impact
99%
0.99xAverage 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/secret-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 label with no substantive content. It fails to describe what the secret scanner does, what types of secrets it detects, or when it should be activated. The duplicated trigger term and lack of any concrete actions or 'Use when' guidance make it ineffective for skill selection.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Scans code and configuration files for hardcoded secrets, API keys, passwords, tokens, and credentials.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about detecting leaked secrets, scanning for API keys, finding hardcoded passwords, checking for exposed credentials, or reviewing .env files.'
Remove the duplicated trigger term and expand with diverse natural keywords users would actually say, such as 'API key leak', 'credential exposure', 'secret detection', 'sensitive data in code'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions. It says 'Secret Scanner' and mentions 'Security Fundamentals' but never describes what the skill actually does — no mention of scanning, detecting, removing, or alerting on secrets/credentials/API keys. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no explanation of capabilities and no explicit 'Use when...' clause with trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'secret scanner, secret scanner' (duplicated). It lacks natural user terms like 'API key', 'credentials', 'leaked secrets', 'hardcoded passwords', 'sensitive data', '.env file', etc. | 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 label, and without specific actions or triggers, it provides no clear niche. | 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 boilerplate meta-descriptions about what the skill would do, without providing any actual instructions, code, patterns, or actionable guidance for secret scanning. It fails on every dimension of the rubric.
Suggestions
Replace the meta-description sections with actual secret scanning content: regex patterns for common secrets (API keys, tokens, passwords), tool configurations (e.g., truffleHog, git-secrets, gitleaks), and executable code examples.
Add a concrete workflow: e.g., 1) scan repository with specific command, 2) review findings, 3) rotate compromised secrets, 4) add pre-commit hooks to prevent future leaks.
Remove all 'When to Use' and 'Example Triggers' boilerplate—these waste tokens and describe skill activation metadata that belongs in frontmatter, not the body.
Include specific examples of secret patterns to detect (e.g., AWS keys matching AKIA*, GitHub tokens matching ghp_*, JWT patterns) with sample detection code or tool commands.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual actionable content. Every section describes rather than instructs, wasting tokens on boilerplate like 'This skill provides automated assistance' and 'Follows industry best practices.' | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific patterns for detecting secrets, no regex examples, no tool configurations. The entire skill is vague meta-commentary ('Provides step-by-step guidance') without any actual steps or executable content. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill merely claims it provides 'step-by-step guidance' without actually containing any steps. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of placeholder text with no references to detailed materials, no links to related files, and no meaningful structural organization beyond generic section headers. | 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.