Skills
100,344 packaged capabilities and playbooks for agents. Install any of them with one command.
All
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.
Use Virse CLI to find and organize assets, inspect existing aesthetic details, upload files or directories, replace originals, restore resources, and preview, download, and package deliveries. For asset management and resource directory tasks; canvas node layout is outside this entry point, and use virse-sharing to change sharing rules.
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”.
Read AI Monitor traces, conversations, formal Bad Traces, overview and Agent/Tool/Model/Skill metrics, cost, security findings, existing diagnosis and investigation reports. Use for scoped observability queries and verified ZIP exports; never creates or cancels analysis.
MANDATORY ENTRY POINT for any tracking-related work — invoke this skill FIRST, before reading any tracking plan file, querying any tracking data, or producing any tracking analysis. Applies to generate, audit, review, optimize, increment/supplement, adjust, Q&A, data verification, troubleshooting (an event has no data / stopped reporting / data looks wrong), and TRACKING CODE GENERATION — requests like 'give me Android/iOS/Unity tracking code' or 'how do I write tracking code' MUST enter here first; this skill runs the four-step identification and then routes to the code-generation execution skill, so naming pre-checks and plan-consistency rules apply. Do NOT invoke execution skills (code generation, plan generation, verification) directly from the user request, and do NOT open tracking xlsx files with openpyxl/pandas or start ad-hoc log/file spelunking, before loading this skill. It holds the canonical naming dictionary, object-group validation rules, 29 category Markdown assets (including partial/shared caches), the no-data diagnosis flow, and the lint script that catches TE platform-import failures — none available outside this package, so ad-hoc work misses import-blocking issues and blind alleys. Costs 1-2 extra turns but prevents invalid plans and misdiagnosis. Trigger words: tracking, tracking plan, event design, tracking audit, tracking review, tracking optimization, supplement, increment, SDK tracking, tracking code, code generation, integration code, data verification, PRD, troubleshoot, diagnose, no data, missing data, event not reported.
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.”
Turn stills into video and do media surgery from the shell — Ken Burns motion, crossfades, narration muxing, contact sheets, frame extraction, GIFs, loudness normalisation and speed changes. Use when the user wants a video, a slideshow, a preview clip, a contact sheet of a video, or needs audio and video combined, trimmed or normalised.
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
Search ~1.01M computer-science papers and a curated research wiki with the `fs` command (FrontierScholar CLI). Use it whenever a task needs CS literature, even if FrontierScholar is not mentioned. This covers finding papers on a topic or before a date cut-off, building a related-work or reading list, finding papers similar to given ones, checking a paper's abstract, method, evaluation or first-version date, finding which papers use a benchmark or dataset, and finding the open problems and rising approaches of a research area. Prefer it over memory for paper ids, titles and dates.
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.
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.”
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.
Use when the user asks to brainstorm, think an idea through, or explore what to build, or brings a rough idea whose goal or reason is not stated yet ("add notifications", "something for onboarding", "I have an idea for an app"), or asks for ideas or options ("give me ideas for X", "what could we do about Y"), in software or outside it. Works in Claude Code and Codex. Produces a design brief the user approved, ready for mstack-write-specs.
Use when the user wants Codex to write the code while Claude manages, reviews and commits it, for a plan or plan folder, a list of issues (GitHub or another tracker) or one larger task, such as "let Codex develop this plan", "Codex writes, you review", "use the Codex plugin to implement these issues", or when an mstack-plan execute-plan.md offers this workflow. Runs in Claude Code only, with the OpenAI Codex plugin; for Claude subagents as writers use mstack-codex-review-workflow. Produces one integration branch with one reviewed commit per phase.
Use when review feedback has arrived and has to be acted on, such as findings from a cross-vendor reviewer, the advisor, a fresh-context reviewer, CI review bots or comments on a pull request, or when the user says "process this review", "address the review comments", "handle these findings" or pastes reviewer output, or when another mstack skill needs a review processed. Works in Claude Code and Codex. Produces verified fixes with tests, reasoned rejections, and a log with a drafted reply per finding.
Set up a "chief of staff" workflow on herdr. One chief agent routes requests to a manager agent per project, and managers run workers in git worktrees and herdr tabs, all in parallel. Use when the user asks to set up numbrone, a chief of staff or multi-project agent workflow on herdr, or to add a project to an existing numbrone setup.
Erklärt CI/CD einer Person ohne Vorwissen mit dem Bild vom Fliessband mit Qualitätskontrolle und richtet es ein: Ein Workflow im Hafen von Albatros (Forgejo, code.aufwind.sh) startet bei jedem Push auf main. Der Arbeiter (Runner) auf dem eigenen Server baut die Seite, liefert sie mit Gesundheitscheck aus, prüft sie über die öffentliche Adresse und springt sonst auf die letzte gute Version zurück. Nutze den Skill bei «Pipeline», «CI/CD», «GitHub Actions», «Forgejo Actions», «Workflow», «Runner», «automatisch ausliefern», «deployen», «wie kommt meine Änderung auf den Server», «Fliessband ist rot», «Deploy fehlgeschlagen».
Take over or hand off a Git code project without needing to re-explain it. Use this skill when the user wants to continue a previous project, switch computers and continue, hand the project to someone else or another agent, or mentions relay, picking up, continuing, handoff, switching computers or devices, another computer, or setting up relay—even without mentioning relay or project memory. At the start of a session, reconcile; at the end, collect. Only project goals need human confirmation; everything else is automated.
Helps bring a small Swiss website into legal compliance, explaining it to people with no prior knowledge using the analogy of a doorbell nameplate and house rules: legal notice (UWG Art. 3 Abs. 1 lit. s), privacy policy under revDSG (information duty Art. 19), cookies (Art. 45c FMG), when the EU GDPR also applies, image rights, and marketing emails only with consent. Not legal advice. Use this skill for “legal notice,” “privacy,” “privacy policy,” “DSG,” “DSGVO,” “cookie banner,” “do I legally need this,” “what must go on my website,” and “contact form privacy.”
Find out whether ChatGPT, Claude, Perplexity, Google, Bing/Copilot, Apple, Meta and other AI crawlers can actually reach your site, and fix what blocks them without opening up what should stay private. Use when the user says or asks "is my site blocking AI crawlers", "can ChatGPT see my website", "check my robots.txt for AI bots", "should I block GPTBot", "GPTBot vs OAI-SearchBot", "block AI training but stay in ChatGPT search", "allow ClaudeBot", "what is Google-Extended", "why doesn't Perplexity cite us", "Cloudflare is blocking AI bots", "are AI bots getting 403s", "opt out of AI training", "noai meta tag", "X-Robots-Tag for AI", "fix robots.txt for AI search". Runs a dependency-free Python checker against the live site and reports each crawler by name and job. Works without a Revnu account.
Audit whether your website gives ChatGPT, Perplexity, Claude, Gemini and Google's AI Overviews something worth quoting, and fix the pages that don't. Use when the user says or asks "is my site ready for AI search", "audit my site for AI answers", "AEO audit", "GEO audit", "why doesn't ChatGPT quote our pricing", "make our pages citable by AI", "do I need llms.txt", "does schema help with ChatGPT", "check our structured data", "is our content visible without JavaScript", "AI SEO audit", "optimize our homepage for AI answers", "LLM SEO check", "why does AI get our product wrong", "fix our site for AI Overviews". Checks fetchability and indexability, answers in the raw HTML, entity facts, schema (including JS-injected markup), headings, dates and llms.txt, then gives at most 10 prioritised fixes and edits the repo when asked. Works without a Revnu account.
Fix what ChatGPT, Perplexity, Google AI Overviews, Copilot or Claude get wrong about your business: list every claim they make, mark it correct, wrong, outdated or missing, find the page it most likely came from and draft the fix (your own copy, your profiles, a correction request). Use when the user says "ChatGPT says the wrong price", "AI thinks we're a different company", "Perplexity says we don't have a free plan", "AI answers describe our old product", "Google's AI Overview is wrong about us", "ChatGPT confuses us with another company", "fix what AI says about us", "AI says we lack a feature we have", "prospects quote wrong things from ChatGPT", "correct our brand in AI answers", "why does Copilot say that about us", "AI uses our old name", "update AI after our rebrand or pricing change", or hands over a revnu-geo-check report. Works without a Revnu account.
Find out whether AI answers mention and cite your business when buyers ask about your category, what they say about you, and which pages they cite instead. Use when the user says or asks "does ChatGPT recommend us", "are we showing up in AI search", "check our AI visibility", "GEO check", "AEO check", "what does Perplexity say about us", "do AI answers cite our site", "why does ChatGPT recommend our competitor", "AI share of voice", "test prompts in ChatGPT", "track our brand in AI answers", "is Gemini getting our pricing wrong", "which sites do AI answers cite for our category", "LLM visibility report", "how often are we mentioned by AI". Runs buyer prompts several times with control prompts on the surfaces this host can actually reach (its web search tool; OpenAI, Perplexity or Gemini APIs only if keys are already set and the user approves the cost), reports rates with sample sizes, and lists every claim made about the business with the page to fix. Works without a Revnu account.
Get onto the third-party pages AI answers and search cite when buyers ask for the best tool in your category: "best X" roundups, directories, review sites, GitHub awesome lists, community threads and comparison pages. Finds which ones are cited, ranks them by fit and effort, and drafts each submission, PR or pitch by the target's own rules. Use when the user says "get us listed", "which directories should we submit to", "how do we get into best-of lists", "why does ChatGPT recommend competitors and not us", "get mentioned in AI answers", "submit to awesome lists", "get on G2", "where are our competitors listed", "pitch listicle authors", "find backlink opportunities", "launch directories", "get into roundups", "Product Hunt alternatives", "where should we be listed", "get cited by Perplexity". Never submits, pays or posts without a yes. Works without a Revnu account.
Write down once who buys, what they're stuck on, what it costs, what proof you have and what you've already tried, so every growth task starts from facts instead of a questionnaire. Creates or updates .agents/revnu-growth.md from the repo, the live site and the user, and imports an existing product-marketing.md. Use when the user says "set up our marketing context", "who is our ideal customer", "write our ICP", "describe the product for marketing", "positioning doc", "what's our brand voice", "remember this about our customers", "log what we tried", "what have we learned from marketing", "we changed pricing, update the context", "update our growth notes", "summarize the business for the agent", "import my product-marketing.md", "start a growth doc", or before a first marketing, SEO, outreach or launch task when no context file exists. Works without a Revnu account.
Helps a small website become easier to find in search engines, explaining it to people with no prior knowledge using the analogy of signposts and a city map. Covers page titles and descriptions, a main heading, descriptive URLs, image descriptions, loading time, sitemap.xml, robots.txt, structured data for local businesses, Google Search Console and Business Profile. Use this skill for “SEO,” “get found on Google,” “Google can’t find my site,” “search engine,” “Sitemap,” “meta description,” “get found locally,” and “Google Maps listing.”
Rundgang durch den eigenen Albatros-Server für eine Person ohne Vorwissen. Erklärt Terminal, Ordner, Speicher, Arbeitsspeicher, laufende Programme und den Hauptschlüssel sudo mit Bildern aus einer Wohnung. Die Person tippt die ersten Befehle selbst. Nutze den Skill bei «was ist auf meinem Server», «wie bewege ich mich im Terminal», «was ist ein Ordner auf dem Server», «ls cd pwd», «wie viel Platz habe ich», «was läuft da», und nach dem ersten erfolgreichen SSH-Besuch.
Pick the right skill for an intent and print a pasteable command. Reads MANIFEST.json (or every SKILL.md frontmatter when there is no manifest) and scores the intent against use_when phrases, curated keywords and not_for exclusions. Use when an agent has several skills installed and must choose one entry point before doing anything, or when you want to know which script handles "make me a logo" versus "read this page".
Erklärt einer Person ohne Vorwissen den SSH-Schlüssel mit dem Bild von Hausschlüssel und Schloss, erzeugt das Schlüsselpaar lokal auf ihrem Computer, hinterlegt nur den öffentlichen Teil bei Albatros und testet den ersten Besuch auf dem Server. Nutze den Skill bei «SSH-Schlüssel», «ssh-keygen», «ich komme nicht auf meinen Server», «Permission denied (publickey)», «was ist ein public key», «neuer Computer», und als Schritt 4 von /albatros:start.
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.