vault-secrets-integrator
Vault Secrets Integrator - Auto-activating skill for DevOps Advanced. Triggers on: vault secrets integrator, vault secrets integrator Part of the DevOps Advanced skill category.
36
3%
Does it follow best practices?
Impact
98%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/02-devops-advanced/vault-secrets-integrator/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a placeholder that provides no useful information beyond the skill's name and category. It fails to describe any concrete capabilities, lacks natural trigger terms users would employ, and provides no guidance on when Claude should select this skill. It is among the weakest possible descriptions for skill selection purposes.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Retrieves, stores, and rotates secrets in HashiCorp Vault. Manages secret engines, access policies, and token lifecycle.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user mentions HashiCorp Vault, secrets management, credential rotation, API keys storage, vault policies, or secret engines.'
Remove the redundant duplicate trigger term ('vault secrets integrator' is listed twice) and replace with diverse natural language variations users would actually say, such as 'vault secrets', 'manage credentials', 'secret rotation', 'vault policies'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only states the skill name and category ('Vault Secrets Integrator', 'DevOps Advanced') without describing what it actually does—no verbs like 'retrieves', 'manages', 'rotates', or any specific capabilities. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no 'Use when...' clause, and the description provides zero information about the skill's functionality beyond its name. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are the skill's own name repeated twice ('vault secrets integrator'). There are no natural user keywords like 'secrets management', 'HashiCorp Vault', 'API keys', 'credentials', 'secret rotation', or other terms a user would naturally use. | 1 / 3 |
Distinctiveness Conflict Risk | The name 'Vault Secrets Integrator' is somewhat specific to a niche (secrets management with Vault), which provides some distinctiveness. However, without concrete actions or triggers, it could still overlap with other DevOps or secrets-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell with no actual technical content. It repeatedly references 'vault secrets integrator' without ever explaining what it is, how to configure it, or providing any executable guidance. It reads as an auto-generated template that was never filled in with real instructions.
Suggestions
Add concrete, executable examples showing how to integrate HashiCorp Vault secrets (e.g., Vault Agent sidecar injection in Kubernetes, Terraform vault provider configuration, or CSI secrets store driver setup).
Define a clear multi-step workflow with validation checkpoints, such as: configure Vault → create policies → set up auth method → inject secrets → verify secret availability in pods.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill abstractly and replace them with actionable technical content.
Add specific code/configuration examples (e.g., Vault Helm chart values, Kubernetes annotations for sidecar injection, Terraform vault_generic_secret resources) that are copy-paste ready.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content. Every section restates the same vague information about 'vault secrets integrator' without adding substance. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no configuration examples, no specific steps for integrating vault secrets. The content only describes rather than instructs, with phrases like 'Provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequences, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive structure with no meaningful organization. There are no references to detailed files, no quick-start section, and no navigation to deeper content. The sections are superficial headers over vacuous content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
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 | 9 / 11 Passed | |
- Commit
c8a915c
- 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.