Skills
100,696 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Shows, copies or rebuilds scrolls-explainer.html: an interactive, offline page that explains how the scrolls skill family works (/scrolls-setup, /scrolls-update, /scrolls-hide, /scrolls-unhide, /scrolls-remove, /scrolls-restore, /scrolls-help) — one tab per command that animates, step by step, what the command does to docs/.scrolls/, SCROLLS.md, CLAUDE.md, AGENTS.md and git, with a callout explaining each step, a tab for how a new agent session reads the memory, and full keyboard navigation (arrows step, [ ] or digits switch tabs, Space pauses, ? lists shortcuts). Use this whenever the user runs /scrolls-explainer, or asks for a visual, diagram, animation, walkthrough, explainer or interactive page of how the scrolls commands or the scrolls memory work, or wants something to show a team. By default (same as --show) it opens the bundled page in place and copies nothing; -o/--output copies it to a file or folder (-o . for ./scrolls-explainer.html), -f/--force overwrites with -o, --open opens the copy, and --build to regenerate the bundled page from the scrolls-* skills as they are now (their tabs, lockstep version, and a review check when a SKILL.md changed). Works on macOS, Linux, and Windows (bash or PowerShell).
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.
Write the design decision for one change as one interactive HTML page — a zoomable map of the proposed design, the decisions with clickable options, a worked trace, constraints, scope — for the person who locks it. Use when invoked by name (/visual-plan, "make a visual plan", "visual plan for …"), or when a planning or explainer skill asks for its interactive page. Not a task list — the implementation plan is a separate document written after the lock.
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”.
Free, anonymous AI image generation and editing with no API key and no account. Use when the user asks for an image, a picture, a mockup, a visual asset, a style transfer, an edit (“make it night”, “remove the car”, “repaint as oil”), or a before/after comparison. Also generates logo/hero/texture candidates and builds labelled contact sheets.
Use this skill for questions about SAP Clean Core Data, including what clean core data is, the five data pillars (data strategy, data governance, data quality, data volume efficiency, data protection), master data management with SAP Master Data Governance, data quality dimensions and the Data Quality Index, data profiling with SAP Information Steward, data volume efficiency and tiering, data lifecycle management and archiving with SAP ILM, data protection principles, SAP Business Data Cloud, SAP Datasphere, SAP Master Data Integration, SAP One Domain Model, the data product economy, or achieving clean data as part of RISE with SAP. Also use it for data KPIs (data volume efficiency, data quality index), governance maturity practices (DAT-01 through DAT-05), or how the RISE with SAP Methodology Dashboard measures data KPIs. For the full dashboard reference, use `clean-core-general`. For broad clean core overview questions, use `clean-core-general` first
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.”
Deep, themed review of a diff: the review-diff flow and its standard lenses, plus one cheap reviewer subagent per theme, using distinctive preferences distilled from Alex North's public GitHub reviews (naming, API shape, errors, tests, coupling, and related themes). Needs the review-diff skill. Use when the user asks for a deep review, themed review, or anorth-style review.
Use when a Dido task has multiple steps or spans more than one session (a new project, milestone, major feature, redesign, migration, a request involving both the app and backend), when Dido asks for a plan, roadmap, steps, "where are we", to resume work, close a milestone or write the closing report, and when one of Dido's requests arrives midway through a plan.
This skill should be used when the user asks to "build electrobun app", "electrobun build", "electrobun canary", "electrobun stable", "set up code signing", "electrobun distribution", or is diagnosing electrobun build failures. Covers dev/canary/stable environments, all three platforms, toolchain prerequisites, artifact output, and CI/CD setup.
Use this skill when the user asks about the “electrobun kitchen sink,” “defineTest,” “AUTO_RUN mode,” “kitchen sink tests,” the “electrobun test runner,” navigating playground windows, or wants to add new electrobun Kitchen Sink test coverage.
This skill should be used when the user asks about cross-platform electrobun support, "electrobun Linux", "electrobun Windows", CEF requirements by platform, "electrobun platform differences", or is setting up multi-platform CI for an electrobun app.
Use this skill when the user asks about “electrobun RPC,” “defineElectrobunRPC,” “Electroview.defineRPC,” “ElectrobunRPCSchema,” bun-to-renderer communication, or renderer-to-bun communication. Activates automatically when RPC code is present.
Use this skill when the user wants to build a complete electrobun feature end to end, asks about the “electrobun SDLC,” “electrobun agent pipeline,” “8-stage electrobun pipeline,” or needs to orchestrate the researcher/architect/planner/dev-squad/QA/test/alignment/docs agents.
Use this skill when the user asks to “write electrobun tests,” “add electrobun test coverage,” “electrobun testing,” use the “defineTest” pattern, generate new electrobun test suites, or reverse-engineer electrobun component behavior from test source.
Use this skill when the user asks about the “electrobun development workflow,” “electrobun pipeline,” “electrobun lifecycle,” “where am I in the electrobun pipeline,” or needs guidance on what stage comes next in electrobun development.
Deliver a change end to end by orchestrating agent profiles: grill, plan, test-first implementation, review, QA, then merge or open a PR. Use when the user's message starts with “deliver” or names flyingnobita-deliver, whatever the size of the work.
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
Build a personal, ranked shortlist of the PostHog Inbox reports the current user is most likely to care about right now. Combines the user's activity summary (what they work on and keep an eye on), the inbox ranking model's open, action and fix probabilities and lifts, suggested-reviewer routing, ownership, pull request state and recency, then returns the top N (25 by default) ordered from most to least relevant. Use when the user says “let's look at my inbox,” “what's in my inbox for me?,” “my top 10 inbox reports,” “what should I look at today?,” or asks to re-rank, focus, or filter that list. For browsing, filtering, drilling into, or acting on a single report, use `inbox-exploration`.
Connect a Supabase project so its auth emails send through PostHog email templates via the Supabase Send Email Hook, in an order that never breaks a sign-up. Use when asked to set up, connect, test, or fix Supabase auth emails, Supabase email templates, or the Supabase Send Email Hook, or when Supabase shows “email rate limit exceeded” or an auth email error.
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.
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».
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.