Loading...
Loading...
Found 149 Skills
Discover genes associated with diseases and traits using GWAS data from the GWAS Catalog (500,000+ associations) and Open Targets Genetics (L2G predictions). Identifies genetic risk factors, prioritizes causal genes via locus-to-gene scoring, and assesses druggability. Use when asked to find genes associated with a disease or trait, discover genetic risk factors, translate GWAS signals to gene targets, or answer questions like "What genes are associated with type 2 diabetes?"
6 buying signals ranked by purchase correlation - Former Customers, New Leadership, High-Intent Website, Tech Stack Change, Expansion, and Hiring/Downsizing. Use when prioritizing outreach, building signal-based campaigns, or setting up intent tracking.
Ghost Security — combined security report. Aggregates findings from all scan skills (scan-deps, scan-secrets, scan-code) into a single prioritized report focused on the highest risk, highest confidence issues. Use when the user requests a security overview, vulnerability summary, full security audit, or combined scan results.
When the user wants to plan SEO strategy, prioritize SEO work, or understand the SEO workflow. Also use when the user mentions "SEO strategy," "SEO plan," "SEO roadmap," "SEO priority," "SEO audit," "SEO workflow," "where to start SEO," "SEO approach," "organic growth strategy," or "search strategy."
Scans codebases for technical debt with AST parsing, prioritizes debt items by impact, and generates trend dashboards. Use when tracking tech debt, prioritizing refactoring, or measuring code quality trends over time.
Analyze JIRA tickets to determine priority and dependency order. Outputs an ordered JIRA ID list. Use before implement/forge, or when asked to "prioritize tickets", "order these JIRAs", "what should I work on first".
Prioritize a backlog of feature ideas based on impact, effort, risk, and strategic alignment with top 5 recommendations. Use when prioritizing a feature backlog, making scope decisions, or ranking product ideas.
Based on the KISS (Keep It Simple, Stupid) and "Minimum Viable Brilliance" complexity control principles. It is used for design and implementation decisions at all levels of projects, systems, modules, code, and functions, helping to prioritize core values, reduce unnecessary complexity, and avoid over-design. Keywords: KISS, simplification, focus, complexity control, Minimum Viable Brilliance.
Make today's plan from my Plane tasks.
Copilot agent that assists with requirements analysis, user story creation, specification definition, and acceptance criteria definition Trigger terms: requirements, EARS format, user stories, functional requirements, non-functional requirements, SRS, requirement analysis, specification, acceptance criteria, requirement validation Use when: User requests involve requirements analyst tasks.
Captures, enriches, tags, and prioritizes roadmap tasks. Use when the user wants to note work quickly, add missing task details, organize a backlog, or reprioritize an existing list of tasks.
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