tessl-onboarding

Interactive Tessl onboarding - install, setup, create example skill, run quality checks

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./adapters/claude-code/SKILL.md

Quality

Content

52%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 thorough, well-sequenced, actionable onboarding script, but it is noticeably verbose with inlined report templates and suffers from progressive-disclosure failures: it depends on referenced files (notably TESSL_ONBOARDING.md) that are not bundled, and inlines content that should live in separate reference files.

Suggestions

Move the full onboarding-summary.md and onboarding-report.md templates into separate bundled reference files (e.g. references/onboarding-summary.template.md) and link to them instead of inlining ~125 lines.

Actually bundle the referenced files (TESSL_ONBOARDING.md, examples/skill-builder/SKILL.md, tile.json, repo-scenarios.json) under references/ or assets/ so the cross-file navigation is not broken.

Trim per-step 'Report:' boilerplate and remove hardcoded fictional scores (85/100, 4/5) that masquerade as real outputs; describe what to report rather than printing invented results.

Dimension	Reasoning	Score
Conciseness	The ~460-line body is noticeably verbose, inlining two full markdown report templates (~125 lines, e.g. the onboarding-report.md block) plus per-step 'Report:' boilerplate and hardcoded fictional scores ('Score: 85/100', '4/5 scenarios passed (80%)') that pad the file without adding instruction.	2 / 5
Actionability	Concrete, mostly-executable commands and MCP tool calls are given throughout ('curl -fsSL https://get.tessl.io \| sh', 'tessl skill review examples/skill-builder --json', 'mcp__tessl__status'), with only minor gaps from unresolved placeholders like '<skill-package-path>' and '<eval-run-id>'.	4 / 5
Workflow Clarity	A clearly sequenced 12-step process with verification checkpoints ('tessl --version', polling auth, 'cat tessl.json') and an Error Handling section providing recovery loops, but there is a timeout inconsistency (Step 9 says 'no max timeout' while Error Handling says 'stop after 5 minutes') and some verification is shallow.	4 / 5
Progressive Disclosure	No bundle files exist, yet the body references unbundled files ('TESSL_ONBOARDING.md' for 'the complete step-by-step instructions', plus 'skill-builder/SKILL.md', 'tile.json', 'repo-scenarios.json') and inlines ~125 lines of report templates that clearly belong in separate reference files.	2 / 5
	Total	12 / 20 Passed

Description

58%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 with several concrete actions and is reasonably distinctive due to the Tessl-specific niche, but it lacks any explicit 'when to use' trigger guidance and omits common keyword synonyms.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill (e.g. 'Use when the user wants to set up or onboard Tessl').

Include natural trigger synonyms such as 'set up', 'getting started', and 'Tessl setup' alongside 'onboarding'.

Tighten 'setup' into a more specific concrete action so the action list is comprehensive.

Dimension	Reasoning	Score
Specificity	Names the domain ('Tessl onboarding') and lists several concrete actions ('install, setup, create example skill, run quality checks'), though 'setup' and 'run quality checks' remain somewhat high-level, leaving minor coverage gaps relative to a fully comprehensive action list.	4 / 5
Completeness	The 'what' is clearly stated ('install, setup, create example skill, run quality checks') but no 'Use when...' or equivalent trigger guidance is present, so per the rubric completeness is capped at 3.	3 / 5
Trigger Term Quality	Relevant natural keywords are present ('onboarding', 'install', 'setup', 'quality checks') but common variations/synonyms (e.g. 'set up', 'getting started') and an explicit trigger phrase are missing.	3 / 5
Distinctiveness Conflict Risk	The 'Tessl' qualifier carves out a clear niche with minimal conflict risk, though the generic verbs ('install, setup') create minor overlap with other setup/onboarding skills.	4 / 5
	Total	14 / 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: ekipo-user/agent-onboarding
Path: adapters/claude-code/SKILL.md
Commit: 9d0fa00

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