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
Quality
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 severely lacking in substance. It provides only a skill name and category without any explanation of capabilities, use cases, or meaningful trigger terms. The description reads as auto-generated boilerplate rather than a useful guide for skill selection.
Suggestions
Add specific capabilities the skill provides, such as 'Retrieves secrets from HashiCorp Vault, manages secret rotation, injects credentials into environment variables, and configures Vault authentication methods.'
Include a 'Use when...' clause with natural trigger terms like 'Use when working with HashiCorp Vault, managing secrets, rotating credentials, or configuring secure access to sensitive data.'
Add common user phrases and file types that would trigger this skill, such as 'vault token', 'secret path', 'KV store', '.vault', 'VAULT_ADDR', or 'secrets engine'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Vault Secrets Integrator' is just a name, and 'Auto-activating skill for DevOps Advanced' provides no information about what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' entirely - there are no capabilities listed. The 'when' is technically present via 'Triggers on' but is circular and unhelpful, just repeating the skill name. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'vault secrets integrator' repeated twice. Missing natural user terms like 'secrets management', 'HashiCorp Vault', 'credentials', 'API keys', 'secret rotation', or 'environment variables'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'Vault Secrets' is somewhat specific to HashiCorp Vault or similar secrets management tools, which provides some distinctiveness. However, without describing actual capabilities, it could still conflict with other DevOps or security-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 content is essentially a placeholder template with no actionable information about vault secrets integration. It contains only generic meta-descriptions of what a skill should do without any actual implementation guidance, code examples, or specific instructions for working with HashiCorp Vault or similar secrets management tools.
Suggestions
Add concrete code examples showing how to integrate vault secrets (e.g., Kubernetes secrets injection, Terraform vault provider configuration, or application-level secret retrieval)
Include a clear workflow with steps like: configure vault connection → authenticate → retrieve secrets → inject into application/infrastructure, with validation at each step
Provide specific commands and configuration snippets for common vault integration patterns (e.g., vault agent sidecar, CSI driver, direct API calls)
Remove generic boilerplate sections ('Purpose', 'Capabilities' with vague descriptions) and replace with actionable quick-start content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about vault secrets integration. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude already understands. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it does abstractly ('provides step-by-step guidance') but never actually provides any steps, examples, or executable instructions for vault secrets integration. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, and no validation checkpoints. The content only describes capabilities in vague terms without any actual process for integrating vault secrets. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic descriptions with no structure pointing to detailed materials. No references to configuration examples, API documentation, or implementation guides are provided. | 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
994edc4
- 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.