CtrlK
BlogDocsLog inGet started
Tessl Logo

wiki-onboarding

Generates four audience-tailored onboarding guides in an onboarding/ folder — Contributor, Staff Engineer, Executive, and Product Manager. Use when the user wants onboarding documentation for a codebase.

64

Quality

81%

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

71%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 is a detailed, actionable, well-sequenced specification with concrete templates and validation checkpoints, scoring well on actionability and workflow clarity. Its weakest area is progressive disclosure: all four guide templates live inline in one long file with no reference files.

Suggestions

Extract each guide's detailed section spec into one-level-deep reference files (e.g., references/contributor-template.md, references/staff-engineer-template.md) and signal them from SKILL.md to reduce inline length.

Add an explicit error-recovery feedback loop in the Validation section (verify → fix → re-verify) rather than a flat checklist.

De-duplicate the Mermaid dark-mode color rules by stating them once globally and referencing them from each guide's Rules block.

DimensionReasoningScore

Conciseness

Largely lean and prescriptive using tables, terse directives, and bullet lists rather than explaining concepts Claude already knows, with minor repetition (per-guide Mermaid/citation rules restated, then re-summarized in the global Mermaid Diagram Rules section).

4 / 5

Actionability

Highly concrete guidance — exact file names, required section titles, table column specs, Mermaid diagram types, and length ranges — that is mostly executable; absence of code is appropriate for this instruction-only generator and is not penalized, with only minor gaps (e.g., conditional linked vs. local citation format).

4 / 5

Workflow Clarity

Clear sequenced process with a mandatory first step ('Source Repository Resolution (MUST DO FIRST)', 'Do NOT proceed until...') and a per-guide 'After generating each guide, verify:' validation block, leaving only minor gaps in interleaved error-recovery feedback loops.

4 / 5

Progressive Disclosure

Well-organized into clear sections and per-guide blocks, but no bundle/reference files exist and the detailed per-guide templates (e.g., the 16-section staff-engineer spec) are inlined in a single ~220-line SKILL.md that could be split into one-level-deep reference files.

3 / 5

Total

15

/

20

Passed

Description

83%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 is strong and well-structured, clearly stating both the deliverable (four named audience-specific guides in an onboarding/ folder) and an explicit trigger condition. The main improvement would be broadening trigger-term synonyms.

Suggestions

Add common trigger synonyms such as 'getting-started guides' or 'onboarding docs' so the description matches more natural user phrasings.

Name the concrete action verb once more (e.g., 'Generates and writes') to reinforce what is produced beyond the folder structure.

DimensionReasoningScore

Specificity

Lists several concrete outputs — 'four audience-tailored onboarding guides' named individually (Contributor, Staff Engineer, Executive, Product Manager) in an 'onboarding/ folder' — with only minor gaps in coverage of the actions themselves.

4 / 5

Completeness

Explicitly answers both what ('Generates four audience-tailored onboarding guides') and when ('Use when the user wants onboarding documentation for a codebase') with a concrete trigger phrase.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('onboarding documentation for a codebase') with good keyword coverage, though a few common synonyms such as 'getting-started guides' or 'onboarding docs' are absent from the description.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (audience-segmented onboarding docs for a codebase) with distinct triggers and minimal conflict risk, though it lightly overlaps with general documentation-generation skills.

4 / 5

Total

17

/

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

relative_links

Relative link issues: 5 missing, 1 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository
freightCognition/linehaulai-claude-marketplace
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.