Agent skill · Code Review & Quality

apprentice-first-week

Plan an apprentice's or new laborer's first week so they're useful by Friday and safe from hour one — day-by-day teaching order, the safety non-negotiables stated before anything else, what they're allowed to touch unsupervised, and the check-out conversation that decides week two. Use when a tradesperson says 'my apprentice starts Monday', 'how do I train the new guy', or 'the apprentice is useless and I don't have time to teach'. Produces a first-week plan, a can/can't-touch list, and the Friday review script.

mohitagw15856github.com/mohitagw15856GitHub ↗
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill apprentice-first-week --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: skills/apprentice-first-week/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Apprentice First Week Skill "Watch me and you'll pick it up" is how apprentices stay useless for a year — and how thumbs get lost in week one. A first week that works is planned like a job: safety rules stated as absolutes before any tool moves, one teachable task-block per day with the *why* attached, an explicit list of what they may do unsupervised (short) versus with eyes on them (everything else), and a Friday conversation that tells both sides the truth. The payoff is selfish and immediate: an apprentice who can safely prep, fetch, and finish doubles a one-person business by Friday afternoon. ## What This Skill Produces - A **day-by-day first week**: one skill-block per day (demonstrate → assist → attempt supervised), plus the standing jobs that make them useful between lessons - The **safety brief**, written to be said aloud on Monday at 7:55: the non-negotiables, what to do when unsure, and the "stop means stop" rule - The **touch list**: may-do-unsupervised / may-do-watched / not-yet — updated Friday - The **Friday review script**: what went well, what to fix, one goal for week two — both directions (the apprentice reviews the teaching too) ## Required Inputs Ask for (if

What's inside
Steps it walks through
  1. What This Skill Produces
  2. Required Inputs
  3. Framework
  4. Output Format
  5. Quality Checks
  6. Anti-Patterns
  7. Related
More from pm-claude-skills
All skills →
About this skill
What does the apprentice-first-week skill do?

Plan an apprentice's or new laborer's first week so they're useful by Friday and safe from hour one — day-by-day teaching order, the safety non-negotiables stated before anything else, what they're allowed to touch unsupervised, and the check-out conversation that decides week two. Use when a tradesperson says 'my apprentice starts Monday', 'how do I train the new guy', or 'the apprentice is useless and I don't have time to teach'. Produces a first-week plan, a can/can't-touch list, and the Friday review script.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill apprentice-first-week --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going