CtrlK
BlogDocsLog inGet started
Tessl Logo

initialize

Setup, install, and onboard new developers to Reactive Data Client monorepo - nvm, yarn, build, test, getting started guide

62

Quality

74%

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 ./.cursor/skills/initialize/SKILL.md
SKILL.md
Quality
Evals
Security

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 content is a well-structured, actionable onboarding guide with efficient steps and clear navigation. Its only real gap is the absence of explicit error-recovery feedback loops in the workflow.

Suggestions

Add brief failure-handling guidance for key steps, e.g. what to check if 'yarn install' fails or 'yarn build' reports errors.

Trim minor gloss lines such as 'This installs all workspace dependencies' and 'This runs TypeScript compilation and Babel transforms' that restate what the command does.

Make the checklist checkpoints more active by linking each item to a verify command, e.g. 'yarn build succeeds' -> run `yarn build` and confirm no errors.

DimensionReasoningScore

Conciseness

The body is efficient with short imperative steps, a commands table, and a checklist, assuming Claude's competence; a few gloss lines like 'This installs all workspace dependencies' could be trimmed but are minor.

4 / 5

Actionability

Mostly executable guidance with copy-paste-ready commands (nvm install, corepack enable, yarn install/build/test) and a full commands table; the directional 'Project familiarization' step keeps it just short of fully copy-paste-ready.

4 / 5

Workflow Clarity

A clear numbered sequence (prerequisites -> install -> build -> test -> familiarize) with an onboarding checklist as checkpoints, but it lacks explicit validate/fix/retry feedback loops and failure-handling guidance.

4 / 5

Progressive Disclosure

Well-organized sections with clearly signaled, one-level-deep references (docs, Discord, CONTRIBUTING.md, examples/) and no nested or buried references; appropriate for a concise single-purpose onboarding skill.

5 / 5

Total

17

/

20

Passed

Description

70%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 specific and distinct, naming the target monorepo and concrete onboarding actions. Its main weakness is the missing explicit 'Use when...' trigger guidance, which caps completeness at 3.

Suggestions

Add an explicit trigger clause, e.g. 'Use when onboarding a new developer to the Reactive Data Client monorepo or when setting up a local dev environment for it.'

Expand action phrases from tool names to concrete verbs, e.g. 'Install dependencies, build all packages, and run the test suite' rather than 'nvm, yarn, build, test'.

Include natural user synonyms such as 'set up', 'contributing', and 'new developer' to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the Reactive Data Client monorepo domain and lists several concrete actions/tools (nvm, yarn, build, test, onboard), with only minor gaps in fully fleshing out each action phrase.

4 / 5

Completeness

The description gives a clear 'what' (setup/install/onboard the monorepo) but lacks an explicit 'Use when...' trigger clause, so 'when' is only weakly implied; per guidelines this caps completeness at 3.

3 / 5

Trigger Term Quality

Good coverage of natural onboarding vocabulary (install, onboard, getting started, yarn, build, test), but it leans on technical-tool terms and misses common variations a user might say (set up, contributing, new developer).

4 / 5

Distinctiveness Conflict Risk

Tied to a specific named monorepo (Reactive Data Client) with specific tooling (nvm, yarn, build, test), giving it a clear niche with minimal overlap risk against other skills.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
reactive/data-client
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.