git-pr-workflows-onboard

You are an **expert onboarding specialist and knowledge transfer architect** with deep experience in remote-first organizations, technical team integration, and accelerated learning methodologies. You

Quality

21%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/git-pr-workflows-onboard/SKILL.md

Quality

Content

35%Weight 40%Scale 1-3

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 and offers concrete checklists and example plans, but it is far too long, largely restates generic onboarding knowledge Claude already has, and is monolithic with no progressive disclosure into reference files. It should be condensed and split so SKILL.md stays a lean overview.

Suggestions

Cut generic content Claude already knows (account creation, ceremony shadowing, Slack etiquette) and keep only role-specific or non-obvious guidance; target a lean overview under ~100 lines.

Move the three example plans and the Day-1 checklist / buddy matrix into separate reference files (e.g. references/example-plans.md) and link to them from the body for proper progressive disclosure.

Tighten the milestone/checkpoint sections into explicit verification gates (criteria to confirm before advancing to the next phase) rather than descriptive success-criteria lists.

Dimension	Reasoning	Score
Conciseness	The ~410-line body is a verbose wall of generic onboarding checklist content (account setup, buddy check-ins, ceremony shadowing) that largely restates knowledge Claude already has, plus templated boilerplate ('Use this skill when', 'Instructions') and redundancy between the milestone and example-plan sections.	1 / 3
Actionability	It provides concrete checklists, time-boxed steps, a buddy-responsibility matrix, and full 30/60/90 example plans, but the guidance is generic and template-like rather than sharply tailored to a specific role/context, so it is actionable yet incomplete in specificity.	2 / 3
Workflow Clarity	The phased sequence (pre-onboarding -> Day 1 -> Week 1 -> 30/60/90 milestones) is clearly laid out with checkpoints and a feedback-loops section, but the checkpoints are descriptive success criteria rather than explicit validation/verification gates with retry, so it sits at the 'sequence present but checkpoints implicit' level.	2 / 3
Progressive Disclosure	No bundle files exist (references/scripts/assets absent) and nothing is split out; the body is a single 410-line document with example plans and reference checklists inlined that would be better placed in separate reference files, though it is well-organized with clear section headers.	2 / 3
	Total	7 / 12 Passed

Description

7%Weight 40%Scale 1-3

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 a truncated persona statement rather than a capability statement: it describes who Claude is, not what the skill does or when to invoke it, and it is cut off mid-sentence. It needs concrete actions, natural trigger terms, an explicit 'Use when...' clause, and third-person voice.

Suggestions

Rewrite in third person listing concrete actions, e.g. 'Creates customized 30/60/90-day onboarding plans, sets up pre-arrival checklists, and tracks ramp-up milestones for new hires.'

Add an explicit trigger clause: 'Use when onboarding a new team member, creating a ramp-up plan, or preparing pre-arrival checklists for new hires.'

Fix the truncation so the sentence completes and remove credential fluff ('expert', 'knowledge transfer architect', 'accelerated learning methodologies') that adds no trigger value.

Dimension	Reasoning	Score
Specificity	The description only offers role/credential framing ('expert onboarding specialist and knowledge transfer architect with deep experience in remote-first organizations, technical team integration, and accelerated learning methodologies') with no concrete actions, and the second-person voice ('You are...') triggers the mandated -1 specificity penalty, flooring it at 1.	1 / 3
Completeness	It answers neither 'what does this do' (only a persona is given, truncated mid-sentence at 'You') nor 'when should Claude use it' (no 'Use when...' clause), so both halves are missing or very weak.	1 / 3
Trigger Term Quality	There are no natural trigger phrases a user would say ('onboard a new hire', 'create an onboarding plan'); instead it uses jargon/credential terms like 'knowledge transfer architect' and 'accelerated learning methodologies'.	1 / 3
Distinctiveness Conflict Risk	'onboarding' names an identifiable niche, but with no concrete capability or trigger stated it could still overlap with generic HR/people-management skills, matching the 'somewhat specific but could overlap' anchor.	2 / 3
	Total	5 / 12 Passed

Validation

100%

Warnings & errors only

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
Commit: e63f7dd

Reviewed: 13 days ago

Table of Contents

Discovery Implementation Validation

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.