CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/gitleaks-scanning

Use when a team needs open-source secret scanning on commits and in CI, or is adopting it on a repo with existing leaks: gitleaks git, dir and stdin scans, custom rules and allowlists in .gitleaks.toml, pre-commit and GitHub Action setup, baselines, and TruffleHog live verification.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

Quality

Content

92%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.

An excellent, highly operational skill body: executable commands and configs throughout, a clearly sequenced workflow with explicit validation and feedback loops, and a clean split of detail into genuinely useful one-level references. The only improvement area is trimming repeated deprecation mentions and some redundancy between the CI-hardening bullets and the anti-patterns table.

DimensionReasoningScore

Conciseness

The body is command-first and information-dense with essentially no explanation of concepts Claude already knows, but the v8.19.0 detect/protect deprecation is restated in three places (Command-API note, Step 6, Step 7) and the CI-hardening bullets slightly repeat the anti-patterns table, so it is efficient-with-minor-trimming rather than lean throughout.

4 / 5

Actionability

Nearly everything is copy-paste executable: install commands, scan invocations with report flags and --log-opts ranges, a TOML rule/allowlist template, pre-commit and GitHub Action YAML, and a runnable proof script that generates fake secrets and asserts exit code 1 — covering the common cases end to end.

5 / 5

Workflow Clarity

The 8-step sequence is numbered up front and elaborated per step, with explicit validation checkpoints ("confirm with gitleaks version", "Prove the config before trusting it... expect exit code 1", re-running the proof without the flags) and error-recovery guidance (Step 5b miss table, rotation workflow, anti-patterns with fixes).

5 / 5

Progressive Disclosure

The body keeps the operational core while deep material is split into real, well-signaled one-level-deep references (custom-rules-and-triage.md, baseline.md, trufflehog.md), each linked at the exact step where it is needed and again in a References section, making navigation easy.

5 / 5

Total

19

/

20

Passed

Description

88%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 pairs an actionable 'Use when' trigger with a comprehensive, tool-specific capability list. Its only weaknesses are a few missing natural synonyms for the trigger terms and modest overlap risk with other secret-scanning skills.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete capabilities — "gitleaks git, dir and stdin scans, custom rules and allowlists in .gitleaks.toml, pre-commit and GitHub Action setup, baselines, and TruffleHog live verification" — covering the tool's full workflow with no notable gaps, matching the comprehensive-coverage anchor.

5 / 5

Completeness

It explicitly answers both questions: "Use when a team needs open-source secret scanning on commits and in CI, or is adopting it on a repo with existing leaks" gives concrete trigger conditions, and the colon-separated list states exactly what the skill does.

5 / 5

Trigger Term Quality

Good natural keyword coverage ("secret scanning", "commits", "CI", "leaks", "pre-commit", "GitHub Action") but a few natural synonyms users might say are missing (e.g., "credentials", "API keys", "tokens", "exposed secrets"), so it falls just short of the synonym-inclusive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The gitleaks-specific commands and .gitleaks.toml pin a clear niche, and TruffleHog is explicitly positioned as a complementary verification layer; however, the broad "secret scanning" trigger terms could still overlap with closely related secret-scanning skills, matching the mostly-distinct anchor rather than minimal-conflict.

4 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

On this page