Loading...
Loading...
Found 1,681 Skills
Universal deep research agent team. 13-agent pipeline for rigorous academic research on any topic. 7 modes: full research, quick brief, paper review, lit-review, fact-check, Socratic guided research dialogue, and systematic review with optional meta-analysis. Covers research question formulation, Socratic mentoring, methodology design, systematic literature search, source verification, cross-source synthesis, risk of bias assessment, meta-analysis, APA 7.0 report compilation, editorial review, devil's advocate challenges, ethics review, and post-research literature monitoring. Triggers on: research, deep research, literature review, systematic review, meta-analysis, PRISMA, evidence synthesis, fact-check, guide my research, help me think through, 研究, 深度研究, 文獻回顧, 文獻探討, 系統性回顧, 後設分析, 事實查核, 引導我的研究, 幫我釐清, 幫我想想, 我不確定要研究什麼, 研究方向, 研究主題.
Mailshake platform help — campaigns, Lead Catcher, recipients, senders, webhooks, API, analytics, integrations, deliverability settings. Use when asking 'how do I do X in Mailshake', configuring Mailshake settings, setting up Lead Catcher, managing campaigns/recipients, connecting integrations, or using the Mailshake API. Do NOT use for building prospect lists (use /sales-prospect-list), enriching contacts (use /sales-enrich), designing cadence strategy (use /sales-cadence), or cross-platform deliverability (use /sales-deliverability).
Woodpecker.co platform help — cold email campaigns, condition-based sequences, email warmup, Bounce Shield, Adaptive Sending, email verification, inbox rotation, centralized inbox, LinkedIn automation, Lead Finder, agency panel, API & webhooks. Use when asking 'how do I do X in Woodpecker', setting up Woodpecker campaigns, configuring Woodpecker warmup or deliverability, using Woodpecker's agency panel, or troubleshooting Woodpecker sending issues. Do NOT use for general outbound cadence strategy (use /sales-cadence), cross-platform email deliverability (use /sales-deliverability), email tracking strategy (use /sales-email-tracking), building prospect lists (use /sales-prospect-list), or connecting Woodpecker to other tools via Zapier (use /sales-integration).
Reply.io platform help — multichannel sequences (email, LinkedIn, calls, SMS, WhatsApp), Jason AI SDR, B2B database, email warmup, deliverability tools, unified inbox, analytics, Salesforce/HubSpot integration, agency features. Use when asking 'how do I do X in Reply.io', setting up Reply.io sequences, configuring Jason AI, connecting Reply.io to Salesforce or HubSpot, using Reply.io warmup, or troubleshooting Reply.io deliverability. Do NOT use for general outbound cadence strategy (use /sales-cadence), cross-platform email deliverability (use /sales-deliverability), email tracking strategy (use /sales-email-tracking), building prospect lists (use /sales-prospect-list), or connecting Reply.io to other tools via Zapier (use /sales-integration).
Severity scoring, scorecard computation, confidence levels, and remediation tracking for web accessibility audits. Use when computing page accessibility scores (0-100 with A-F grades), tracking remediation progress across audits, or generating cross-page comparison scorecards.
Create or update root and nested AGENTS.md files that document scoped conventions, monorepo module maps, cross-domain workflows, and (optionally) per-module feature maps (feature -> paths, entrypoints, tests, docs). Use when the user asks for AGENTS.md, nested agent instructions, or a module/feature map.
Anymail Finder platform help — email finder and verification tool with 97%+ delivery guarantee. Finds emails by person name, company/domain, decision-maker role, or LinkedIn URL, with bulk search up to 100K rows and a GeoLead Finder. Use when looking up emails by name and company, finding decision-maker emails by role, verifying emails, running bulk email searches, finding emails from LinkedIn URLs, or working with the Anymail Finder API. Do NOT use for cross-platform enrichment strategy (use /sales-enrich), email deliverability strategy (use /sales-deliverability), or prospect list strategy (use /sales-prospect-list).
Build a personal knowledge wiki from your notes, journals, and documents. LLM ingests data, synthesizes cross-linked Wikipedia-style articles, and serves a web UI.
📡 Pulse — Twice-daily tech briefing for group distribution. Designed to be triggered by cronjob at morning and evening, or manually. Use this skill only when the user says "pulse" or "/pulse".
Build, review, or migrate .NET MAUI applications across Android, iOS, macOS, and Windows with correct cross-platform UI, platform integration, and native packaging assumptions.
Identifies upsell and cross-sell opportunities within existing customer accounts. Analyzes product usage, feature gaps, team growth, industry benchmarks, and competitive pressure to surface revenue expansion plays scored by potential, effort, and likelihood. Generates an expansion-playbook.md with account-by-account opportunities, recommended pitch, timing, and approach.
Decision Coaching for Vue Component/Composable Refactoring — Users paste a piece of code or point to an SFC, and the skill first performs a diagnosis ("Fat Trunk" / "UI & IO Entanglement" / "Reactivity & Business Logic Entanglement"), then selects one from three recipes, and provides a specific sequence of extraction steps (which variable to move first, what errors the compiler will throw, how to fix them one by one, when rollback is possible). The entire process ensures behavioral equivalence through compiler green lights + step-by-step rollback, without relying on test safeguards. Trigger scenarios: Users say "This Vue component is too fat / I want to extract the logic / Split this SFC / This composable is too messy / Extract a composable / Split into humble / Pure functionalize", or point to an obviously overlong .vue / composable file and request "Refactor / Optimize / Split". Only handles Vue (Vue 2 Options, Vue 2/3 `<script setup>`, composable, pinia store). Does not handle: Adding new features (follow feature process), fixing bugs (follow issue process), cross-module architecture restructuring, backend code.