ssh-penetration-testing

This skill should be used when the user asks to "pentest SSH services", "enumerate SSH configurations", "brute force SSH credentials", "exploit SSH vulnerabilities", "perform SSH tunneling", or "audit SSH security". It provides comprehensive SSH penetration testing methodologies and techniques.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with ready-to-run commands and a complete script, and it is clearly phased, but it is padded with basic-concept explanations, lacks validation checkpoints for destructive and batch operations, and is a monolithic single file that would benefit from splitting into reference files.

Suggestions

Remove the 'Required Knowledge' bullets and trim the Purpose section so the body stops re-explaining SSH fundamentals Claude already knows.

Add validation/verification steps after destructive and batch operations (e.g., confirm a brute-forced credential actually logs in before reporting it; verify an authorized_keys edit took effect and is reversible) to lift workflow clarity above 2.

Split the long Paramiko script and the command/quick-reference tables into separate files under scripts/ and references/, linking to them from a concise overview, to move progressive disclosure toward a one-level-deep reference structure.

Dimension	Reasoning	Score
Conciseness	The bulk is dense, executable commands that earn their tokens, but the 'Required Knowledge' section (SSH protocol fundamentals, public/private key auth, Linux CLI proficiency) explains concepts Claude already knows and the Purpose section restates the frontmatter — matching 'mostly efficient but includes some unnecessary explanation'. Not level 3 because of that padding; not level 1 because it is not verbose prose.	2 / 3
Actionability	Commands are complete and copy-paste ready (hydra, nmap NSE, ssh -L/-R/-D) and the Paramiko Python script is a full executable module, matching the level-3 'fully executable, specific examples' anchor.	3 / 3
Workflow Clarity	Phases 1–10 give a clear sequence, but destructive/batch operations (echo key >> authorized_keys persistence, brute-force loops) have no validation or verification checkpoints, so per the guideline workflow_clarity is capped at 2. Not level 1 because the sequence is explicit; not level 3 because checkpoints are absent.	2 / 3
Progressive Disclosure	Content is well-sectioned into phases and tables, but it is a single ~480-line monolithic file with content (the Python script, quick-reference tables, detailed command blocks) that could be split into separate references and no external file references at all — matching the level-2 'content that should be separate is inline' anchor. Not level 1 because organization is clear; not level 3 because nothing is split out and the under-50-line exception does not apply.	2 / 3
	Total	9 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it names concrete actions, uses natural user-facing trigger phrases, and explicitly covers both what the skill does and when to invoke it within a well-scoped niche. It is concise and avoids over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'pentest SSH services', 'enumerate SSH configurations', 'brute force SSH credentials', 'exploit SSH vulnerabilities', 'perform SSH tunneling', 'audit SSH security' — matching the level-3 anchor of multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers both 'when' ('when the user asks to...') and 'what' ('provides comprehensive SSH penetration testing methodologies and techniques') with explicit triggers, satisfying the level-3 anchor and not triggering the missing-'Use when' cap.	3 / 3
Trigger Term Quality	The quoted phrases ('pentest SSH services', 'brute force SSH credentials', 'perform SSH tunneling') are natural terms a user would actually say, giving good coverage per the level-3 anchor.	3 / 3
Distinctiveness Conflict Risk	SSH penetration testing is a clear niche with distinct triggers unlikely to conflict with unrelated skills, matching the level-3 anchor; it uses third-person voice so no voice penalty applies.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: zebbern/claude-code-guide
Path: skills/ssh-penetration-testing/SKILL.md
Commit: af7d491

Reviewed: about 8 hours ago

Table of Contents

Discovery Implementation Validation

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.