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 body is highly actionable with executable commands, clear sequenced workflows and validation, and tight, padding-free prose; the only gap is that everything is inlined with no one-level-deep references to factor out the recipe library.

DimensionReasoningScore

Conciseness

Lean and competence-assuming with no concept padding; a few recipe blocks are long, but each earns its place, leaving only minor trim opportunities.

4 / 5

Actionability

Fully executable, copy-paste-ready commands and complete self-contained recipes cover the common cases (HTTP, TCP, TLS, auth gates, webhooks, MCP, LLM endpoints).

5 / 5

Workflow Clarity

The 5-step procedure is explicitly sequenced with validation checkpoints (confirm origin, parse URL, verify, 502 recovery) and a teardown step; no destructive/batch cap applies.

5 / 5

Progressive Disclosure

A single well-organized file with clear section headers and a good quick-reference block; structure is strong though all content lives inline rather than split across referenced files.

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 specific to its niche but omits explicit trigger guidance and natural user phrasings, leaving both the when-to-use and keyword coverage underdeveloped.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when you need to expose a local dev server, webhook receiver, or any localhost port to the public internet.'

Include natural trigger terms users actually say ('public URL', 'share my dev server', 'tunnel port N') to improve trigger term quality.

Optionally enumerate one or two concrete capabilities (expose HTTP/TCP/TLS, add basic-auth or bearer-token gates) to lift specificity.

DimensionReasoningScore

Specificity

Names the domain and mechanism ('localhost tunnels over SSH via Pinggy') plus the zero-install attribute, but only implies a single action rather than listing several concrete capabilities.

3 / 5

Completeness

The 'what' is clear, but there is no 'Use when...' trigger clause, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

'localhost tunnels' and 'SSH' are natural terms, but common user phrasings like 'expose my dev server', 'get a public URL', or 'share this locally' are absent.

3 / 5

Distinctiveness Conflict Risk

Pegs a specific niche (Pinggy SSH tunnels) unlikely to collide with other skills, with only minor overlap risk against generic tunneling tools.

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.