CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

66

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/ssh-penetration-testing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-5

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

The body is a highly actionable SSH pentest cheatsheet with executable code throughout, but it is monolithic and lacks validation checkpoints for its batch/destructive operations. Splitting the script and reference material into bundle files would materially improve it.

Suggestions

Add explicit validation/success-check steps to the credential-attack phases (e.g., stop on first valid login, detect Fail2ban lockouts) so destructive batch operations have feedback loops.

Move the Paramiko script into ./scripts/ and the quick-reference tables into ./references/, keeping SKILL.md as a concise overview that links one level deep.

De-duplicate the Metasploit coverage (Phase 6 vs Phase 10) and trim introductory prose like the Purpose/Prerequisites narration that Claude already knows.

DimensionReasoningScore

Conciseness

Mostly efficient command reference, but ~480 lines with redundancy (Metasploit appears in Phase 6 and Phase 10, quick-reference tables repeat inline commands) and some introductory prose Claude does not need, so it sits at the midpoint.

3 / 5

Actionability

Copy-paste ready commands and a complete executable Paramiko script cover the common SSH testing cases throughout all ten phases.

5 / 5

Workflow Clarity

Phases 1–10 are sequenced, but batch/destructive operations (brute-forcing, password spraying, persistence via authorized_keys) lack explicit validation checkpoints or success/lockout feedback loops, which caps this dimension at 3 per the rubric.

3 / 5

Progressive Disclosure

Good section structure (phases, quick-reference tables) but entirely monolithic at ~480 lines — the Paramiko script and reference tables that clearly belong in separate bundle files are inlined with no external references.

3 / 5

Total

14

/

20

Passed

Description

92%Weight 40%Scale 1-5

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 well-constructed: third-person voice, explicit trigger guidance, and a clear what/when structure. It is comprehensive and distinct with negligible conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "pentest", "enumerate", "brute force", "exploit", "perform tunneling", "audit" — covering the SSH testing domain comprehensively, matching the top anchor.

5 / 5

Completeness

Explicitly answers both "what" ("provides comprehensive SSH penetration testing methodologies and techniques") and "when" ("should be used when the user asks to …") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Six natural verb-phrase triggers ("pentest SSH services", "brute force SSH credentials", "audit SSH security") are quoted as users would say them; minor synonyms/variants are absent so it sits just below the top anchor.

4 / 5

Distinctiveness Conflict Risk

A clear SSH-only niche with distinct triggers; minimal overlap risk with other skills, matching the top anchor.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
zebbern/claude-code-guide
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.