workspace-guide

Workspace guide to introduce OpenWork and onboard new users.

Quality

53%

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

Fix and improve this skill with Tessl

tessl review fix ./.opencode/skills/workspace-guide/SKILL.md

Quality

Content

78%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 body is a lean, well-structured onboarding guide that branches cleanly on user technical level and provides concrete example prompts plus real documentation links. Its main limitation is minor high-level phrasing in a couple of setup steps rather than any structural or verbosity problem.

Dimension	Reasoning	Score
Conciseness	The ~40-line body is efficient and the product-specific lines ("open-source alternative to Claude's cowork") convey info Claude does not already know rather than padding; only minor conversational filler like "Hi, I'm Ben" could be trimmed, matching anchor 4; not a 5 because of that slight filler, not a 3 because there is no unnecessary concept explanation.	4 / 5
Actionability	It gives concrete example prompts ("Summarize the files in this workspace.") and numbered steps with real URLs ("Install OpenCode from opencode.ai", docs links), which is mostly executable guidance with minor high-level gaps like "Configure providers there", fitting anchor 4; not a 5 because a few steps stay high-level, not a 3 because the guidance is concrete and usable as-is.	4 / 5
Workflow Clarity	The flow is explicitly sequenced ("Before we start, use the question tool to ask...", branch by technical level, "End with two friendly next actions"), giving a clear branching sequence with well-delineated sections, matching anchor 4; no validation checkpoints are needed since there are no destructive or batch operations, so it is not penalized to 3 and not raised to 5 as no feedback loop is relevant.	4 / 5
Progressive Disclosure	At under 50 lines with no bundle files needed, the content is well-organized into clear sections and uses one-level-deep external doc URLs (e.g. https://opencode.ai/docs/skills) as signaled references; per the simple-skill exception this matches anchor 5, and it is not a 4 because organization and reference signaling are clean with no inlined bulk that belongs elsewhere.	5 / 5
	Total	17 / 20 Passed

Description

28%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 names the domain and target audience but relies on generic verbs and lacks any "Use when..." trigger guidance, so it under-specifies both what concretely happens and when Claude should invoke it. Its strongest aspect is a modest niche tie to OpenWork onboarding that limits conflict risk.

Suggestions

Add concrete actions the skill performs, e.g. 'Introduces OpenWork, gauges the user's technical level, and delivers a tailored onboarding walkthrough.'

Append a 'Use when...' clause with natural trigger phrases, e.g. 'Use when a new user asks to get started with OpenWork, wants an intro to the workspace, or needs onboarding.'

Include common synonyms/users' phrasings like 'get started', 'show me around', and 'onboard' to improve trigger-term quality.

Dimension	Reasoning	Score
Specificity	Quotes "introduce OpenWork and onboard new users" name the domain (OpenWork, new users) but the actions are minimal and generic rather than concrete, matching the anchor 'Names the domain but actions are minimal or generic'; it is above a 1 because it does name a domain and verbs, but not a 3 since no concrete actions like 'extract' or 'fill' are present.	2 / 5
Completeness	It gives a vague "what" ("introduce OpenWork and onboard new users") and has no "when"/"Use when..." clause at all; the missing trigger guidance caps completeness at 3, and with a vague what plus no when this matches anchor 2 rather than 3's clear-what bar.	2 / 5
Trigger Term Quality	Phrases like "Workspace guide" and "onboard new users" provide one or two generic keywords, but the natural trigger phrases a user would say (e.g. "help me get started with OpenWork", "show me around") are missing, fitting anchor 2; not a 3 because common variations and synonyms are absent.	2 / 5
Distinctiveness Conflict Risk	Tying the skill to OpenWork and the onboarding niche makes it somewhat specific, but "Workspace guide" is broad and could overlap with similar general-purpose skills, matching anchor 3; it is not a 4 because the niche is not sharply distinct and not a 2 because the OpenWork/onboarding tie narrows it.	3 / 5
	Total	9 / 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: trackdubllc/Babel-Player-Alpha
Path: .opencode/skills/workspace-guide/SKILL.md
Commit: 2237ca2

Reviewed: 6 hours 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.