CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

secret-scan

Find leaked API keys, tokens and passwords in files, commits, history or pasted text, and stop your coding agent from writing or committing them. Use when: Check a repository and its full git history before making it public; Block commits that contain API keys with a pre-commit hook; Stop Claude Code from hardcoding a key or committing one.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/nex-dev-essentials/skills/secret-scan/SKILL.md

The canonical home for this skill is secret-scan in NexaiGuy/nex-ai-skills

SKILL.md
Quality
Evals
Security

Quality

Content

62%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well organized with an exemplary validated remediation workflow and concrete commands, but as a standalone skill bundle it is incomplete: the scanner script and the referenced references/remediation.md are missing, and promotional/duplicated material inflates the token cost. Fixing the dangling reference and trimming the marketing content would raise both actionability and conciseness.

Suggestions

Bundle the actual secret_scan.py script (and the Claude Code hook / pre-commit templates) in scripts/ so the documented commands are executable, or inline minimal install instructions for obtaining them.

Ship references/remediation.md with the exact git filter-repo --replace-text mirror-clone commands promised in remediation step 3, or inline those commands in the Example section.

Remove the promotional duplication — the footer catalog link, the repeated 'Built by Nex AI' lines, and the FAQ question that restates Known limitations — to tighten token efficiency.

DimensionReasoningScore

Conciseness

The core material (command menu, remediation steps, limitations) is efficient and assumes competence, but there is real padding a skill should not carry: promotional lines appear three times ("Free skill by Nex AI", "Built by Nex AI, nex-ai.be", the footer advertising the paid catalog), and the first FAQ answer ("Does it check whether a key is live? No...") restates the Known limitations section almost verbatim. This sits between the 3 anchor (mostly efficient, some unnecessary sections) and the 2 anchor (several padded sections), but the bulk remains useful, so 3 fits best.

3 / 5

Actionability

Concrete, copy-pasteable commands are present ("secret_scan.py --staged", "--diff origin/main", "--history", "--stdin", "install-hook", plus a specific remediation sequence with os.environ replacements), but key execution details are missing from the bundle: the skill states "Scripts, extension source, and templates from the original package are not in this folder", so secret_scan.py itself is absent, and step 3 defers the exact history-rewrite commands to "references/remediation.md", a file that does not exist in this folder. This matches the 3 anchor (some concrete guidance but incomplete, missing key details) rather than 4, whose minor gaps would not include the tool itself.

3 / 5

Workflow Clarity

The remediation workflow is a model of sequencing and validation: "Do this, in this order" gives five numbered steps — rotate first ("Removing them from git does not make them safe"), move values to environment, rewrite history, "**Re-scan**: secret_scan.py --history must come back clean", then install the guard hook. The re-scan requirement is an explicit validation checkpoint with an implied fix-and-retry loop for a destructive operation (history rewrite), so the destructive-operation cap does not apply and the content matches the 5 anchor.

5 / 5

Progressive Disclosure

Section structure is clear (What it does / Rules / Guard rails / When to use / Known limitations / Example / Questions) and the body stays a reasonable length, but the one reference it makes — "exact commands are in references/remediation.md" — points to a file that is not in the bundle (no references/, scripts/, or assets/ directories exist), and the referenced script is likewise absent. This lands at the 3 anchor: decent organization, but a reference that is signaled yet broken and detail that is neither inline nor available elsewhere keeps it below 4.

3 / 5

Total

14

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that explicitly states both capabilities and trigger scenarios with concrete, natural keywords and a well-differentiated niche. Its only deductions are the second-person "your coding agent" phrasing (a voice violation per the guidelines) and a handful of missing synonyms such as "secrets" and "credentials".

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Find leaked API keys, tokens and passwords in files, commits, history or pasted text", "stop your coding agent from writing or committing them", "Block commits that contain API keys with a pre-commit hook" — which alone would merit a 5 for comprehensive coverage. However, the phrase "stop your coding agent" uses second-person voice ("your"), which the judging guidelines explicitly penalize by reducing the specificity score by 1.

4 / 5

Completeness

Both halves are explicit: the "what" is stated up front ("Find leaked API keys... and stop your coding agent from writing or committing them") and the "when" is an explicit "Use when:" clause with three concrete trigger scenarios ("Check a repository and its full git history before making it public; Block commits... with a pre-commit hook; Stop Claude Code from hardcoding a key or committing one"). This matches the 5 anchor's pattern of concrete trigger phrases; a 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Natural user phrasing is well covered: "API keys", "tokens", "passwords", "leaked", "git history", "pre-commit hook", "commits", and "pasted text" are all terms a user would realistically say. It falls short of a 5 because common synonyms like "secrets", "credentials", "exposed", and ".env" are missing; it is clearly above a 3 because the included keywords go beyond domain jargon to the phrases users actually utter.

4 / 5

Distinctiveness Conflict Risk

The niche — leaked-credential scanning and prevention — is clearly staked out with distinct triggers (leaked API keys, full git history before going public, pre-commit blocking, stopping an agent from hardcoding a key) that would not naturally fire for a general code-review or linting skill. Conflict risk with adjacent skills (e.g., generic security review) is minimal, matching the 5 anchor.

5 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

NexaiGuy/nex-ai-skills

Path

plugins/nex-dev-essentials/skills/secret-scan/SKILL.md

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.