CtrlK
BlogDocsLog inGet started
Tessl Logo

workspace-guide

Workspace guide to introduce OpenWork and onboard new users.

54

Quality

60%

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

85%

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, actionable onboarding guide that respects token budget and leads users through a clear branch-on-expertise workflow, with only minor conversational padding in the intro.

DimensionReasoningScore

Conciseness

The body is mostly lean and avoids explaining concepts Claude already knows, but the first-person conversational opener ("Hi, I'm Ben and this is OpenWork...") adds tokens that could be tightened without losing clarity.

2 / 3

Actionability

It provides concrete, copy-ready guidance: specific try-commands, a numbered install/configure/start sequence, and direct documentation URLs, all immediately executable for an onboarding skill.

3 / 3

Workflow Clarity

For a simple single-purpose skill, the flow is clear and well-sequenced: branch on technical level, give tailored next steps, and close with concrete follow-up actions; no destructive operation requires validation checkpoints here.

3 / 3

Progressive Disclosure

At under 50 lines with no external references needed, the content is organized into clearly labeled sections (non-technical vs technical, skills/plugins/MCP) that serve as an effective overview with easy navigation.

3 / 3

Total

11

/

12

Passed

Description

35%

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 conveys a general purpose but lacks concrete capability verbs, natural trigger terms, and an explicit "Use when..." clause, leaving it vague about when Claude should invoke it.

Suggestions

Replace the single abstract action with concrete capabilities, e.g. "Introduces OpenWork, explains skills/plugins/MCP setup, and walks new users through their first session."

Add an explicit trigger clause: "Use when a user is new to OpenWork, asks to get started, or needs help setting up skills, plugins, or MCP servers."

Include natural user-facing terms like "onboarding", "getting started", and "first session" so the description matches how users actually ask for help.

DimensionReasoningScore

Specificity

"introduce OpenWork and onboard new users" names a domain (onboarding) but offers only one abstract action rather than a list of concrete capabilities, sitting between vague and comprehensive.

2 / 3

Completeness

It states what the skill does (introduce/onboard) but gives no "when to use" guidance, and the rubric caps completeness at 2 when a "Use when..." clause is missing.

2 / 3

Trigger Term Quality

No natural trigger keywords a user would say appear; the description lacks terms like "onboarding", "getting started", or "introduction", relying on generic phrasing rather than natural request language.

1 / 3

Distinctiveness Conflict Risk

Tying it to OpenWork adds some specificity, but the stated intent (workspace guide / onboarding) is generic enough to overlap with other onboarding or orientation skills.

2 / 3

Total

7

/

12

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.