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

17%

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

23%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is a comprehensive but extremely verbose onboarding handbook that reads more like an HR document than actionable instructions for Claude. It lacks concrete, executable guidance — there are no commands, code, or tool-specific steps Claude can actually perform. The content would benefit enormously from being condensed to essential decision-making guidance and split across multiple reference files.

Suggestions

Reduce the content by 80%+ — remove all generic onboarding knowledge Claude already knows (what HR paperwork is, what a buddy system is, etc.) and focus only on the specific decision logic, templates, and output formats Claude should use when generating onboarding plans.

Define a concrete input schema for $ARGUMENTS and specify the exact output format (e.g., a structured onboarding plan document) so Claude knows what to produce.

Move the example plans (Software Engineer, Remote Employee, Senior/Lead) into separate bundle files and reference them from the main SKILL.md with clear navigation links.

Add validation steps Claude should perform — e.g., verify all checklist items are role-appropriate, confirm timeline feasibility, check for missing access requirements before finalizing a plan.

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive content Claude already knows about onboarding processes. The skill reads like a comprehensive HR handbook rather than targeted instructions for Claude. It explains basic concepts like what a buddy system is, what HR paperwork involves, and general onboarding philosophy — none of which add value for an AI assistant. At 300+ lines, the vast majority of tokens are spent on generic organizational knowledge.	1 / 5
Actionability	While the skill contains checklists and structured plans, the guidance is almost entirely high-level organizational advice rather than concrete, executable steps Claude can take. There are no actual code examples, commands, or tool invocations. Instructions like 'Create all necessary accounts' and 'Configure SSO and 2FA requirements' are vague directives without specifying how Claude should accomplish them. The $ARGUMENTS parsing section lacks any concrete format or schema.	2 / 5
Workflow Clarity	There is a clear chronological sequence (pre-boarding → Day 1 → Week 1 → 30/60/90 days) with milestone checkpoints. However, there are no validation steps or feedback loops within the actual execution workflow — the 'Feedback Loops' section describes organizational processes rather than verification steps Claude should perform. The skill lacks any error handling or decision points for when things go wrong during execution.	3 / 5
Progressive Disclosure	The content is a monolithic wall of text with no meaningful separation into referenced files. It mentions 'resources/implementation-playbook.md' but no bundle files are provided. The massive amount of inline content (example plans, checklists, buddy matrices) should clearly be split into separate reference files. Everything is dumped into a single document with no navigation strategy.	2 / 5
	Total	8 / 20 Passed

Description

11%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.

This description is essentially a persona declaration rather than a functional skill description. It contains no concrete actions, no 'when to use' guidance, and appears to be truncated mid-sentence. It uses second-person voice ('You are') which violates the third-person convention, and relies entirely on buzzwords like 'knowledge transfer architect' and 'accelerated learning methodologies' without specifying any actual capabilities.

Suggestions

Replace the persona declaration with concrete actions in third person, e.g., 'Creates onboarding plans, generates team integration checklists, and builds knowledge transfer documentation for new hires.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when onboarding new team members, creating training plans, or setting up knowledge bases for remote teams.'

Complete the truncated description and remove abstract buzzwords like 'knowledge transfer architect' and 'accelerated learning methodologies' in favor of specific, actionable capabilities.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. It only describes a persona ('expert onboarding specialist and knowledge transfer architect') using vague, abstract language with no mention of what the skill actually does.	1 / 5
Completeness	The description answers neither 'what does this do' nor 'when should Claude use it'. It only establishes a persona identity without any functional description or trigger guidance. The description also appears truncated.	1 / 5
Trigger Term Quality	The terms 'onboarding', 'knowledge transfer', and 'remote-first' are somewhat relevant keywords a user might mention, but they are buried in persona fluff rather than presented as natural trigger terms. Most natural user phrases are missing.	2 / 5
Distinctiveness Conflict Risk	While 'onboarding' and 'knowledge transfer' hint at a domain, the description is so vague and persona-focused that it could easily overlap with any HR, documentation, or team management skill.	2 / 5
	Total	6 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: 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.