CtrlK
BlogDocsLog inGet started
Tessl Logo

integrating-secrets-managers

Manage this skill enables AI assistant to seamlessly integrate with various secrets managers like hashicorp vault and aws secrets manager. it generates configurations and setup code, ensuring best practices for secure credential management. use this skill when... Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.

46

Quality

50%

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/devops/secrets-manager-integrator/skills/integrating-secrets-managers/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-3

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

The content is concise, well-organized, and includes a useful error-handling table, but the core workflow stays at an abstract descriptive level without executable code or validation checkpoints, and it fails to point to the bundled scripts and templates that would make it actionable.

Suggestions

Add executable code or command snippets to the Instructions (e.g., a Vault policy HCL snippet, an AWS CLI create-secret command, or a reference to scripts/aws_secrets_manager_setup.py) so the guidance is copy-paste ready.

Insert validation checkpoints into the workflow (e.g., after creating a policy, verify access with a test secret read before proceeding), turning the numbered list into a validate-then-proceed loop.

Reference the bundle files explicitly from the body — point to the vault_config_template.hcl and aws_iam_policy_template.json assets and the setup/rotation scripts — so progressive disclosure is fully wired up.

DimensionReasoningScore

Conciseness

The body is lean and well-sectioned (Overview, Prerequisites, Instructions, Output, Error Handling, Examples, Resources) with no padding explaining concepts Claude already knows; every section earns its place.

3 / 3

Actionability

The Error Handling table offers concrete commands ("vault kv get", "aws secretsmanager describe-secret") and the instructions include specific path/CLI examples, but the core 9-step workflow is descriptive ("Inventory all secrets", "Generate access policies with least-privilege") with no executable code despite a bundled setup script and templates existing.

2 / 3

Workflow Clarity

The nine instructions form a clear ordered sequence, but there are no validation checkpoints or feedback loops for risky operations like creating IAM policies and secrets, which per the scoring notes caps workflow clarity at 2.

2 / 3

Progressive Disclosure

The body is cleanly organized into sections and uses one-level-deep external doc URLs, but the bundled files in scripts/ (aws_secrets_manager_setup.py, vault_config_generator.py, secrets_rotation.py) and assets/ (templates) are never referenced or navigated to from the body, leaving the bundle structure un-signaled.

2 / 3

Total

9

/

12

Passed

Description

35%Weight 40%Scale 1-3

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

The description identifies a clear niche and some capabilities but is marred by broken grammar and a placeholder trigger clause that provides no real activation guidance. It reads like an unfinished template rather than a polished, actionable description.

Suggestions

Fix the broken opening syntax ("Manage this skill enables AI assistant...") into clean third-person voice, e.g. "Integrates applications with secrets managers (HashiCorp Vault, AWS Secrets Manager) and generates auth configs, access policies, and rotation setup code."

Replace the placeholder trigger ("Use when appropriate context detected. Trigger with relevant phrases based on skill purpose") with concrete triggers, e.g. "Use when the user asks to set up Vault/AWS Secrets Manager, rotate secrets, replace hardcoded credentials, or configure secret retrieval."

Use third person consistently and avoid the first/second-person phrasing to satisfy the voice guideline.

DimensionReasoningScore

Specificity

It names the domain ("various secrets managers like hashicorp vault and aws secrets manager") and some concrete actions ("generates configurations and setup code"), but the actions are not comprehensive and the broken grammar ("Manage this skill enables AI assistant to seamlessly integrate") muddies what is actually offered.

2 / 3

Completeness

It states what the skill does (integrate secrets managers, generate configs and setup code), but the 'when' is only a non-answer placeholder ("Use when appropriate context detected") rather than an explicit trigger, which per the guidelines caps completeness below 3.

2 / 3

Trigger Term Quality

The trigger clause is an empty placeholder — "use this skill when... Use when appropriate context detected. Trigger with relevant phrases based on skill purpose" — with no actual natural keywords a user would say, so it matches the 'no natural keywords' anchor.

1 / 3

Distinctiveness Conflict Risk

The secrets-manager niche is reasonably specific and distinguishable from generic skills, but the absent real triggers mean it could still overlap with adjacent devops/security skills, matching 'somewhat specific but could still overlap'.

2 / 3

Total

7

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.