CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

onboarding

Guides a first-time omo user through setup and the core workflow. Use when a new user asks to get started with omo.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./packages/omo-senpi/skills/onboarding/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

An unusually rigorous instruction skill: every lane is executable with exact tools, commands, formulas, consent gates, and decline paths, and the multi-step flow is sequenced with explicit checkpoints. Its weaknesses are duplicated phrasing across sections and a monolithic structure that inlines a long catalog and a computation spec that belong in reference files.

Suggestions

Move the baked feature catalog (16 bullets) and the lane 4 value-mapping computation rules into a references/ file (e.g. references/catalog.md and references/value-mapping.md), keeping a short summary plus a pointer in SKILL.md.

State the 'omo --onboard on OmO Native vs senpi --onboard on a plain senpi install' install-name rule once in the Purpose section and reference it from the tour bullet and lane 6 instead of repeating it verbatim.

Trim conversational asides in the tour catalog (e.g. 'don't try to memorize the workflows up front — you'll pick them up by using them') to tighten the body without losing the relayed content.

DimensionReasoningScore

Conciseness

The body is dense and operational with no filler explaining concepts Claude already knows, but it duplicates content across sections: the 'omo --onboard on OmO Native / senpi --onboard on a plain senpi install' disambiguation appears verbatim in both the tour catalog and lane 6, and the Value summary quoting rule is stated in both Purpose and lane 4. This matches anchor 3 ('mostly efficient but... could be tightened') rather than anchor 4's 'minor instances'.

3 / 5

Actionability

Guidance is fully concrete throughout: exact tool calls ('call onboarding_understand with consent: true', 'call onboarding_memory_apply with exactly the ids they picked'), exact commands ('git rev-parse --show-toplevel', 'omo setup --yes'), exact arithmetic formulas for cost, savings, and caching rate with rounding rules, exact file paths, and a copy-paste seed line template. Nothing remains at the level of vague direction.

5 / 5

Workflow Clarity

The six lanes are explicitly ordered in the Purpose section, entry modes are defined, each opt-in lane has a defined decline fallback ('If they say no, skip to lane 3'), consent checkpoints are explicit ('Show the plan and WAIT for the user to accept it'), and lane 6 has an ordered three-gate eligibility check with silent-skip behavior. Error paths are handled (pricing API unavailable, malformed timestamps, understanding falling back to scan-only).

5 / 5

Progressive Disclosure

Section structure is good — one header per lane plus Purpose and Entry modes — but this is a ~295-line single file with no bundle files at all, and clearly separable content is inlined: the 16-item baked feature catalog and the detailed value-mapping computation algorithm (attribution rules, price resolution, aggregation) would each fit naturally in a reference file. This matches anchor 3 ('some structure but... content that should be separate is inline') rather than anchor 2, since navigation is easy.

3 / 5

Total

16

/

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.

A serviceable description with a clear product-scoped trigger and both 'what' and 'when' present, held back by a vague 'core workflow' phrase and thin trigger-term coverage. Listing two or three concrete onboarding activities and adding synonyms like 'onboarding' or 'tour' would lift it substantially.

Suggestions

Replace the vague 'setup and the core workflow' with two or three concrete activities, e.g. 'Runs a feature tour, imports settings from other coding agents, analyzes past sessions, and proposes project documentation setup.'

Broaden the trigger clause with natural synonyms: 'Use when a new user asks to get started with omo, wants the onboarding tour, or says they are new to omo.'

State the opt-in nature of the migration and session-analysis steps so the description's scope matches what the skill actually does.

DimensionReasoningScore

Specificity

The description names the domain ('first-time omo user', 'setup') but the actions are thin — 'guides... through setup and the core workflow' offers only one semi-concrete action plus a generic 'core workflow'. It is not a 4 because it never lists several specific actions (e.g. feature tour, migration import, session analysis), and not a 2 because the domain and one concrete action are present.

3 / 5

Completeness

Both parts are present: a 'what' ('Guides a first-time omo user through setup and the core workflow') and an explicit 'when' ('Use when a new user asks to get started with omo'). It falls short of anchor 5 because the 'what' is vague about what the workflow actually contains and the trigger guidance covers only one phrasing.

4 / 5

Trigger Term Quality

'Use when a new user asks to get started with omo' includes the natural phrase 'get started', but misses common variations users would say such as 'onboarding', 'tour', 'setup help', or 'introduction to omo'. Coverage exists but synonyms are missing, matching anchor 3 rather than the fuller coverage of anchor 4.

3 / 5

Distinctiveness Conflict Risk

The trigger is anchored to the product name ('get started with omo') and scoped to first-time users, giving a clear niche with minimal overlap risk against other skills. The generic 'get started' phrase alone would be a 3-4, but the product scoping makes conflicts unlikely.

5 / 5

Total

15

/

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

code-yeongyu/oh-my-openagent

Path

packages/omo-senpi/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.