tailscale

Tailscale VPN sharing, Serve, and Funnel for remote access

Quality

33%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./src/skills/bundled/tailscale/SKILL.md

Quality

Content

27%

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

This skill is a comprehensive but overly verbose reference document that tries to be both a quick-start guide and a complete API reference in one file. The TypeScript examples reference a potentially fictional library ('clodds/tailscale'), undermining actionability. The content would benefit significantly from splitting into a concise overview with links to detailed reference files, and adding workflow validation steps for operations like Funnel setup that have security implications.

Suggestions

Split the TypeScript API reference into a separate REFERENCE.md file and keep only a quick-start example (serve + funnel) in the main SKILL.md

Add validation/verification steps: after starting serve or funnel, show how to confirm it's working (e.g., check status, curl the URL)

Verify that the 'clodds/tailscale' TypeScript library actually exists; if not, replace with real Tailscale CLI commands or the actual Tailscale API

Remove the verbose console.log lines and explanatory comments in code examples — Claude can infer what status fields mean

Dimension	Reasoning	Score
Conciseness	The content is extremely verbose at ~200 lines, with extensive API reference material that could be in a separate file. The TypeScript API examples are exhaustive with unnecessary console.log demonstrations, and the 'Chat Commands' section lists commands Claude likely already knows. The Serve vs Funnel comparison table and URL formats table add bulk for relatively simple distinctions.	1 / 3
Actionability	The TypeScript code examples appear executable and concrete, but they reference a fictional 'clodds/tailscale' library that may not exist, making them potentially non-functional. The chat commands are concrete but it's unclear if these are actual slash commands in a specific tool or CLI commands. The mix of real Tailscale CLI and a possibly fabricated TypeScript SDK reduces reliability.	2 / 3
Workflow Clarity	Individual operations are clear, but there's no sequenced workflow for common multi-step processes. For example, setting up Funnel requires Tailscale to be installed, logged in, and Funnel enabled in admin — but there's no step-by-step workflow with validation checkpoints. The Requirements section is at the bottom rather than being integrated into a workflow. No error handling or verification steps are provided.	2 / 3
Progressive Disclosure	This is a monolithic wall of content with no references to external files. The full TypeScript API reference, all chat commands, use cases, comparison tables, and best practices are all inlined in a single file. The API reference section alone should be in a separate REFERENCE.md, with the main skill providing a quick-start overview and links.	1 / 3
	Total	6 / 12 Passed

Description

40%

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 identifies a clear niche (Tailscale-specific features) which gives it strong distinctiveness, but it reads more like a topic label than a functional description. It lacks concrete actions, natural trigger terms users might say, and has no 'Use when...' clause to guide skill selection.

Suggestions

Add a 'Use when...' clause, e.g., 'Use when the user wants to expose local services, share devices on a tailnet, or set up public URLs via Tailscale.'

List specific concrete actions such as 'Configure Tailscale Serve to expose local ports, set up Funnel for public HTTPS access, share nodes across tailnets.'

Include natural trigger terms users might say, such as 'expose localhost', 'public URL', 'tunnel', 'share local server', 'tailnet', or 'remote access to dev server'.

Dimension	Reasoning	Score
Specificity	Names the domain (Tailscale VPN) and some features (sharing, Serve, Funnel, remote access), but doesn't list concrete actions like 'configure Serve endpoints', 'set up Funnel for public access', or 'share nodes with other users'.	2 / 3
Completeness	Provides a partial 'what' (Tailscale VPN sharing, Serve, Funnel) but has no explicit 'when' clause or trigger guidance. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also weak, so this scores 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Tailscale', 'VPN', 'Serve', 'Funnel', and 'remote access', but misses common user variations like 'expose local port', 'share localhost', 'public URL', 'tailnet', or 'tunnel'.	2 / 3
Distinctiveness Conflict Risk	Tailscale is a very specific product with distinct features (Serve, Funnel), making this clearly distinguishable from other networking or VPN skills. Unlikely to conflict with other skills.	3 / 3
	Total	8 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: alsk1992/CloddsBot
Commit: e71a5f6

Reviewed: 2 months 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.