CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

git-pr-workflows-onboard

Plan technical onboarding with environment setup, codebase orientation, team integration, and learning milestones. Use when helping developers join a project or preparing onboarding materials.

Quality

77%

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 ./skills/git-pr-workflows-onboard/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 delivers a well-sequenced, genuinely actionable onboarding playbook with strong milestones and checkpoints, but it is significantly overlong: boilerplate persona/use-when sections and exhaustive generic checklists pad the token budget, and the entire bulk lives in one file with no progressive disclosure. The frontmatter name ("git-pr-workflows-onboard") also mismatches the onboarding content, though that sits outside the body evaluation.

Suggestions

Remove the boilerplate persona paragraph, the circular "Use this skill when" / "Do not use this skill when" sections, and the generic Instructions section — they restate the obvious and burn context without adding guidance.

Move the three full example plans (Software Engineer 30/60/90, Remote Employee, Senior/Lead) and the Day 1 checklists into references/ files, keeping SKILL.md as a concise overview with clearly signaled links.

Trim exhaustive generic checklist items (standard practices like SSO setup, HR paperwork, buddy check-ins that Claude already knows) down to the non-obvious, organization-specific specifics that actually add value.

DimensionReasoningScore

Conciseness

Noticeably verbose: persona padding ("You are an expert onboarding specialist and knowledge transfer architect..."), circular filler ("Working on onboard tasks or workflows"; "The task is unrelated to onboard"), generic instructions ("Clarify goals, constraints, and required inputs"), and ~400 lines of standard onboarding checklists Claude could largely generate on its own. Not 1 because it never explains basic concepts and the checklists do carry domain substance.

2 / 5

Actionability

Concrete, usable guidance throughout: timed Day 1 agenda ("Manager welcome and agenda review (30 min)"), measurable milestones ("Merge at least 3 pull requests"), and the buddy responsibility matrix with time commitments. Not 5 because many items remain high-level directives ("Complete all mandatory training", "Establish working relationships across teams") and no templates or commands for producing the actual plan artifact are given.

4 / 5

Workflow Clarity

Clear multi-phase sequence (Pre-Onboarding → Day 1 → Week 1 → 30/60/90 milestones) with explicit checkpoints ("Day 60 Checkpoint: First feature shipped to production") and feedback loops (weekly pulse surveys, quarterly retrospectives). Not 5 because checkpoints state outcome criteria without validation steps for verifying progress, and sequencing has redundancy (environment setup appears both inside Week 1 and as a later standalone section).

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/ directories), so all ~415 lines are inlined in SKILL.md. Section headers provide reasonable navigation, but content that clearly belongs in separate files — three complete example plans and the reference checklists/schedules — is fully inline with no offloading. Not 2 because the consistent headers make it navigable, unlike a headerless wall of text.

3 / 5

Total

13

/

20

Passed

Description

87%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: third-person voice, concrete action areas, an explicit "Use when" clause with natural trigger phrases, and a distinct niche. Minor headroom exists in trigger synonym coverage ("new hire", "ramp up") and in expressing multiple distinct actions rather than one planning verb.

DimensionReasoningScore

Specificity

Lists several concrete action areas ("environment setup, codebase orientation, team integration, and learning milestones") beyond just naming the domain. Not 5 because it relies on a single verb ("Plan") with object areas rather than multiple distinct concrete actions.

4 / 5

Completeness

Explicitly answers both what ("Plan technical onboarding with environment setup, codebase orientation, team integration, and learning milestones") and when ("Use when helping developers join a project or preparing onboarding materials") with concrete trigger phrases, matching the top anchor's structure.

5 / 5

Trigger Term Quality

Includes natural terms users would say: "onboarding", "onboarding materials", "developers join a project". A few natural variations are missing (e.g., "new hire", "new team member", "ramp up"), keeping it below comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

"Technical onboarding" is a clear niche with distinct triggers around joining a project and preparing onboarding materials; minimal overlap risk with other skills. It is clearly distinguishable rather than only "mostly distinct".

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

rmyndharis/antigravity-skills

Path

skills/git-pr-workflows-onboard/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.