Loading...
Loading...
Found 279 Skills
Prioritize SEO initiatives as product roadmap work with impact, effort, confidence, resourcing, executive pitch, cross-functional ownership, quarterly planning, and business KPI alignment. Use when building SEO roadmaps, scoring SEO work, requesting engineering/design/content resources, annual planning, executive buy-in, or turning SEO recommendations into product-ready asks.
When legal analysis identifies multiple possible conclusions, risk points, or issues in dispute, these risks must be systematically prioritized according to their likelihood of occurrence and magnitude of impact, helping decision-makers focus on the most critical risks and allocate resources rationally. This skill is triggered in the following scenarios: (1) multiple compliance risks identified during legal due diligence need to be prioritized; (2) litigation strategy development requires evaluating the likelihood and consequences of multiple unfavorable outcomes; (3) transaction structuring requires identifying and ranking key legal obstacles; (4) contract review identifies multiple risky provisions whose revision priorities must be determined; (5) regulatory compliance assessment requires tiering and managing multiple violations risks; and (6) any scenario requiring strategic trade-offs among legal risks under resource constraints.
A framework for classifying product decisions based on impact and reversibility. Use this when you feel like a bottleneck for your team, when you have a massive backlog of choices to make, or when you need to justify spending weeks of research on a single high-stakes problem.
Comprehensive computational validation of drug targets for early-stage drug discovery. Evaluates targets across 10 dimensions (disambiguation, disease association, druggability, chemical matter, clinical precedent, safety, pathway context, validation evidence, structural insights, validation roadmap) using 60+ ToolUniverse tools. Produces a quantitative Target Validation Score (0-100) with GO/NO-GO recommendation. Use when users ask about target validation, druggability assessment, target prioritization, or "is X a good drug target for Y?"
Conduct Pareto Analysis (80/20 Rule) to identify the vital few causes driving the majority of problems. Guides data collection, category definition, chart creation, cumulative percentage calculation, and prioritization. Generates professional Pareto charts (SVG) and HTML reports with quality scoring. Use when prioritizing defects, complaints, failures, or improvement opportunities; when user mentions "Pareto", "80/20 rule", "vital few", "trivial many", "prioritization", or needs to identify which factors contribute most to a problem.
Evaluate strategic options by NPV vs ease of implementation. Use for project prioritization, resource allocation, and strategic decision making.
Build MECE issue trees for complex business problems. Use when you need rigorous problem decomposition, branch prioritization, and a decision-ready analysis backlog.
[Project Management] Capture ideas, manage product backlogs, apply prioritization frameworks (RICE, MoSCoW), and facilitate stakeholder communication. Triggers: product owner, backlog management, user story prioritization, product roadmap, product backlog.
Analyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.
Use production telemetry as INPUT to design new tests. Covers OpenTelemetry integration with tests, trace-based assertions, log-informed test creation, production-error analysis for coverage gaps, and telemetry-driven test prioritization. Use when: "trace-based testing," "design tests from logs," "OpenTelemetry assertions," "production errors point to test gaps," "telemetry-driven testing." Not for: safe rollout techniques (flags, canary) during release — use testing-in-production. Not for: scheduled post-deploy probes — use synthetic-monitoring. Not for: triaging CI failures — use ai-bug-triage. Related: testing-in-production, synthetic-monitoring, qa-metrics, ai-bug-triage.
Product requirements and planning specialist. Creates PRDs and tech specs with functional/non-functional requirements, prioritizes features using MoSCoW/RICE frameworks, breaks down epics into user stories, and ensures requirements are testable and traceable. Use for PRD creation, requirements definition, feature prioritization, tech specs, epics, user stories, and acceptance criteria.
Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.