Skills
97,222 packaged capabilities and playbooks for agents. Install any of them with one command.
Productivity
Run structured multi-source research that produces a cited, adversarially verified synthesis with explicit confidence. Use when a question needs more than a single lookup and being wrong is costly — comparing options, validating a claim, surveying a market, briefing a decision.
Ingest a codebase into memory as code pages connected by wiki links. Walks the tree, classifies each code file by role, applies a role template, and writes a code page for each meaningful unit under <wiki root>/code/. Resumable: skips files already ingested and current. Not for prose documents; use /loam::adding-to-memory for those.
Answer questions using existing memory (the wiki substrate). Use whenever the user asks what is happening in the project, directory, codebase, architecture, workflow, decisions, or current state and the wiki likely contains the answer—even if they do not explicitly mention the wiki. Also use for summaries, comparisons, and reusable analyses grounded in current wiki pages. Routes authoritative goal-state questions to /loam::setting-goals. Not for surfacing unresolved gaps; use /loam::reviewing-memory for that.
Reconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes, incidents), then hand back a tight current-state brief. Use for “recall my work on X”, “catch me up”, “what have I been working on”, “where did I leave off”, before starting or resuming work.
Download academic paper PDFs. Supports 8 data sources: Elsevier, Springer Nature, IEEE Xplore, arXiv, Unpaywall, Semantic Scholar, PubMed Central, and CNKI. Automatically routes to the corresponding data source based on the DOI prefix; for unknown DOIs it tries Unpaywall → Semantic Scholar.
Use for requests involving in-depth research, systematic research, competitive analysis, solution comparison, trend analysis, or fact-checking. Proactively use this skill when any of the following apply; do not just search a few things and answer: (1) the user uses trigger terms such as in-depth research, comprehensive research, investigation, due diligence, industry research, market research, competitive analysis, policy research, technology research, trend research, fact-checking, research report, deep report, or deep research; (2) the request requires evidence across multiple sources, multidimensional comparison, and cross-validation for a reliable conclusion; (3) the user requests a report, white paper, industry analysis, or due diligence document; (4) the topic involves current policies, markets, products, prices, or regulations and requires systematic verification. Do not use for simple general-knowledge questions that do not require verification. Broad or vague requests like “research/learn about X” should also preferably trigger. Exclusions: one-sentence summaries, organizing a single provided source, and pure copyediting or rewriting.
Search and monitor Reddit using x402-protected APIs. Use for searching Reddit posts and discussions, getting comments from Reddit threads, and social media monitoring and research. Triggers: "reddit", "subreddit", "reddit discussion", "what are people saying", "social media", "sentiment", "trending", "viral", "popular posts". Use `npx agentcash@latest fetch` for Reddit endpoints. Reddit $0.02/call. Important: Use exact endpoint paths from the Quick Reference table below.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
Search, read, and query research papers via Feynman's alphaXiv-backed alpha tools. Use when the user asks about academic papers, wants to find research on a topic, needs to read a specific paper, ask questions about a paper, inspect a paper's code repository, or manage paper annotations.
Track CawPlan release progress for a version: ticket completion, risk level, open items, target release dates, unresolved Critical-priority bugs, features not yet at QA Testing, what's Ready for QA/QA Testing, descope suggestions, what's blocking QA testing, assignee overload, per-QA pending counts, and tickets stale for more than N days. Use when: the user asks to track a release, check release progress, review open tickets for a version, assess release/delay risk, ask what to descope, ask what's Ready for QA / in QA Testing for a version, ask what's blocking QA testing, ask if any assignee has too many high-priority issues piled up, ask how many tickets each QA still has to verify, or ask which tickets haven't been fixed in over N days. NOT for: creating versions or tickets, product-wide metrics dashboards not scoped to a version, user activity summaries, or open-ended critical-issue search across products (use `cawplan critical search` directly for that).
Aggregate CawPlan product insights: user feedback and critical issues. Use when: the user asks for a product health overview, user feedback trends, or a combined product insights summary. NOT for: date-range activity reports, ticket creation, single-metric queries, user activity, or device/app adoption metrics (installations, crash rate -- that public endpoint has been retired, no longer available via CLI).
Common conventions for writing Markdown documents that cite external sources (survey reports, paper explainers, and any deliverable that surfaces facts from outside). Defines mandatory citation, in-text reference format, quotation-versus-prose separation, the ban on fabricated associations, and the source-list format. Referenced by survey, ja-explainer, and any skill that produces sourced output.
Use when a factual claim or assertion needs verification — a targeted claim verification pipeline: search multiple independent sources, cross-check for agreement or contradiction, rate confidence (verified / likely true / disputed / unverified / outdated), and produce a cited verification report.
Create, inspect, download, and organize Jinkō reference PDFs and their extracts through the jinko-sdk. Use this skill whenever the user wants to upload a paper or source PDF to a Jinkō project, retrieve a reference PDF already in the project so it can be read, create textual highlights from a quoted passage, create rectangular or formula extracts, inspect a paper's bibliography or existing extracts, or use a project reference while reproducing a publication. Do not use it for literature search, model authoring, or data-table creation.
Find and shortlist biomedical publications from PubMed for knowledge, data, or reusable-model evidence. Use for query framing, PMID/DOI discovery, bibliographic normalization, evidence prioritization, and best-effort public full-text retrieval before synthesis, extraction, or modeling. Do not use for ClinicalTrials.gov-only scoping, systematic reviews, quantitative extraction, curve digitization, calibration, or model implementation.
Find and shortlist ClinicalTrials.gov registry and posted-results records for biomedical modeling evidence. Use for NCT discovery, status/phase/results screening, endpoint and population inventory, comparator landscapes, and ongoing-trial intelligence. Do not use for PubMed publication discovery, quantitative extraction, protocol authoring, Jinkō trial execution, calibration, model building, or systematic reviews.
Interact with Jira using the orbit CLI to create, list, view, edit, and transition issues, manage sprints and epics, export epic hierarchies to markdown, manage dashboards and gadgets, manage saved filters, manage custom fields and screen configurations, list statuses and issue types, and write properly formatted descriptions using Jira wiki markup. Use this skill whenever the user asks about Jira tasks, tickets, issues, sprints, epics, dashboards, filters, gadgets, or needs to manage project work items using orbit. Also trigger when the user says things like “create a ticket,” “create epics,” “move this to done,” “assign the issue,” “update the description,” “format for Jira,” “create a custom field,” “add field to screen,” “list statuses,” “configure Jira,” “create a dashboard,” “add a gadget,” “list filters,” “search filters,” “export epic,” “dump epic hierarchy,” or any Jira-related workflow — even casual references like “update Jira,” “what tickets are in this sprint,” “add a comment to PROJ-123,” “set up AI tracking fields,” “show me the dashboards,” or “create a metrics dashboard.” Trigger especially when descriptions need proper formatting (headings, bullets, tables, links) since Jira Server uses wiki markup, not markdown.
Structured roundtable discussion framework with a truth-seeking moderator who invites representative figures for dialectical debate on any topic. Use when user says "圆桌讨论", "圆桌", "roundtable", "辩论", or wants to explore a topic through multi-perspective structured debate.
Correct or update existing wiki content when newer evidence shows the wiki is wrong, stale, incomplete, or contradicted. Use this when the agent discovers the wiki says X but we now know Y, when code or real-world changes invalidate a wiki claim, or when the user asks to fix or amend the wiki. Not for adding new sources, routine learnings capture, structural normalization, or health checks; use /loam::adding-to-memory, /loam::learning-from-session, /loam::normalizing-memory, or /loam::linting-memory.
Surface and classify all open questions, unresolved contradictions, stale claims, and knowledge gaps from existing memory. Use this when the user wants to see what's still open, what needs attention, what's unresolved, or what still needs research or ingest. Does not classify incomplete goals as memory gaps. Not for answering questions, fixing issues, or adding new material; use /loam::querying-memory, /loam::linting-memory, /loam::amending-memory, /loam::adding-to-memory, or /loam::learning-from-session.
Research Reddit discussions with high signal using reddit_leads_scrape and reddit_scrape — pain points, intent discovery, and trend tracking. Use when the user wants to mine subreddits for leads, find threads worth replying to, or track what a community says about a topic.
Generate a comprehensive, structured learning guide for any technical topic or technology. Use this skill whenever a user wants to learn a new technology, programming language, framework, tool, or concept—even if they phrase it casually (e.g., “teach me Rust”, “how do I get started with Kubernetes”, “I want to learn React”, “help me understand GraphQL”, “give me a roadmap for learning Docker”). This skill covers concept identification and categorization, weekly study schedules, local dev setup, concept explanations with examples, exercises, popular libraries, project ideas, and resources. Trigger for any “how do I learn X”, “roadmap for X”, “getting started with X”, “study plan for X”, or “teach me X” request—even if they don't explicitly ask for a guide or roadmap.
Dual-context skill: Personal TELOS reads and updates goals, beliefs, narratives, strategies, and more with timestamped backups; Project TELOS analyzes .md/.csv directories for dependency chains, bottlenecks, and alignment, generating reports, narrative points, or dashboards. USE WHEN Telos, life goals, projects, dependencies, update TELOS, narrative points, McKinsey report, dashboard, what am I wrong about, life frames, mental models. NOT FOR conversational constitutional review (use Interview).
Review and send Telegram response drafts, manage follow-ups for unanswered outbound messages. Use when the user says "/tg-responder review", "/tg-responder status", "/tg-responder follow-ups", "check telegram drafts", "review pending messages", "telegram inbox", "who hasn't replied", or "follow up".
Daily digest of 3-7 genuinely surprising items from newsletters and Telegram channels. Scores content for epistemic friction, not just relevance. Appends to daily note. Use when the user says "/wow-digest", "run the wow digest", "what's surprising today", "morning reading", or "digest my newsletters".
Prepares agendas, diagnoses struggling 1:1 relationships, and gives frameworks for running effective 1:1 meetings with direct reports. Use when the user wants to prepare for, run, improve, or follow up on a 1:1, or says “1:1 agenda,” “prepare for my 1:1,” “1:1 notes,” “what should I talk about with,” “my direct report,” “check in with my report,” “make my 1:1s better,” “1:1 template,” or “my 1:1s feel like status updates.” Do NOT use when the user needs to deliver specific feedback (use feedback) or discuss performance reviews (use performance-reviews).
Comprehensive guide for Google Apps Script development covering all built-in services (SpreadsheetApp, DocumentApp, GmailApp, DriveApp, CalendarApp, FormApp, SlidesApp), triggers, authorisation, error handling, and performance optimisation. Use when automating Google Sheets operations, creating Google Docs, managing Gmail/email, working with Google Drive files, automating Calendar events, implementing triggers (time-based, event-based), building custom functions, creating add-ons, handling OAuth scopes, optimising Apps Script performance, working with UrlFetchApp for API calls, using PropertiesService for persistent storage, or implementing CacheService for temporary data. Covers batch operations, error recovery, and JavaScript ES6+ runtime. Do NOT use for standalone Node.js scripts, Google Cloud Functions, Cloud Run, or any non-Apps-Script JavaScript runtime — those use different APIs and quotas.
Interview prediction, simulated follow-up questioning, and practice skill driven by a Chinese-language resume and target role: extract experience claims that need verification, build question and scoring contracts by interview round, and check real mastery through one question at a time, evidence-based feedback, and repeat practice on weak areas; use when the user enters "/interview" or asks for interview prediction, mock interviews, resume follow-up questions, stress interviews, scenario design questions, or checking interview mastery.
Apply Andrej Karpathy AI methodology and principles from his 2023-2026 insights. Use this skill when the user wants to apply Karpathy-style thinking, needs guidance on agentic engineering, LLM knowledge bases, minimalist coding, understanding-first principles, or any of the 14 core methodologies distilled from his work. Also triggers on: "karpathy method", "karpathy approach", "karpathy way", "AK style", "like karpathy does", "karpathy principles", or when user asks how Karpathy would approach any programming or AI problem.
Inspect an existing memory corpus (wiki substrate) and align it to this repo's Obsidian-friendly note-graph conventions. Use this when the user wants to import, normalize, retrofit, or clean up existing memory, notes folder, vault, docs tree, or mixed markdown knowledge base. In monorepos, also use it to align relevant AGENTS.md and CLAUDE.md files. Excludes goals/ from normalization. Not for routine wiki maintenance; use /loam::linting-memory for that
Automate source-grounded research with Google NotebookLM. Create notebooks from URLs, text, or local files; ask cited questions; run fast or deep web research; create articles and social drafts; and generate or download audio, video, cinematic video, slides, reports, study guides, quizzes, flashcards, mind maps, infographics, and data tables. Use when a user asks for NotebookLM, cited source analysis, research-to-content workflows, podcasts, slides, study material, artifact generation, RSS digests, or trend research.
Agent-callable Notion tools for searching pages and databases, reading and creating pages, querying data sources, appending content, and managing schemas. Use when the user mentions Notion or wants to find, read, create, or edit Notion content, even if they don't name Notion explicitly.
Read, search, and download emails and attachments from Microsoft Outlook via OAuth2. Use when the user asks to (1) check, read, or fetch emails or messages from Outlook, (2) search emails by keyword, sender, or subject, (3) download email attachments such as contracts, NDAs, or documents, (4) chain email content into other skills (e.g. "read the latest email from X and review the attached NDA"), or (5) any task involving Microsoft Outlook, Office 365, or Exchange email access.
Creative discovery partner for ideation and concept shaping. Use when brainstorming, exploring product ideas, expanding vague concepts, comparing directions, finding opportunities, or engaging in creative ideation. Triggers: 'brainstorm', 'product ideas', 'concept exploration', 'idea expansion', 'creative thinking', 'product discovery', 'what if', 'I have an idea'.
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.