Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
日本語の概要は準備中です。原文の説明を表示しています。
Generate STAR stories, practice questions, and talking points from resume
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Use this skill when the user wants to:
SITUATION: "At [Company], we faced [specific challenge/context]..."
TASK: "I was responsible for [specific ownership]..."
ACTION: "I [specific action 1], [specific action 2], and [specific action 3]..."
RESULT: "As a result, [quantified outcome]. This led to [business impact]."
Question: "Tell me about a time you led a team through a difficult project."
Answer:
SITUATION: "At TechCorp, our main product was losing customers to a competitor who had launched a better mobile experience. We were seeing 5% monthly churn, up from our normal 2%."
TASK: "As the product manager, I was responsible for turning around our mobile product to stop the bleeding and win back customers."
ACTION: "I started by interviewing 30 churned customers to understand exactly why they left. Based on that research, I prioritized 5 critical features that would achieve parity with competitors. I then worked with engineering to restructure our roadmap, negotiated with leadership to add 2 contract developers, and implemented weekly sprint reviews to keep the project on track. I also started a beta program with 50 of our best customers to get feedback before full launch."
RESULT: "We launched the improved mobile app in 3 months, reducing churn from 5% back to 2% within 60 days. We recovered 35% of churned customers and the NPS for our mobile app increased from 32 to 58. This project was recognized in our company all-hands as a turnaround success."
Time: 90 seconds to 2 minutes
Leadership Stories Needed:
Problem-Solving Stories Needed:
Collaboration Stories Needed:
Achievement Stories Needed:
Failure/Growth Stories Needed:
For each resume bullet, create a full STAR story:
RESUME BULLET: "Led cross-functional team of 12 to deliver $2M product launch"
STAR EXPANSION:
SITUATION: Our company was losing market share to a competitor, and leadership decided we needed to launch a new product line within 6 months.
TASK: As Product Manager, I was tasked with leading the product from concept to launch, coordinating across engineering, design, marketing, and sales teams (12 people total).
ACTION:
- I established weekly cross-functional syncs and a shared Notion workspace
- Created a detailed project plan with milestones and dependencies
- Implemented a rapid prototyping process with 2-week design sprints
- Personally resolved 3 major conflicts between engineering and marketing
- Presented monthly updates to leadership to maintain alignment
RESULT:
- Launched on time and under budget
- Generated $2M revenue in first year
- Acquired 50 new enterprise customers
- Team received company innovation award
Each story should have:
Leadership:
Problem-Solving:
Collaboration:
Achievement:
Failure/Growth:
Product Management:
Engineering:
Marketing:
Sales:
About You:
About the Role:
About the Company:
Formula: Real weakness + Self-awareness + Improvement steps
"I tend to be overly detail-oriented, which can sometimes slow me down. I've recognized this and now set time limits for tasks and ask for feedback on when good enough is good enough. In my current role, I've also learned to delegate detailed work when appropriate."
Keep it:
"I've learned a lot at [Company], but I'm looking for [specific opportunity] that I don't see available in my current path. This role at [Company] offers exactly that - the chance to [specific thing]."
Must include:
"In my first year as a PM, I launched a feature without sufficient user research. The feature was technically sound but users found it confusing. Only 10% adopted it. I learned the hard way that building the right thing matters more than building the thing right. Since then, I never skip user research - I now always do at least 10 user interviews before major feature decisions."
Deflect until you have to answer:
"I'm flexible on compensation and more focused on finding the right role. Can you share the range budgeted for this position?"
If pressed:
"Based on my research and experience, I'm looking for something in the range of $X-$Y, but I'm open to discussing the full compensation package."
When generating interview prep:
# INTERVIEW PREP: [POSITION] AT [COMPANY]
## Role Analysis
**Key competencies they'll test:**
1. [Competency] - Evidence: [From JD]
2. [Competency] - Evidence: [From JD]
3. [Competency] - Evidence: [From JD]
## Predicted Questions
### High Probability (prepare thoroughly)
1. [Question] → Use story: [Story name]
2. [Question] → Use story: [Story name]
3. [Question] → Use story: [Story name]
### Medium Probability
1. [Question]
2. [Question]
## Your STAR Story Bank
### Story 1: [Name - e.g., "Product Launch Success"]
**Use for:** Leadership, Achievement, Cross-functional
**STAR:**
- S: [Situation]
- T: [Task]
- A: [Action]
- R: [Result with metrics]
**Short version:** [60 second version]
### Story 2: [Name]
[Same structure]
## "Tell Me About Yourself" Script
[2-minute pitch tailored to this role]
## Questions to Ask
**For Hiring Manager:**
1. [Question]
2. [Question]
**For Team:**
1. [Question]
2. [Question]
## Company Research Notes
- Recent news: [Item]
- Key facts to reference: [Facts]
- Potential concerns: [Items to be ready for]
## Red Flag Answers to Avoid
- Don't mention: [Topics]
- Don't criticize: [Past employer aspects]
- Watch out for: [Potential trap questions]
For complete interview prep:
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.
日本語の概要は準備中です。原文の説明を表示しています。
Format CVs for academic positions with publications, grants, and teaching
日本語の概要は準備中です。原文の説明を表示しています。
Conduct a comprehensive accessibility audit against WCAG guidelines with severity ratings and remediation steps.
日本語の概要は準備中です。原文の説明を表示しています。
Create accessibility testing plans covering assistive technologies and WCAG criteria.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'ad performance optimization,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' or 'I need more ad variations.' Use this whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see ads. For landing page copy, see copywriting.
日本語の概要は準備中です。原文の説明を表示しています。