Name: initialize
Rating: 62.4 (1 reviews)
Author: reactive

initialize

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

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 ./.agents/skills/initialize/SKILL.md

Quality

Content

82%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 lean, actionable, and well-structured with concrete commands and a verification checklist. Main gaps are explicit validation checkpoints within the step sequence and a couple of trimmable explanatory lines.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands and brief bullets; a few explanatory lines like "This installs all workspace dependencies" could be trimmed.	4 / 5
Actionability	Copy-paste-ready commands (`nvm install`, `corepack enable`, `yarn install`, `yarn build`, `yarn test`) cover the common onboarding cases, plus a command reference table.	5 / 5
Workflow Clarity	Steps are clearly sequenced 1–6 and an onboarding checklist provides verification, but there are no explicit inline validation checkpoints or error-recovery feedback loops.	4 / 5
Progressive Disclosure	Well-organized into Overview, Steps, Checklist, Commands, and Resources with only one-level links; the inline package-structure listing is reasonable but the skill slightly exceeds the simple-skill line count.	4 / 5
	Total	17 / 20 Passed

Description

66%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 clearly states what the skill does and names specific tooling, but omits any explicit "when to use it" trigger guidance. Adding a Use-when clause would lift the completeness and trigger-term dimensions.

Suggestions

Append a trigger clause, e.g. "Use when a new developer needs to set up, install, or onboard to the Reactive Data Client monorepo."

Include natural synonyms users might say such as "getting started", "set up", or "first time" to broaden trigger coverage.

Mention the test framework (Jest) or build tooling in the description to strengthen specificity.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions and specific tooling — "Setup, install, and onboard", "nvm, yarn, build, test" — but leaves minor coverage gaps (no test-framework specifics).	4 / 5
Completeness	The "what" is clear (onboard to the Reactive Data Client monorepo) but there is no "Use when..." trigger clause, capping completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Natural terms like "setup", "install", "onboard new developers", "build", "test", and "getting started guide" are present, though a few common synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	Tied to the named "Reactive Data Client monorepo" gives it a clear niche with minimal conflict risk, though generic setup verbs leave slight overlap with general dev-onboarding skills.	4 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: reactive/data-client
Path: .agents/skills/initialize/SKILL.md
Commit: 44cb7e6

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