CtrlK
BlogDocsLog inGet started
Tessl Logo

onboarding

Get up to speed on a new team, project, or area — surface key people, foundational docs, current priorities, and recent activity. Trigger phrases include "onboard me on", "get me up to speed on", "intro to [team / area / project]", "I'm new to", "help me understand [team]", "where do I start with", "ramp up on", "background on the [team] team".

67

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

70%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 content is well-structured with a clear phased workflow, explicit vetting/validation checklists, and concrete tool calls. Its weaknesses are length — the inlined deliverable template is heavy — and the absence of any reference files to offload the large template.

Suggestions

Move the ~90-line onboarding-guide output template into a references/ file (e.g. references/onboarding_guide_template.md) and keep only a short pointer in SKILL.md to improve progressive disclosure and token efficiency.

Trim the "Core Principles" bullets or fold them into the relevant phases to reduce overhead Claude doesn't need.

Add concrete argument examples for the search/meeting_lookup calls (e.g. show the exact filter syntax) to close the actionability gaps and reach fully copy-paste-ready guidance.

DimensionReasoningScore

Conciseness

The body is mostly efficient and avoids explaining concepts Claude already knows, but the ~90-line prescriptive output template plus the "Core Principles" list could be tightened; it lands between efficient and noticeably heavy rather than fully lean.

3 / 5

Actionability

It gives concrete tool invocations (Glean chat, employee_search, search, meeting_lookup) with example arguments and a structured deliverable template, but some calls remain templated/placeholder-y, leaving minor gaps versus fully copy-paste-ready.

4 / 5

Workflow Clarity

Five phases are clearly sequenced (Overview → People → Documents → Vet → Generate), with Phase 4 marked CRITICAL providing explicit validation checklists (Essential/Freshness/Accuracy tests) and a Troubleshooting section giving feedback loops for error recovery.

5 / 5

Progressive Disclosure

No bundle files exist, so there are no one-level-deep references to signal; the body is a single long file with the large output template inlined, and at ~250 lines it does not qualify for the simple-skill exception, so organization is only adequate.

3 / 5

Total

15

/

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: it clearly states what the skill does and when to use it, backed by a rich set of natural trigger phrases. The main weakness is that the capability verbs are slightly abstract relative to the best-in-class examples.

DimensionReasoningScore

Specificity

The description names the onboarding domain and several concrete actions — "surface key people, foundational docs, current priorities, and recent activity" — but the verbs stay slightly high-level compared to the 5-anchor's granular action list, leaving minor coverage gaps.

4 / 5

Completeness

It explicitly answers both "what" (surface people, docs, priorities, activity) and "when" ("Trigger phrases include ...") with concrete trigger phrases, hitting the top anchor.

5 / 5

Trigger Term Quality

It provides eight natural trigger phrases ("onboard me on", "get me up to speed on", "ramp up on", "I'm new to", etc.) covering synonyms and phrasings a user would actually say, matching the comprehensive-coverage anchor.

5 / 5

Distinctiveness Conflict Risk

The onboarding niche is mostly distinct with onboarding-specific triggers, but generic phrases like "help me understand [team]" and "where do I start with" carry minor overlap risk with general research/explanation skills.

4 / 5

Total

18

/

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