CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

welcome

First-touch experience for new Ouroboros users

Quality

57%

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

Fix and improve this skill with Tessl

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

Quality

Content

70%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 highly actionable, rigorously sequenced onboarding skill whose fatal flaw is token efficiency: the same readiness-check and YAML-parsing code is inlined two to three times instead of being extracted to a bundle script. Structure and references are decent but the body carries far too much executable weight for a SKILL.md.

Suggestions

Move the `ouroboros_python` resolver and the YAML/TOML readiness checks into `scripts/` files and invoke them by path; the fallback `load_yaml` parser is repeated three times and the Codex readiness script twice.

Have the Setup Gate reuse the readiness values already computed by the Pre-Check (re-running standalone gates only when the Pre-Check did not run), eliminating the duplicated gate scripts.

Trim the fallback YAML parser to a single shared script and reference it, keeping SKILL.md as an overview of the onboarding flow rather than a code repository.

DimensionReasoningScore

Conciseness

The body duplicates large code blocks verbatim: the fallback `load_yaml` parser appears three times and the Codex readiness check twice, padding the skill with hundreds of redundant tokens. It does not explain known concepts (which would warrant 1), but it is noticeably verbose with several duplicated/padded sections.

2 / 5

Actionability

Every step is copy-paste ready: complete bash/python snippets (`ouroboros_python` resolver, readiness gates, atomic config rewrite), exact prompts with option labels, and exact commands (`gh api -X PUT /user/starred/Q00/ouroboros`, `uvx ... ouroboros tui monitor`) covering common cases including fallbacks.

5 / 5

Workflow Clarity

The flow is clearly sequenced (Pre-Check → Routing → Setup Gate → Steps 1–4 → footer) with explicit validation: readiness gates print verdicts, the config rewrite must be confirmed successful before the marker is recorded, and interrupted-migration recovery is handled. Routing after the pre-check enumerates every outcome.

5 / 5

Progressive Disclosure

Sections are well-organized and the references to `../setup/SKILL.md` and `../config/SKILL.md` are clearly signaled one level deep, but roughly 400 lines of inline Python (a shell resolver plus duplicated YAML/TOML parsers) clearly belong in a `scripts/` file rather than in SKILL.md.

3 / 5

Total

15

/

20

Passed

Description

28%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 identifies the audience and product but says nothing about what the skill actually does or when it applies — no actions, no trigger terms, no "Use when" guidance. It reads like a title, not a capability description.

Suggestions

List concrete actions, e.g., "Runs interactive onboarding for new Ouroboros users: checks runtime setup readiness, guides first-run configuration (Claude Code or Codex), and records completion in ~/.ouroboros/prefs.json."

Add explicit trigger guidance such as "Use when the user first runs /ouroboros:welcome or asks to get started with, set up, or onboard to Ouroboros."

Include natural trigger keywords ("welcome", "onboarding", "getting started") rather than the abstract "first-touch experience" phrasing.

DimensionReasoningScore

Specificity

"First-touch experience for new Ouroboros users" names the domain (onboarding for a specific product's new users) but offers no concrete actions — "first-touch experience" is a state, not an operation. It is not 3 because no action is described, and not 1 because the domain and audience are named.

2 / 5

Completeness

The "what" is vague ("first-touch experience" does not say what the skill does) and there is no "when" clause at all. This is below the anchor-3 pattern, which requires a clear "what".

2 / 5

Trigger Term Quality

Only "new users" and "first-touch" appear; the natural phrases a user would actually say ("welcome", "onboarding", "getting started", "set up Ouroboros") are absent from the description.

2 / 5

Distinctiveness Conflict Risk

Being anchored to the product name distinguishes it from unrelated skills, but "first-touch experience for new users" broadly overlaps the setup/config sibling skills it routes to, so it is only somewhat specific.

3 / 5

Total

9

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (710 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

Q00/ouroboros

Path

skills/welcome/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.