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

28%

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

48%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 is a thorough, well-sequenced onboarding playbook with concrete checklists and milestone checkpoints, but it is over-long and generic in places, inlines content that would benefit from separate reference files, and has one malformed code block. It is actionable but not token-efficient.

Suggestions

Trim generic boilerplate (culture overviews, Slack etiquette) that Claude already knows, and move the three example 30/60/90 plans and the buddy matrix into separate reference files linked from the body.

Fix the 'Local Environment' fenced block: it is a bulleted list wrapped in ``` fences rather than a real code block; convert it to executable commands or remove the fence.

Add explicit validation gates to the multi-step setup workflow (e.g. 'Verify all accounts/2FA are working before Day 1') to strengthen the feedback loops.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose for an instruction skill, with ~400 lines of generic onboarding boilerplate ('Company mission, values, and culture overview', 'Slack etiquette and channel purposes') that largely restates widely-known onboarding concepts rather than adding specialized guidance Claude lacks.	2 / 5
Actionability	Guidance is mostly concrete checklists and specific items (e.g. '$1,500 home office stipend', 'Manager 1:1 welcome (30 min)', 'Merge at least 3 pull requests'), but the local-environment code block is misformatted as a plain list inside ``` fences rather than executable commands, leaving some key details incomplete.	3 / 5
Workflow Clarity	Multi-step processes (pre-onboarding -> Day 1 -> Week 1 -> 30/60/90 milestones) are clearly sequenced with checkpoint summaries, and feedback loops appear via pulse surveys and milestone reviews; however there are no explicit validate-then-proceed gates for the batch/setup operations.	4 / 5
Progressive Disclosure	The file has good section structure but is a single ~400-line monolith with no bundle files in references/, scripts/, or assets/ and no one-level-deep pointers; the example plans and matrices are inlined where separate reference files would aid navigation.	3 / 5
	Total	12 / 20 Passed

Description

8%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 frontmatter description is truncated mid-sentence and written in second person ('You are...'), both of which the rubric penalizes; it defines a verbose persona rather than concrete capabilities and includes no 'Use when' trigger guidance. It needs to be rewritten in third person, completed, and given explicit trigger phrases.

Suggestions

Rewrite the description in third person and complete the truncated sentence, e.g. 'Creates customized onboarding plans for new team members...'.

Add an explicit 'Use when...' clause with natural trigger phrases such as 'onboarding', 'new hire', 'ramp-up plan', or '30/60/90 day plan'.

Replace the persona buzzwords ('knowledge transfer architect', 'accelerated learning methodologies') with 3-5 concrete actions the skill performs.

Dimension	Reasoning	Score
Specificity	The description names a domain ('onboarding specialist and knowledge transfer architect') but lists no concrete actions, and the text is truncated mid-sentence at 'methodologies. You', so it never specifies what the skill actually does.	2 / 5
Completeness	The description is cut off ('methodologies. You') so it answers neither 'what does this do' nor 'when should Claude use it'; the explicit 'Use when...' trigger guidance is entirely missing, which would cap completeness at 3 even if the 'what' were present.	1 / 5
Trigger Term Quality	No natural keywords a user would say when needing onboarding help; it uses persona/credential jargon ('knowledge transfer architect', 'accelerated learning methodologies') rather than trigger phrases like 'onboarding', 'new hire', or 'ramp up'.	1 / 5
Distinctiveness Conflict Risk	The persona framing is very broad and could overlap with general HR/team-management skills, and with no concrete action list or triggers it is hard to distinguish from related people-ops skills.	2 / 5
	Total	6 / 20 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: 3eff4af

Reviewed: 1 day 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.