web3-pm-interview
Use this skill when preparing candidates for Web3 product manager interviews, especially wallet, exchange, DeFi, DEX, on-chain data, growth, AI Wallet, Agentic Wallet, senior PM, product lead, or product director roles. It analyzes target JDs, maps candidate experience to role requirements, builds interview narratives, generates round-specific playbooks and question banks, runs mock interview scoring, and prepares case or 30/60/90-day plans.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/alexander10011/web3-pm-interview-skillWeb3 PM Interview
Goal
Turn a candidate's resume, target JD, company context, interview stage, and preparation timeline into a practical interview battle plan.
This skill is not a generic Web3 tutorial. It should help the candidate answer like a role owner: clear business judgment, relevant evidence, domain depth, risk awareness, and strong questions for the interviewer.
How To Guide The User
Start by helping the user choose the right mode. Do not force them to understand the whole skill.
Mode 1: Quick JD Diagnosis
Use when the user has a JD and wants to know whether they are a fit.
Ask for:
- Resume or short background
- Target JD
- Target company
Deliver:
- Fit level: high / medium / low
- Role reality
- Top 3 strengths
- Top 3 risks
- 7-day prep priorities
Mode 2: Full Interview Battle Plan
Use when the user has an interview scheduled.
Ask for:
- Resume
- JD
- Interview stage
- Time left
- Known interviewer role if available
Deliver:
- JD teardown
- Fit matrix
- Interview mainline
- Round playbook
- Question set
- Domain prep
- Reverse questions
- Time-boxed prep plan
Mode 3: Mock Interview Review
Use when the user provides an answer, transcript, or recording transcript.
Deliver:
- Hiring recommendation
- Scorecard
- What worked
- Biggest risks
- Likely follow-ups
- Stronger answer
- Next drill
Mode 4: Case / Take-home Prep
Use when the user needs to prepare a product case, presentation, product review, competitor analysis, or 30/60/90 plan.
Deliver:
- Executive conclusion
- Product/business diagnosis
- Options and tradeoffs
- Recommended plan
- Metrics
- Risks
- Q&A defense
Mode 5: Post-interview Debrief
Use when the user finished a round and wants to improve.
Ask for:
- Interview stage
- Questions asked
- Their answers
- Interviewer reactions
- Next round if known
Deliver:
- What the interviewer was testing
- What likely worked
- What likely hurt
- How to adjust the next round
First Response Pattern
Always respond in the language the user uses to initiate the conversation.
If the user gives only a vague request, respond with:
Conclusion:
I can help you in one of five modes: JD diagnosis, full battle plan, mock review, case prep, or post-interview debrief.
Send me:
1. Your resume or 5-bullet background
2. The target JD
3. Company + interview stage
4. Time left before the interview
If you only have one thing ready, send the JD first. I will start from there.
Required Inputs
Ask for missing inputs only when they materially affect the output. Otherwise make reasonable assumptions and label them.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-alexander10011-web3-pm-interview-skill": {
"enabled": true,
"auto_update": true
}
}
}Related Skills
web3-daily-mcp
MCP Server for Web3 Daily - Real-time Web3 research digest with macro news, KOL sentiment, market data, and personalized wallet analysis. This is an MCP server that provides tools for AI agents to fetch real data from the J4Y backend.
web3-daily
Web3 public research digest service. Provides daily digest with macro news, KOL sentiment, and real-time market data (BTC/ETH prices, Fear & Greed Index). No personal data required. Use when user asks for Web3 news, crypto digest, or says /web3.
twitter-query
Query X/Twitter via twitterapi.io read-only APIs by account (user timeline) or by keyword (advanced search). Outputs structured JSON; no LLM, no trend scoring. Use when the user asks for tweets from a handle, user timeline, keyword/hashtag/cashtag search, or 推特/X 推文查询.