
Post-deploy canary monitoring. Watches the live app for console errors, performance regressions, and page failures using the browse daemon. Takes periodic screenshots, compares against pre-deploy baselines, and alerts on anomalies. Use when: "monitor deploy", "canary", "post-deploy check", "watch production", "verify deploy".
Help users conduct effective hiring interviews. Use when someone is designing an interview loop, crafting interview questions, evaluating candidates in real-time, or building a structured interview process.
Help users work effectively across functions. Use when someone is navigating PM-engineering relationships, resolving cross-team conflicts, building product trios, or improving handoffs between design, engineering, and product.
Help users implement effective dogfooding practices. Use when someone is trying to get their team to use their own product, designing internal usage programs, or building user empathy through personal product use.
Help users plan and execute product launches. Use when someone is planning a product launch, preparing PR outreach, coordinating a go-to-market campaign, launching on Product Hunt, or asking how to generate buzz for a new feature or product.
Help users manage technical debt strategically. Use when someone is dealing with legacy code, planning refactoring work, deciding between rewrites vs. incremental fixes, trying to get buy-in for tech debt reduction, or balancing new features with maintenance.
Help users design effective organizational structures. Use when someone is thinking about team structure, deciding between functional vs. divisional models, planning a reorg, or figuring out how to structure product teams.
Help users design effective product onboarding. Use when someone is creating first-user experiences, trying to improve activation rates, designing the first 30 seconds of product usage, or working on the path to the aha moment.
Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. Iteratively fixes issues in source code, committing each fix atomically and re-verifying with before/after screenshots. For plan-mode design review (before implementation), use /plan-design-review. Use when asked to "audit the design", "visual QA", "check if it looks good", or "design polish". Proactively suggest when the user mentions visual inconsistencies or wants to polish the look of a live site.
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas. Use when asked to "weekly retro", "what did we ship", or "engineering retrospective". Proactively suggest at the end of a work week or sprint.
CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Four modes: SCOPE EXPANSION (dream big), SELECTIVE EXPANSION (hold scope + cherry-pick expansions), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials). Use when asked to "think bigger", "expand scope", "strategy review", "rethink this", or "is this ambitious enough". Proactively suggest when the user is questioning scope or ambition of a plan, or when the plan feels like it could be thinking bigger.
Performance regression detection using the browse daemon. Establishes baselines for page load times, Core Web Vitals, and resource sizes. Compares before/after on every PR. Tracks performance trends over time. Use when: "performance", "benchmark", "page speed", "lighthouse", "web vitals", "bundle size", "load time".
Design consultation: understands your product, researches the landscape, proposes a complete design system (aesthetic, typography, color, layout, spacing, motion), and generates font+color preview pages. Creates DESIGN.md as your project's design source of truth. For existing sites, use /plan-design-review to infer the system instead. Use when asked to "design system", "brand guidelines", or "create DESIGN.md". Proactively suggest when starting a new project's UI with no existing design system or DESIGN.md.
Land and deploy workflow. Merges the PR, waits for CI and deploy, verifies production health via canary checks. Takes over after /ship creates the PR. Use when: "merge", "land", "deploy", "merge and verify", "land it", "ship it to production".
YC Office Hours — two modes. Startup mode: six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. Builder mode: design thinking brainstorming for side projects, hackathons, learning, and open source. Saves a design doc. Use when asked to "brainstorm this", "I have an idea", "help me think through this", "office hours", or "is this worth building". Proactively suggest when the user describes a new product idea or is exploring whether something is worth building — before any code is written. Use before /plan-ceo-review or /plan-eng-review.
Configure deployment settings for /land-and-deploy. Detects your deploy platform (Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, custom), production URL, health check endpoints, and deploy status commands. Writes the configuration to CLAUDE.md so all future deploys are automatic. Use when: "setup deploy", "configure deployment", "set up land-and-deploy", "how do I deploy with gstack", "add deploy config".
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. Use when asked to "ship", "deploy", "push to main", "create a PR", or "merge and push". Proactively suggest when the user says code is ready or asks about deploying.
Clear the freeze boundary set by /freeze, allowing edits to all directories again. Use when you want to widen edit scope without ending the session. Use when asked to "unfreeze", "unlock edits", "remove freeze", or "allow all edits".
Help users build and grow product communities. Use when someone is starting a community, scaling an ambassador program, driving community-led growth, or choosing between user, developer, or partner communities.
Help users craft compelling brand narratives. Use when someone is defining brand strategy, writing company positioning, creating pitch narratives, developing messaging frameworks, or trying to make their company story more memorable.
Help users build effective AI applications. Use when someone is building with LLMs, writing prompts, designing AI features, implementing RAG, creating agents, running evals, or trying to improve AI output quality.
Help users delegate effectively. Use when someone is struggling to let go of tasks, deciding what to delegate, building team autonomy, or balancing being hands-on vs hands-off.
Help users plan products and strategy when outcomes are unpredictable. Use when someone is dealing with ambiguous timelines, building in fast-moving markets, planning AI/ML projects, or asking how to make commitments when they don't know what will happen.
Help users build and scale internal platforms and technical infrastructure. Use when someone is deciding whether to build vs buy tooling, designing developer platforms, creating shared services, or managing technical debt at scale.
Help users implement product-led sales motions. Use when someone is transitioning from pure PLG to sales-assisted, defining PQLs, building sales handoff processes, or trying to expand self-serve users into enterprise contracts.
Help users develop product taste and intuition. Use when someone wants to improve their product judgment, struggles to evaluate design quality, needs to make decisions without complete data, or wants to build better product instincts.
Help users run effective one-on-one meetings. Use when someone is a new manager setting up 1:1s, struggling to make 1:1s productive, wants to improve career conversations with reports, or needs to handle difficult 1:1 situations.
Help users generate and evaluate startup ideas. Use when someone is brainstorming business ideas, trying to find a startup concept, evaluating whether an idea is worth pursuing, or looking for unique market opportunities.
Help users design effective team rituals. Use when someone is building team culture, creating recurring team practices, trying to improve team communication, or establishing operational rhythms for their organization.
Help users define their North Star metric. Use when someone is choosing their primary success metric, trying to align the team around a key measure, struggling with metric proliferation, or setting up their measurement strategy.
Help users write effective PRDs. Use when someone is documenting product requirements, preparing specs for engineering, writing feature briefs, or defining what to build for their team.
Render line charts from provided timeseries data into PNG images for reports. Use when the user asks for trend charts, 7-day/30-day/90-day net value charts, or visual time-series evidence instead of text-only trend blocks.
使用遗忘曲线管理会话记忆(SQLite):按永久记忆/衰减记忆分类写入、按时间自动更新 fresh/active/fading/blurry/forgotten 状态、按话题检索、执行遗忘删除、从周归档恢复,以及生成每周记忆汇总。适用于用户要求“记住/别记/恢复记忆/周总结/记忆系统落库”等场景。
# Skill: news_collector ## 目标 收集影响资产配置或增强仓位的重要新闻线索,并形成结构化摘要。 ## 对应项目目的 - 新闻信息收集 - 风险预警 - 投资辅助建议 ## 输入 - 时间范围:最近一周或最近一月 - 主题范围:宏观、政策、行业、基金、公司 - 可选关注主题:电网、机器人、科技基础设施 ## 输出 - 新闻条目列表 - 分类汇总 - 事实 / 解读 / 待验证假设 - 对仓位或风险的可能影响 ## 步骤 1. 收集指定时间范围内的新闻 2. 按主题分类 3. 区分事实、解读、待验证假设 4. 标记可能影响的资产类别或行业 5. 输出结构化结果 ## 失败处理 - 若缺少可靠来源:只输出线索,不给结论 - 若影响不明确:标记为观察项
Implements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring >5 tool calls. Supports automatic session recovery after /clear.
Analyze policy documents and current affairs for decision signals using a seven-step framework with pre-analysis knowledge diagnosis and active knowledge-gap filling. Use for policy/event interpretation, impact analysis, and action-oriented briefings (not plain summaries). Supports source labeling ([数据库]/[推断]/[待验证]/[知识缺口]/[外部补充]/[外部补充:browser]) and SQLite knowledge sedimentation.
Search and collect policy/current-affairs source materials before analysis. Use when input is fragmented (keywords, fuzzy title, retell, or URL), when weekly/manual inspection is requested, or when analysis workflow reports critical knowledge gaps. Separates retrieval from analysis and controls agent-browser usage by priority.
# Skill: portfolio_analyzer ## 目标 分析当前仓位,输出总资产、各大类占比、偏离情况、低配与高配项。 ## 对应项目目的 - 管理仓位 - 风险预警 - 周报月报 ## 输入 - `system/portfolio_state.json` - `system/target_allocation.json` ## 输出 - `total_value` - `allocation` - `deviation` - `underweight` - `overweight` - `status` ## 步骤 1. 读取资产数据 2. 按 category 聚合 3. 计算总值与占比 4. 与目标配置比较 5. 输出结构化结果 ## 失败处理 - 缺少资产值:返回 `incomplete_data` - 总资产为 0:返回 `calculation_blocked` - 未知分类:写入 `uncategorized`
Add, update, remove, reset, or sync portfolio holdings from natural-language instructions or daily position screenshots, updating portfolio_state.json and related snapshot files while explaining provider support and downstream workflow impact.
轻量主动代理增强。用于在不显著增加 token 的前提下引入 4 个高价值机制:VBR(先验证再汇报)、Autonomous vs Prompted Cron 区分、工具迁移检查清单、会话压缩恢复流程。适用于避免“改了文本没改机制”、减少自动任务失效、提高会话连续性。
# Skill: rebalancing_engine ## 目标 判断是否触发再平衡检查,并给出优先方案。 ## 对应项目目的 - 管理仓位 - 风险预警 - 月报 ## 输入 - `portfolio_analyzer` 输出结果 - 再平衡阈值:±10% ## 输出 - 是否触发 - 触发原因 - 优先处理顺序 - 是否需要继续观察 ## 步骤 1. 检查各类资产偏离 2. 判断是否超出阈值 3. 若触发,优先给出用新资金修正方案 4. 必要时给出卖出讨论项 ## 失败处理 - 若分析结果缺失:返回 `need_portfolio_analysis`
# Skill: report_generator ## 目标 输出周报或月报。 ## 对应项目目的 - 风险预警 - 周报月报 - 投资辅助建议 ## 输入 - `portfolio_analyzer` 结果 - `rebalancing_engine` 结果 - `monthly_planner` 结果(用于月报) - `news_collector` 结果(用于周报或月报) ## 输出 - 周报或月报 markdown - 结论摘要 - 风险摘要 - 观察项 ## 步骤 1. 识别报告类型 2. 汇总仓位、风险、建议、新闻 3. 用固定模板生成报告 ## 失败处理 - 缺少新闻时,可只输出仓位与风险部分 - 缺少月度建议时,月报中明确标记待补充
Add, update, remove, or audit asset research objects in asset_research.json so newly added holdings can participate in signal evaluation, report highlights, news topic mapping, and future watchlist workflows.
Compact long Telegram chat sessions and prevent silent non-replies caused by high context usage. Use when a Telegram conversation becomes slow, misses replies, or session tokens are high (for example above ~80-85%), and when the user asks to clean, rotate, or shrink Telegram context.
Restrict file edits to a specific directory for the session. Blocks Edit and Write outside the allowed path. Use when debugging to prevent accidentally "fixing" unrelated code, or when you want to scope changes to one module. Use when asked to "freeze", "restrict edits", "only edit this folder", or "lock down edits".
Designer's eye plan review — interactive, like CEO and Eng review. Rates each design dimension 0-10, explains what would make it a 10, then fixes the plan to get there. Works in plan mode. For live site visual audits, use /design-review. Use when asked to "review the design plan" or "design critique". Proactively suggest when the user has a plan with UI/UX components that should be reviewed before implementation.
Report-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead. Proactively suggest when the user wants a bug report without any code changes.
Help users define AI product strategy. Use when someone is building an AI product, deciding where to apply AI in their product, planning an AI roadmap, evaluating build vs buy for AI capabilities, or figuring out how to integrate AI into existing products.
Help users create and run AI evaluations. Use when someone is building evals for LLM products, measuring model quality, creating test cases, designing rubrics, or trying to systematically measure AI output quality.
Help users synthesize and act on customer feedback. Use when someone is analyzing NPS responses, processing support tickets, reviewing user research, synthesizing feedback from multiple channels, or trying to identify patterns in customer input.
Help users get promoted at work. Use when someone is preparing for a promotion conversation, building their case for advancement, trying to understand what's blocking their promotion, or figuring out how to get to the next level in their career.
Help users navigate career changes and pivots. Use when someone is considering a new role, transitioning into product management, evaluating job offers, taking a sabbatical, or feeling stuck in their current position.
Help users run better customer and user interviews. Use when someone is preparing for user research, planning discovery interviews, writing interview questions, analyzing interview findings, or trying to understand customer needs.
Help users create compelling product visions. Use when someone is writing a vision statement, defining a long-term product direction, aligning teams on the future state, or distinguishing vision from strategy.
Help users build and scale design systems. Use when someone is creating a component library, establishing design tokens, scaling brand consistency, or deciding when to invest in a design system.
Help users manage their energy for sustained performance. Use when someone is feeling burned out, trying to find their zone of genius, scheduling for productivity, or identifying what drains vs energizes them.
Help users evaluate emerging technologies. Use when someone is assessing new tools, making build vs buy decisions, evaluating AI vendors, or deciding on technical architecture.
Help founders close their first customers and build repeatable sales processes. Use when someone is doing founder-led sales, trying to get their first customers, writing cold outreach, running early sales calls, or asking when to hire their first salesperson.
Help users build relationships with mentors and sponsors for career growth. Use when someone is looking for career guidance, wants to find a mentor, needs an advocate at work, is trying to build their professional network, or asking how to get advice from senior leaders.
Help users build and manage marketplace liquidity. Use when someone is working on a marketplace business, struggling with supply/demand balance, trying to improve match rates, or asking how to reach critical mass in a two-sided market.
Help users build relationships with journalists and get press coverage. Use when someone is pitching reporters, preparing for media outreach, trying to get press coverage, or managing ongoing journalist relationships.
Help users negotiate job offers and compensation. Use when someone is negotiating salary, equity, or other terms of a job offer, preparing for a compensation conversation, or asking how to ask for more money.
Help users transform organizations toward modern product practices. Use when someone is trying to shift from feature teams to product teams, introduce empowered teams, modernize legacy processes, or drive cultural change in how product is built.
Help users navigate tough feedback, performance conversations, and conflict. Use when someone needs to give hard feedback, have a performance conversation, fire someone, address conflict with a colleague, or deliver disappointing news like a denied promotion.
Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. Use when asked to "review this PR", "code review", "pre-landing review", or "check my diff". Proactively suggest when the user is about to merge or land code changes.
# Skill: monthly_planner ## 目标 根据当前仓位与目标配置,给出月度定投建议。 ## 对应项目目的 - 管理仓位 - 风险预警 - 月报 ## 输入 - `system/portfolio_state.json` - `system/target_allocation.json` - 月度资金,默认 12000 ## 输出 - 建议投向 - 分配金额 - 建议理由 - 风险提示 ## 步骤 1. 调用 `portfolio_analyzer` 2. 识别低配资产 3. 按低配程度分配新资金 4. 若偏离很大,附带再平衡提示 5. 输出结构化建议 ## 失败处理 - 若仓位数据不足:只输出需要补充的数据 - 若没有明显低配项:按目标配置近似分配
Import daily portfolio screenshots from local files or future Telegram attachments, use a vision model first and OCR as fallback, then hand structured candidate objects to portfolio_editor for validated sync.
Fast browser automation via agent-browser (accessibility snapshot + ref-based interaction). Use when automating multi-step web workflows, deterministic element selection is needed, SPA pages are complex, or isolated browser sessions/state persistence are required.
Help users design and execute platform business strategies. Use when someone is building a marketplace, creating an ecosystem, deciding on API strategy, thinking about multi-sided network effects, or building developer platforms.
Help users prioritize product roadmaps and backlogs. Use when someone is deciding what to build next, sequencing features, allocating resources across projects, handling stakeholder requests, or struggling with too many competing priorities.
Help users design and optimize pricing strategies. Use when someone is setting prices for the first time, considering freemium vs paid models, optimizing monetization, dealing with willingness to pay questions, or transitioning between pricing models.
Help users run effective design reviews and critiques. Use when someone is giving design feedback, establishing design review processes, struggling to evaluate designs, or wants to improve how their team discusses design work.
Help users align stakeholders and get buy-in. Use when someone is struggling to get approval, facing resistance to their ideas, needs to influence without authority, or is preparing for an important executive presentation.
Help users design sales compensation plans. Use when someone is hiring their first sales rep, restructuring sales comp, trying to align sales incentives with business goals, or dealing with comp plan issues like sandbagging or churn.
Help users scope projects and cut features effectively. Use when someone is defining an MVP, dealing with scope creep, trying to ship faster, or needs to make tradeoffs about what to build.
Help users ship products faster and with higher quality. Use when someone is planning a launch, struggling to release features, dealing with shipping velocity issues, or trying to establish better release practices.
Help users decide when and how to pivot their startup. Use when someone is questioning their current direction, seeing poor traction, considering a major strategy change, or stuck in the pre-PMF stage.
Help users think in systems and understand complex dynamics. Use when someone is dealing with multi-stakeholder problems, trying to understand second-order effects, managing platform ecosystems, or analyzing complex organizational dynamics.
Help users conduct effective usability testing. Use when someone is planning user tests, designing prototype validation, preparing usability studies, or trying to understand why users struggle with their product.
轻量自我改进记录技能。用于把错误、用户纠正、知识缺口、功能诉求写入 `.learnings/`,并在每天回顾时将高价值经验提升到 AGENTS.md / SOUL.md / TOOLS.md / MEMORY.md。适用于“避免重复犯错、沉淀经验、降低长期 token 浪费”的场景;默认不启用高频 hooks。
Send local files to Telegram chats through OpenClaw CLI delivery. Use when a user asks to send or forward a file (md/txt/pdf/image/video) to Telegram, especially from workspace paths. Supports direct chat targets and group/topic targets.
Help users set and hit realistic deadlines. Use when someone is planning project timelines, struggling to hit deadlines, dealing with timeline pressure from stakeholders, or trying to improve estimation accuracy.
Help users assess and achieve product-market fit. Use when someone is trying to determine if they have PMF, measuring user engagement and retention, running the Sean Ellis survey, or figuring out if they should scale or keep iterating.
Help users make better decisions between competing options. Use when someone is weighing pros and cons, comparing alternatives, struggling with a difficult choice, deciding between speed and quality, or asking "should we do X or Y?"
Post-ship documentation update. Reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped, polishes CHANGELOG voice, cleans up TODOS, and optionally bumps VERSION. Use when asked to "update the docs", "sync documentation", or "post-ship docs". Proactively suggest after a PR is merged or code is shipped.
Fast headless browser for QA testing and site dogfooding. Navigate any URL, interact with elements, verify page state, diff before/after actions, take annotated screenshots, check responsive layouts, test forms and uploads, handle dialogs, and assert element states. ~100ms per command. Use when you need to test a feature, verify a deployment, dogfood a user flow, or file a bug with evidence. Use when asked to "open in browser", "test the site", "take a screenshot", or "dogfood this".
Safety guardrails for destructive commands. Warns before rm -rf, DROP TABLE, force-push, git reset --hard, kubectl delete, and similar destructive operations. User can override each warning. Use when touching prod, debugging live systems, or working in a shared environment. Use when asked to "be careful", "safety mode", "prod mode", or "careful mode".
OpenAI Codex CLI wrapper — three modes. Code review: independent diff review via codex review with pass/fail gate. Challenge: adversarial mode that tries to break your code. Consult: ask codex anything with session continuity for follow-ups. The "200 IQ autistic developer" second opinion. Use when asked to "codex review", "codex challenge", "ask codex", "second opinion", or "consult codex".
Upgrade gstack to the latest version. Detects global vs vendored install, runs the upgrade, and shows what's new. Use when asked to "upgrade gstack", "update gstack", or "get latest version".
Full safety mode: destructive command warnings + directory-scoped edits. Combines /careful (warns before rm -rf, DROP TABLE, force-push, etc.) with /freeze (blocks edits outside a specified directory). Use for maximum safety when touching prod or debugging live systems. Use when asked to "guard mode", "full safety", "lock it down", or "maximum safety".
Systematic debugging with root cause investigation. Four phases: investigate, analyze, hypothesize, implement. Iron Law: no fixes without root cause. Use when asked to "debug this", "fix this bug", "why is this broken", "investigate this error", or "root cause analysis". Proactively suggest when the user reports errors, unexpected behavior, or is troubleshooting why something stopped working.
Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when the user has a plan or design doc and is about to start coding — to catch architecture issues before implementation.
Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Proactively suggest when the user says a feature is ready for testing or asks "does this work?". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only.
Import cookies from your real browser (Comet, Chrome, Arc, Brave, Edge) into the headless browse session. Opens an interactive picker UI where you select which cookie domains to import. Use before QA testing authenticated pages. Use when asked to "import cookies", "login to the site", or "authenticate the browser".
Help users apply behavioral science to product design. Use when someone is designing for habit formation, reducing friction, applying psychology to UX, increasing retention through behavioral principles, or using nudges to influence user behavior.
Help users build and scale their sales organization. Use when someone is hiring their first salespeople, deciding when to bring on sales leadership, structuring sales compensation, or transitioning from founder-led sales.
Help users build and maintain strong team culture. Use when someone is defining team values, creating psychological safety, onboarding to a new team, navigating cultural change, or building distributed team norms.
Help users develop and coach product managers. Use when someone is managing PMs, creating development plans, running performance reviews, or trying to level up their PM team's capabilities.
Help users understand and respond to competition. Use when someone is positioning against competitors, evaluating market threats, running competitive war games, or deciding how much to focus on competitors versus customers.
Help users build content marketing strategies. Use when someone is starting a blog, building SEO, creating thought leadership content, or deciding on content formats and distribution channels.
Help users understand and build design engineering capabilities. Use when someone is creating a design engineering function, hiring design engineers, or bridging the gap between design and engineering teams.
Help users design and optimize growth loops. Use when someone is building viral mechanics, designing referral programs, creating product-led acquisition, or figuring out how to make their product grow itself.
Help users design effective surveys. Use when someone is creating customer surveys, NPS measurements, product-market fit surveys, or feedback collection mechanisms.
Help users build strong engineering culture. Use when someone is improving developer experience, fostering technical excellence, designing engineering practices, or scaling an engineering organization.
Help users navigate enterprise sales. Use when someone is closing large deals, managing complex buying committees, handling procurement, or converting PLG users to enterprise contracts.
Help users make better hiring decisions. Use when someone is evaluating job candidates, making hiring decisions, conducting reference checks, reviewing work samples or take-homes, calibrating their hiring bar, or deciding between finalists.
Help founders raise capital and build investor relationships. Use when someone is preparing a pitch deck, deciding whether to raise venture capital, meeting with investors, or asking about fundraising strategy.
Help users create and deliver compelling presentations. Use when someone is preparing a talk, building a slide deck, dealing with presentation anxiety, practicing for a keynote, or asking how to be more engaging when presenting.
Help users work through feelings of inadequacy and self-doubt. Use when someone feels like a fraud, doubts their qualifications, is anxious about being "found out," or struggling with confidence in a new or challenging role.
Help users work effectively with their manager and executives. Use when someone is struggling with their manager relationship, needs to influence leadership, wants to get better at executive communication, or is trying to build trust with their boss.
Help users onboard new team members effectively. Use when someone is planning onboarding for a new hire, starting a new job themselves, designing a first-90-days plan, or trying to ramp up new employees faster.
Help users build strategic partnerships and business development deals. Use when someone is pursuing a partnership, negotiating a BD deal, working with platforms like Google or Facebook, or trying to build distribution through partners.
Help users manage their time and tasks more effectively. Use when someone is overwhelmed with work, struggling with focus, trying to balance multiple responsibilities, or asking how to get more done.
Help users craft product positioning and messaging. Use when someone is launching a product, differentiating from competitors, writing marketing copy, struggling to explain what their product does, or working on value propositions and taglines.
Help users run effective post-mortems and retrospectives. Use when someone is reviewing a project that succeeded or failed, wants to establish learning practices, is dealing with failure aftermath, or needs to improve team learning loops.
Help users define problems clearly before jumping to solutions. Use when someone is scoping a new feature, validating a product idea, struggling to articulate what they're building, or falling into the "shiny object trap" with new technology.
Help users improve retention and engagement metrics. Use when someone is dealing with churn, optimizing activation flows, building habit-forming products, or trying to increase user engagement and lifetime value.
Help users build and scale product operations functions. Use when someone is scaling a product team, struggling with cross-functional coordination, needs to standardize product processes, or wants to improve how insights reach product teams.
Help users run effective decision-making processes. Use when someone is facing a high-stakes decision, dealing with analysis paralysis, needs to align stakeholders on a choice, or wants to establish decision frameworks like DACI or RAPID.
Help users set effective OKRs and goals. Use when someone is creating quarterly objectives, defining key results, setting team goals, planning annual targets, or struggling with goal alignment across their organization.
Help users run more effective meetings. Use when someone is dealing with meeting overload, wants to improve meeting culture, is preparing an important meeting, or struggles to get decisions made in meetings.
Help users qualify sales leads effectively. Use when someone is wasting time on bad leads, struggling with low conversion rates, needs to build a qualification framework, or wants to improve their discovery process.
Help users plan and run effective team offsites. Use when someone is organizing a team retreat, planning a strategy offsite, trying to improve remote team cohesion, or preparing for quarterly planning sessions.
Help users create technical roadmaps. Use when someone is planning engineering work, prioritizing tech debt, building architecture roadmaps, or aligning technical and product strategy.
Help users build software using AI coding tools. Use when someone is using AI to generate code, building prototypes without deep technical skills, or exploring how non-engineers can create functional software through natural language.
Help users apply the working backwards methodology. Use when someone is defining a new product, writing a PR/FAQ, planning from a future state, or trying to clarify a product's value proposition before building.
Help users write effective job descriptions. Use when someone is creating a job posting, defining a new role, preparing to hire, or trying to attract the right candidates for an open position.
Help users write effective specs and design documents. Use when someone is creating technical specs, feature specs, design docs, or trying to communicate product requirements to engineering and design teams.
Help users communicate more effectively in writing. Use when someone is drafting memos, emails, strategy docs, announcements, or any written communication that needs to be clear, concise, and persuasive.