Research skills
Browse reusable Agent Skills, each with a clear purpose and practical guidance.
alphaear-search
Perform web searches and local context searches. Use when the user needs general info from the web (Jina/DDG/Baidu) or needs to retrieve information from a local document store (RAG).
blz-docs-search
Teaches effective documentation search using the blz CLI tool. Use when searching documentation with blz, looking up APIs, finding code examples, retrieving citations, or when questions mention libraries, frameworks, "how to", or documentation topics. Covers BM25 full-text search patterns, citation retrieval, and efficient querying.
cass-search
Search past AI sessions with CASS. Use when looking for past solutions, searching session history, finding how something was done before, or when the user mentions "cass", "history", or "past sessions".
code-researcher
Technical "Documentarian" for codebase analysis. Specializes in mapping existing systems, tracing data flows, and identifying patterns without introducing design changes.
Corporate Filings Search
Search SEC and state corporate filings for financial and regulatory information
cortex-query
Search and query your Knowledge Cortex (~/.cortex/). Use when asked to "cortex stats", "cortex search", "cortex client", "cortex contacts", "cortex export", "cortex prune", "search my knowledge base", or "what do I know about COMPANY". Queries portable JSONL/JSON files for contacts, clients, communications, and facts.
cs-customer-research
Pesquisa multi-fonte sobre pergunta ou tópico de cliente com atribuição de fontes. Use quando um cliente pergunta algo que precisa ser verificado, investigando se um bug foi reportado antes, verificando o que foi dito anteriormente a uma conta específica, ou coletando contexto antes de redigir uma resposta. / Multi-source research on a customer question or topic with source attribution. Use when a customer asks something you need to look up, investigating whether a bug has been reported before, checking what was previously told to a specific account, or gathering background before drafting a response.
decision-archaeology
Investigate why code was written a certain way. Use when tracing decision history through git blame, commit logs, PRs, and issues to understand the reasoning behind code changes.