Skills
101,174 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Integration with Obsidian vault for managing notes, tasks, and knowledge when working with Claude. Supports adding notes, creating tasks, and organizing project documentation. Updated with 2025-2026 best practices including MOCs, properties, practical organization patterns, and Obsidian CLI (1.12+).
Access NewsLiquid / 6551 through the OnchainOS CLI. Use for explicitly chosen NewsLiquid, News Liquid, 6551 or 6551Team operations and clear continuations, including information queries, wallet-backed service plans and WSS client guidance; explain supported services locally.
Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser through the `orca` CLI. Use when the user says "$orca-cli", "Orca worktree", "child worktree", "spawn codex/claude in a worktree", "read/wait/send Orca terminal", "handoff" / "handover" / "give this to another agent", "Orca browser", "orca artifacts", or "share skills". It also owns single-session terminal work: "session", "sub-agent", "create a session", "stop a session", "fork a session", "attach to a session", "worktree session", and troubleshooting a stuck or misconfigured agent terminal. Prefer it over raw git worktree, ad hoc PTYs, or Computer Use when Orca state is involved. Use `orchestration` instead to fan out several agents at once or to supervise them. Use Computer Use only when a visible window needs GUI control that a CLI, filesystem, or API cannot do.
Build frontend Solana applications with Phantom Connect SDK and Helius infrastructure. Covers React, React Native, and browser SDK integration, transaction signing via Helius Sender, API key proxying, token gating, NFT minting, crypto payments, real-time updates, and secure frontend architecture.
Use when modernizing PHP code: PHP 8.1-8.5 features, PSR/PHP-FIG/PER-CS compliance, PHPStan/Rector/PHP-CS-Fixer/PHPat tooling, DTOs/enums/readonly/property hooks, type safety. Triggers: PHP modernization, type safety, PHPStan, Rector, PHP-CS-Fixer, enum, DTO, readonly, strict_types, property hooks, PHP 8.4, PHP 8.5.
Pincaimao - Resume Diagnosis. Use when calling the Pincaimao Resume Diagnosis Assistant API to parse and diagnose a candidate resume against a job description. Requires uploading the resume file first to get the cos_key. Requires the PCM_RESUME_DIAGNOSIS_KEY env var.
Expert skill for building pixel art idle/incremental games with procedural sprite generation, React/TypeScript/Zustand architecture, and contemplative game design. Use when creating pixel art games, implementing idle game mechanics, generating procedural sprites via Canvas API, building collection-based games, or implementing incremental game economies. Triggers on requests for pixel art, idle games, sprite generation, incremental games, collection games, or contemplative game experiences.
Guide for authoring comprehensive PRDs with parallel planning support. Use for drafting technical specifications, defining requirements, and synthesizing planner outputs. Use proactively when creating PRDs, architecture designs, or implementation plans. Examples: - user: "Draft a PRD for user auth" → create PRD with purpose, requirements, and scenarios - user: "Analyze these PRD requirements" → verify SHALL/MUST usage and scenario structure - user: "Synthesize planner outputs" → merge the strongest parts of multiple generated PRDs - user: "Create a PRD template" → setup standard sections and placeholder content
Manage pre-commit hooks with preference memory and template-based configuration. Use when installing, configuring, enabling/disabling, or checking status of pre-commit hooks. Supports templates for python, javascript, typescript, go, rust, and generic projects.
Pre-publish assistant for new blog posts. Use when the user wants to classify a new post with categories and tags, generate SEO metadata (title, description, focus keyphrase), or get intelligent suggestions with rationale. Works with draft content (file path, URL, or text) and suggests from existing taxonomy to maintain balanced distribution.
Prepare React Router release notes before running the changes/versioning scripts. Use when asked to review, polish, normalize, or prepare pending change files under packages/*/.changes, remove semantic commit prefixes from release bullets, enforce imperative tense, decide whether a manual scripts/changes/whats-changed.md section is warranted, or draft long-form release notes for new features, stable future flags, or unstable flags.
Ensures HeyEddi projects have the right engineering stack: Vue (Vite/Vitest), FastAPI backend, or Firebase tooling. Audits gaps, scaffolds as needed, installs deps, runs tests, documents local dev servers. Use when the repo is thin or before design/feature work on any HeyEddi app.
Write winning proposals and quotes for a solopreneur business. Use when putting together a proposal for a potential client, structuring a sales document, pricing a project scope, or improving proposal win rates. Covers proposal structure, scoping, pricing presentation, objection pre-emption, and the psychology of persuasive proposals. Trigger on "write a proposal", "proposal template", "sales proposal", "quote for client", "how to structure a proposal", "proposal writing", "win more proposals", "client proposal".
Use when a sandbox or test purchase does not work, or when someone is about to make their first one. Triggers on "my sandbox purchase isn't going through", "the purchase sheet doesn't appear", "I bought it but nothing happened", "the paywall is blank on my phone", "no event in the Adapty dashboard", "how do I test purchases", "test on a real device", "restore doesn't work". Diagnoses first, so nobody is sent back to a console before the cheap checks have run. Complements `adapty-integration`, which owns writing the code and connecting the stores.
Use PyTRIO to write, debug, or explain remote large language model training and inference code. Use when the user mentions pytrio, TRIO, PyTRIO SDK, ServiceClient, TrainingClient, SamplingClient, LoRA training, SFT, asynchronous SFT, PyTRIO-Jev, PyTRIO Decision Model, multimodal inference, multimodal training, Vision GRPO, visual RLVR, ImageChunk, RL, GRPO, OPD, Search-R1, ReTool, DAPO, GSPO, ALFWorld, TextWorld, Agentic RL, OPSD, On-Policy Self-Distillation, DPO, custom loss functions, forward_backward_custom, forward_backward_custom_async, tool-calling reinforcement learning, HuggingFace datasets, the PyTRIO OpenAI-compatible API, SwanLab training records, saving weights, checkpoints, or remote LLM post-training.
Map test cases — manual (markdown) and automated e2e (Playwright, Cypress, WebdriverIO, CodeceptJS, Puppeteer, Appium) — to source code files and produce a `coverage.tests.yml` mapping consumed by `@testomatio/reporter --filter "coverage:..."`. Use this skill when the user wants to run only the tests affected by a code change, generate a coverage file (manual, e2e, or both), build a traceability matrix between tests and source code, or set up change-aware regression.
React bindings for TanStack DB. Prefer useLiveQuery({ query }) with derived structured query identity. Provide queryKey only for opaque functional query variants or very hot render paths. Dependency arrays are legacy and warn before 1.0 removal. useLiveSuspenseQuery for React Suspense with Error Boundaries (data always defined). useLiveInfiniteQuery for cursor-based pagination (pageSize, fetchNextPage, hasNextPage, isFetchingNextPage). usePacedMutations for debounced React state updates. Return shape: data, state, collection, status, isLoading, isReady, isLoadingError, isCrashed, isSyncError, health. Import from @tanstack/react-db (re-exports all of @tanstack/db).
Write and debug React Native Harness tests for app code. Use when the user asks to create or fix tests that import from react-native-harness, mock modules, spy on functions, render React Native components on-device, use setupFiles or setupFilesAfterEnv, or add optional UI tests with @react-native-harness/ui.
Simulated-audience Q&A rehearsal for conference talks, thesis defenses, job talks, and poster sessions. Use when a researcher says "rehearse Q&A", "practice questions", "mock Q&A", "grill me on my paper", "what will the audience ask", "hostile questions", "defense practice", "viva prep", "anticipate questions for my talk", or "questions I hope nobody asks". Sizes a drill to the real Q&A slot, fires hostile and curious questions one at a time in audience personas (hostile skeptic, methods stickler, statistician, adjacent-field expert, big-picture senior, confused newcomer, industry practitioner, self-promoter, rambler) calibrated to the venue family, mines the paper for dreaded weak-point questions, coaches concise answer-first responses, and grades transcripts deterministically for timing, hedging, filler, and buried answers. Coaches honest answers only — never spin — and never invents prior-work citations in drill questions.
Removes and identifies AI watermarks and provenance marks in images and video the user generated or edited. Covers Gemini sparkles, SynthID, Microsoft InvisMark, Meta Content Seal, C2PA, EXIF/XMP/IPTC metadata, and Sora/Veo/Seedance/Doubao/Dola/Hailuo/Vidu/Kling and Wan labels. Use when the user wants to strip or clean AI watermarks and generation labels, or asks whether a file was AI-generated or carries AI provenance, even if they do not name remove-ai-watermarks. Do not use for stock-agency, marketplace, classifieds, or other third-party paid-asset watermarks.
Systematically evaluates claims by triangulating sources, rating evidence quality (primary/secondary/tertiary), assessing source credibility, and reaching confidence-rated conclusions to prevent confirmation bias and reliance on unreliable sources. Use when verifying claims before decisions, fact-checking statements, conducting due diligence, evaluating conflicting evidence, or when user mentions "fact-check", "verify this", "is this true", "evaluate sources", "conflicting evidence", or "due diligence".
Plan and optimize resource allocation. Trigger with "resource planning", "capacity", "utilization", "staffing plan", "who should work on what", "we're stretched thin", or when the user needs help allocating people, budget, or time across projects and teams.
Operates a local Red Hat Developer Hub environment with the rhdh-local-setup customization system: enable or disable dynamic plugins, apply configuration, switch pristine and customized modes, start or stop containers, inspect health and logs, run plugin verification, and back up or restore customizations. Use for local RHDH, podman compose plugin testing, PR artifact verification, 504 or startup troubleshooting, and local Extensions Catalog checks.
Best practices for ROS 2 robotics development, covering package structure, nodes, topics/services/actions, launch files, QoS, tf2 transforms, and testing. Use when creating ROS 2 packages, writing nodes in rclpy or rclcpp, defining custom messages/services/actions, writing launch files, configuring QoS profiles, working with tf2 transforms, or building and testing a colcon workspace.
Find the right Salla documentation or API schema fast. Use when you need a doc link, an endpoint's exact request/response shape, an event payload schema, React theme documentation (routes, hooks, components, slots), or you're unsure where something is documented. Routes each topic to its scoped public docs entry point on docs.salla.dev. Never start from the full docs index (llms.txt) — it spans the Merchant API, storefront themes, and more; app development is only a small slice of it.
Audit the structured data a page actually declares, decide which entities belong on it, and draft validated JSON-LD from verified facts only, separating Schema.org validity from Google rich-result eligibility. Use when the user asks about schema markup, structured data, JSON-LD, or whether a page is eligible for rich results
Use Scry's read-only SQL research surface (/v1/scry/schema, /v1/scry/query) for bounded SQL over the public internet and vector helpers. Also use when a research ask wants diverse, orthogonal sources, angles, hypotheses, or probe phrasings — includes the enumeration discipline and the /v1/creativity/outsized fan-out.
A heavyweight Harness skill that turns the SDD-RIPER methodology into a strictly executable process. It helps users clarify the final goal, generate a codemap/context, split out the smallest chaos unit, maintain a complete spec, enforce RIPER phase gates, block high-risk actions, and preserve a local task trail that can be resumed in a new chat.
Active runtime recovery for coding agents: when something breaks mid-task, diagnose the root cause, write a fix, VERIFY by re-running the broken thing, then file a `HEAL-` entry to `.learnings/HEALS.md` with proof. Use whenever a command, test, build, or lint fails or exits non-zero; on missing tooling, dependency/lockfile mismatch, wrong runtime version, venv or permission errors, port conflicts, dirty git state, or a missing `.env`; when the agent needs a helper or one-off script that doesn't exist yet; when an external API, tool, or MCP errors or rate-limits; or when a test flakes. Search `HEALS.md` by `Pattern-Key` first — most heals are recurrences, so increment `Recurrence-Count` instead of duplicating. Verify is mandatory: mark `pending-verify` honestly if sandboxed, `abandoned` if the fix can't be made to work. Pairs with `self-improvement` (which promotes recurring heals to durable memory) but owns the verify-before-persist discipline self-improvement doesn't.
Apply repository-grounded senior engineering judgment to substantial Python work and bounded Python changes with production or cross-boundary risk. Do not use for trivial syntax questions, generic tutoring, or tasks with no Python artifact unless explicitly invoked. Use for writing, review, diagnosis, design, refactoring, or maintenance where correctness, state, effects, concurrency, compatibility, security, reuse, testing, or long-term ownership materially matters.
DEPRECATED: Opus 4.7's adaptive thinking covers most cases natively. Structured, reflective problem-solving through sequential chain-of-thought reasoning that replaced the Sequential Thinking MCP server. Retained as a reference pattern when deterministic, reviewable reasoning traces are required regardless of the model's adaptive-thinking choice.
Create reusable agent users for Omni-Channel setup and routing validation. TRIGGER when users ask to create Omni agents, provision Omni test users, seed sandbox users for routing, create Omni-Channel routing agents, or repair missing demo agents. DO NOT TRIGGER for queue membership, permission-set assignment, or supervisor-user creation.
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
UK, US, and Canadian shipping, logistics, customs, duties, and tariff expert with automotive commodity code expertise. Covers import/export documentation, HS/HTS codes, rules of origin, FTAs, and landed cost calculations. USE WHEN user says 'shipping', 'customs', 'tariff', 'duty', 'import', 'export', 'HS code', 'HTS code', 'commodity code', 'landed cost', 'incoterms', 'customs broker', 'freight', 'logistics', 'rules of origin', 'CUSMA', 'USMCA', 'TCA', or needs help with international trade compliance.
Creates, audits, and validates agent skills following the Agent Skills open standard. Covers YAML frontmatter, description writing, progressive disclosure, directory structure, 9-phase audits, severity classification, and manifest-implementation drift detection. Use when creating new skills, writing skill descriptions, auditing existing skills, detecting version drift, validating implementations match manifests, or debugging skill discovery issues.
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.