CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

onboarding

Personalize COG for your workflow - creates profile, interests, and watchlist files with guided setup (run this first!)

Quality

70%

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 ./.claude/skills/onboarding/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%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-structured, highly actionable onboarding workflow with clear sequencing, explicit confirmation checkpoints, error recovery, and success criteria. The main weaknesses are mild verbosity (Philosophy/Privacy sections and repeated file listings) and one template inlined where the existing references file should carry it.

Suggestions

Move the verbatim MY-INTEGRATIONS.md template from step 5.6 into references/profile-templates.md alongside the other profile document templates.

Trim the 'Philosophy' and 'Benefits of markdown storage' sections, which explain concepts Claude already knows; a one-line rationale suffices.

Consolidate the file-path listings (Success Criteria, Privacy & Data) into a single section to avoid repeating the same paths three times.

DimensionReasoningScore

Conciseness

The body is mostly efficient, concrete guidance, but the 'Philosophy' and 'Privacy & Data' sections explain benefits of markdown storage Claude already knows and restate file paths listed elsewhere, and the full MY-INTEGRATIONS.md template is inlined rather than referenced. Not 4: the redundant sections and repeated file lists are more than minor trims.

3 / 5

Actionability

Verbatim copy-paste dialogue scripts, an extraction table with concrete patterns ('I'm Alex, a PM at a fintech startup'), exact file paths, and full directory trees make the guidance mostly executable. Not 5: minor gaps remain, such as unspecified project-slug format and loosely defined fuzzy matching in role-pack matching.

4 / 5

Workflow Clarity

Steps 1–9 are clearly sequenced with explicit validation checkpoints ('Wait for confirmation' before file generation), a success-criteria checklist, and error-handling feedback loops (directory failure → report/manual instructions/continue; mid-exit → partial profile with resume). This matches the anchor for explicit validation, error recovery, and checklists.

5 / 5

Progressive Disclosure

Both references (references/profile-templates.md, references/welcome-guide.md) are real files, clearly signaled, and one level deep. Not 5: the complete MY-INTEGRATIONS.md template is inlined in step 5.6 even though references/profile-templates.md exists precisely to hold the profile document templates.

4 / 5

Total

16

/

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 a clear what (creates profile/interests/watchlist files) tied to the COG niche, but lacks an explicit 'Use when...' trigger clause and omits the skill's own name ('onboarding') and other natural trigger phrases. Coverage of the skill's actual outputs is partial.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user is new to COG, says "onboarding", "set up COG", or wants to update their profile or interests.'

Include the word 'onboarding' and other natural variations ('new user setup', 'get started with COG') so the description matches phrases users actually say.

Mention the remaining outputs (integrations file, welcome guide, project directories) to make the 'what' comprehensive.

DimensionReasoningScore

Specificity

The description names the domain (COG personalization) and lists concrete actions ('creates profile, interests, and watchlist files'), but coverage is not comprehensive — the skill also handles integrations, role-pack matching, directory creation, and a welcome guide, none of which are mentioned — and 'guided setup' is generic.

3 / 5

Completeness

The 'what' is clear ('creates profile, interests, and watchlist files with guided setup'), but the only 'when' guidance is '(run this first!)', which is a sequencing directive rather than an explicit trigger clause, capping completeness at 3.

3 / 5

Trigger Term Quality

Some relevant keywords are present ('personalize', 'setup', 'profile'), but the most natural user phrase — 'onboarding' — is missing entirely, along with common variations like 'new user', 'get started', or '/onboarding'.

3 / 5

Distinctiveness Conflict Risk

'Personalize COG' carves a clear niche tied to a specific system, making confusion with unrelated skills unlikely. It falls short of 5 because the trigger phrasing is not distinct enough to rule out overlap with other COG configuration/profile skills.

4 / 5

Total

13

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

huytieu/COG-second-brain

Path

.claude/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.