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.
34
0%
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
0%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 only repeats the skill name and its category. It provides zero information about what the skill does, what actions it performs, or when it should be selected. It would be nearly impossible for Claude to correctly choose this skill from a list of available skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Retrieves, rotates, and injects secrets from HashiCorp Vault into application configurations and CI/CD pipelines.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user mentions Vault secrets, secret management, credential injection, API key rotation, HashiCorp Vault, or secure environment variable configuration.'
Remove the duplicate trigger term ('vault secrets integrator' is listed twice) and replace with varied natural keywords users would actually say, such as 'secrets', 'credentials', 'vault integration', 'secret rotation', '.env secrets'.
| 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 'injects' secrets. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no explanation of capabilities and no explicit 'Use when...' clause with trigger guidance. | 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 'environment variables' that a user would naturally say. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it could overlap with any secrets management, DevOps, or configuration skill. Without specifying what kind of vault, what operations, or what integrations, it provides no clear niche. | 1 / 3 |
Total | 4 / 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 a hollow template with no actual technical content. It contains only generic boilerplate descriptions about what it would do without providing any concrete guidance on vault secrets integration (e.g., HashiCorp Vault setup, secret injection patterns, Kubernetes integration, sidecar/init-container approaches, or Terraform vault provider usage). It fails on every dimension of the rubric.
Suggestions
Add concrete, executable examples such as Vault Agent sidecar configuration YAML, Terraform vault_generic_secret resources, or Kubernetes ExternalSecret manifests.
Define a clear multi-step workflow for common vault secrets integration patterns (e.g., 1. Enable secrets engine, 2. Create policy, 3. Configure auth method, 4. Inject secrets into pods) with validation steps at each stage.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill rather than teaching the task—these waste tokens and provide no value.
Add references to supporting files for advanced topics (e.g., VAULT_KUBERNETES_AUTH.md, DYNAMIC_SECRETS.md) or inline the most critical patterns if the skill is meant to be self-contained.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, provides no specific technical content about vault secrets integration, and wastes tokens on generic meta-descriptions like 'Provides step-by-step guidance' without actually providing any. | 1 / 3 |
Actionability | There is zero actionable content—no code, no commands, no configuration examples, no concrete steps for integrating vault secrets. Every section is abstract description rather than instruction. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | There is no meaningful content to organize, no references to supporting files, and no bundle files exist. The structure is just a series of empty-calorie headings with no substance beneath them. | 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
13d35b8
- 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.