CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tailscale

Tailscale VPN sharing, Serve, and Funnel for remote access

59

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/tailscale/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 commands and code, but it is a monolithic inlined API reference lacking progressive disclosure and any validation checkpoints for the risky public-exposure operations.

Suggestions

Move the bulk TypeScript API reference and command catalog into separate reference files (e.g. reference/api.md, reference/commands.md) and keep SKILL.md as a concise overview with one-level-deep links.

Add an explicit status/verification step after Funnel operations (e.g. run `/tailscale funnel status` to confirm the public URL and exposure) to introduce a validation checkpoint.

Trim redundancy between the Chat Commands and TypeScript API Reference sections by cross-referencing rather than restating.

DimensionReasoningScore

Conciseness

The body is dense reference material (commands, code, tables) with little concept over-explanation; minor redundancy between the chat-command and TypeScript API sections could be trimmed.

4 / 5

Actionability

Copy-paste-ready chat commands and complete, executable TypeScript examples cover the common cases (serve, funnel, status, file transfer) with concrete URLs and return values.

5 / 5

Workflow Clarity

Individual operations are unambiguous, but this is a flat reference of independent commands with no sequenced workflow or validation checkpoints; the risky Funnel (public exposure) operation lacks verify/status checkpoints, capping workflow clarity at 3.

3 / 5

Progressive Disclosure

Section headers provide structure, but the full TypeScript API reference and command catalog are inlined in SKILL.md with no references to separate files, and no bundle files exist to offload the detail.

3 / 5

Total

15

/

20

Passed

Description

65%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 distinct and reasonably specific to the Tailscale niche with good trigger keywords, but it lacks an explicit "Use when..." trigger clause and relies on feature nouns rather than concrete action verbs.

Suggestions

Add an explicit trigger clause, e.g. "Use when sharing local services over Tailscale, exposing ports publicly via Funnel, or accessing a machine remotely."

Reframe feature nouns as concrete actions (e.g. "Share local ports over a tailnet, expose services to the public internet via Funnel") to lift specificity.

Include a few natural synonyms ("expose", "tunnel", "public access") to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ("Tailscale VPN") and concrete features ("Serve, and Funnel", "sharing") but uses noun phrases rather than action verbs, so coverage is not comprehensive.

3 / 5

Completeness

The "what" is clear (VPN sharing/Serve/Funnel) but there is no explicit "Use when..." trigger clause, only the weakly implied "for remote access", capping completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Natural keywords a user would say are present ("Tailscale", "VPN", "remote access", "Serve", "Funnel"), though a few common synonyms (e.g. "expose", "tunnel", "public access") are missing.

4 / 5

Distinctiveness Conflict Risk

The Tailscale-specific niche with distinct triggers ("Tailscale", "Serve", "Funnel") makes conflict with other skills minimal.

5 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

alsk1992/CloddsBot

Path

src/skills/bundled/tailscale/SKILL.md

Revision

c930628

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill