CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

88%

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

SKILL.md
Quality
Evals
Security

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.

A tight, highly actionable tool reference with excellent conciseness and copy-paste examples. The main gap is the absence of validation/verification around the destructive write operation in the workflow, which caps workflow clarity.

Suggestions

Add a validation checkpoint before workspace_file_write (e.g., check whether the target path already exists, or confirm overwrite with the user) and a verify step after writing (e.g., re-read or list to confirm) to lift workflow_clarity past the destructive-operation cap.

Reconcile the slight overlap between the Typical Workflow and Guidelines sections so the workflow reads as a single sequenced procedure with the checkpoints above.

Consider noting error/exit-code handling for the bash commands (e.g., what a failed `tai tool` call returns) so Claude can detect and recover from failures.

DimensionReasoningScore

Conciseness

Lean per-tool sections with one-line descriptions, executable examples, and parameter tables; no padding or explanation of concepts Claude already knows, so every token earns its place rather than merely being mostly-efficient.

5 / 5

Actionability

Each tool ships copy-paste-ready bash commands with concrete JSON arguments covering common cases including base64 encoding for binary files, matching the fully-executable anchor rather than the minor-gaps level below.

5 / 5

Workflow Clarity

A clear 5-step Typical Workflow sequence exists, but workspace_file_write is a destructive overwrite operation with no validation or verify-checkpoint step, triggering the destructive-operation cap that precludes scoring above 3.

3 / 5

Progressive Disclosure

Well-organized single-file reference with consistent per-tool sections and no nested or buried references, but no one-level-deep reference split is used (none is strictly needed), so it sits at good-structure rather than the reference-split top anchor.

4 / 5

Total

17

/

20

Passed

Description

92%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, specific description that clearly states capabilities and explicit invocation triggers while drawing a clean boundary against local filesystem tools. Slight room for more natural synonym coverage in trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "list workspaces", "read or write files", "browse workspace directories" — giving comprehensive coverage of the workspace I/O domain, matching the anchor for several specific concrete actions rather than the minor-gaps level below.

5 / 5

Completeness

Explicitly answers both what ("Workspace file I/O expert" plus concrete actions) and when ("ALWAYS invoke this skill when you need to list workspaces, read or write files...") with concrete trigger phrases, satisfying the top anchor rather than the weaker-'when' level below.

5 / 5

Trigger Term Quality

Natural phrases like "list workspaces", "read or write files", and "browse workspace directories" are present, but "cross-node file operations" is somewhat jargony and a few natural synonyms (e.g., copy, upload/download, remote files) are missing, placing it just below comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

Carves a clear remote-node workspace I/O niche and explicitly redirects local-sandbox cases to standard filesystem tools, minimizing conflict risk with overlapping file skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
YaoApp/yao
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.