Skills
97,501 packaged capabilities and playbooks for agents. Install any of them with one command.
All
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.
Publish the next stable release by the project's own stable process — check that the main branch is green, choose the version and write its notes (through write-release-notes), publish whatever platforms still go out by hand, then push the version tag once the user has the notes, watch the build and check what it published and which release is marked latest. Use when the user asks to release, cut, ship or publish a stable version, push a version tag, or invokes /release-stable. Stops at a red main branch or a missing instruction instead of guessing; never moves, deletes or force-pushes a version tag.
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.
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
Explains Git to someone with no prior knowledge using the analogy of a logbook aboard a ship and its copy in the harbor (Albatros's Git service, code.aufwind.sh). Gets the repo from the harbor, guides them through their first entries (Commit) with good notes, sends them to the harbor (Push), and checks that the copy arrives on the Albatros server at ~/projekt. Rules: main only, stage only your own files individually, never force-push. Use this skill for “Git,” “GitHub,” “harbor,” “commit,” “push,” “pull,” “Repo,” “what is a repository,” “save my changes,” “push rejected,” and “conflict,” and before committing anything for the person.
Explain how a resource or subsystem works, its runtime flow across client, server and NUI, and where things live, through read-only subagents. Use when the user asks how something works, where code should live or which layer owns it, or when a skill such as architect calls for it
Helps someone with no prior knowledge write and choose text and images for their website: a homepage in three sentences, short text for people reading on mobile, their own photos instead of stock images, image rights and image size, and making AI text sound like their own voice. The result is a content list in docs/inhalte.md and the text on the site. Use this skill for “writing text,” “what should I write on the homepage,” “About us,” “images for the website,” “may I use this image,” “text sounds like AI,” and “content.”
Install and configure a PostHog SDK in a repository you can read and edit, following PostHog's docs for the framework. Use when a user working in their codebase asks to add, install, or set up PostHog, product analytics, session replay, or a PostHog SDK. Covers finding the right docs page, installing the latest package, getting the project token and ingestion host from project-get, keeping them in the env file, server-side setup, identifying users, and verifying the change. If you can't access the user's code, as is common in ChatGPT on the web or Claude on the web, use installing-posthog-from-chat instead.
Plans and guides a project's move from Albatros to its own server, explaining it with the analogy of moving into your own house: a moving checklist; renting and setting up a server (SSH with keys only, firewall, updates, Caddy for HTTPS); taking the Logbuch on GitHub along; switching Fliessband there to the new destination over SSH with your own key; bringing data and secrets; testing; changing the address in DNS, or transferring a domain bought through Albatros to a new registrar with the auth code from domain_mitnehmen; and handling backups yourself. Use this skill for “own server,” “move,” “away from Albatros,” “Hetzner,” “VPS,” “self-host,” “landing,” and “what do I need for my own server.”
Hauptskill von Albatros: der Fluglotse. Fragt mit dem Werkzeug lage den echten Stand der Person ab (Abo, Schlüssel, Server oder Seite, Fliessband, Domain, Mission) und folgt dann genau dem Skill, der jetzt dran ist; nach jedem geschafften Schritt fragt er neu. Ohne Anmeldung zeigt er die offene Bibliothek aller Skills zum Selbstwählen und erklärt, wie die Anmeldung geht. Nutze den Skill, sobald jemand an seinem Albatros-Projekt weiterarbeitet oder fragt «was jetzt?», «wie weiter?», «was ist der nächste Schritt?», «wo stehe ich?», «es geht nicht», «es klemmt», «ich weiss nicht weiter», bei /albatros:lotse und am Ende des Skills start. Bei einer klaren Frage zu einem Thema (z. B. «wie verbinde ich meine Domain?», «was ist ein SSH-Schlüssel?») hat der passende Fach-Skill Vorrang.
Lua best practices for FiveM resources built on ox_lib, the way Overextended structures its own resources. Use when reading or editing any .lua file or fxmanifest.lua, or when the user asks when to use require, lib.load or lib.loadJson, how to split a resource into modules, where config goes, or how to use cache, lib.onCache, lib.points, lib.callback or locales.
Delete the comments in a diff that the code should make unnecessary, through a fresh read-only reviewer, then fix the code each deleted workaround comment was excusing. Use before a change goes to review, or when the user asks to strip comments from a diff.
Use when posing, animating, or explaining a 3D human skeleton/manikin: anatomical joints, ROM clamps, walk/run/dance/backflip sequences, Three.js viewer, or agent-driven WebMCP figure control (reach/look_at). Phrases like pose the manikin, skeleton scheme, animate a walk cycle. Not for general 3D scenes, physics/ragdoll, IK foot-locking, or mocap import.
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.