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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill vault-secrets-integratorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely lacking in substance. It follows a template format that provides category metadata but completely omits what the skill actually does - there are no actions, capabilities, or use cases described. The trigger terms are redundant repetitions of the skill name rather than natural user language.
Suggestions
Add specific actions the skill performs, e.g., 'Retrieves secrets from HashiCorp Vault, injects credentials into configuration files, manages secret rotation and access policies.'
Include a 'Use when...' clause with natural trigger terms like 'vault secrets', 'HashiCorp', 'credentials', 'secret management', 'inject secrets', 'API keys', 'environment variables'.
Remove the redundant trigger phrase repetition and replace with meaningful variations users would actually say when needing this functionality.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only states it's an 'auto-activating skill' and mentions trigger phrases, but never explains what the skill actually does with vault secrets. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' entirely - there's no explanation of capabilities. The 'when' is technically present via 'Triggers on' but it's just the skill name, not meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just the skill name repeated ('vault secrets integrator') with no natural user language variations like 'secrets management', 'HashiCorp Vault', 'retrieve secrets', 'inject credentials', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'vault secrets' is somewhat specific to secrets management tooling, which provides some distinctiveness. However, without explaining what operations it performs, it could conflict with other secrets-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder with no substantive content. It describes what a vault secrets integrator skill would do without providing any actual instructions, code examples, or concrete guidance. The entire content could be replaced with 'Help with vault secrets' and convey the same information.
Suggestions
Add concrete code examples showing how to integrate HashiCorp Vault (or similar) with Kubernetes secrets, including authentication methods and secret injection patterns
Provide a clear workflow with validation steps: e.g., 1) Configure vault auth, 2) Create secret policies, 3) Deploy vault agent injector, 4) Validate secret injection in pods
Include specific commands for common operations like `vault kv put`, `kubectl create secret`, and Terraform vault provider configurations
Reference external files for advanced topics like dynamic secrets, secret rotation, and multi-cluster setups rather than keeping everything vague
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with zero actionable information. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever - no code, no commands, no specific steps, no examples of actual vault integration. The entire skill describes what it does rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. Despite claiming to provide 'step-by-step guidance,' there are zero actual steps for integrating vault secrets with any system. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no structure for discovery. No references to detailed documentation, no links to examples, and no organization of content by complexity or use case. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
- 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.