Loading...
Loading...
Found 1,438 Skills
Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.
Validate environment variables on server start and before builds. Catch missing or invalid variables early with clear error messages.
Connect GWAS variants to biological pathways for drug target discovery. Maps disease-associated SNPs to causal genes via eQTL colocalization (GTEx), links genes to enriched pathways (Reactome, KEGG, MetaCyc), and identifies druggable targets within disease-relevant pathways. Use when asked to translate GWAS findings into mechanistic insights, find pathways enriched for disease genes, discover drug targets from genetic evidence, or answer questions like "What pathways are disrupted in type 2 diabetes based on GWAS data?"
Risk-return optimisation for investment portfolios via Longbridge — builds risk-adjusted return-optimal portfolios based on fund size, risk preference (conservative / balanced / aggressive), and investment horizon. Asset allocation across equities / bonds / cash / commodities / alternatives. Evaluates current portfolio efficiency versus the efficient frontier. Triggers: "风险收益优化", "组合效率", "有效前沿", "风险偏好配置", "最优组合", "风险调整收益", "大类资产配置", "投资组合优化", "風險收益優化", "組合效率", "有效前沿", "風險偏好配置", "最優組合", "risk-return optimization", "portfolio efficiency", "efficient frontier", "risk preference", "optimal portfolio", "risk-adjusted return", "asset class allocation", "portfolio optimisation", "mean variance".
Use when you want to retrieve quantitative RNA expression data and variant eQTL information from the GTEx (Genotype-Tissue Expression) Project across 54 non-diseased tissue sites.
How to handle "why did this work stop / why is this looping?" assignments. Forensics first on the named tree, surface the exact stop-point, frame the fix as a general product rule that respects three invariants (productive work continues, only real blockers stop work, no infinite loops), and deliver a plan — no code changes — gated by board/CTO approval before child issues are created. Use whenever the issue title or body asks for forensics on a stalled, looping, or "went too deep" tree.
Multi-agent trading analysis for a stock ticker. Runs technical, news, fundamentals, and macro analysts in parallel, then an adversarial bull/bear debate, then Research Manager, Trader, and Portfolio Manager to produce a final BUY/SELL/HOLD decision with entry, stop, and sizing.
Create Pydantic models following the multi-model pattern with Base, Create, Update, Response, and InDB variants. Use when defining API request/response schemas, database models, or data validation in Python applications using Pydantic v2.
Writes, classifies, and revises WhatsApp templates for Sent, including utility, marketing, and authentication category decisions, variable samples, component structure, rejection-risk review, and Sent template submission. Use when a user says WhatsApp template, WABA template, template category, utility vs marketing, authentication template, Meta rejection, template samples, buttons, or wants approved WhatsApp copy in Sent.
Runs a full inbox triage using the knowledge base created by the 'inbox-setup' skill. Light-intake by design (most invocations skip questions and run with KB-default preferences); asks at most 2 grill-me override questions when invocation is outside normal cadence or includes category-skip intent. Searches recent emails, classifies them via the user's taxonomy, researches new senders, generates recommendations, drafts replies (NEVER sends), delivers a report in the user's preferred format, and updates the knowledge base with learnings. Designed to run on a recurring schedule (1-3x daily) or on demand. Triggers: 'triage my inbox', 'inbox triage', 'check my email', 'run email triage', 'process my inbox', 'what's new in my email', 'handle my email', 'email triage', or any variation where the user wants their inbox processed. Requires the inbox-setup skill to have been run first.
Designs and audits a Sent template builder UI for cross-channel SMS, WhatsApp, and RCS templates, including component editing, variable samples, status handling, channel-specific validation, and submission workflows. Use when a user says template builder, template editor, Sent templates, WhatsApp template UI, RCS template, SMS template, Meta import, JSON template, approval status, or wants a product spec for template creation. Do not use for generic templating engines (Jinja, Handlebars, Mustache, email/HTML templates) or non-Sent template systems.
A structured root-cause investigation protocol for complex, ambiguous, or multi-layer technical problems. Activate this skill whenever: a problem has resisted two or more fix attempts; the root cause is unknown or assumed; you are tempted to try a variation of something that already failed; a system has multiple interacting layers (hardware, OS, runtime, middleware, config, network); the user says "ultrathink", "think deeper", "figure out why", "stop guessing", "find the root cause", or "it's still broken after your fix". Also activate proactively when you catch yourself about to write a fix before you have verified the cause — that instinct is the signal the protocol is needed. The protocol enforces three disciplines that distinguish root-cause investigation from trial-and-error: (1) explicit THOUGHT/ACTION/OBSERVATION cycles, (2) a hard gate that blocks implementation until the cause is verified by direct evidence, and (3) structured escalation when in-process diagnostic tools are exhausted.