repo-onboard

Given any Git repository — a GitHub URL, an org/repo slug, a local path on disk, or the repo you're already inside — get productive fast and land a mergeable commit. Clone/orient, get the build+test loop green, extract the contribution rules that gate a PR, map the 20% of the code you'll touch, locate the change site, and lay out the shortest path to a passing commit. Use when the user points at a repo (remote or local) and wants to "onboard", "get productive", "start contributing", "make my first commit", "ship a change", or "get set up to work in this codebase".

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

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

A well-structured, highly actionable onboarding workflow with strong sequencing and explicit validation/confirmation checkpoints. The main improvement is trimming a few motivational lines to tighten conciseness.

Suggestions

Tighten conciseness by removing motivational framing ('This is the crux.', 'A commit that fails local checks is a wasted round trip.') since the numbered steps already convey the intent.

Consider condensing the closing 'Verify, don't assume' and 'Stay reversible until told otherwise' principles, which restate guidance already embedded in Phases 2 and 6.

The sibling-skill pointer to rapid-onboard is good; if more detail on any phase grows, split it into a references/ file rather than expanding SKILL.md.

Dimension	Reasoning	Score
Conciseness	Largely lean and assumes Claude's competence (no explanations of git/builds), but a few motivational lines ('This is the crux.', 'A commit that fails local checks is a wasted round trip.') and the repeated closing principles could be trimmed.	4 / 5
Actionability	Highly executable throughout: concrete commands (`git remote -v`, `npm ci`, `pip install -e .`, `cargo build`, `ruff`, `git commit -s`, `git checkout -b`) and specific files to inspect (Makefile, justfile, .github/workflows/*.yml, CODEOWNERS).	5 / 5
Workflow Clarity	Six phases are clearly sequenced with explicit validation checkpoints — a pre-existing red baseline before touching anything, 'Fix until green locally', and 'stop and confirm with the user before pushing or opening a PR' for the outward-facing step.	5 / 5
Progressive Disclosure	Well-organized into clear section headers with a clearly signaled one-level reference to the sibling skill; no nested references. No bundle files exist, and the content appropriately lives in a single SKILL.md, though at ~90 lines it slightly exceeds the simple-skill exception.	4 / 5
	Total	18 / 20 Passed

Description

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

A strong description: third-person voice, concrete multi-step capabilities, comprehensive natural triggers, and both what/when answered explicitly with a clearly distinct niche from its sibling skill.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Clone/orient, get the build+test loop green, extract the contribution rules that gate a PR, map the 20% of the code you'll touch, locate the change site, and lay out the shortest path to a passing commit' — giving comprehensive coverage of what the skill does.	5 / 5
Completeness	Explicitly answers both 'what' (the clone/orient→commit pipeline) and 'when' ('Use when the user points at a repo... and wants to...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrases users would actually say: 'onboard', 'get productive', 'start contributing', 'make my first commit', 'ship a change', 'get set up to work in this codebase', with synonym coverage.	5 / 5
Distinctiveness Conflict Risk	Clear niche — onboarding a Git repo to land a mergeable commit — with an explicit boundary against the sibling rapid-onboard skill (docs URL vs source code), minimizing conflict risk.	5 / 5
	Total	20 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	14 / 16 Passed

Repository: moodec/useful-claude-skills
Path: skills/repo-onboard/SKILL.md
Commit: 84f0498

Reviewed: 20 hours 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.