get-started

Guide users through the get started setup and Chrome DevTools demo.

Quality

74%

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/get-started/SKILL.md

Quality

Content

100%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 model of concise, fully actionable instruction with an explicit navigation-completion checkpoint and clean section structure appropriate for a short single-purpose skill. No bundle files are referenced, so progressive disclosure is satisfied by organization alone.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding or explanation of concepts Claude already knows — exact lines and terse conditional steps, matching the score-5 anchor 'Lean and efficient; assumes Claude's competence; every token earns its place'.	5 / 5
Actionability	It gives copy-ready exact reply text ("hey there welcome..."), explicit trigger phrases ("go on google.com" / "hey go on google.com"), and a concrete tool call ("use the chrome-devtools MCP"), matching the score-5 fully-executable anchor.	5 / 5
Workflow Clarity	The simple two-phase sequence (reply with four lines, then conditional MCP navigation) has an explicit completion checkpoint ("After the navigation completes"), and as a non-destructive simple skill it qualifies for the score-5 simple-skill exception; not capped because there is no batch/destructive operation.	5 / 5
Progressive Disclosure	Under 50 lines with no need for external references (no references/scripts/assets bundle exists) and well-organized sections (When to use, What to do, Then), matching the guideline that such skills can score 5 with just well-organized sections.	5 / 5
	Total	20 / 20 Passed

Description

48%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 a clear niche (get-started onboarding plus a Chrome DevTools demo) but uses only a generic verb and omits any explicit 'Use when' trigger clause, capping completeness and specificity. Adding concrete actions and a trigger phrase would lift it substantially.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user says "get started" or asks for the Chrome DevTools demo.'

Replace the generic 'Guide users through' with concrete actions the skill performs (e.g. 'Replies with the onboarding prompt and opens google.com via the chrome-devtools MCP').

Include natural trigger synonyms such as 'onboarding', 'getting started', and 'open google.com' to improve keyword coverage.

Dimension	Reasoning	Score
Specificity	Quotes "Guide users through the get started setup and Chrome DevTools demo" name the domain but the only action ("Guide users through") is generic, matching the score-2 anchor "Names the domain but actions are minimal or generic"; it lacks the 1-2 concrete actions needed for a 3.	2 / 5
Completeness	It gives a clear 'what' ("Guide users through the get started setup and Chrome DevTools demo") but no explicit 'Use when...' trigger, so per the guideline a missing trigger clause caps completeness at 3; not a 4 because 'when' is not present at all.	3 / 5
Trigger Term Quality	"get started" is a natural phrase a user would say, but "Chrome DevTools demo" is technical and common variations/synonyms are absent, fitting the score-3 anchor of some relevant keywords missing variations; not a 4 because coverage is thin rather than merely missing a few terms.	3 / 5
Distinctiveness Conflict Risk	The "get started" onboarding niche plus "Chrome DevTools demo" is a distinct trigger unlikely to fire for unrelated skills, matching "Mostly distinct; minor overlap risk"; not a 5 because "Guide users through" is generic and could overlap with other onboarding-style skills.	4 / 5
	Total	12 / 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/get-started/SKILL.md
Commit: 2237ca2

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