Research & Search

reinamaccredy Bundle

Answer an evidence question without touching production code - research external facts against primary sources, build or iterate a disposable prototype (its own bugfixes included), or baseline current repository behavior before deciding or implementing. Use when the question is answerable by reading, building, or measuring with no user decision required; unsettled decisions belong to maestro-design. Prototypes are throwaway.

byronxlg Skill

Gather information, evaluate sources, and synthesize findings.

vltansky Bundle

Research a technical topic and produce an RFC document backed by real code evidence from GitHub. Use when user says 'write an RFC', 'RFC research', 'create RFC for', 'technical proposal', 'design doc', 'investigate X', 'research X and write a proposal', 'architecture decision record', 'ADR', or needs a structured technical decision document with prior art analysis.

walkerkiller Bundle

Build and serve the static course knowledge base locally. Rebuilds from workspace data and starts an HTTP server on port 8765.

yaphet2015 Bundle

Use when the user needs to fetch Chinese A-share market data, K-lines, financial indicators, cash flow, announcements, or news evidence from public data sources for stock/investment research.

agentic-tend Bundle

Build and evaluate a research-literature corpus for a scientific landscape, attribution or priority question, version comparison, source conflict, or bounded absence search. Return source roles, claim-level evidence, version state, and search limits. Do not use for generic web search, bibliography formatting, or checking one already-supplied citation.

ali-demirbas Skill

Use when the user asks to find news coverage of an event, check what press outlets reported, or research how an announcement was covered. Triggers on "find news about", "what did press say", "news coverage of", "news research". Produces evidence records (URL + verbatim quote + wire/syndication check), never conclusions. Do NOT use for the underlying official announcement itself (use official-source-research — trace to it, don't just cite the reprint), blog opinion pieces (use blog-research), or academic coverage (use academic-research).

ali-demirbas Skill

Use when the user asks to search GitHub, find repositories, check what a project's code/issues/PRs/releases say, or look up how something is implemented in open source. Triggers on "search GitHub", "find a repo for", "check the issues on", "how do they implement X", "github research". Produces evidence records (URL pinned to a commit SHA + verbatim quote + date), never conclusions. Do NOT use for general web search (use web-research), Reddit/community discussion (use reddit-research), or when the user just wants you to write code (that's normal coding, not research).

ali-demirbas Skill

Use when the user asks to search Reddit, check what people are saying on a subreddit, find complaints or pain points, validate a product idea against community discussion, or track sentiment/trends on Reddit. Triggers on "search Reddit", "check r/", "what are people saying about", "Reddit complaints", "pain points on Reddit", "reddit research". Produces community-signal evidence records (permalink + verbatim quote + timestamp), never conclusions. Do NOT use for GitHub content (use github-research) or general web search (use web-research) — Reddit discussion ABOUT a GitHub project still belongs here, not github-research.

ali-demirbas Skill

