Skills as Onboarding
A skill file is not only an agent command. It is a way to package expert behavior so new people or agents inherit the team's best procedure on day one.
The Anthropic sales-ramp bookmark is a clear operating pattern: when demand grew too fast for a traditional ramp, the company documented what its top reps did and shipped that behavior as Claude skills plus an MCP-style connector. The local visual artifact says the important line directly: "We documented what our top reps do and shipped them as Skills to everyone." Source: local artifact, 2026-06-30
That reframes skills from "prompts for agents" into procedural onboarding assets. A good skill captures the moves of a strong performer: what context to gather, which tool to call, what order to follow, what risks to watch, what evidence to produce, and where the output flows next. The new hire or agent still needs judgment, but the blank-page ramp disappears.
Pattern
- Observe the top performers doing the work.
- Write the repeated procedure down as a skill, not as a slide deck.
- Attach the skill to the real tool/data surface through MCP, CLI, API, or browser automation.
- Give new reps or agents a small bootcamp plus the executable skill.
- Track outcomes and revise the skill when the field reality changes.
The pattern works because it bundles knowledge, tool access, and review criteria together. A training doc transfers memory; a skill transfers memory plus action.
Kevin Stack Implication
This is the org-scale version of No One-Off Work. If Kevin or a team member does a repeated workflow manually, the next version should become a skill, automation, or capsule. The sales example matters because it shows the same mechanism outside engineering: support, sales, recruiting, customer onboarding, diligence, and content operations can all have first-class skills.
For Agent Machines, this points at a product boundary: teams do not only need agents. They need their best employee workflows compiled into portable skills and attached to their actual systems. That is Services-as-Software in miniature: sell the work, then keep improving the procedure.
Failure Modes
- Skill as vague advice: "be consultative" does not help an agent or a rep. The skill must name inputs, tools, steps, outputs, and review gates.
- Skill without data access: a playbook that cannot read the CRM, docs, tickets, or territory data stays performative.
- Frozen skill: the skill must be revised from field evidence. Otherwise it becomes onboarding theater.
- No human owner: skills need a manager who owns truth, compliance, and taste.
Timeline
- 2026-05-23 | Jason Lemkin shared the Anthropic sales-ramp example: quick bootcamp plus a sales plugin made from an MCP connector and five Claude skills. Source: X/@jasonlk, 2026-05-23
- 2026-06-30 | Deep-reviewed the SaaStr article, local video thumbnail, thread reply, and artifact record. Promoted the reusable pattern as Skills as Onboarding. Source: SaaStr, 2026-05-23