CtrlK
BlogDocsLog inGet started
Tessl Logo

pinggy-tunnel

Zero-install localhost tunnels over SSH via Pinggy.

60

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/devops/pinggy-tunnel/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 content is highly actionable with executable code throughout, a clearly sequenced workflow with validation and error-recovery feedback, and a useful pitfalls checklist; its only weak spots are mild repetition of the tunnel boilerplate across recipes and a single-file layout that, while well-organized, could offload some recipes to reference files.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious, skill-specific detail (the username keyword system, free-tier limits, pitfalls) and assumes SSH competence rather than explaining basics, but the base tunnel command is repeated across Quick Reference, the Procedure, and the four recipes, which is minor redundancy that could be tightened.

4 / 5

Actionability

Every section provides copy-paste-ready, fully executable bash (Quick Reference variants, the numbered Procedure, and four self-contained recipes), with specific examples covering the common cases including verification curls and teardown.

5 / 5

Workflow Clarity

The Procedure is a clearly numbered sequence (confirm origin, launch, parse URL, verify, teardown) with an explicit validation checkpoint (curl head check) and a feedback loop ("If you get 502... the local origin isn't listening — fix step 1 first"), plus a Pitfalls checklist of failure modes.

5 / 5

Progressive Disclosure

The single SKILL.md is well-organized with clear section headers and easy navigation, and no bundle files exist to reference; however at ~309 lines the four recipes and Quick Reference could arguably live in separate reference files, so structure is good but not a textbook one-level-deep split.

4 / 5

Total

18

/

20

Passed

Description

53%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 concise and third-person with a clear "what" and a distinct niche, but it omits any explicit "when to use" trigger guidance and lacks the natural user-facing phrases that would improve trigger-term quality and completeness.

Suggestions

Add a "Use when..." clause with concrete trigger phrases, e.g. "Use when exposing a local dev server, receiving a webhook callback, or getting a public URL for a local service."

Include natural user terms alongside the technical ones, such as "share localhost", "public URL", or "tunnel a port", so the description matches how users actually ask.

Optionally list 1-2 more concrete actions (e.g. "with optional basic-auth, bearer-token, or IP-whitelist gating") to lift specificity from a single action toward comprehensive coverage.

DimensionReasoningScore

Specificity

"localhost tunnels over SSH via Pinggy" names the domain and one concrete mechanism (SSH reverse tunnel via Pinggy), matching the anchor that names a domain with 1-2 concrete actions but is not comprehensive; it lists a single action rather than the several needed for a 4.

3 / 5

Completeness

It clearly answers "what" (zero-install localhost tunnels over SSH via Pinggy) but has no "Use when..." clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

The terms "localhost tunnels", "SSH", and "Pinggy" are relevant but lean technical; natural user phrases like "expose my dev server", "share localhost", or "get a public URL" are absent, so it has some relevant keywords while missing common variations.

3 / 5

Distinctiveness Conflict Risk

Naming the specific service "Pinggy" carves a clear niche distinct from cloudflared/ngrok skills, but there is minor overlap risk with sibling tunnel skills, keeping it just below a 5.

4 / 5

Total

13

/

20

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.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository
NousResearch/hermes-agent
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.