CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

onboard

Guides new team members through complete dev environment setup. Use when user says "help me get started", "set up my environment", "onboarding", "get started", or asks about setting up their development environment.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/onboard/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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.

A well-sequenced, highly actionable onboarding workflow with clear phases, OS-awareness, and a verification step. Its weaknesses are redundancy across the teaching/personality/principles sections and heavy inlining of per-tool setup that progressive disclosure would move into separate reference files.

Suggestions

Collapse the 'Stepwise Teaching Pattern', 'Your Personality', and 'Key Principles' sections into a single concise teaching protocol to remove the repeated 'one tool at a time / explain before and after' guidance.

Move the per-tool install command blocks (Ghostty, shell, Karabiner, power tools, lazygit, Docker, etc.) into reference files under references/ and link to them from the phase steps, leaving SKILL.md as an overview.

Add a per-phase or per-install verification checkpoint (e.g., re-run the relevant `which` check after each install) instead of relying solely on the final `./doctor.sh`.

DimensionReasoningScore

Conciseness

The bulk is concrete commands, but the ~380-line body carries noticeable redundancy — the Stepwise Teaching Pattern, Your Personality, and Key Principles sections restate the same 'one tool at a time / explain before and after' guidance — and some user-facing teaching prose pads length; not a 2 because most tokens are actionable, not a 4 because the repetition could be trimmed.

3 / 5

Actionability

Cross-platform executable commands (brew/apt/dnf/pacman, gh auth login, OS-detection and which-check scripts) are copy-paste ready and cover common cases; minor gaps where steps defer entirely to referenced skills ('use the /setup-X skill') without showing the underlying commands.

4 / 5

Workflow Clarity

Phases 0–5 are clearly sequenced with OS detection up front, a stated critical path (gh auth), a stepwise ASK-before-install gate, and a final `./doctor.sh` verification plus a self-healing PR feedback loop; not a 5 because per-install validation is absent and verification is concentrated at the end rather than at each checkpoint.

4 / 5

Progressive Disclosure

Manifests (steps/MANIFEST.yaml, skills/MANIFEST.yaml) and config.json are clearly signaled as the source of truth one level deep, but no bundled reference files exist and the bulk of per-tool install commands are inlined in the SKILL.md rather than split into separate references; structure is present but a large share of content that could live elsewhere is inline.

3 / 5

Total

14

/

20

Passed

Description

78%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.

A strong description with explicit 'what' and 'when' guidance plus natural trigger phrases in proper third-person voice. Its main limitation is specificity: it describes the broad goal rather than the concrete setup actions the skill performs.

DimensionReasoningScore

Specificity

It names the domain ('dev environment setup') and one guiding action, but 'complete dev environment setup' is broad rather than enumerating concrete actions like installing git, gh, shell, or tmux; not a level 2 because the domain and action are explicit, not minimal/generic.

3 / 5

Completeness

Both 'what' (guides new team members through complete dev environment setup) and 'when' (Use when user says...) are explicitly answered with concrete trigger phrases, matching the top anchor; not lower because neither element is missing or vague.

5 / 5

Trigger Term Quality

Natural phrases users would actually say are well covered — "help me get started", "set up my environment", "onboarding", "get started", "setting up their development environment" — with synonym variation; a few natural terms (e.g. "new to the team", "first day") are absent, keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

The new-team-member onboarding / dev environment setup niche is clear and unlikely to trigger for unrelated skills; minor overlap risk with generic setup or env-configuration skills keeps it just below a fully distinct 5.

4 / 5

Total

16

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

runpod/lazy-agent

Path

skills/onboard/SKILL.md

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.