Name: git-pr-workflows-onboard
Rating: 43.2 (1 reviews)
Author: administrakt0r

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

44%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/git-pr-workflows-onboard/SKILL.md

The canonical home for this skill is git-pr-workflows-onboard in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

52%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 heavily verbose and monolithic. Its only progressive-disclosure reference points to a file that does not exist, undermining navigation.

Suggestions

Trim generic onboarding advice Claude already knows (communication norms, culture overview) to reduce the body toward a lean overview.

Move the three full example plans and reference checklists into a real bundle file under references/ and link to it one level deep, instead of the missing 'resources/implementation-playbook.md'.

Create the referenced implementation-playbook file (or fix the path) so the progressive-disclosure pointer resolves to actual content.

Dimension	Reasoning	Score
Conciseness	The ~400-line body is noticeably verbose, padding in generic best-practice material Claude already knows ('Slack etiquette and channel purposes', 'company mission, values, and culture overview') that adds little beyond common onboarding knowledge.	2 / 5
Actionability	For an instruction-only skill it gives concrete, specific guidance — time-boxed Day 1 schedules, a buddy-responsibility matrix, and 30/60/90 checkpoints with measurable criteria ('merge at least 3 pull requests', '10+ commits merged').	4 / 5
Workflow Clarity	The process is clearly sequenced (Pre-Onboarding → Day 1 → Week 1 → 30/60/90 milestones) with explicit checkpoints at each milestone; it is not a destructive/batch operation so the validation cap does not apply, though error-recovery feedback loops are absent.	4 / 5
Progressive Disclosure	The body is a monolithic wall of text with everything inlined, and its single reference ('resources/implementation-playbook.md') points to a non-existent file — no bundle files exist — so navigation to deeper material is broken rather than one level deep.	2 / 5
	Total	12 / 20 Passed

Description

36%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 broken: it is truncated mid-sentence and frames a persona ('You are an expert onboarding specialist...') rather than stating concrete actions or a use-trigger. It names the domain but fails to tell Claude what the skill does or when to invoke it.

Suggestions

Rewrite in third person as a concrete capability statement, e.g. 'Creates customized onboarding plans (pre-arrival through 90 days) for new team members based on role, seniority, location, and team structure.'

Add an explicit 'Use when...' trigger clause, e.g. 'Use when onboarding a new hire, ramping up a new team member, or building a 30/60/90-day plan.'

Fix the truncation — the description currently ends mid-sentence at 'You', which makes it unreadable.

Dimension	Reasoning	Score
Specificity	The description names the domain ('onboarding specialist and knowledge transfer architect', 'remote-first organizations', 'technical team integration') but states no concrete actions at all — it describes a persona, not what the skill does, and is truncated mid-sentence at 'You'.	2 / 5
Completeness	It offers only a vague persona-level 'what' ('You are an expert onboarding specialist...') and no 'when' / 'Use when...' clause at all, so per the rubric a missing trigger clause caps completeness and the vague what pushes it to 2.	2 / 5
Trigger Term Quality	Some natural keywords are present ('onboarding', 'remote-first organizations', 'knowledge transfer'), but common variations a user would actually say ('new hire', 'ramp up', 'integrate a new team member') are missing and there is no trigger phrasing.	3 / 5
Distinctiveness Conflict Risk	'Onboarding / knowledge transfer' is a somewhat specific niche, but the persona framing and absence of distinct trigger phrases leave overlap risk with general HR or team-management skills.	3 / 5
	Total	10 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/git-pr-workflows-onboard/SKILL.md
Commit: 57c135b

Reviewed: 4 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.