Loading...
Loading...
Found 129 Skills
This skill should be used when the user asks about enterprise strategy, corporate strategy, business unit strategy, portfolio prioritization, strategic roadmap, growth strategy, diversification, operating model, capability map, strategic initiative, enterprise transformation, board strategy, scenario planning, or competitive positioning at enterprise level. Guides corporate and BU strategy, portfolio prioritization, growth and diversification, market positioning, operating model and capabilities, transformation roadmaps, M&A/partnership/divestiture framing (strategy—not legal DD), scenarios, executive alignment, and KPI trees—not product backlog or program RAID (technical-program-manager), financial models only (financial-analyst), contracts (commercial-counsel), cloud or system architecture alone (enterprise-cloud-architect, senior-system-architecture), or consulting workshops without enterprise portfolio scope (business-consultant).
Ecology, biodiversity, and conservation biology research — species identification (GBIF, NCBI Taxonomy), invasive species impact, ecosystem dynamics, conservation status (IUCN), niche ecology. Use for biodiversity questions, species comparison, invasion biology, conservation prioritization, and ecology-related literature search.
Google Search Console indexing assistant. Use when the user wants to track page indexing status, compare sitemap against GSC indexed pages, manage submission tracking, or move false positives (pages indexed per URL Inspection but not yet in GSC export) to the indexed list. Maintains two tracking files (indexed.md, to-index.md) with prioritization support.
Focus testing effort on highest-risk areas using risk assessment and prioritization. Use when planning test strategy, allocating testing resources, or making coverage decisions.
50 growth hacking tactics ranked by effort vs impact. Each experiment includes setup instructions, expected timeline, and success metrics. Data-driven prioritization for resource-constrained startups. Follow @WeiYipei on X.
"What is important is seldom urgent and what is urgent is seldom important." Master Dwight D. Eisenhower's prioritization framework to focus on what truly matters. Use when: **Feeling overwhelmed** by too many tasks and not enough time; **Weekly planning** to set priorities for the week ahead; **Daily triage** when everything seems urgent; **Delegation decisions** to identify what others should handle; **Saying no** by recognizing tasks that shouldn't be done at all
Revenue.io platform help — Salesforce-native revenue orchestration with RingDNA dialer, Guided Selling cadences, Moments real-time coaching, conversation intelligence, and Revenue Intelligence dashboards. Use when calls not logging to Salesforce from Revenue.io, setting up Guided Selling cadences and task prioritization, configuring Moments real-time coaching notifications, choosing between Activate vs Engage vs Orchestrate tiers, dialer call dispositions not syncing to Salesforce, or Revenue.io vs Gong for conversation intelligence. Do NOT use for general conversation intelligence strategy (use /sales-note-taker) or building a coaching program (use /sales-coaching).
Run a structured business analysis workflow: requirements elicitation with stakeholder interviews and MoSCoW prioritization, as-is/to-be process mapping with BPMN notation, data-driven analysis (CBA, SWOT, root cause), and production-ready documentation (BRD, FRD, user stories with INVEST acceptance criteria). Triggers on "gather requirements", "write user stories", "map business process", "BRD", "FRD", "gap analysis", "cost-benefit analysis", "facilitate workshop", "business requirements", "process mapping", "as-is to-be", "stakeholder interview", or "business analyst". For management consulting (issue trees, steerCo business cases, operating model), use business-consultant—not business-analyst. For business model canvas, market sizing, and unit economics research, use business-model-researcher. Human data / labeling platform PRDs: product-management-human-data-platform. Monetization PRDs and packaging: product-management-monetization.
Comprehensive OSINT methodology for external red-team operations and authorized attack-surface assessments. Covers the 5-stage recon pipeline (seed discovery, asset expansion, enrichment, exposure analysis, reporting), asset-graph discipline with 29 asset types, severity rubric (CRITICAL/HIGH/MEDIUM/LOW/INFO), confidence upgrade workflows, time budgeting, asset-level triage rules, scale-based tactics, identity-fabric mapping (Entra/Okta/ADFS/Google/SAML/M365 Teams+SharePoint+OAuth), API and auth-map methodology, JavaScript deep analysis, mobile attack surface, cloud attack surface, breach×identity correlation, detectability tagging, detection-aware probing (back-off, persona rotation), read-only validator discipline, WAF/CDN bypass + origin discovery, vulnerability prioritization (CVE/EPSS/KEV), phishing infrastructure planning + pretext development, bug bounty submission templates, client deliverable templates with risk translation, threat-actor investigation (incl. RU/CN pivots), cryptocurrency tracing, image/video forensics, chronolocation. Use when planning or executing reconnaissance against authorized targets, mapping an organization's external attack surface, investigating a person/entity, tracing crypto flows, geolocating media, or performing attribution work.
Orchestrated, idea-to-plan PM workflow. Establishes context once, then composes the PM generative ladder in order — problem → discovery → users → riskiest-assumption test → prioritization → spec → metrics — gating each step, enforcing evidence before the spec, and handing the result to product-review. Trigger when the user wants to go from a raw idea to a build-ready plan ("take me from problem to plan", "I have an app idea, where do I start", "turn this idea into a product plan", "plan a new product end to end") — but NOT when they ask for one specific PM artifact (let that skill trigger directly), and NOT for the strategy/launch arc (vision, competitive analysis, roadmap, GTM — offer those next).
Use this skill to shape product or engineering work before committing time to it: set appetites instead of estimates, narrow raw ideas into bounded problems, sketch solutions at the right level of abstraction, de-risk rabbit holes, write pitches, bet with capped downside (circuit breaker), and govern builds with discovered scopes and scope hammering. Adapted from Basecamp's Shape Up and extended for human+AI-agent teams. Use when a raw idea, feature request, or "redesign X" grab-bag needs to become a bounded project before anyone builds; when planning how much work an idea is worth; or when delegated agent builds need budgets, kill criteria, and non-convergence rules. Do not use for discovering whether a problem is real (use product-discovery), for portfolio-level sequencing across quarters (product-roadmapping-and-portfolio), for formal specification after the bet is placed (spec-driven-development), or for task-level prioritization frameworks like RICE (product-methodology).
Track, categorize, and prioritize technical debt when the user asks to manage tech debt, create a tech debt register, assess code quality, or plan refactoring work