CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

Install with Tessl CLI

npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill ssh-key-manager
What are skills?

Overall
score

19%

Does it follow best practices?

Validation for skill structure

SKILL.md
Review
Evals

Activation

7%

This description is essentially a placeholder with no functional content. It fails to describe any concrete capabilities, lacks natural trigger terms users would actually say, and provides no guidance on when Claude should select this skill. The only distinguishing element is the 'ssh key' domain reference.

Suggestions

Add specific actions the skill performs, e.g., 'Generates SSH key pairs, manages authorized_keys files, configures SSH config entries, and troubleshoots SSH connection issues.'

Include a 'Use when...' clause with natural trigger terms: 'Use when the user mentions ssh-keygen, generating SSH keys, adding keys to servers, SSH authentication, or public/private key pairs.'

Remove the duplicate trigger term and expand to include variations users naturally say: 'ssh key', 'generate key pair', 'authorized_keys', 'ssh config', 'passwordless ssh'.

DimensionReasoningScore

Specificity

The description contains no concrete actions - only the name 'Ssh Key Manager' and category metadata. It doesn't describe what the skill actually does (e.g., generate keys, manage authorized_keys, configure SSH config).

1 / 3

Completeness

Neither 'what does this do' nor 'when should Claude use it' is answered. The description only provides category metadata without any functional information or explicit usage triggers.

1 / 3

Trigger Term Quality

The only trigger terms listed are 'ssh key manager' repeated twice. Missing natural variations users would say like 'generate ssh key', 'ssh-keygen', 'authorized_keys', 'ssh config', 'public key', 'private key'.

1 / 3

Distinctiveness Conflict Risk

The term 'ssh key' is somewhat specific to a domain, but without describing actual capabilities, it could overlap with general SSH skills, security skills, or DevOps automation skills.

2 / 3

Total

5

/

12

Passed

Implementation

0%

This skill is entirely meta-content with zero actionable information about SSH key management. It describes what a skill should do rather than actually teaching SSH key operations like generation, permissions, agent configuration, or config file setup. The content would need to be completely rewritten to provide any value.

Suggestions

Add concrete SSH key generation commands (e.g., `ssh-keygen -t ed25519 -C 'email@example.com'`) with explanation of key types

Include specific steps for SSH agent setup and key permissions (`chmod 600 ~/.ssh/id_ed25519`)

Provide example ~/.ssh/config file snippets for common scenarios (multiple keys, jump hosts)

Remove all meta-description content ('This skill provides...', 'Capabilities include...') and replace with actual instructions

DimensionReasoningScore

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 commands, no code, no specific steps for SSH key management. The entire content describes what the skill supposedly does without actually teaching how to do anything.

1 / 3

Workflow Clarity

No workflow is provided. Despite SSH key management involving clear steps (generation, permissions, agent setup, config), none are documented. The skill promises 'step-by-step guidance' but delivers none.

1 / 3

Progressive Disclosure

The content is a monolithic block of meta-description with no actual content to organize. There are no references to detailed materials, no structure beyond generic headings, and nothing to progressively disclose.

1 / 3

Total

4

/

12

Passed

Validation

69%

Validation11 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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.