CtrlK
BlogDocsLog inGet started
Tessl Logo

onboarding

Onboard a user to Wren Engine end-to-end. Walks through environment checks, project scaffolding, connection configuration via .env, and first query. Use when: user wants to install Wren Engine, set up a new data source connection, or bootstrap a new project from scratch. Triggers: '/wren-onboarding', 'install wren', 'set up wren engine', 'wren onboarding', 'connect new database to wren'.

74

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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-engineered onboarding workflow with executable commands, strong validation checkpoints and feedback loops, and good external-reference discipline. Slight verbosity and a few inline sections that could be deferred keep conciseness and progressive disclosure just below the top anchor.

Suggestions

Tighten repeated connect.md cross-references (per-datasource notes and troubleshooting are linked multiple times) to a single canonical pointer.

Move the inline 'On error' troubleshooting bullet list entirely to connect.md#troubleshooting, keeping only the fallback 'I hit an error I don't know how to fix' message inline.

Consolidate the 'Mode of operation' rules and per-step guardrails to reduce overlap with rules restated inside individual steps.

DimensionReasoningScore

Conciseness

Dense and operational, assuming Claude's competence (no explaining of Python/venv/pip basics), with minor repeated cross-references to connect.md and operational-rule framing that could be trimmed slightly.

4 / 5

Actionability

Fully executable concrete commands throughout — `wren docs connection-info <ds> --format md`, `wren profile add`, `wren context init` — plus a copy-paste-ready postgres .env template covering the common case.

5 / 5

Workflow Clarity

Numbered Preflight→Step 5 sequence with explicit validation checkpoints ('Only after the user replies done', success/warning branching) and feedback loops (validate→fix→retry via `wren context validate`/`build`) plus a hard guard against querying before MDL.

5 / 5

Progressive Disclosure

Clear overview that pushes detail to one-level-deep reference docs with explicit rationale ('never duplicate their content') and a cross-skill routing table, but the inline 'On error' section and troubleshooting list could be more fully deferred to keep the overview lean.

4 / 5

Total

18

/

20

Passed

Description

96%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, third-person description that concretely states capabilities, provides natural trigger phrases, and explicitly answers both what and when. Minor overlap risk with sibling Wren skills keeps distinctiveness just below the top anchor.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'environment checks, project scaffolding, connection configuration via .env, and first query' — giving comprehensive coverage of what onboarding entails.

5 / 5

Completeness

Explicitly answers both 'what' (end-to-end onboarding via checks/scaffolding/config/first query) and 'when' (a dedicated 'Use when:' clause with concrete trigger scenarios).

5 / 5

Trigger Term Quality

Natural trigger phrases users would actually say — 'install wren', 'set up wren engine', 'wren onboarding', 'connect new database to wren' — plus a slash-command trigger, giving comprehensive coverage.

5 / 5

Distinctiveness Conflict Risk

Clear Wren-Engine-onboarding niche with distinct triggers, but minor overlap risk with closely related sibling skills (generate-mdl, usage) that the body's routing table only partially resolves.

4 / 5

Total

19

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
Canner/WrenAI
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.