integrating-secrets-managers
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill integrating-secrets-managersManage 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.
Validation
81%| Criteria | Description | Result |
|---|---|---|
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 |
Total | 13 / 16 Passed | |
Implementation
0%This skill is a template placeholder with no actionable content. It describes what a secrets manager integration skill should do but provides zero executable code, configuration examples, or concrete guidance. Every section uses generic language that could apply to any skill, making it essentially useless for actually integrating Vault or AWS Secrets Manager.
Suggestions
Replace the abstract 'Examples' section with actual executable code: Vault policy HCL files, Kubernetes YAML manifests with Vault annotations, AWS IAM policy JSON, and Python/Node code for retrieving secrets
Remove the generic sections ('Overview', 'How It Works', 'When to Use This Skill', 'Integration', 'Prerequisites', 'Instructions', 'Output', 'Error Handling', 'Resources') and replace with concrete configuration templates
Add a clear workflow with validation steps, e.g., '1. Create policy: vault policy write... 2. Verify: vault policy read... 3. Create role: vault write auth/kubernetes/role/...'
Include specific CLI commands for both Vault and AWS Secrets Manager with expected outputs and error handling for common failure modes
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive padding explaining what the skill does rather than how to do it. Sections like 'Overview', 'How It Works', 'When to Use This Skill', and 'Integration' explain concepts Claude already understands and add no actionable value. | 1 / 3 |
Actionability | No concrete code, commands, or executable examples anywhere. The 'Examples' section describes what the skill 'will do' in abstract terms but provides zero actual configuration files, code snippets, or copy-paste ready content. | 1 / 3 |
Workflow Clarity | The 'Instructions' section is completely generic ('Invoke this skill when trigger conditions are met') with no actual workflow steps. No validation checkpoints, no specific sequences for Vault or AWS integration, and no error recovery guidance. | 1 / 3 |
Progressive Disclosure | Monolithic content with no references to external files for detailed configurations. All sections are shallow placeholders with no actual depth or navigation to more detailed resources. | 1 / 3 |
Total | 4 / 12 Passed |
Activation
33%This description has a reasonable foundation with specific tool names and domain focus, but is severely undermined by placeholder text in the 'Use when' clause that provides no actual trigger guidance. The description also uses inconsistent voice and lacks the concrete action verbs and natural user trigger terms needed for effective skill selection.
Suggestions
Replace the placeholder 'Use when...' text with specific triggers like 'Use when the user mentions secrets, API keys, credentials, vault, environment variables, or needs to securely store/retrieve sensitive configuration.'
Add more concrete actions such as 'retrieve secrets', 'rotate credentials', 'configure secret backends', 'manage access policies'.
Include additional natural trigger terms users would say: 'API keys', 'passwords', '.env files', 'secret rotation', 'credential storage'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (secrets managers) and mentions specific tools (HashiCorp Vault, AWS Secrets Manager) with some actions (generates configurations and setup code), but lacks comprehensive concrete actions like 'rotate secrets', 'retrieve credentials', or 'audit access'. | 2 / 3 |
Completeness | The 'what' is partially addressed, but the 'when' clause is completely useless placeholder text ('Use when appropriate context detected. Trigger with relevant phrases based on skill purpose') that provides zero actual guidance on when to use this skill. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'hashicorp vault', 'aws secrets manager', 'credentials', but missing common variations users would say like 'API keys', 'passwords', 'environment variables', '.env files', or 'secret rotation'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of specific tools (HashiCorp Vault, AWS Secrets Manager) provides some distinctiveness, but 'secure credential management' is broad enough to potentially overlap with general security or configuration management skills. | 2 / 3 |
Total | 7 / 12 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.