CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

using-life-os

Entry point skill - introduces available Life OS skills, provides command reference, and guides users through the system

Quality

65%

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 ./skills/using-life-os/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 succeeds as an actionable index: commands are concrete, the getting-started sequence is clear, and navigation between sibling skills is well explained. Its main weaknesses are significant redundancy across four sections that repeat the same commands and marketing fluff, which roughly doubles the token cost of the guidance it delivers.

Suggestions

Consolidate the duplicated material: merge Command Reference with Example Workflows, and Getting Started with the First-Time Setup workflow, keeping each command shown once.

Trim marketing language ('works seamlessly across devices', 'truly useful throughout the day', 'Welcome to Life OS... 🚀') that adds tokens without guidance.

Consider moving the full command reference and example workflows to a references/ file, keeping SKILL.md as a lean overview with clearly signaled one-level-deep links.

DimensionReasoningScore

Conciseness

Three sections largely duplicate others (Overview bullets restate Available Skills, Command Reference repeats in Example Workflows, Getting Started repeats the First-Time Setup workflow) and marketing padding ('works seamlessly', 'truly useful throughout the day', the rocket sign-off) adds tokens without guidance — noticeably verbose rather than just needing tightening.

2 / 5

Actionability

Concrete copy-paste '/skill' commands paired with realistic example prompts ('Plan my meals for the week - I'm vegetarian, budget is $150, prefer quick dinners') cover the common cases; a few prompts remain bracketed templates ('[dietary preference]', '[number]'), keeping it just short of fully executable.

4 / 5

Workflow Clarity

Getting Started provides a clearly sequenced 5-step path (assessment, briefings, meal plan, grocery list, ongoing usage) and Example Walkthroughs reinforce it; no validation checkpoints are needed for a navigation-only skill with no destructive or batch operations, but the multi-step workflow lacks the explicit checkpoints of anchor 5.

4 / 5

Progressive Disclosure

The body is well-organized into clear sections (Overview, Available Skills, Command Reference, Getting Started, Integration, Workflows, Tips) with no nested or buried references, but at ~200 lines with everything inline — including a command reference and workflow examples that could live in separate files — it exceeds the under-50-line exception for a sections-only score of 5.

4 / 5

Total

14

/

20

Passed

Description

53%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 communicates the skill's index/entry-point role and names Life OS explicitly, but it omits any 'Use when' trigger guidance and leans on generic phrasing ('guides users through the system') instead of concrete capabilities or natural user phrases. It is a serviceable but below-average description that would rarely be selected by a user's actual words.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when getting started with Life OS, exploring available skills, or asking what Life OS can do') to raise completeness above 3.

Replace 'guides users through the system' with concrete capabilities (e.g., 'lists available skills with use cases, provides command reference, and walks through first-time setup').

Include natural trigger terms users would say, such as 'getting started', 'Life OS overview', 'what can Life OS do', to improve trigger term quality.

DimensionReasoningScore

Specificity

Names the domain ('available Life OS skills', 'command reference') and two concrete actions, but 'guides users through the system' is generic filler and the system's actual capabilities (meal planning, tasks, briefings) are absent, matching the '1-2 concrete actions, not comprehensive' anchor rather than the minor-gaps level above.

3 / 5

Completeness

The 'what' is clear (introduces skills, provides command reference) but there is no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

'Life OS' and 'command reference' are relevant keywords, but the natural phrases a user would actually say when needing this skill ('getting started', 'what can Life OS do', 'how to use Life OS') are missing, so coverage falls short of anchor 4 while exceeding the single-generic-keyword level of anchor 2.

3 / 5

Distinctiveness Conflict Risk

Explicitly naming 'Life OS' and the entry-point role makes it mostly distinct from unrelated skills; the residual overlap with sibling Life OS skills is inherent to an index skill, fitting anchor 4 better than the vaguer anchor 3.

4 / 5

Total

13

/

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

kmondlane/ExoMind

Path

skills/using-life-os/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.