Skills
97,222 packaged capabilities and playbooks for agents. Install any of them with one command.
All
100 questions about Binance Agentic Wallet. Uses Chinese Q&A to guide an agent in understanding Binance on-chain wallets, choosing official baw routes, checking transaction approvals and risk boundaries, and designing constrained automation extensions. Covers meme coin risks and honeypot detection, rug pull prevention, and verifying smart-money signals. For product questions, troubleshooting, trading strategy constraints, meme coin risk control, and wallet workflows; does not replace the official wallet skill and is not for placing Binance exchange futures orders.
Runs a local (LAN) and instant public host (Zero-Config Tunneling via Cloudflare/Localtunnel) for simultaneous multiplayer educational quizzes and board games in a classroom, without router configuration or a paid domain. Includes an automatic gradebook (real-time grade ledger), instant QR Codes for student smartphones, and export of grade summaries to Excel/JSON.
Assess, set up, and verify how an AI development environment uses an organization's actual design system. Use when someone wants to keep AI on their system's rails, connect system knowledge and tools to coding agents, establish reuse and gap policies, or check whether those guardrails work. Focuses on the workflow and its evidence; ordinary page building or a full system inspection alone does not require this skill.
Researches evidence unavailable locally: external documentation, public repositories at specific refs, archives, and published dependency artifacts (JARs, source JARs, POMs, dependency graphs), reusing a persistent cache of Git clones and Maven artifacts. Use for library docs, upstream source and history, dependency source or metadata, or any question needing external evidence
Use when the user asks to fix, patch or upgrade a self-managed GitLab vulnerability (e.g. 'Please fix my GitLab vulnerability'), CVE-2026-110264 or the GitLab 19.5.1 critical patch release, across Omnibus, Docker, Helm chart and IaC deployments. Read-only inventory, approval gate, post-deploy checklist, focused PRs.
Humanize prose or draft it from supplied facts when explicitly asked to "humanize", "de-AI", "remove AI-sounding language", or write in a human voice. Simplify by cutting filler, stale content, and needless complexity. Confirm scope each run and offer four voice presets.
Build NHCX (India's National Health Claims Exchange) payer communication into an existing HMIS: receiving payer queries, notifications and notes on a pre-authorisation or claim, replying with text and documents, and acknowledging notifications, with the embedded NHCX gateway it needs. Use when a hospital system must answer insurer or PMJAY queries over NHCX.
Build NHCX (India's National Health Claims Exchange) payment notices into an existing HMIS: receiving the payer's payment notice and reconciliation breakdown, matching it to the claim, and acknowledging it, with the embedded NHCX gateway it needs. Use when a hospital system must record insurer or PMJAY payments arriving over NHCX.
Build NHCX (India's National Health Claims Exchange) claim reprocess and balance release into an existing HMIS: asking the payer to look again at a decided claim, asking for the unpaid balance of a partly paid claim, and applying the payer's answers, with the embedded NHCX gateway it needs. Use when a hospital system must contest a claim decision or recover a withheld balance over NHCX.
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". Prefer it over raw git worktree, ad hoc PTYs, or Computer Use when Orca state is involved. Use Computer Use only when a visible window needs GUI control that a CLI, filesystem, or API cannot do.
Audit the skill inventory for quality, coverage, and staleness. Detect overlapping, incomplete, or outdated skills and produce a health report. Activate when: skill audit, stocktake, skill inventory, check skills, which skills exist, audit skills, skill quality, skill coverage.
Connects and operates the Visant Labs MCP (requires a Visant Labs account): brand guidelines, mockups, creative studio, canvas, budgets, moodboard, PDF extraction. Use on "connect visant", "use the visant tools", "setup visant mcp", "conecta o visant", "usar as tools do visant", "extrair PDF pelo visant".
Visant's official brand-building methodology: 9 stages in 3 phases and the dependency cascade between them. Use to generate or audit a full branding, or to write the prompt for one stage. Use on "Visant methodology", "full branding", "audit branding", "metodologia Visant", "branding completo", "auditar branding".
Preflight for a large client project: one question round with whoever owns the work, plus five premise checks (brand source of truth, loadable fonts, photo resolution, brand files, sourced numbers). Use BEFORE "new site", "redesign", "new proposal", "criar site", "redesenhar", "nova proposta", "montar campanha", "hidratar a marca".
Assembles a rough cut in Premiere Pro via premiere-pro-mcp from a JSON cut plan: frame-exact cuts, markers, punch-ins, cards, b-roll, -14 LUFS delivery. Use on “build it in Premiere”, “Premiere rough cut”, “punch-in”, “cover with b-roll”, “monta no Premiere”, “marcadores pra narrar”, “exporta as aulas”, /visant-premiere-editor.
Edits vlogs, event videos and video lessons from raw footage: breakdown, silence cuts that never clip a word, loudness and chapters, with a self-test against silent failures. Use on “edit this vlog”, “cut the silence”, “edit this lesson”, “monta um vlog”, “decupagem”, “edita essa aula”, “tira o silêncio do vídeo”, /visant-video-editor.
Build a website with someone without prior knowledge in eight fixed steps: mockup, design (two or three options based on characteristics), framework, PRD for approval, build and show locally, send to the harbor and show it there in a browser, assembly line, site or server. Open the island in Cockpit and report each step with schritt_melden. Use this skill whenever a website is being built: after webseite-planen, after the inventory in webseite-modernisieren, or for “build me the site”, “mockup”, “draft”, “PRD”, “view locally”, or “what happens after the plan”.
Help a person with no prior knowledge decide whether their website needs a content management system (CMS), and set it up if needed, for example Strapi in Docker on the Albatros server, accessible through a secure tunnel. Explain CMS using the image of a bulletin board. Use this skill for “CMS,” “Strapi,” “change content myself without code,” “blog,” “news,” “manage events,” “my colleague should be able to edit text,” “WordPress,” and “admin area.”
Work step by step with a person who has no prior knowledge and their AI to improve a small website's usability and appearance. First review it from three perspectives (flows, access, states, and language), then fix usability, offer three clearly different directions to choose from, set fixed values for colors, typography, and spacing (tokens), and rebuild all pages with photos at mobile and desktop widths. Use this skill for “design,” “looks boring,” “looks homemade,” “make it prettier,” “colors,” “font,” “redesign,” “three options,” “looks unprofessional,” and “layout.”
Help the person create an honest budget for their project: Albatros subscription, domain, AI subscription, email, add-on services, and later a server of their own. Explain which costs are fixed and which are variable, how to avoid unpleasant surprises, and when moving is worthwhile. Use this skill for “what does this cost,” “costs,” “prices,” “too expensive,” “budget,” “bill,” “is it worth it,” “how much does a server cost,” and before the person adds a new paid service.
Review the diff since a fixed point along Standards and Spec axes in parallel sub-agents, reporting findings without editing the target or deciding the final verdict. Use when the user wants to review a branch, PR, or work-in-progress diff, or when review-loop or project-review requests a specialist software check
Execute one bounded, already-decided work item — code, document, configuration, research artifact, Skill, or generic project task — by inspecting relevant context, offering agent-config routing when materially useful, verifying locally, and handing the result to review-loop with the appropriate specialist reviewer
Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent. Light Skills version of mattpocock/skills `research`; install one or the other, not both
Authoring, modifying, reviewing or building openSUSE RPM packages — .spec and .changes files, osc / OBS, and the Git packaging workflow on src.opensuse.org (Gitea). Use for a .osc/ checkout or a *.spec file; when the user mentions osc, OBS, rpmbuild, git-obs, tea, rpmlint or spec-cleaner; or asks to update, build, submit, review or fork a package, check if packages are out of date, or open a package pull request.
Check a US stock watchlist for price alerts - price above/below, % daily move, gaps, 52-week highs/lows, moving-average crosses, RSI, ATM IV, volume spikes, intraday range, stop/target hits, and upcoming earnings - with dedupe, cooldowns, NYSE market hours, optional ntfy/Slack/webhook delivery, pre/after-market, holidays and US/Eastern time. Use when the user asks "any alerts?", "check my watchlist", "alert me if AAPL drops below 200", "send alerts to ntfy", or when running a scheduled/heartbeat check
Backfill an existing product's screens into your design system's Storybook as representative page templates, rebuilt from the LOCAL design system wherever the product already uses it, with every region that isn't from the system flagged in plain sight. Use when the user says \"get this product into Storybook\", \"backfill our screens\", \"represent this product in the design system\", \"I want to see how a component change ripples across products\", \"relocate these pages into Storybook\", or names a product (a site, an app, a repo, a URL) and a Storybook. Relocation, not translation: it moves screens in and flags what isn't from the system; it never converts bespoke UI onto the system (that's vibe-killer) and never plans a migration (that's ds-adoption-plan). Also runs a refresh that reports how far the product has drifted from its Storybook copy since the last capture.
Coordinate root Herdr orchestrators across the local server and enabled saved machines. Ask for their current work and progress, relay messages verbatim, and route task execution through workers. Pair with the shunk031-herdr-orchestrate-workers skill for worker dispatch. Use when one session oversees multiple Herdr orchestrators; use the herdr skill for a single-pane or single-agent task.
For Japanese writing and editing, decide whether to organize from the structure, locally refine AI-like wording while preserving the original meaning and strength of claims, concisely summarize business or technical documents, or turn content into an outline, telegraphic prose, or technical slides, then choose the appropriate skill. Use as an entry point for choosing a writing approach when asked to “write something,” “make it easier to read,” or “fix the AI-like tone.” Do not use for ordinary conversation or code-only editing requests.
Help a person with no prior knowledge secure their project using the image of a house with keys, a safe, windows, and locks: never put secrets in the logbook (Git), but in .env on the server (and, if the conveyor belt needs one, in the harbor's safe); immediately regenerate accidentally published keys; use one key per purpose; leave open only the necessary doors; keep things updated. Use this skill for “security,” “password in code,” “API key,” “.env,” “Secret,” “I uploaded a key to GitHub,” “is my site secure,” “hacked,” “updates,” “firewall,” and before adding a new secret to the project.
Open an acceptance-testing session — the user is about to try finished work by hand. Points them at the feature's ACCEPTANCE.md, or writes one from what actually changed when there is none, then takes their notes, screenshots and corrections one at a time, recording each verdict beside its check and fixing or carrying what it finds. Anything that looks like a pattern rather than an incident — a missed requirement, a recurring bug, a design error — is written as a candidate to docs/acceptances/ATTENTION.<feature>.md for end-acceptance to promote, with the user, into docs/acceptances/ATTENTION.md. Runs no test suite during the session, because it is too slow while a person waits; end-acceptance runs it once. Use when the user says they are starting acceptance, about to test or try the feature, or invokes /start-acceptance <feature>.
Interview a team about its ICP, turn its account-fit rules into an explainable rubric, build and test a Clay scoring workflow, and calibrate it on five familiar accounts. Territory carving is an optional, separately reviewed proposal after scoring works. Use whenever someone asks: help us build account fit scoring, translate our ICP into scores, score our accounts for territory planning, test our rubric, or propose balanced books for reps. Do NOT use it to source a new market, score individual people, route inbound leads, launch outreach, merge records, or silently change CRM owners.
Produce a concise pre-market (morning) or after-close summary of a US stock watchlist - price and % change, RSI, trend, distance to stop and targets, biggest movers, upcoming earnings, and any alerts. Use when the user asks for a "morning brief", "market recap", "how did my watchlist do today", or on a scheduled morning/close run
Manage a US stock/ETF watchlist file: add, remove, update, list and validate tickers with thesis, entry, price targets, stop, tags, and per-ticker alert rules. Use when the user says things like “add NVDA to my watchlist”, “set a stop on AAPL at 210”, “what's on my watchlist”, “remove TSLA”, or “tag these as semis”.
Acquire official research-paper PDF/BibTeX pairs; discover venue/topic corpora or an author's publications; audit, update, import, and organize local paper libraries; configure named IEEE institution access; or investigate literature evidence and gaps.
Personal data access and knowledge base use. Use when a task needs the user's own historical documents, customer materials, past plans, meeting notes, or study materials—for example, “prepare for a meeting using previous materials,” “write a version based on the old plan,” or “why did we decide this before?” The user does not need to say “knowledge base” or name Bailian. Also use when the user wants to reuse a collection of materials, or asks to connect, update, view, pause, resume, or clear the repository. Also handles explicit bl knowledge / kscli resource operations. Do not trigger for general Q&A, summarizing only the current attachment, or writing that needs no historical materials; personal preferences and chat memory belong to bailian-memory, while DingTalk document management, model selection, and fine-tuning are outside this Skill.
Prüft und verbessert die Barrierefreiheit einer kleinen Webseite mit einer Person ohne Vorwissen, nach WCAG 2.2 AA in einfachen Worten: Kontrast, Schriftgrösse und Zoom, Bildbeschreibungen, Bedienung mit der Tastatur, Formulare, Vorlesen, Bewegung. Ergebnis ist ein Prüfprotokoll in docs/barrierefreiheit.md. Nutze den Skill bei «Barrierefreiheit», «barrierefrei», «Accessibility», «a11y», «WCAG», «Kontrast», «Alt-Text», «Screenreader», «für ältere Menschen lesbar», «mit Tastatur bedienen».
Send an independent judge that is not the author: a fresh evaluator subagent that checks finished work against pass criteria written before it was built (evaluator mode), or audits a batch against its source of truth (audit mode), with evidence for every verdict and never a fix. Use when the owner asks for an evaluator, reviewer, auditor or judge, or says 'send a judge', 'evaluate this', 'check my work with a fresh agent', 'get a second agent to review this', 'audit this folder', 'audit my registry', 'verify this against the source of truth', or 'LLM-as-judge'. Runs only when asked; it does not fire on its own at the end of a task. Not for checks a machine can run (tests, schema validation, a search that must return zero), not for hundreds of identical units, and not for fixing anything.
Use when an agent needs live China travel data — geocoding, POI search, driving routes and map tiles (高德 Amap), flight schedules, transfers and fares (飞常准 Variflight), high-speed rail tickets (携程 Ctrip), weather and city coordinates (Open-Meteo) — or the planning order and mode trade-offs behind a trip. Triggers on 查航班 / 查火车票 / 查天气 / 查景点坐标 / 查驾车距离 / 行程该先定什么. Not for generating a full itinerary or shortlisting attractions.
Finds, buys, or connects a custom domain (e.g. meinladen.ch) for the Albatros server. Explains domains and DNS with the analogy of an address and phone book, suggests names, checks availability with domain_suchen, and buys through Albatros using domain_kaufen (the person is the owner and enters their details only on the payment page). If the person already has a domain, the skill connects it with domain_verbinden: DNS records, TXT proof _albatros, and checks until the site appears with a lock in the browser. Use this skill for “custom domain,” “my address,” “buy .ch,” “which domain is available,” “search for a domain,” “DNS,” “A record,” “CNAME,” “TXT record,” “domain doesn’t point to my site,” “certificate,” and “https isn’t working.”
Group a scope of Issues into Waves that can be implemented concurrently without stepping on each other — estimate what each Issue touches, exclude the ones that need a human, and print launch lines. Use when the user has several prepared Issues and wants to know which can run in parallel unattended
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.