Measure and optimize growth using the AARRR (Pirate Metrics) framework with stage-specific KPIs and funnel analysis
中文简介正在准备中。当前显示原文说明。
Design and run effective 1:1 meetings that build trust, develop people, and surface problems early. Covers cadence setup, agenda ownership, conversation frameworks, question banks, and handling difficult topics. Use when: a new manager learning to run 1:1s, resetting unproductive 1:1s that became status updates, onboarding a new direct report, preparing for a difficult performance conversation, building trust with a new team, or coaching through career development discussions.
中文简介正在准备中。当前显示原文说明。
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Design and run effective 1:1 meetings that build trust, develop people, and surface problems before they become crises.
| Aspect | Details |
|---|---|
| Sources | Andy Grove (High Output Management), Kim Scott (Radical Candor), Michael Lopp (Managing Humans) |
| Core Principle | The 1:1 is the direct report's meeting, not the manager's — their time to surface what matters to them |
| Key Ratio | Manager talks 10-30% of the time; listens 70-90% |
| Claude Does | You Decide |
|---|---|
| Designs 1:1 cadence and structure for your team size | Personal relationship-building approach |
| Generates conversation frameworks and question banks | Which questions fit each person |
| Creates agenda templates and running-notes docs | How to adapt for individual personalities |
| Prepares scripts for difficult conversations | Final wording and tone for sensitive topics |
| Suggests development discussion frameworks | Career advice based on your knowledge of the person |
Cadence by maturity:
| Task-Relevant Maturity | Frequency | Duration |
|---|---|---|
| New or struggling | 2x/week | 30-45 min |
| Developing | Weekly | 30-45 min |
| Senior / independent | Bi-weekly | 45-60 min |
Rules: Same time each week. Rarely cancel. They own the agenda (shared doc, they add topics first). Private space for sensitive topics.
30-minute structure:
| Time | Activity |
|---|---|
| 0-5 min | Check-in: "How are you, really?" |
| 5-20 min | Their agenda items |
| 20-25 min | Your topics (feedback, context) |
| 25-30 min | Commitments and close |
Opening — Understand where they're at: "What's on your mind this week?" / "How's your energy level?"
Middle (their agenda) — Coach, don't solve:
Resist the urge to fix immediately. Ask → Listen → Ask more → Let them reach conclusions.
Middle (your topics) — Keep secondary. Feedback, context, observations.
Closing — Capture commitments: "What are you committing to? What am I committing to?" Document and review next time.
Career Development (monthly/quarterly):
Feedback:
Performance concern:
Validation checkpoint: After a performance conversation, check in at the next 1:1. If no improvement after 2-3 follow-ups, escalate to formal process.
Trust-building (new relationship):
| Problem | Likely Cause | Fix |
|---|---|---|
| "Everything is fine" every week | Lack of trust or wrong questions | Wait in silence longer; share your own challenges first; ask "What would you change if you could?" |
| Turns into status update | Habit, no agenda ownership | "I can read status — what do you need from me?"; use shared doc for status, meeting for discussion |
| Same complaints, no action | Venting without ownership | "We've discussed this for weeks. Are you ready to address it?" |
| Surface-level only | Trust not established yet | Walk-and-talks, share about yourself, be patient |
| Too busy to hold 1:1s | Too many reports or not delegating | 1:1s are core management work, not optional — restructure |
Week 1 (60 min): Getting to know each other — their story, working preferences, how they like feedback, your context and priorities.
Weeks 2-4 (30 min, 2x/week): Frequent check-ins — "What's surprising? What's confusing? What do you need?"
Week 4+: Transition to weekly cadence with shared running doc. Add development topics monthly.
90-day check-in: "How's it going overall? What's working? What's not? What do you want to focus on next quarter?"
The reset conversation: "I've noticed our 1:1s have become mostly status updates. I want to use this time for things you can't get elsewhere — challenges, development, feedback. What would make these more valuable for you?"
Then: implement shared agenda doc, change opening from "What's your update?" to "What's on your mind?", add 10 minutes for development each week, experiment with format (walks, coffee).
See QUESTIONS.md for a complete question bank organized by category (opening, work, development, relationship, closing).
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Measure and optimize growth using the AARRR (Pirate Metrics) framework with stage-specific KPIs and funnel analysis
中文简介正在准备中。当前显示原文说明。
Calculate A/B test statistical significance. Use when: determining if test results are significant; calculating required sample size; estimating test duration; analyzing conversion experiments; making data-driven decisions
中文简介正在准备中。当前显示原文说明。
Assess customer account health using product usage, support sentiment, payment status, and relationship signals
中文简介正在准备中。当前显示原文说明。
Analyze paid advertising performance across channels and recommend budget reallocation to maximize ROAS and minimize CAC. Use when: planning quarterly ad budget allocation, diagnosing underperforming ad channels, deciding whether to scale spend on a channel, calculating marginal ROI across Google Ads, Meta, LinkedIn, or TikTok, rebalancing media mix after performance shifts, or setting up a test-and-scale framework for new channels.
中文简介正在准备中。当前显示原文说明。
Use when testing skills, commands, or agents for quality. Use after creating new skills, before deploying agents, or when debugging inconsistent agent behavior. Triggers on "evaluate", "test quality", "is this skill working", or QA of AI workflows.
中文简介正在准备中。当前显示原文说明。
Use when analyzing server logs to understand how AI crawlers (GPTBot, ClaudeBot, PerplexityBot) interact with your site. Use when optimizing content placement for LLM retrieval, diagnosing why AI search isn't citing your content, or auditing crawl patterns to find optimization gaps.
中文简介正在准备中。当前显示原文说明。