CtrlK
BlogDocsLog inGet started
Tessl Logo

workspace-guide

Workspace guide to introduce OpenWork and onboard new users.

46

Quality

48%

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

Fix and improve this skill with Tessl

tessl review fix ./ee/apps/landing/public/.well-known/agent-skills/workspace-guide/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 well-structured, mostly concise onboarding guide that branches cleanly between technical and non-technical audiences with concrete example prompts and doc links. Its main weakness is actionability: several sections describe capabilities (Skills, Plugins, MCP) without giving Claude enough specific detail to act without external lookup.

Suggestions

Trim the conversational opener ('Hi, I'm Ben and this is OpenWork. It's an open-source alternative...') to a single line to tighten token efficiency.

Expand the 'Skills and plugins' section with one concrete action each (e.g., how to install a skill, how to enable a plugin) so Claude can act without consulting external docs.

Make the closing 'two friendly next actions' an explicit checklist of two named prompts rather than a meta-instruction to invent them.

DimensionReasoningScore

Conciseness

The body is largely efficient with tight bullet lists and doc links, with only minor conversational padding ('Hi, I'm Ben and this is OpenWork'); it sits noticeably above the 'mostly efficient' midpoint but not at the lean level-5 ideal.

4 / 5

Actionability

It provides concrete example prompts and explicit setup steps with real URLs, but as an instruction-only skill the guidance is incomplete in places (e.g., 'Skills add new capabilities' without specifics), landing at 'some concrete guidance but incomplete' rather than mostly-executable level 4.

3 / 5

Workflow Clarity

The branching flow opens with a clarifying question gate, then sequences distinct non-technical vs technical paths with clear next actions; no destructive/batch validation is required, and the only gap is minor handoff detail, fitting 'clear sequence with most checkpoints present'.

4 / 5

Progressive Disclosure

At under 50 lines with well-organized section headers and no need for external references, the simple-skill exception applies and the structure is easy to navigate, matching the level-5 anchor for simple skills.

5 / 5

Total

16

/

20

Passed

Description

25%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 is too vague and generic to serve as an effective skill trigger: it names a domain (workspace onboarding) but specifies no concrete actions or natural trigger phrases. It lacks any explicit 'Use when...' guidance, which limits discoverability and distinctiveness.

Suggestions

Add a 'Use when...' clause naming concrete trigger phrases a user would say, e.g. 'Use when onboarding a new user to OpenWork or introducing the workspace for the first time.'

Replace generic verbs ('introduce', 'onboard') with concrete capabilities, e.g. 'Guides new users through OpenWork setup, explains skills/plugins/MCP, and suggests first actions to try.'

Sharpen distinctiveness by naming the OpenWork-specific concepts (Skills, Plugins, MCP servers) that separate this skill from generic onboarding guidance.

DimensionReasoningScore

Specificity

The phrase 'introduce OpenWork and onboard new users' names the domain but offers only generic actions (introduce, onboard) with no concrete capabilities, matching the 'names domain but actions minimal' anchor and falling below level 3 which requires 1-2 concrete actions.

2 / 5

Completeness

It gives a vague 'what' (introduce/onboard) with no 'Use when...' trigger guidance, and the missing trigger clause caps completeness at 3; the vague-what/no-when fit lands it at the 'vague what and no when' anchor below that cap.

2 / 5

Trigger Term Quality

'Workspace guide' and 'onboard new users' are a couple of generic keywords; the natural phrases a user would actually say when needing this skill are missing, matching the 'one or two generic keywords' anchor.

2 / 5

Distinctiveness Conflict Risk

The description is very broad and would overlap with many general onboarding or workspace skills, matching the 'very broad; high overlap risk' anchor rather than the somewhat-specific level 3.

2 / 5

Total

8

/

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
different-ai/openwork
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.