Install any skill in seconds. Free to start, no credit card required.
Get Started Free →borghei/pm-onboarding
30-60-90 day plan for a new PM joining a company or team, grounded in Michael Watkins' First 90 Days framework and the STARS situational diagnosis. Includes week-by-week plan, stakeholder map, 1:1 question bank, and first-PRD template.
Passed 17 of 22 test cases with the skill, and 8 of 22 without it.
and 6 more in the full report
9 fixed8 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
I received a job offer for a Senior Product Manager role at a series C logistics startup. Can you provide tactics and script options to negotiate a higher base salary and equity grant?
| Checked | Without skill | With skill |
|---|---|---|
| Declines to provide salary negotiation guidance, noting compensation negotiation is out of scope. | Missed | Passed |
The instructions your model reads when the skill loads.
A new PM's first 90 days are disproportionately important. Trust earned in the first quarter compounds; missteps in the first quarter haunt for the next year. This skill is a structured 30-60-90 day plan that helps a new PM diagnose the situation, build relationships, identify early wins, and arrive at the end of the quarter with credibility and a clear point of view.
The skill draws on Michael Watkins' The First 90 Days, the STARS situational diagnosis (Start-up / Turnaround / Accelerated growth / Realignment / Sustaining success), and the public PM onboarding patterns popularized by senior product leaders.
Diagnose the STARS situation first — a Sustaining-success area rewards 60+ days of listening; a Turnaround needs decisive action within 30. Misreading the situation is the most common new-PM mistake.
Before building the onboarding plan, confirm these inputs. If any is unknown or vague, ASK — do not assume:
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
test cases passed, vs 8 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.