Loading...
Loading...
Found 149 Skills
Guidelines for using skills effectively - load relevant skills before complex tasks, not every message
Run /check-posthog, then create GitHub issues for all findings. Each finding becomes a separate, actionable issue with clear acceptance criteria. Invoke for: PostHog audit to issues, analytics backlog creation.
Identifies which user segment to focus on first using pain severity, willingness to pay, reachability, and strategic alignment. Use when choosing your initial target audience or re-evaluating segment focus.
Use when user asks to "discover tasks", "find next task", or "prioritize issues". Discovers and ranks tasks from GitHub, GitLab, local files, and custom sources.
Daily standup assistant for Benjamin that compiles work priorities from Jira and Slack into a single prioritized task list. This skill should be used when Benjamin asks for morning standup, daily priorities, what to work on today, or needs to compile work items.
Identify and prioritize causal variants at GWAS loci using statistical fine-mapping and locus-to-gene predictions. Computes posterior probabilities for causal variants, links variants to genes via L2G predictions, annotates functional consequences, and suggests validation strategies. Use when asked to fine-map GWAS loci, prioritize causal variants, identify credible sets, or link GWAS signals to causal genes.
James Bach's HTSM Product Factors (SFDIPOT) analysis for comprehensive test strategy generation. Use when analyzing requirements, epics, or user stories to generate prioritized test ideas across Structure, Function, Data, Interfaces, Platform, Operations, and Time dimensions.
Analyzes album state and recommends the optimal next action. Use when the user asks "what should I do next?" or "what's left to do?"
Product manager that decomposes requirements into actionable tasks with priorities and dependencies
Use when research direction needs assessment, critical knowledge gaps must be identified, or priorities must be recommended based on impact, dependencies, and effort (especially at project milestones or when scope questions arise)
Use when theoretical calculations need experimental validation, protocols must be designed with clear hypotheses and success criteria, or resource requirements (equipment, materials, expertise) must be estimated for proposed experiments
Analyze existing PRD to identify and recommend the single highest-priority task to work on next