CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

77

1.11x
Quality

70%

Does it follow best practices?

Impact

86%

1.11x

Average score across 3 eval scenarios

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/cicd-automation/skills/secrets-management/SKILL.md

The canonical home for this skill is secrets-management in wshobson/agents

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.

A content-rich skill with broad, mostly executable coverage of secrets tooling, but it carries conceptual filler, lacks validation/rollback feedback for destructive rotation, and signals reference files that are absent from the bundle.

Suggestions

Add validation and rollback to the rotation workflows: after updating a secret, verify the new credential works before revoking the old one, and define a recovery path on failure, so destructive operations clear the workflow_clarity cap.

Create the referenced files (references/vault-setup.md and references/github-secrets.md) or remove the dangling references, and move the bulky per-tool integration blocks into them so SKILL.md stays a lean overview.

Trim the tool feature bullet lists and the duplicated Purpose/intro paragraphs, and make the Python rotation example runnable by defining or importing generate_strong_password and update_database_password.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete code, but the per-tool feature bullet lists ("Centralized secrets management", "Dynamic secrets generation", etc.) and the repeated Purpose/intro statements explain things Claude already knows and could be trimmed.

3 / 5

Actionability

Provides many concrete, copy-paste-ready examples across Vault CLI, GitHub Actions, GitLab CI, AWS CLI, Terraform, and Kubernetes, but the Python rotation example relies on undefined helpers (generate_strong_password, update_database_password) so it is not fully runnable.

4 / 5

Workflow Clarity

The manual rotation sequence includes a verify step, but the automated rotation example has no validation or rollback, and no destructive-op feedback loops exist; the destructive-operation cap holds this at 3.

3 / 5

Progressive Disclosure

Sections are well-organized and references are clearly signaled, but the referenced files (references/vault-setup.md, references/github-secrets.md) do not exist in the bundle, and large tool-specific blocks are inlined rather than split into the missing reference files.

3 / 5

Total

13

/

20

Passed

Description

83%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, third-person description that clearly states both capability and trigger conditions with named tools. It is specific and well-targeted, with only minor gaps in action specificity and synonym coverage.

DimensionReasoningScore

Specificity

Names the domain plus concrete tools ("Vault, AWS Secrets Manager, or native platform solutions") and several specific actions ("handling sensitive credentials, rotating secrets, or securing CI/CD environments"), but the verbs are slightly generic rather than crisply comprehensive.

4 / 5

Completeness

Explicitly answers both what ("Implement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or native platform solutions") and when ("Use when handling sensitive credentials, rotating secrets, or securing CI/CD environments") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural terms users would say ("secrets management", "CI/CD pipelines", "credentials", "rotating secrets", "Vault"), with good coverage but missing common synonyms like API keys, passwords, or tokens.

4 / 5

Distinctiveness Conflict Risk

Carves a clear niche (secrets management for CI/CD) with distinct triggers, but has minor overlap risk with general deployment-pipeline and devops skills.

4 / 5

Total

17

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 4 missing

Warning

Total

15

/

16

Passed

Repository
Dicklesworthstone/pi_agent_rust
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.