tailscale

Tailscale VPN sharing, Serve, and Funnel for remote access

Quality

52%

Does it follow best practices?

Impact

Pending

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

Discovery

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) but lacks actionable detail about what the skill actually does and completely omits guidance on when to use it. The product-specific terminology provides good distinctiveness, but the description needs concrete actions and explicit trigger conditions to be effective for skill selection.

Suggestions

Add a 'Use when...' clause with trigger terms like 'expose local server', 'share localhost', 'public URL', 'tailscale serve', 'tailscale funnel'

List specific concrete actions such as 'Configure Tailscale Serve to expose local services, set up Funnel for public access, share devices across tailnet'

Include common user phrasings like 'make my local app accessible', 'share my dev server', 'tunnel to my machine'

Dimension	Reasoning	Score
Specificity	Names the domain (Tailscale VPN) and mentions specific features (sharing, Serve, Funnel, remote access), but doesn't describe concrete actions like 'configure tunnels', 'expose local services', or 'share devices'.	2 / 3
Completeness	Only addresses 'what' at a high level with no 'Use when...' clause or explicit trigger guidance. Missing clear indication of when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Tailscale', 'VPN', 'Serve', 'Funnel', and 'remote access', but missing common variations users might say like 'tunnel', 'expose localhost', 'share port', or 'public URL'.	2 / 3
Distinctiveness Conflict Risk	Tailscale is a specific product with distinct terminology (Serve, Funnel). Unlikely to conflict with generic VPN or networking skills due to the product-specific naming.	3 / 3
	Total	8 / 12 Passed

Implementation

64%

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

This skill provides comprehensive, actionable guidance for Tailscale operations with excellent code examples. However, it's somewhat verbose for a skill file, mixing quick-reference commands with detailed API documentation that could be split out. The lack of error handling patterns and validation steps for network operations is a notable gap.

Suggestions

Add validation steps before serve/funnel operations (e.g., check tailscale.status() for online state, verify Funnel is enabled in admin)

Move the detailed TypeScript API reference to a separate REFERENCE.md file, keeping only quick-start examples in SKILL.md

Remove the 'Best Practices' section - these are generic security principles Claude already knows

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient but includes some redundancy (e.g., the comparison table and URL formats sections overlap conceptually). The best practices section states obvious security advice Claude already knows.	2 / 3
Actionability	Provides fully executable TypeScript code examples that are copy-paste ready, with concrete commands for chat interface and complete API usage patterns including configuration options.	3 / 3
Workflow Clarity	Commands and API methods are clearly listed, but there's no validation workflow for checking if Tailscale is properly configured before attempting operations, and no error handling patterns for common failure modes.	2 / 3
Progressive Disclosure	Content is well-organized with clear sections, but the entire API reference is inline rather than split into separate files. For a skill this comprehensive, the TypeScript API could be in a separate REFERENCE.md file.	2 / 3
	Total	9 / 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: 2a8c94e

Reviewed: 29 days 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.