ssh-key-manager
Ssh Key Manager - Auto-activating skill for DevOps Basics. Triggers on: ssh key manager, ssh key manager Part of the DevOps Basics skill category.
36
3%
Does it follow best practices?
Impact
97%
1.01xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/01-devops-basics/ssh-key-manager/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 with no substantive content. It names the skill and its category but provides zero information about what actions it performs, what problems it solves, or when it should be selected. It would be nearly useless for Claude to differentiate this skill from others in a large skill library.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates SSH key pairs, configures authorized_keys files, manages known_hosts, and sets up SSH agent forwarding.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about generating SSH keys, setting up SSH access, configuring ssh-keygen, adding public keys to servers, or troubleshooting SSH authentication.'
Remove the duplicate trigger term ('ssh key manager' is listed twice) and expand with varied natural phrases users might say, such as 'ssh-keygen', 'public key authentication', 'id_rsa', 'authorized_keys', or 'SSH setup'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only names the skill ('Ssh Key Manager') and its category ('DevOps Basics') without describing what it actually does—no mention of generating, managing, copying, configuring, or any other SSH key operations. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'ssh key manager' repeated twice. There are no natural user phrases like 'generate ssh key', 'ssh-keygen', 'authorized_keys', 'public key', 'private key', or 'add ssh key to server' that users would actually say. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'ssh key' does narrow the domain somewhat, making it unlikely to conflict with unrelated skills. However, the lack of specific actions means it could overlap with broader 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 is an empty template/placeholder with no actual content about SSH key management. It contains no commands (e.g., ssh-keygen, ssh-copy-id), no configuration examples, no security best practices, and no actionable guidance of any kind. It merely restates the skill name in various boilerplate sections.
Suggestions
Add concrete, executable commands for SSH key generation (e.g., `ssh-keygen -t ed25519 -C 'user@host'`), copying keys (`ssh-copy-id`), and configuring `~/.ssh/config`.
Include a clear workflow: 1. Generate key pair → 2. Set permissions (`chmod 600`) → 3. Add to agent → 4. Copy to remote host → 5. Verify connection with `ssh -T`.
Add security best practices as concise bullet points: key types to prefer (ed25519 > rsa), passphrase usage, key rotation guidance, and common pitfalls.
Remove all boilerplate sections (Purpose, When to Use, Example Triggers, Capabilities) that provide no actionable information and replace with actual SSH key management content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It explains what the skill does in abstract terms without providing any actual SSH key management guidance. Every section restates the same vague concept. | 1 / 3 |
Actionability | There are zero concrete commands, code examples, or specific instructions. No SSH key generation commands (ssh-keygen), no configuration examples, no file paths—nothing actionable whatsoever. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, and no validation checkpoints. The skill merely claims it 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Progressive Disclosure | No references to external files, no structured content hierarchy, and no navigation aids. The content is a flat, repetitive placeholder with no meaningful organization of information. | 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.