CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

onboarding

Connect a new user's accounts, learn their real work, choose a voice, and set up concrete help.

Quality

69%

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 ./plugins/onboarding/skills/onboarding/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.

The skill delivers a clearly sequenced, highly actionable onboarding workflow with concrete endpoints, curl commands, and persistence rules — genuinely executable guidance for an instruction-only skill. Its weaknesses are repetition that inflates token cost (~177 lines where the admin/Slack material could be split into referenced files) and validation checkpoints that are explicit for admin flows but only implicit for user-facing connection steps.

Suggestions

Move the admin connector-source and Slack-bot walkthrough detail into a separate referenced file (e.g. ADMIN_SETUP.md) and keep a short decision summary in SKILL.md to cut repetition and improve progressive disclosure.

Deduplicate restated rules — e.g., collapse the three "skip silently" Slack bullets into one condition table, and merge the repeated 'never ask regular users / never infer absence' caveats.

Add an explicit validation step after the user approves OAuth consent links (e.g., re-query connected accounts before proceeding to 'Read their work') to close the workflow's remaining checkpoint gap.

DimensionReasoningScore

Conciseness

The body is mostly dense operational guidance with no basic-concept padding, but it is noticeably repetitive and could be tightened: "skip silently" appears in three consecutive Slack-bot bullets, "Never use a remembered setup state as a live check, and never ask regular users to provision it. Personal Slack or Composio access does not install the separate bot" stacks several caveats, and the connector-source checks are restated across sections. Not 4 because several sentences restate prior rules rather than adding new information.

3 / 5

Actionability

Concrete, executable guidance throughout: exact endpoints (`GET /v1/composio/toolkits`, `GET /v1/admin/slack-installation`), copy-paste curl blocks with headers and payloads, exact memory marker strings (`Onboarding: pending v2 since YYYY-MM-DD.`), and named example voices. Not 5 because key details are delegated off-file ("using the signals in the admin skill's Check connector sources section", "as described in the admin skill") and the mint curl leaves `<configured-provider>` unresolved, so a reader of this file alone cannot execute those parts.

4 / 5

Workflow Clarity

A clear four-step sequence is given up front ("1. For an org admin... 2. Choose how you should sound. 3. Read connected tools... 4. Confirm your read, then... create concrete help") and expanded in ordered sections, with most checkpoints present: "Summarize your read... and ask for corrections", "Confirm exact behavior and timing before creating anything", "Build and exercise an app locally before publishing", and "When they say it is done, re-check and continue". Not 5 because some checkpoints are implicit (e.g., no explicit verification step after the user taps the OAuth consent links) and error-recovery paths are only spelled out for the admin flows.

4 / 5

Progressive Disclosure

The body has real section structure (## State and persistence, ## 1. Connect accounts, ## Voice, ## 2. Read their work, ## 3. Confirm and help), but no bundle files exist and content that could live in separate references is inlined — the ~40-line Slack bot walkthrough/admin-check block and the voice/SOUL procedure are prime candidates. Cross-skill pointers ("read the admin skill's Guide Slack installation section") are signaled but not organized as navigable references. Not 2 because headers keep the document navigable; not 4 because the 170+ line single file mixes overview-level and deep procedural detail that belongs in split files.

3 / 5

Total

14

/

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 uses third person and names four distinct capabilities, giving it solid specificity and distinctiveness. However, it lacks any "Use when..." trigger clause (capping completeness at 3) and offers few natural trigger phrases or synonyms, so users asking to "onboard" or "set up" in their own words may not surface it.

Suggestions

Add an explicit trigger clause, e.g. "Use when onboarding is pending, the user asks to onboard or set up their account, or they want to connect apps and configure a voice."

Include natural synonyms users would actually say — "onboard", "get started", "set me up", "connect my accounts" — to improve trigger term coverage.

Make "set up concrete help" more concrete (e.g. "create recurring reminders, follow-ups, and published tool links") so the final capability reads as specific as the others.

DimensionReasoningScore

Specificity

Quotes: "Connect a new user's accounts", "learn their real work", "choose a voice", "set up concrete help" — four named actions in third person covering the skill's scope. Not 5 because "learn their real work" and "set up concrete help" are semi-generic rather than fully concrete; not 3 because more than 1-2 specific actions with only minor coverage gaps are listed.

4 / 5

Completeness

Quotes: "Connect a new user's accounts... set up concrete help" — a clear 'what' is present, but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because 'when' is entirely absent rather than just under-specified.

3 / 5

Trigger Term Quality

Quotes: "accounts", "voice", "onboarding" (via skill name only) — some natural terms a user might say, but missing common variations like "onboard me", "set me up", "connect my apps", or "get started". Not 4 because keyword coverage is thin with several natural phrasings absent; not 2 because the terms present are relevant rather than entirely generic.

3 / 5

Distinctiveness Conflict Risk

Quotes: "Connect a new user's accounts... choose a voice" — an onboarding-specific niche (account connection, voice selection, help setup) that most skills would not claim. Not 5 because without any 'when' triggers, a vague request like "help me set things up" could still route here over a generic setup skill; not 3 because the described capability set is clearly distinguishable from typical document/code/data skills.

4 / 5

Total

14

/

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

yc-software/qm

Path

plugins/onboarding/skills/onboarding/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.