Name: git-pr-workflows-onboard
Rating: 39.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

38%

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

45%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 well-sequenced onboarding playbook with useful milestone checkpoints, but it is overly verbose, restates generic HR knowledge, and fails at progressive disclosure by inlining everything and pointing to a non-existent reference file.

Suggestions

Move the long example plans, Day 1 checklists, and buddy matrix into separate reference files and link to them from a concise overview, fixing the broken `resources/implementation-playbook.md` path.

Trim generic advice Claude already knows (e.g. what Slack etiquette or company culture overviews are) and keep only the non-obvious specifics like stipend amounts, time commitments, and milestone criteria.

Add concrete artifacts (templates, sample welcome emails, checklist files) so the guidance is copy-paste ready rather than descriptive.

Dimension	Reasoning	Score
Conciseness	The ~400-line body is a padded playbook of generic onboarding knowledge Claude already has ("Slack etiquette", "company mission, values, and culture overview"), with extensive bullet lists that add little specialized information; it is noticeably verbose with several padded sections.	2 / 5
Actionability	Checklists, time estimates, a buddy matrix, and 30/60/90-day deliverables give concrete task-level guidance, but it remains high-level process description with no specific commands, templates, or copy-paste artifacts, so key execution details are missing.	3 / 5
Workflow Clarity	The timeline is clearly sequenced (Pre-Onboarding -> Day 1 -> Week 1 -> milestones) with explicit 30/60/90-day checkpoints that function as validation gates and a dedicated feedback section; minor gaps keep it just below a 5.	4 / 5
Progressive Disclosure	The skill is monolithic with all example plans, checklists, and matrices inlined in SKILL.md, and its single reference to `resources/implementation-playbook.md` is broken (no references/scripts/assets bundle directory exists), so content that belongs in separate files is inlined and the one reference is dead.	2 / 5
	Total	11 / 20 Passed

Description

31%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 a truncated, persona-driven fragment that never states concrete capabilities or a use-when trigger, and it violates the third-person voice requirement. It reads more like an opening line of a prompt than a functional skill description.

Suggestions

Rewrite the description in third person stating concrete actions, e.g. "Creates customized 30/60/90-day onboarding plans for new hires, prepares pre-arrival setup, and tracks milestone progress."

Add an explicit "Use when..." clause with natural trigger terms such as "new hire", "new team member", "onboarding plan", or "remote onboarding".

Remove the persona preamble and fix the truncation so the description is a complete, self-contained sentence.

Dimension	Reasoning	Score
Specificity	The text only establishes a persona ("expert onboarding specialist and knowledge transfer architect") with no concrete actions; it is also truncated mid-sentence and uses second-person voice ("You are an... You"), which per the rubric reduces the specificity score by one from a base of 2.	1 / 5
Completeness	It offers only a vague persona-based "what" and contains no "Use when..." trigger clause, and the sentence is truncated so even the "what" is incomplete; this matches the anchor for a vague what with no when.	2 / 5
Trigger Term Quality	It includes relevant keywords ("onboarding", "knowledge transfer", "remote-first organizations") but misses the natural phrases users actually say ("new hire", "new team member", "onboarding plan") and is cut off before completing a thought.	3 / 5
Distinctiveness Conflict Risk	"Onboarding" is a somewhat distinct niche, but the description is generic and persona-framed with no clear triggers, so it could still overlap with general HR or team-management skills.	3 / 5
	Total	9 / 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/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.