CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wiki-onboarding

Generate two complementary onboarding documents that together give any engineer — from newcomer to principal — a complete understanding of a codebase. Use when user asks for onboarding docs or getting-started guides, user runs /deep-wiki, or user wants to help new team members understand a codebase.

Quality

76%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/wiki-onboarding/SKILL.md

The canonical home for this skill is wiki-onboarding in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

65%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 reasonably lean, structured checklist that clearly specifies what both onboarding guides must contain, undermined by missing validation steps, zero output examples, and a dangling cross-skill reference. The duplicated When to Use section is obvious dead weight.

Suggestions

Delete the trailing duplicate 'When to Use' section and its filler sentence; the triggers are already stated in the opening section and the frontmatter description.

Add validation checkpoints to the workflow, e.g., 'After drafting each guide, verify every (file_path:line_number) citation resolves to real code and each Mermaid diagram renders' with a fix-and-retry loop.

Resolve the dangling '(see wiki-vitepress skill)' reference — either inline the dark-mode color values, point to a concrete reference file in the bundle, or drop the dependency.

DimensionReasoningScore

Conciseness

The body is a lean section checklist with no explanations of concepts Claude already knows, but it wastes tokens on a duplicated "When to Use" section and the pure-filler sentence "This skill is applicable to execute the workflow or actions described in the overview.", fitting 'efficient; minor instances that could be trimmed' rather than the fully lean anchor at 5.

4 / 5

Actionability

Concrete requirements like "Every claim backed by (file_path:line_number) citation", "Minimum 3 Mermaid diagrams", and the exact build-file-to-language table give mostly specific guidance for an instruction-only skill, but there are no output examples and the dangling "(see wiki-vitepress skill)" pointer leaves minor gaps, keeping it below 5.

4 / 5

Workflow Clarity

The sequence (detect language, then produce Guide 1 and Guide 2) is present but implicit, and there are no validation checkpoints such as verifying cited file:line references resolve or Mermaid diagrams render — matching 'steps listed but validation gaps' rather than anchor 4, which requires most checkpoints present.

3 / 5

Progressive Disclosure

The body is well-sectioned with clear headers, but the only external reference — "All Mermaid diagrams use dark-mode colors (see wiki-vitepress skill)" — is not a resolvable path or linked file, and the duplicated When to Use section shows organization could be better, fitting anchor 3 rather than the mostly-clear anchor at 4.

3 / 5

Total

14

/

20

Passed

Description

78%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 strong description that clearly states what it produces and when to use it, with natural trigger phrases and a distinct niche. Its only weakness is modest action specificity — it announces the artifact but not the substance of the two guides.

DimensionReasoningScore

Specificity

"Generate two complementary onboarding documents" names the domain and one concrete action with audience detail, but does not enumerate several specific actions — it matches 'names domain and 1-2 concrete actions, but not comprehensive' rather than the multi-action anchor at 4.

3 / 5

Completeness

The description explicitly answers both what ("Generate two complementary onboarding documents that together give any engineer — from newcomer to principal — a complete understanding of a codebase") and when ("Use when user asks for onboarding docs or getting-started guides, user runs /deep-wiki, or user wants to help new team members understand a codebase") with concrete trigger phrases, matching the anchor at 5 exactly.

5 / 5

Trigger Term Quality

Natural phrases like "onboarding docs", "getting-started guides", "help new team members understand a codebase", and the "/deep-wiki" command give good coverage, but a few natural synonyms (e.g., "onboarding documentation", "codebase walkthrough", "developer onboarding") are missing, so it falls short of the comprehensive anchor at 5.

4 / 5

Distinctiveness Conflict Risk

The onboarding-docs niche with a distinct "/deep-wiki" trigger is mostly distinct with only minor overlap risk against closely related documentation-generation skills, fitting anchor 4 rather than the minimal-conflict anchor at 5.

4 / 5

Total

16

/

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

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/wiki-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.