Use when the user asks to search X/Twitter, LinkedIn, Hacker News, Discord, or general forums for discussion of a topic (not Reddit — that's reddit-research). Triggers on "search Twitter/X", "check Hacker News", "LinkedIn discussion", "forum discussion about", "social research". Produces community-signal evidence records (URL + verbatim quote + timestamp), never conclusions. Do NOT use for Reddit (use reddit-research, which has its own dedicated access chain), GitHub discussion (use github-research), or general web pages (use web-research).

ali-demirbas Skill

Use when a research question needs to be broken into sub-questions, matched to which source skills apply, and given a search budget and stopping condition — before any source skill starts collecting. Triggers on "plan this research", "break this question down", or is invoked automatically by the research-intelligence orchestrator as its first stage. Do NOT use this to collect evidence yourself (dispatch the source skills for that) or to judge evidence quality (that's source-verify and the validator).

ali-demirbas Skill

Use when the user asks to find research papers, check what a study found, look up peer-reviewed literature, or verify a scientific/technical claim against published research. Triggers on "find papers on", "what does the research say", "peer-reviewed studies on", "academic research", "literature on X". Produces evidence records (DOI/URL + verbatim quote + peer-review status), never conclusions. Do NOT use for a blog's summary or interpretation of a paper (use blog-research, then cross-check against this skill when the claim is load-bearing), or for general web content (use web-research).

anthropics Skill

How to pull SEC EDGAR data with the edgartools Python package — company lookup, filings, XBRL financial statements, and filing sections like Item 1A risk factors. Use whenever a task involves SEC filings, 10-K/10-Q data, or company financials.

anthropics Skill

Workshop coach for the Research Desk (SEC agents) workshop. Use when the user types /workshop, asks for a workshop act or module ("act 2", "next act", "where am I"), wants a TODO(workshop-N) implemented or explained, or asks for help following WORKSHOP.md.

arpitbbhayani Skill

Masterclass teacher that takes any concept, note, URL, paper, or write-up, expands on it if needed, and teaches it through and through, step by step. Uses real-world and engineering mental models, selective and intuitive analogies with breaking points only where needed, visual ASCII diagrams, minimal code snippets, in-between check questions, web research when required, and prompts to up the ante and go deeper until the user explicitly signals they are done. Trigger on "ape teach", "teach me", "masterclass on this", "explain this step by step", or when the user provides a concept, note, paper, or link and asks to learn or be taught it thoroughly.

arpitbbhayani Skill

Defines how to write and format git commit messages. Use this skill whenever the user asks you to write, draft, suggest, or format a git commit message, summarize changes into a commit, or help stage and describe code changes. Trigger even for casual requests like "write me a commit for this" or "what should my commit say".

arpitbbhayani Skill

Digests dense content -- a post, paper, doc, or thread -- into a TLDR that keeps the numbers and caveats, a so-what naming why it matters, the key points, and an analogy with its breaking point. Trigger on "ape understand", "tldr this", "help me understand this", "give me an analogy", or when the user shares a post, paper, doc, or thread and asks to digest or summarize it. Do not trigger for plain questions that want a direct answer, not a digest.

asebesta Bundle

Research competitor apps on the Apple App Store. Extracts app metadata (title, subtitle, description, rating, reviews, category, developer, version, price) and downloads all screenshots. Use when user wants to analyze a competitor's app, research app store listings, gather competitive intelligence, or download app screenshots. Triggers on App Store URLs (apps.apple.com) or requests like "research this app", "analyze competitor", "get app store info", "download app screenshots".

trpc-group Bundle

Generate concise research bullet points for the team leader.

pengelbrecht Bundle

Research a topic from the last 30 days on Reddit + X + Web, become an expert, and write copy-paste-ready prompts for the user's target tool.

dxy-hub Bundle

When user asks to summarize text, articles, documents, meetings, emails, YouTube transcripts, books, PDFs, reports, conversations, or any long content. Also handles bullet points, key takeaways, action items, TL;DR, ELI5, executive summaries, chapter summaries, comparison summaries, translation summaries, thread summaries, and custom-length summaries. 20-feature AI summarizer with multiple formats, languages, and export options. All processing happens locally — NO external API calls, NO network requests, NO data sent to any server.

commercetools Skill

Research a Jira ticket and create a Confluence context page with current understanding, dev action items, related tickets, domain docs, and people to consult. Use when asked to "create a context page for", "research this ticket", "gather context for", "create a knowledge brief for", "collect information about this Jira issue", "create a Confluence page for ticket", or "what do I need to know to solve this ticket".

jeffallan Bundle

Use when ingesting source material for a writing project, building a knowledge map from notes and documents, identifying research gaps, or preparing a research corpus for content creation.

jeffallan Bundle

Use when planning a multi-article content strategy from a research corpus, creating domain maps for content topology, building production plans for pillar and cluster articles, or tracking cross-article production.

jeffallan Bundle

Use when capturing research artifacts to a vault or knowledge base, formatting source citations, saving synthesized connections from a writing project, or enriching a knowledge base with produced content.

jefrnc Skill

Use when working with historical financial data, backtests, point-in-time analysis, SEC filings, XBRL data, or any time-series quant research. Prevents look-ahead bias and survivorship bias by enforcing filing_date / accepted as the known-date, never period_end. Triggers on phrases like "as of", "historical", "backtest", "lookahead", "point-in-time".

jek-bao-choo Bundle

This skill should be used when the user wants to summarise Slack messages from a channel over a specific timeframe, extract technical Q&A from Slack discussions, catch up on what happened in a channel, or generate a structured knowledge summary from Slack history. It applies when the user says "summarise #channel-name for the past 5 days", "what technical questions were discussed in #support this week", "catch me up on #engineering since Monday", "give me a digest of #announcements", or "what did I miss in #team-updates". It also applies when the user mentions channel summary, channel recap, Slack knowledge extraction, or technical Q&A summary — even if they don't explicitly say "summarise". Make sure to use this skill whenever the user asks about Slack channel activity, wants to review discussions, or needs to extract insights from Slack message history.

jjfroehlich Bundle

Use when the user is acting as an author, reviewer, or editor-facing correspondent in a scientific publication process and needs help with journal submission packages, cover letters, presubmission or editor inquiries, peer-review reports, reviewer ethics, conflicts, confidentiality, editorial decision interpretation, appeals, transfers, resubmission strategy, or response-to-reviewers letters. Trigger on concrete publication-process decisions or artifacts, not on general manuscript prose editing, figure design, grant review, literature summaries, or journal-ranking curiosity without an active submission/review context.

jjfroehlich Bundle

Use this skill when the user needs research-group mentoring, lab-management, or lab-culture help that turns expectations into concrete systems, documents, routines, scripts, or escalation paths. Trigger on lab handbooks, onboarding, mentoring compacts, IDP meetings, feedback scripts, authorship or credit norms, conflict diagnosis, performance concerns, PI/lab leadership systems, power dynamics, belonging, work-life boundaries, and culture repair in scientific labs. Do not trigger for personal career decisions, research-project strategy, manuscript/grant work, or legal/clinical determinations.

jmech-pepa Skill

Osobní knowledge base s compound effect — ukládání článků, YT videí, knih, insights a poznámek. Inbox buffer, auto-linking mezi zdroji, evolving concept pages. Data na Google Drive, sync mezi počítači.

cfircoo Skill

Summarize current session, a specific file, or a topic from the vault. Use when the user says "tldr", "summarize", "recap", "what happened", "summary of", "catch me up", or wants a quick overview of something.

commercetools Skill

Persist guidelines, conventions, and architectural decisions into the repository's knowledge base. Use when told to remember something for future sessions.

irsdl Bundle

Creates an evidence-backed development plan or design document for a non-trivial ysonet change and saves the draft under dev-kitchen/ideas/ for review before implementation. Use when the user asks to plan, propose, design, research a proposed change, or draft an approach for a refactor, architecture or UI change, new gadget, plugin, serializer, build change, dependency change, or other work that should be settled before code is written. Not for immediate implementation, diagnosis-only requests, or tiny mechanical edits.

jcosta33 Skill

Produce one recommendation from independent analysis of legitimate alternatives. Use when a consequential technical, architectural, operational, or product choice needs several perspectives before a decision. Do not use when direct evidence settles the choice, the user has stated a decision in the thread, or the work needs factual research instead of deliberation.

joshsymonds Skill

RimWorld reference module and mod development for Savecraft. Use when working on files in plugins/rimworld/, including reference modules (surgery, crops, combat, materials, drugs, raids, genes, research), the datagen XML parser, decompiling Assembly-CSharp.dll, or the Harmony mod. Triggers on RimWorld plugin code, XML Defs, datagen, reference.wasm, decompilation, patch verification, or RimWorld game formulas.

jpoindexter Bundle

Draft, edit, and finish concise design case-study copy from an evidence ledger or structured outline. Use when a portfolio case study is verbose, vague, generic, overly chronological, full of UX process theater, missing scannable headings and captions, inconsistent in voice, or needs publication-ready structure without inventing research, metrics, outcomes, or quotes.