CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

60

Quality

71%

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

51%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-organized specification of two onboarding documents with clear required-section lists and grounding rules, but it lacks an explicit sequenced workflow with validation checkpoints, provides no executable examples or templates, and inlines everything rather than using progressive disclosure via bundle files.

Suggestions

Add an explicit numbered workflow with validation checkpoints (e.g. detect language -> draft Guide 1 -> verify every claim has a (file:line) citation and ≥3 Mermaid diagrams exist -> draft Guide 2 -> verify commands are copy-pasteable) to raise workflow clarity past the batch-operation cap.

Provide concrete, executable templates or examples — at minimum a Mermaid dark-mode color snippet and a citation format example — rather than only describing what sections should contain.

Move the large section/rule lists into reference files (e.g. references/principal-guide.md, references/contributor-guide.md) and have SKILL.md point to them one level deep, and remove the duplicate '## When to Use' section at the bottom.

DimensionReasoningScore

Conciseness

The body is largely a compact spec of required sections and rules with little padding and minimal over-explanation of concepts Claude already knows, but the duplicate '## When to Use' section (repeated near-verbatim at the top and bottom, with the bottom one adding only a vague restatement) is a minor verbosity inefficiency.

4 / 5

Actionability

It gives concrete, specific guidance on what each section should contain and enforces citation/diagram rules, but provides no executable code, exact commands, or templates — it describes what to produce rather than giving copy-paste-ready instructions, and code examples are required by rules yet none are shown.

3 / 5

Workflow Clarity

There is only a rough implied sequence (detect language, then generate Guide 1, then Guide 2) with no explicit ordered steps, and no validation/verification checkpoints for a batch document-generation workflow that produces two long grounded documents — the rubric caps workflow clarity at 3 for batch operations without validation, and here validation is absent and sequencing is implicit, so it sits below the cap.

2 / 5

Progressive Disclosure

Structure is reasonable with clear sections for each guide and its required parts, but the whole spec is inlined in SKILL.md with no bundle files (references/ scripts/ assets/ are empty), and it references an external 'wiki-vitepress skill' for Mermaid colors without a real local path — content that could be split (e.g. section templates, citation rules) is inline.

3 / 5

Total

12

/

20

Passed

Description

91%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 does and when to use it with natural, comprehensive trigger phrases. Minor room to sharpen specificity by enumerating the two document types more concretely, and small overlap risk with general codebase-explanation skills.

Suggestions

Name the two output document types (e.g. 'a principal-level architecture guide and a zero-to-hero contributor guide') instead of 'two complementary onboarding documents' to lift specificity.

Consider a more distinctive trigger than 'getting-started guides' to reduce overlap with generic documentation/explanation skills.

DimensionReasoningScore

Specificity

It names the concrete action ('Generate two complementary onboarding documents') plus audiences and scope, but the actions are at the document-generation level rather than a comprehensive list of distinct capabilities — minor gaps versus the 'multiple specific concrete actions' anchor.

4 / 5

Completeness

It explicitly answers both 'what' (generate two complementary onboarding documents) 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') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

It covers natural trigger phrases users would say ('onboarding docs', 'getting-started guides', 'help new team members understand a codebase') plus a command trigger ('/deep-wiki'), giving comprehensive keyword coverage including synonyms and a command.

5 / 5

Distinctiveness Conflict Risk

The onboarding-docs/codebase-understanding niche is fairly distinct with a command trigger, but 'getting-started guides' and 'help new team members understand a codebase' could overlap somewhat with general codebase-explanation or documentation skills — mostly distinct with minor overlap risk.

4 / 5

Total

18

/

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