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 boilerplate template with no substantive content. It fails to describe any concrete capabilities, lacks natural trigger terms users would use, and provides no guidance on when Claude should select this skill. The only slight positive is that 'SSH key' is a reasonably specific domain term.
Suggestions
Add concrete actions the skill performs, e.g., 'Generates, manages, and configures SSH key pairs. Handles tasks like creating keys with ssh-keygen, adding keys to authorized_keys, configuring SSH agents, and troubleshooting SSH authentication issues.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user mentions SSH keys, ssh-keygen, public/private keys, authorized_keys, SSH authentication, key permissions, or SSH agent forwarding.'
Remove the duplicate trigger term ('ssh key manager' is listed twice) and expand with varied natural phrases users would actually say, such as 'generate SSH key', 'set up SSH access', 'SSH permission denied', or 'copy SSH key to server'.
| 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' that users would actually say. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'SSH key' is somewhat specific to a niche domain, which provides some distinctiveness. However, the lack of concrete 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 technical content about SSH key management. It contains only meta-descriptions of what the skill claims to do without any concrete instructions, commands, code examples, or workflows. It would provide zero value to Claude when attempting to help users with SSH key management tasks.
Suggestions
Replace the meta-description sections with actual SSH key management content: include concrete commands for ssh-keygen, ssh-copy-id, and ssh-agent usage with specific flags and options.
Add a clear workflow for common SSH key tasks: generating keys (with recommended algorithms like ed25519), deploying public keys to servers, configuring ~/.ssh/config, and rotating/revoking keys.
Include validation steps such as testing SSH connections after key deployment (`ssh -T user@host`), verifying key permissions (`ls -la ~/.ssh/`), and checking authorized_keys format.
Add security best practices as concrete rules: required key types, minimum key lengths, passphrase requirements, and file permission settings (600 for private keys, 644 for public keys).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'ssh key manager' excessively, and provides zero actual technical content about SSH key management. | 1 / 3 |
Actionability | There are no concrete commands, code examples, or specific instructions. The skill contains only vague descriptions like 'Provides step-by-step guidance' without actually providing any guidance. No ssh-keygen commands, no key formats, no configuration examples. | 1 / 3 |
Workflow Clarity | There is no workflow whatsoever—no steps for generating, distributing, rotating, or revoking SSH keys. The content only describes what the skill theoretically does without any actual process or validation steps. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no structure pointing to detailed resources, no references to supporting files, and no bundle files exist. The sections present (Purpose, When to Use, Capabilities, etc.) are all meta-information about the skill rather than actual instructional content. | 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.