CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

secrets-management

Implement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or native platform solutions. Use when handling sensitive credentials, rotating secrets, or securing CI/CD environments.

Quality

74%

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/cicd-automation/skills/secrets-management/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 body is code-rich and mostly executable across Vault, AWS, and native CI/CD platforms, but it is padded with a known-concept tool catalog, its destructive secret-rotation workflow lacks validation and rollback, and it inlines all platform details rather than using progressive disclosure. Structure and headers are good, which keeps it navigable despite the length.

Suggestions

Replace the 'Secrets Management Tools' feature-bullet catalog and the redundant 'Purpose'/'When to Use' sections with a brief task-to-tool selection table, removing explanation of concepts Claude already knows (targets conciseness).

Add verification and rollback to the automated rotation Lambda: test the new credential before cutover and revert the secret on failure, mirroring the verify-then-revoke ordering already present in the manual process (targets workflow_clarity).

Move per-platform integration details (GitHub Actions, GitLab CI, Terraform, External Secrets Operator, secret scanning) into references/ files and keep SKILL.md as a concise overview with clearly signaled one-level-deep links (targets progressive_disclosure).

DimensionReasoningScore

Conciseness

The code sections are dense and efficient, but the 'Secrets Management Tools' catalog ('Centralized secrets management', 'Dynamic secrets generation', 'HSM-backed keys', 'Versioning') plus the redundant 'Purpose' and 'When to Use' sections restate tool knowledge Claude already has. More than minor over-explanation (not 4), yet the majority of the file is tight executable code rather than padded prose (not 2).

3 / 5

Actionability

Most examples are copy-paste ready: vault CLI setup, the vault-action GitHub workflow, AWS CLI retrieval with '::add-mask::', Terraform, External Secrets Operator manifests, and the TruffleHog pre-commit hook. Not anchor 5 because the rotation Lambda calls undefined pseudocode functions 'generate_strong_password()' and 'update_database_password(new_password)', so that example is not executable as written.

4 / 5

Workflow Clarity

The manual rotation sequence includes '4. Verify functionality' before revocation and the GitLab example fails on missing variables, but the automated rotation Lambda changes a database password with no verification, error handling, or rollback, and there is no overall tool-selection-to-integration sequence. The destructive-rotation-without-validation guideline caps this dimension at 3.

3 / 5

Progressive Disclosure

Section headers and logical grouping make the file navigable (better than the minimal-structure anchor 2), but roughly 300 lines of per-platform integration details (GitHub Actions, GitLab, Terraform, Kubernetes, scanning) are inlined in a single 345-line SKILL.md with no bundle files, when this content clearly belongs in separate reference files. Not anchor 4 because essentially nothing is split out.

3 / 5

Total

13

/

20

Passed

Description

78%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 what/when structure, natural trigger phrases, and named tools that aid distinctiveness. The main gaps are thin action coverage (a single 'implement' verb) and missing common synonyms like 'API keys', 'passwords', and 'tokens'.

DimensionReasoningScore

Specificity

Names the domain and concrete tools ('using Vault, AWS Secrets Manager, or native platform solutions') but offers only one real action verb ('Implement secure secrets management'), and 'native platform solutions' is generic. It does not list several distinct concrete actions (store, retrieve, rotate, audit), so it matches the anchor for domain plus 1-2 actions rather than the several-actions anchor above.

3 / 5

Completeness

Explicitly answers both parts: what ('Implement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or native platform solutions') and when with three concrete trigger phrases ('Use when handling sensitive credentials, rotating secrets, or securing CI/CD environments'), mirroring the top anchor's structure. Not anchor 4, whose 'when' clause is a single generic condition.

5 / 5

Trigger Term Quality

Includes natural phrases users would say: 'handling sensitive credentials, rotating secrets, or securing CI/CD environments' plus tool names 'Vault' and 'AWS Secrets Manager'. Not anchor 5 because common synonyms such as 'API keys', 'passwords', 'tokens', or 'environment variables' are missing.

4 / 5

Distinctiveness Conflict Risk

A clear niche (secrets management in CI/CD with named tools) makes it mostly distinct. Minor overlap risk remains with generic security-hardening or CI/CD provisioning skills because 'rotating secrets' and 'securing CI/CD environments' are broad triggers, so not the minimal-conflict anchor 5.

4 / 5

Total

16

/

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.

Repository

wshobson/agents

Path

plugins/cicd-automation/skills/secrets-management/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.