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
Quality
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 severely underdeveloped, consisting only of a title and category metadata without any substantive content. It fails to describe what the skill actually does, what specific SSH key operations it supports, or when Claude should select it. The repeated trigger term suggests a template that wasn't properly filled out.
Suggestions
Add specific actions the skill performs, e.g., 'Generates SSH key pairs, adds keys to ssh-agent, configures authorized_keys files, and manages known_hosts entries.'
Include a 'Use when...' clause with natural trigger terms like 'generate ssh key', 'ssh-keygen', 'add public key', 'ssh authentication', 'id_rsa', 'authorized_keys'.
Specify the contexts or scenarios where this skill applies, e.g., 'Use when setting up SSH access to remote servers, configuring Git SSH authentication, or troubleshooting SSH connection issues.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Ssh Key Manager' without describing any concrete actions. There are no verbs or specific capabilities listed - no mention of what operations can be performed (generate, add, remove, configure, etc.). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'ssh key manager' repeated twice. Missing natural variations users would say like 'generate ssh key', 'add ssh key', 'ssh-keygen', 'authorized_keys', 'id_rsa', or 'public key'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'SSH key' is somewhat specific to a domain, the lack of concrete actions means it could overlap with general DevOps, security, or authentication skills. The category mention 'DevOps Basics' is too broad to provide distinctiveness. | 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 that provides no actual guidance on SSH key management. It contains only meta-descriptions of what the skill claims to do without any concrete commands (ssh-keygen, ssh-copy-id), key management workflows, security best practices, or examples. The content would be completely unhelpful for Claude attempting to assist with SSH key tasks.
Suggestions
Add concrete SSH key generation commands: `ssh-keygen -t ed25519 -C 'email@example.com'` with explanation of key types and security considerations
Include a workflow for key deployment: generate -> add to ssh-agent -> copy to remote host -> verify connection
Provide examples for common scenarios: GitHub/GitLab authentication, server access, key rotation procedures
Add validation steps: how to verify key fingerprints, test connections, and troubleshoot common errors like permission issues
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely boilerplate with no actual SSH key management information. It explains what the skill does in abstract terms without providing any concrete guidance, wasting tokens on meta-description rather than actionable content. | 1 / 3 |
Actionability | No concrete commands, code examples, or specific instructions for SSH key management are provided. Phrases like 'provides step-by-step guidance' and 'generates production-ready code' describe capabilities without demonstrating them. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps for generating, managing, or deploying SSH keys. The content lacks any sequence of operations or validation checkpoints for SSH key operations. | 1 / 3 |
Progressive Disclosure | The content is a flat template with no meaningful structure. There are no references to detailed documentation, no organized sections with actual content, and no navigation to related materials. | 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.