Claude Skills
The open format is called Agent Skills and works in Claude Code, Codex, Cursor and other agents — most people know it as Claude Skills.
Every Agent Skill we could find on GitHub, deduplicated by content. 79 341 files from 1 736 authors, of which 61 700 are unique — the rest is the same skill repackaged into someone else's repository. For each one: what it weighs in tokens, whether it ships runnable scripts, and which MCP servers it needs.
Executes OpenAI Codex CLI for code analysis, refactoring, and automated editing. Activates when users mention codex commands, code review requests, or automated code transformations requiring advanced reasoning models.
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: \"Index this repo\", \"Reanalyze the codebase\", \"Generate a wiki\
Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: \"How does X work?\", \"What calls this function?\", \"Show me the auth flow\
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: \"Is it safe to change X?\", \"What depends on this?\", \"What will break?\
Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: \"What GitNexus tools are available?\", \"How do I use GitNexus?\
> Facilitate structured brainstorming sessions as a coach and hybrid thinking techniques (SCAMPER, Six Thinking Hats, reversal, analogical thinking, question storming, role playing…), one technique at a time, with the user generating ideas first and the AI building on them with clearly labeled additions — then converge, categorize, and deliver a session document with priorities and next steps. Use this skill whenever the user wants ideas or wants to think out loud together — "brainstorm with me", "give me ideas for…", "help me come up with…", "let's explore options for…", "I'm stuck on the name / the features / the campaign angle" — in any language (e.g. Vietnamese "brainstorm cùng tôi", "cho tôi ý tưởng", "nghĩ cùng tôi xem", "gợi ý phương án giúp tôi"; Spanish "ayúdame a generar ideas"; Japanese 「アイデア出しを手伝って」), even when they never say the word "brainstorm". Trigger for open-ended exploration of a topic, product, name, feature set, campaign, event, career move, or any generative question that does not first require diagnosing why something is broken. Also trigger when the user asks for multiple perspectives on their ideas or a structured devil's-advocate pass — "give me different angles on these ideas", "phản biện mấy ý tưởng này giúp tôi", "party mode" — the skill's party mode handles multi-role ideation and counterpoint. (If the request is "X is failing and we don't know why", root-cause diagnosis comes first — the problem-solver skill in this family leads there; if the question is who the users are and what they need, with real research, design-thinking leads; company-level strategic bets belong to strategy-board.)
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: \"Why is X failing?\", \"Where does this error come from?\", \"Trace this bug\
Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: \"Rename this function\", \"Extract this into a module\", \"Refactor this class\", \"Move this to a separate file\
> Audit the reasoning of any document or argument — a memo, proposal, investment analysis, board paper, article, or the user's own draft — and fallacies, and what would falsify it, with every finding anchored to exact quoted text. Runs a commit-first coaching loop that asks for the user's own judgment before revealing the audit, tracks their recurring blind spots in a persistent reasoning profile, and turns every audit into a rep that sharpens the user's thinking instead of replacing it. Use this skill whenever the user wants reasoning examined — "audit this argument", "is this analysis sound", "poke holes in this proposal", "review the logic of my draft", "what's wrong with this reasoning" — in any language (e.g. Vietnamese "phản biện giúp tôi", "soi lập luận này", "tài liệu này có lỗ hổng gì", "đánh giá đề xuất này giúp tôi", "góp ý bản nháp của tôi"; Spanish "analiza los argumentos de esta propuesta"; Chinese "帮我审一下这份提案的论证"; Japanese "この提案の論理をチェックして"; French "analyse les failles de ce raisonnement"), even when they never say "critical thinking". Also trigger when the user drops a document and asks whether to trust or act on it, or asks to see their thinking progress / reasoning profile. (Company-level strategic bets with a full analysis belong to strategy-board; learning a new topic through dialogue belongs to socratic-questor — this skill leads when the question is whether a specific piece of reasoning holds up, and it is the daily-driver for document-level judgment calls.)
> data problem, explore and audit datasets, run defensible statistical analysis, build and validate predictive models, and turn results into decision-ready reports. Use this skill whenever the user asks to analyze, explore, or profile a dataset or CSV/Parquet/Excel file; asks what drives a metric or why a number changed ("why did churn go up?"); wants to test whether a difference is real (A/B tests, experiments, "is this significant?", "how many samples do I need?"); wants a predictive model (churn, forecast, scoring, segmentation, classification, regression); asks to review an existing analysis, notebook, or model for flaws; or needs analysis results written up for decision-makers — in any language ("phân tích dữ liệu", "xây model dự đoán", "kiểm định A/B"), even when they never say "data science" or "statistics".
Score candidate CVs on a 100-point scale against a Job Description. Use this skill when the user wants to evaluate, score, rank, or screen candidate CVs/resumes against a JD. Also trigger when the user mentions 'review CV', 'screen resume', 'rate candidates', 'shortlist', or any context involving matching resumes to job requirements.
>- Deep-read long books and papers using Mortimer Adler's inspectional / analytical / syntopical method, the Recite step from SQ3R, and S. Keshav's three-pass method for papers, with page-anchored notes as external memory so the agent never has to load the whole text into one context window. Use this skill whenever the user asks to read, study, summarize, analyze, review, or answer questions about a long book, textbook, PDF, EPUB, thesis, dissertation, survey paper, or any document of roughly 50+ pages. Also use it when a `<slug>-notes/` workspace from a previous session already sits next to a source file and the user asks a follow-up question about that book — search the existing notes before re-reading anything. Trigger on these requests in whatever language the user writes them — for example Vietnamese "đọc sách", "tóm tắt sách", "phân tích luận án", or equivalent phrasing in any other language. Do not use this skill for short documents (under ~30 pages) that fit comfortably in context — read those directly instead; the pipeline is overhead they don't need.
> Facilitate a full design-thinking engagement — Empathize, Define, Ideate, Prototype, Test — as a disciplined facilitator and thinking partner that observation plans, experiments with pass/fail criteria), the user brings back real data, and every insight traces to registered evidence. Use this skill whenever the user wants to understand users deeply and design a solution or experience for them — "run design thinking", "understand our users", "design user interviews", "synthesize these interview notes", "build personas", "write How-Might-We questions", "brainstorm solutions for…", "prototype this concept", "design an experiment / usability test to validate…", "our users are churning and we don't know why" — in any language ("tư duy thiết kế", "nghiên cứu người dùng", "phỏng vấn khách hàng", "デザイン思考", "设计思维"), even when the user never says "design thinking". Also trigger when the user drops raw interview notes, transcripts, or survey exports and wants them turned into insights, personas, or product decisions. (For "is there a market for X" desk questions, the market-researcher skill leads; this skill leads when the question is who the users are and what to build for them.)
>- Write, restructure, classify, and review documentation using the Diataxis framework. Use this skill whenever the user asks to create, improve, audit, or reorganize docs, documentation, knowledge bases, help centers, onboarding guides, internal process docs, manuals, runbooks, product docs, API/developer docs, tutorials, how-to guides, references, or explanations. Also use it when the user mentions Diataxis, tutorial, how-to, reference, explanation, docs taxonomy, documentation architecture, or asks why a document feels confusing. Do not use it for marketing copy, legal contracts, fiction, sales proposals, press releases, or persuasion-first writing unless the user explicitly wants a Diataxis-style documentation analysis.
> A complete fiction-writing studio, run as a team of named specialist agents, that guides an author from a bare idea to a polished prose manuscript. Use this skill whenever the user wants to write, plan, or revise fiction — a novel, novella, short story, or series. Trigger on requests like "help me write a novel", "I have an idea for a story", "develop my characters", "build a world for my fantasy", "outline my plot", "fix this scene", "my dialogue feels flat", "give me beta-reader feedback", or any time the user is doing creative storytelling and would benefit from structured, craft-aware guidance. Also trigger when the user names a studio member (Homer, Aristotle, Fyodor, Tolkien, Scheherazade, Oscar, Max, Virginia, Borges, Bloom) or asks to switch creative roles / bring in a specialist.
> scans, market sizing (TAM/SAM/SOM), competitor analysis, customer demand signals, and trend/macro (PESTEL) analysis. Use this skill whenever the user wants to research, size, validate, or enter a market — "is there a market for…", "how big is the market for…", "who are the competitors of…", "should I build/launch/sell…", "validate this business idea", "market research for…", "market entry" — in any language and for any country's market (e.g. "nghiên cứu thị trường", "étude de marché", "市場調査", "análisis de mercado"), even when the user never says the words "market research". Also use it when another skill or workflow (strategy-board, design-thinking, a product brief) needs external market facts delivered into its fact base or research folder.
> facilitator that turns "X is broken and we don't know why" into a precise problem statement, bounds it with Is/Is-Not analysis, finds root causes with the method that fits the problem's shape (Five Whys for linear chains, fishbone for multi-factor tangles, causal loops for systems that fight back), labels every causal claim verified or assumed, designs verification tests, then generates solutions traced to root causes, drives an evidence-cited decision, and plans rollout with pivot triggers. Use this skill whenever the user reports something failing, breaking, slowing, or recurring without a known cause — "sales dropped and we don't know why", "this keeps happening", "orders keep arriving late", "why does X keep failing", "find the root cause", "run a post-mortem", "5 whys" — in any language (e.g. Vietnamese "sao cứ bị vậy hoài", "tìm nguyên nhân gốc", "X đang hỏng "give me ideas to fix falling sales" is a diagnosis request wearing a brainstorm costume. Trigger for operational, process, technical, and business problems with an unknown or unverified cause. (If nothing is broken and the user wants open-ended ideas, brainstorm-coach leads; if the problem is really about understanding users and their behavior — churn driven by what users feel and need — design-thinking leads; company-level strategic bets belong to strategy-board.)
> Act as a disciplined product manager copilot that turns evidence into prioritization with sensitivity analysis, PRDs with story maps and user stories, north-star metrics and OKRs, experiment designs, launch plans with rollback criteria, feedback triage, platform-vs-feature decisions, and light pricing/packaging — all inside a persistent per-product workspace where every number declares its origin. Use this skill whenever the user wants to decide what to build, spec it, or ship it — "write a PRD for…", "prioritize our backlog / these features", "what should we build next", "plan OKRs for the quarter", "define our north star metric", "design an A/B test for…", "plan the launch of…", "triage this pile of customer feedback", "should this be a platform or a feature", "help me manage this product" — in any language ("viết PRD", "ưu tiên tính năng nào", "quản lý sản phẩm", "lập kế hoạch ra mắt", "プロダクト管理", "产品经理"), even when the user never says "product manager". Also trigger when the user returns to an existing `<product>-pm/` workspace with any product question. (Deep user discovery belongs to design-thinking, desk market facts to market-researcher, company-level strategic bets to strategy-board — this skill leads when the question is what to build, in what order, and how to ship it.)
> Act as a disciplined project-management copilot (PM/PMO) that runs the delivery loop — initiation & charter, planning & scheduling, estimation with reference-class checks, risk management (ROAM), honest status reporting, scope change control, stakeholder communication, meetings turned into tracked actions, lessons learned, and portfolio roll-ups — methodology-agnostic (predictive, agile, hybrid) inside a fixed per-project `_project/` workspace where every status color, percent-complete, and estimate declares its evidence. Use this skill whenever the user wants to start, plan, track, rescue, or report on a project — "kick off this project", "make a project plan / timeline / WBS", "estimate how long this will take", "what date can I commit to", "build a risk register", "run a pre-mortem", "write the weekly status report for the steering committee", "the deadline slipped, what now", "turn this meeting transcript into action items and decisions", "prepare the steering-committee pack", "review my project portfolio" — in any language ("gestion de projet", "Projektmanagement", "quản lý dự án", "プロジェクト管理", "项目管理", "gestión de proyectos"), even when they never say "project management". Also trigger whenever a `_project/` directory exists in the working tree and the user asks anything about schedule, deadline, risk, status, scope, budget, or stakeholders. (What to build belongs to product-manager; company-level bets to strategy-board — this skill leads when the question is whether committed work will land on time, in scope, on budget, and who needs to know.)
>- Build interactive presentation websites — slide decks projected to a room, controlled by one presenter. Use this skill WHENEVER the user wants to create, build, or design a presentation, slide deck, talk, or "bài thuyết trình / slide / trình chiếu", and also when they ask to add/edit slides, restyle a deck, scaffold a new presentation project, reuse their presentation setup in another repo, or export slides to PDF — even if they don't say the word "slide" but clearly need projected talk visuals (e.g. "I'm giving a talk next week and need visuals", "dựng deck cho buổi chia sẻ", "làm mấy trang chiếu project. Do NOT use it for printable documents, normal web apps, or dashboards meant for individual users to interact with.
> Socratic questioning partner named Gadfly for deep learning through dialogue. Use this skill when the user wants to learn, understand, or explore a topic through questions rather than explanations. Trigger when the user says "teach me about...", "help me understand...", "I want to learn...", "ask me questions about...", "quiz me", "Socratic method", "Gadfly", or wants to deeply understand something through dialogue rather than passive reading. Also trigger when the user provides a text or document and wants to be questioned about it, or wants to check their own understanding of a concept.
> A C-level strategy advisory board, run as a team of named specialist agents, that takes an executive from a raw strategic question to a defended, board-ready recommendation. Use this skill whenever the user faces a significant business decision or wants strategic analysis — market entry, build-vs-buy, M&A, digital transformation, annual planning, portfolio prioritization, pricing, a big investment, a competitive threat, a turnaround. Trigger on requests like "should we invest in / build / buy / enter…", "develop a strategy for…", "evaluate this opportunity", "make the business case", "stress-test this plan", "run a pre-mortem", or "prepare a board presentation" — in any language, even when the user doesn't say the word "strategy". Also trigger when the user names a board member (Drucker, Porter, Christensen, Graham, Grove, Wack, Taleb, Minto) or asks to convene the board / open a boardroom session.
Create high-quality, model-aware system prompts for any LLM (Claude, GPT, Gemini, open-source, etc.). Use this skill whenever the user wants to create, write, build, design, draft, or improve a system prompt, system instructions, or custom instructions for any AI model. Also trigger when the user asks about prompt engineering, prompt design, prompt optimization, or wants to define behavior for an AI assistant, chatbot, agent, or any LLM-powered application — even if they don't explicitly say "system prompt". Covers all use cases including chatbots, agentic systems, tool-use workflows, content generation, data extraction, code assistants, and multi-turn conversations.
> Deploy OpenSearch search applications to Amazon OpenSearch Service or Amazon OpenSearch Serverless. Use this skill when the user wants to provision an OpenSearch domain or serverless collection on AWS, deploy search configurations to AWS, set up Bedrock connectors, configure IAM roles for OpenSearch, migrate a local search setup to AWS, or manage Amazon OpenSearch infrastructure. Activate even if the user says AOS, AOSS, OpenSearch Service, serverless collection, Bedrock connector, SigV4, or AWS deployment without mentioning search.
> Ingest documents at scale into Amazon OpenSearch using OpenSearch Ingestion Service (OSIS) pipelines. Upload pre-generated JSONL chunks to S3 and OSIS indexes them — optionally using semantic_enrichment in the sink to create the index with ASE automatically. Cloud ingestion — uploading raw PDF/DOCX and letting document_extractor parse them in the cloud — is available via private beta. Use this skill when the user wants to ingest documents into a cloud OpenSearch domain or collection, process documents at full volume beyond local limits, or set up an OSIS pipeline. Activate even if the user says OSIS, ingestion pipeline, document extraction, S3 ingestion, managed ingestion, or cloud processing.
> Analyze logs and investigate traces in OpenSearch. Use this skill when the user wants to query logs with PPL, analyze error patterns, discover log patterns, investigate traces, check stack health, or perform any observability task. Activate even if the user says log analysis, Fluent Bit, Fluentd, Logstash, syslog, traceId, OpenTelemetry, PPL, span, latency, error rate, anomaly detection, or log analytics without mentioning OpenSearch.
> Process unstructured documents into search-ready chunks. Use this skill when the user wants to process PDFs or unstructured documents into JSONL chunks using Docling. Activate even if the user says document processing, chunking, Docling, PDF processing, or chunk quality evaluation. For cloud-scale ingestion via OSIS pipelines, see cloud/managed-ingestion-service.
> Process unstructured documents (PDF, DOCX, PPTX, XLSX) into search-ready JSONL chunks using Docling. Runs locally — no AWS or cloud services needed. Use this skill when the user wants to prepare documents for indexing, chunk documents, evaluate chunk quality, or convert PDFs to searchable text. Activate even if the user says process documents, chunk my files, prepare for search, or Docling.
> Build search applications and query log analytics data with OpenSearch. Use this skill when the user mentions OpenSearch, search app, index setup, search architecture, semantic search, vector search, hybrid search, BM25, dense vector, sparse vector, agentic search, RAG, embeddings, KNN, PDF ingestion, document processing, or any related search topic. Also use for log analytics and observability — when the user wants to set up log ingestion, query logs with PPL, analyze error patterns, set up index lifecycle policies, investigate traces, or check stack health. Activate even if the user says log analysis, Fluent Bit, Fluentd, Logstash, syslog, traceId, OpenTelemetry, or log analytics without mentioning OpenSearch.
> Deploy OpenSearch search applications to AWS. Use this skill when the user wants to provision an OpenSearch domain or serverless collection on AWS, deploy search configurations, set up Bedrock connectors, configure IAM roles for OpenSearch, or migrate a local setup to Amazon OpenSearch Service or Serverless. Activate even if the user says AOS, AOSS, OpenSearch Service, serverless collection, Bedrock connector, SigV4, or AWS deployment.
Use when provisioning or deprovisioning OpenSearch Serverless collections, creating collection groups, setting up AOSS NextGen, or tearing down AOSS resources
> Build search applications with OpenSearch. Use this skill when the user mentions search app, index setup, search architecture, semantic search, vector search, hybrid search, BM25, dense vector, sparse vector, agentic search, RAG, embeddings, KNN, PDF ingestion, document processing, search quality evaluation, or any related search topic.
> Investigate distributed traces and spans in OpenSearch. Use this skill when the user wants to analyze traces, investigate slow spans, find error spans, track agent invocations, measure token usage, reconstruct trace trees, query service maps, or debug distributed systems through trace data. Activate even if the user says traceId, spanId, OpenTelemetry, OTel, distributed tracing, latency, span duration, service map, or trace investigation without mentioning OpenSearch.
> Build search applications with OpenSearch from scratch. Use this skill when the user mentions search app, index setup, search architecture, semantic search, vector search, hybrid search, BM25, dense vector, sparse vector, agentic search, RAG, embeddings, KNN, PDF ingestion, document processing, or any related search topic. Activate even if the user says search quality, evaluation, nDCG, precision, relevance tuning, or search builder without mentioning OpenSearch.
> Analyze logs in OpenSearch using PPL and Query DSL. Use this skill when the user wants to query logs, analyze error patterns, discover log patterns, check error rates, perform anomaly detection on logs, or investigate application issues through log data. Activate even if the user says log analysis, Fluent Bit, Fluentd, Logstash, syslog, PPL, error rate, anomaly detection, log patterns, or log analytics without mentioning OpenSearch.
> Query Data912 market data endpoints for Argentina and USA instruments. Use when the user asks for MEP/CCL quotes, live Argentine market panels (stocks, options, cedears, notes, corporate debt, bonds), USA panels (ADRs, stocks), OHLC historical series by ticker, USA option chains, or volatility/risk metrics. Also use when the user mentions "Data912", "mep", "ccl", "cedears", "option chain", "historical bars", "OHLC", "implied volatility", "historical volatility", or "volatility percentiles" and expects API-backed market snapshots.
> Consulta cotizaciones de criptomonedas con CriptoYa por exchange y en forma agregada. Usar cuando el usuario pida "precio BTC en ARS", "cotizacion USDT", "precio ETH en USD", "mejor precio por exchange", "comparar exchanges", "precio en belo/ripio/lemon/binance/bybit", o cuando pida comisiones de retiro y fees por red.
> Consulta cotizaciones de dolar en Argentina usando DolarAPI. Usar cuando el usuario pida "dolar hoy", "dolar blue", "dolar oficial", "dolar bolsa", "MEP", "CCL", "dolar tarjeta", "dolar mayorista", "dolar cripto", o quiera comparar compra/venta y actualizacion de cotizaciones. Tambien usar cuando el usuario pida cotizacion de euro, real brasileno, peso chileno o peso uruguayo con endpoints de /v1/cotizaciones.
> Query the BCRA (Banco Central de la República Argentina) Central de Deudores API to check the credit status of individuals or companies in Argentina's financial system. Use when the user asks to check someone's debt situation, credit report, financial standing, rejected checks, or credit history using a CUIT/CUIL/CDI number. Also use when the user mentions "central de deudores", "situación crediticia", "deudas BCRA", "cheques rechazados", "historial crediticio", "informe crediticio", or wants to know if a person or company has debts reported in Argentina's financial system.
> Build and operate a URL shortner on Cloudflare Workers with Upstash Redis and D1. Use when the user asks to create shortlinks, redirects, click tracking, analytics, request metadata capture (country/city/ip/user-agent), non-blocking tracking, or resilient alerting (for example Telegram) on failures.
> Consulta precios, market cap, trending, historico OHLC, Fear & Greed y datos DEX/onchain via APIs keyless (sin API key) de CoinGecko, GeckoTerminal y CoinMarketCap. Usar cuando el usuario pida "precio bitcoin", "market cap eth", "trending crypto", "fear and greed", "pools solana", "ohlcv dex", "conversion BTC a USD/ARS", "CoinGecko", "CoinMarketCap", "GeckoTerminal", o datos crypto publicos sin autenticacion.
> Consulta cotizaciones Pix en ComparaPix para comparar apps por simbolo y precio. Usar cuando el usuario pida cotizacion pix, mejor app para pagar con pix, BRLARS/BRLUSD/BRLUSDT, comparar apps pix, precio real tarjeta vs pix, o cotizaciones de comparapix.
> Consulta informacion publica de fondos comunes de inversion en Argentina via CAFCI, combinando catalogo JSON (fondos, clases, IDs y honorarios/fees), planilla diaria XLSX (patrimonio, valor cuotaparte, variaciones, market share) y ficha markdown por fondo (rendimientos por periodo). Usar cuando el usuario pida fondos comunes en Argentina, busqueda de fondo por nombre, fees/comisiones de un fondo, top fondos por patrimonio en una categoria, rendimientos por periodo, o mencione CAFCI.
> Consulta IPC de Argentina con la serie de inflacion mensual desde Anduin API. Usar cuando el usuario pida "inflacion argentina", "ipc argentina", "inflacion mensual", "ultimo dato de inflacion", "serie historica de inflacion", "inflacion por fecha", "inflacion por periodo" o "variacion mensual ipc".
Consult hedge fund and superinvestor portfolios and recent moves from DataRoma using defuddle.md markdown pages. Use when the user asks for holdings, portfolio composition, 13F-style updates, activity, buys, sells, manager movements, or comparisons between investors from DataRoma.
> Integrates Dub Links API endpoints to create, update, delete, retrieve, list, count, and run bulk operations on short links. Use when the user asks for "dub links api", "create link dub", "upsert link dub", "list links", "count links", "bulk links", or lookups by linkId/domain+key/externalId.
> Technical guide to integrate mapcn in React + shadcn projects. Use when the user asks to integrate mapcn, add mapcn to a shadcn app, use mapcn MapControls/Markers/Routes/Clusters, implement controlled viewport state, use the useMap hook, or access MapLibre through mapcn.
Guided process for shaping product ideas, features, and specs by systematically uncovering the user's unknowns before anything gets built. Use this whenever the user wants to shape, spec, define, scope, or think through a product or feature — including phrases like "I have an idea for...", "help me shape...", "let's spec out...", "write a PRD/brief for...", "should we build...", or when they bring a vague product problem (churn, activation, a new market) and need to turn it into a concrete, buildable pitch. Also use when the user asks to brainstorm product directions or wants mockups to react to before committing to a spec.
> Canonical registry and recipes for Ripio wFiat LATAM stablecoins (wARS, wBRL, query prices/DEX via CoinGecko, GeckoTerminal, and Uniswap v4 subgraph. Always present wFiat prices inverted (fiat per 1 USD, e.g. USD/ARS). Use when the user mentions "wARS", "wBRL", "wMXN", "wCOP", "wPEN", "wCLP", "wfiat", "wFiat", "Ripio stablecoin", "stablecoin local Ripio", "peso wrapeado", "wrapped ARS/BRL/MXN/COP/PEN/CLP", or asks for addresses/prices/pools of these tokens.
> Consulta riesgo pais de Argentina con serie historica desde Anduin API. Usar cuando el usuario pida "riesgo pais argentina", "ultimo riesgo pais", "serie historica de riesgo pais", "riesgo pais por fecha o periodo", o "evolucion del riesgo pais".
> Consulta promociones de viajes desde Argentina usando Anduin Promos API. Usar cuando el usuario pida promos de viaje en Argentina, promociones de vuelos, hoteles o paquetes, mejores ofertas del dia, promos a brasil/usa/europa, ranking por score o ultimas promos de promociones-aereas.
>- before adding (poster + synopsis), list/remove shows, list today's and upcoming episodes, and run a silent daily cron that alerts only when a tracked show airs. Use when the user wants series tracking, episode air-day alerts, "add this show", "what airs today", TVmaze, TV calendar, or favorite-shows monitoring.
> metrics, pool state, swaps, tokens, positions, and day/hour aggregates. Use when the user asks for Uniswap v4 pools, liquidity, volume, TVL, recent swaps, hooks, positions by NFT tokenId, poolDayData, or mentions "Uniswap v4 subgraph", "The Graph Uniswap v4", or v4 PoolManager queries.
> Read and write a Workflowy outline via its official REST API. Use when the user asks to access, list, read, export, create, update, move, complete/uncomplete, or delete Workflowy bullets/nodes, discover shortcuts/targets, or mentions "workflowy". No native MCP connector exists — call the API over HTTP (curl) with a Bearer API key.
> Audit and improve user-provided writing for clarity, concision, and impact. Use when the user asks to audit, review, improve, edit, or rewrite text. Apply seven checks (sentence length, clutter, unsupported modifiers, weasel words, jargon/acronyms, "so what", and flow), then return severity-ranked findings and a full rewrite suggestion.
Display repository status with PRs, issues, CI/CD health, and suggested tasks
Review and approve/merge pull requests as a maintainer (full workflow with approve, request changes, merge, close actions)
Finalize and ship changes with quality checks, commits, and PR creation
Release packages to GitHub via uvr. Use when user says "release", "publish packages", "cut a release", or wants to publish new package versions.
> How to create overlay image packages that layer on top of base images. Use when creating a new overlay package like quicksand-agent, scaffolding an overlay, or modifying hatch_build.py for overlay builds.
Claude Skills — questions
Answers built from the skills we actually parsed.