Tessl • The management layer for AI agent skills

SkillPublic

yao-workspace

Workspace file I/O expert. ALWAYS invoke this skill when you need to list workspaces, read or write files in a workspace on a remote node, or browse workspace directories. Use this for cross-node file operations — for local sandbox files, use standard filesystem tools instead.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

83%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.

An efficient, highly actionable reference: every tool is documented with executable commands and typed parameter tables, and the workflow ordering is clear. The main gap is the total absence of validation or verification steps around the potentially destructive workspace_file_write operation.

Suggestions

Add a verification step after workspace_file_write, e.g. 'After writing, verify with workspace_file_read that the content round-trips correctly.'

Add an overwrite caution before writes, e.g. 'Use workspace_file_list to check whether the target path already exists before overwriting it.'

Consider moving the per-tool parameter tables into a reference file if the skill grows, keeping SKILL.md as a command-example overview.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence: compact parameter tables, ready-to-run commands, and no explanations of concepts Claude already knows; every Guidelines line adds non-obvious information ($CTX_WORKSPACE_ID, the >1MB local-mount note, relative-path rule).	5 / 5
Actionability	Every tool has copy-paste-ready 'tai tool' bash commands with concrete JSON arguments covering the common cases (text and base64 read/write, filtered node listing, subdirectory browsing), plus typed parameter tables with defaults.	5 / 5
Workflow Clarity	The Typical Workflow section sequences all five steps clearly, but no validation checkpoints exist anywhere and the terminal write step can destructively overwrite files, matching the anchor 'steps listed but validation gaps; checkpoints missing or implicit' and triggering the destructive-operation cap.	3 / 5
Progressive Disclosure	No bundle files exist and none are needed; per-tool sections are well organized and nothing that belongs in a separate file is inlined. However, at ~91 lines it exceeds the under-50-line simple-skill threshold where structure alone earns a 5, so 'good structure, minor organization gaps' is the best fit.	4 / 5
	Total	17 / 20 Passed

Description

82%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.

A strong description with explicit what/when coverage, concrete trigger phrases, and excellent boundary guidance that sharply reduces conflict risk. Its main weaknesses are the second-person trigger phrasing ('when you need to'), which violates the third-person voice requirement, and slightly incomplete action coverage.

Suggestions

Rewrite the trigger clause in third person to avoid the specificity penalty, e.g. 'Workspace file I/O expert: lists workspaces, reads and writes files in workspaces on remote nodes, and browses workspace directories. Use when performing cross-node workspace file operations.'

Mention the detail-retrieval capability explicitly (e.g., 'retrieve full workspace details such as node, owner, and labels') so all five tool functions are represented in the action list.

Add one or two natural synonyms users might say, such as 'copy files to a workspace' or 'view workspace contents', to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	The description lists several concrete actions ('list workspaces, read or write files in a workspace on a remote node, or browse workspace directories') which would anchor at 4, but the second-person phrasing 'ALWAYS invoke this skill when you need to...' incurs the rubric's 1-point specificity penalty, and workspace detail retrieval (workspace_get) is not mentioned.	3 / 5
Completeness	It explicitly answers what ('Workspace file I/O expert' plus the concrete actions) and when ('ALWAYS invoke this skill when you need to list workspaces, read or write files... or browse workspace directories'), with concrete trigger phrases and even boundary guidance ('for local sandbox files, use standard filesystem tools instead').	5 / 5
Trigger Term Quality	Natural phrases like 'list workspaces', 'read or write files', and 'browse workspace directories' match what a user would say, but coverage lacks synonyms or variations (e.g., 'copy files', 'workspace contents', 'remote node files'), fitting the 'good coverage, a few natural terms missing' anchor.	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche (workspace file I/O on a remote node, cross-node operations) and explicitly disambiguates from the closest competing capability ('for local sandbox files, use standard filesystem tools instead'), minimizing wrong-skill triggering.	5 / 5
	Total	17 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: YaoApp/yao
Path: tools/skills/yao-workspace/SKILL.md
Revision: 22a7a2c

Reviewed: 28 days ago

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.

yao-workspace

Table of Contents

Is this your skill?