CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/secrets-rotation-runner

Use when a secret is found in code or history, or for scheduled rotation: identify the provider, rotate the credential through its API (AWS IAM, GitHub, Stripe, GCP, Azure, Twilio, Slack and more), revoke the old one, log the audit trail and link the post-mortem. Scrubbing git history is not enough.

Quality

85%

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

Overview
Quality
Evals
Security
Files

Quality

Content

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

A well-structured, actionable rotation runbook with concrete CLI examples, sequencing, verification steps, and an end-to-end checklist. It uniformly falls just short of excellent due to repeated framing, a couple of non-portable/placeholder commands, and no explicit failure-recovery loop.

Suggestions

State the git-history-scrub caveat once (Overview or Anti-patterns) instead of three times, and drop filler like "This is the 'test that catches the bug' pattern for security" to tighten conciseness.

Add an explicit recovery step for Step 3A: what to do when a consumer still uses the old key after the observation window (e.g., re-activate, fix consumer, re-deactivate) to close the workflow-clarity feedback loop.

Fix portability gaps in commands: replace BSD-only `date -u -v-7d` with a portable alternative (e.g., GNU/BSD-safe `date` invocation or a noted assumption), and expand the "Deploy new key to all consumers..." placeholder with at least one concrete consumer-update example (Kubernetes secret or Vault path).

DimensionReasoningScore

Conciseness

Tables and commands are tight, but the history-scrub-is-cosmetic point is repeated three times (Overview, Anti-patterns, description) and phrases like "This is the 'test that catches the bug' pattern for security" are trimmable filler.

4 / 5

Actionability

Provides concrete executable commands (aws iam create-access-key pipeline with jq, cloudtrail lookup-events, gh secret list) and a detection-to-provider mapping table, with minor gaps: `date -u -v-7d` is BSD-only and the consumer-deploy step is an unexpanded placeholder comment.

4 / 5

Workflow Clarity

Nine clearly sequenced steps with blast-radius assessment, audit-log verification, an observation window, and a Step 9 checklist; however, no explicit error-recovery loop exists for the case where a consumer regresses after old-key deactivation.

4 / 5

Progressive Disclosure

Well-organized sections with a flat, one-level-deep References list of external doc URLs and no nested references, but all ~250 lines live inline in SKILL.md with no bundle files splitting per-provider detail.

4 / 5

Total

16

/

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 with an explicit use-when clause, concrete multi-action capability list, and named providers. Its only weaknesses are missing common synonyms (leaked/exposed/compromised) and slight trigger overlap with secret-detection skills.

DimensionReasoningScore

Specificity

Lists four concrete actions ("identify the provider, rotate the credential through its API (AWS IAM, GitHub, Stripe, GCP, Azure, Twilio, Slack and more), revoke the old one, log the audit trail and link the post-mortem") with named providers, giving comprehensive coverage of the workflow.

5 / 5

Completeness

Explicitly answers both parts: "Use when a secret is found in code or history, or for scheduled rotation" gives concrete triggers, and the enumerated action list clearly states what the skill does.

5 / 5

Trigger Term Quality

Natural phrases like "secret is found in code or history", "scheduled rotation", and "rotate the credential" are present, but common synonyms such as "leaked", "exposed", or "compromised key" are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

The rotation niche is distinct and "Scrubbing git history is not enough" draws a boundary, but the "secret is found in code" trigger overlaps with detection-oriented skills like the referenced gitleaks-scanning, leaving minor conflict risk.

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