Skills
101,174 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Debugs failing GitHub Actions CI runs for PostHog PRs, commits, and branches, and answers broad CI-health questions ("is CI red?", "is master green today?", "what's broken right now?"). Use when the user asks why CI is red, asks for the current CI or master status, or mentions a failing check, GitHub Actions run, Depot runner, Depot CI run, workflow, job, shard, merge queue kick, flaky test, lint failure, typecheck failure, snapshot diff, migration check, generated types drift, or skills build failure. Interactive runs start with the `hogli ci:insights` digest (cross-run CI history from engineering analytics), then use read-only inspection, failure classification, the smallest local reproduction with hogli, and safe reporting without rerunning CI or posting to GitHub. Running unattended as the "Master-red diagnosis" workflow: see references/master-red-incident.md for its sandbox-compatible first step.
Multi-agent investigation for stubborn bugs. Use when: going in circles debugging, need to investigate browser/API interactions, complex bugs resisting normal debugging, or when symptoms don't match expectations. Launches parallel agents with different perspectives and uses Chrome tools for evidence gathering
Build a new service, app, API, agent, bot, script, or tool on this ryra machine. Use this WHENEVER the user wants to develop, build, scaffold, make, create, or start a new project here -- it sets up the ryra service layout (service.toml / test.toml) so the thing can be added, run, and upgraded as a managed service
You are a debugging expert specializing in setting up comprehensive debugging environments, distributed tracing, and diagnostic tools. Configure debugging workflows, implement tracing solutions, and establish troubleshooting practices for development and production environments.
Use this skill when debugging any DOCA symptom—a build that won't compile, a link step that can't resolve a doca_* symbol, a runtime call returning DOCA_ERROR_*, a silent service or tool, or a stack trace / valgrind / core dump—and the user needs the layered ladder (install → version → build → link → runtime → program → driver), verbosity controls (--sdk-log-level, DOCA_LOG_LEVEL, the doca-{lib}-trace flavor), container-debug constraints, or guidance on capturing state for a Developer Forum post. Trigger even when the user does not say "DOCA debug"—implicit phrasings include "undefined reference to doca_*", "how do I get more logs", "packets aren't reaching the wire", "doca_caps returned nothing", or "hugepages empty in the container". Refuse and route elsewhere for library-specific debug (Flow pipe trace, RDMA QP, Comch stats), env-class pkg-config or hugepages symptoms, the DOCA_ERROR_* taxonomy and lifecycle interpretation, and performance or incident-response work—those belong to other skills.
Docker on Windows with Git Bash / MINGW path conversion. PROACTIVELY activate for: (1) Docker commands failing on Windows Git Bash with path errors, (2) volume mount path conversion (-v $(pwd):/app), (3) MSYS_NO_PATHCONV and MSYS2_ARG_CONV_EXCL workarounds, (4) double-slash escapes (//c/foo) for MINGW, (5) docker-compose volume mounts on Windows, (6) WSL2 vs Hyper-V backend path interop, (7) line-ending issues in mounted scripts (CRLF vs LF), (8) UNC path limitations. Provides: MSYS path-conversion explainer, copy-pasteable env-var workarounds, double-slash recipes, line-ending fixes, and compose-mount patterns for Windows
Use when bootstrapping docs or when a task may change public behavior, APIs, CLI commands, configuration, environment variables, schemas, setup, deployment, operations, architecture, release notes, durable project decisions, README, reference docs, changelog, ADRs, playbooks, or agent guidance
Entry point for Drupal Canvas Code Components (React/JSX). Points to the officially maintained drupal-canvas/skills suite (component definition, metadata, push, styling, data fetching, regions, page definition, content templates) and to this repo's complements for Twig SDCs and upstream contribution. Use when creating, modifying, or pushing Canvas Code Components, or when deciding which Canvas skill applies.
Use this skill whenever the user submits a non-trivial mathematical claim that needs a rigorous proof or audit. Trigger on IMO/Putnam/USAMO/Olympiad-style problems, ML/AI theoretical statements, research conjectures, suspected-false claims, multi-step proofs the user already failed on, proof drafts with possible hidden assumptions, or any request containing 'prove rigorously', 'verify this', 'is this true', 'find the gap', 'audit my proof', 'find a counterexample', or 'use EvoMath' that targets a mathematical claim. Activate also when the problem requires more than three reasoning steps. Do NOT use for single-step calculations, definition lookups, textbook exercises with a known recipe, code analysis tasks, literature survey questions, pure symbolic manipulation, or non-mathematical applications of those trigger phrases (e.g., 'is it true that GPT-4 can solve math?', 'verify this LaTeX syntax'); hand those back instead
Reasoning protocol distilled from Claude Fable 5 — Floor check, multi-hypothesis diagnosis, adversarial self-review, Constraint Loop for hard output constraints. Use when the user says "fable5", "bật thinking mode", "reason like fable 5", or invokes /fable5. Once invoked it stays active for the rest of the session (toggle off with "stop fable5" / "normal mode")
Feishu task management tool for creating, querying, and updating tasks and lists. Use this Skill when: (1) creating, querying, or updating tasks; (2) creating or managing task lists; (3) viewing task lists or tasks in a list; (4) the user mentions “task,” “to-do,” “list,” or “清单”; (5) setting task owners, followers, or deadlines, or adding members; (6) appending task step records (Task steps); (7) uploading task attachments (supports task / task_delivery); (8) registering an Agent or updating Agent information (register / update_profile).
File and directory operations via Claude Code built-in tools, replacing the Filesystem MCP server. Triggers on: “read this file”, “write to file”, “edit file”, “find files matching”, “search for text in files”, “list directory”, “show directory tree”, “rename file”.
Guide a first-time Forge builder through building Forge Guru, a Rovo Agent that answers Forge questions. Use for Forge onboarding, a first Forge or Rovo app, or resuming this tutorial. Route unrelated existing-app changes, debugging, reviews, and connector work to the specialist skills.
Provider-independent production workflow for AI agents creating game trailers and promos, including announcement, gameplay, launch, DLC/update, store-page videos, social cutdowns, and generated/engine-capture hybrid trailers. Use when planning, scripting, capturing, generating, editing, localizing, reviewing, or QAing game marketing videos where gameplay truthfulness, platform/store constraints, ratings, accessibility, claims, CTA metadata, and rights provenance matter.
B2B SaaS Growth — PLG vs SLG Playbook — Diagnose whether your problem is distribution, pricing, or PMF. PLG/SLG selection by ACV and sales cycle, the 5-stage path from $0 to $10M ARR, NRR discipline, affiliate & channel motion, enterprise tiering. Built from HeyGen, Deel, Vercel, Supabase, Snowflake patterns. B2B SaaS growth — PLG vs SLG decision guide — Diagnose whether your bottleneck is distribution, pricing, or PMF. Choose PLG/SLG based on ACV and sales cycle, the 5-stage path from $0 to $10M ARR, NRR discipline, affiliate and channel tactics, enterprise tiering. Drawn from HeyGen, Deel, Vercel, Supabase, and Snowflake. B2B SaaS growth — PLG vs SLG playbook — Diagnose whether the challenge is distribution, pricing, or PMF. Choose PLG/SLG based on ACV and sales cycle, the 5-stage path from $0 to $10M ARR, NRR discipline, affiliate and channel strategies. Triggers: "B2B growth" | "B2B SaaS" | "PLG" | "SLG" | "product-led growth" | "sales-led growth" | "PLG or SLG" | "SaaS pricing" | "ARR growth" | "NRR" | "go to market" | "enterprise sales" | "affiliate" | "PMF" | "B2B 增长" | "PLG 还是 SLG" | "SaaS 定价" | "渠道合作" | "PLG/SLG 선택"
KOL Outreach & Influencer Marketing Playbook — Complete SOP from discovery to ROI tracking. Battle-tested with 200+ KOL campaigns at AFFiNE (60k stars). Includes pricing benchmarks, email templates, content packages, platform algorithm guides, and data-driven evaluation frameworks. KOL 外联与红人营销实战手册 — 从发现筛选到 ROI 追踪的完整 SOP。基于 AFFiNE（60k stars）200+ 次 KOL 合作实战验证。包含报价基准、邮件模板、内容包模板、各平台算法指南、数据评估体系。KOLアウトリーチ＆インフルエンサーマーケティング実践ガイド — 発見からROI追跡までの完全SOP。AFFiNE（60k stars）での200回以上のKOLキャンペーン実績。価格ベンチマーク、メールテンプレート、コンテンツパッケージ、プラットフォームアルゴリズムガイド。KOL 아웃리치 & 인플루언서 마케팅 플레이북 — 발굴부터 ROI 추적까지 완전한 SOP. AFFiNE(60k stars) 200+ KOL 캠페인 실전 검증. 가격 벤치마크, 이메일 템플릿, 콘텐츠 패키지, 플랫폼 알고리즘 가이드. Triggers: "KOL outreach" | "influencer marketing" | "KOL campaign" | "influencer outreach" | "creator partnership" | "KOL strategy" | "red人" | "红人营销" | "KOL合作" | "达人合作" | "influencer pricing" | "KOL ROI" | "content creator outreach" | "KOL筛选"
Upload local images or videos to a GitHub PR and embed them in the description or comments. Use when asked to "attach screenshots to PR", "add images to PR", "upload test results to PR", "embed screenshots in PR description", "add before/after images to PR", "attach UI screenshots", "show test results in PR", "add visual evidence to PR", or any request involving images and PRs. Always use this skill when the user wants to visually document changes in a pull request, even if they don't use the word "upload" — phrases like "put the screenshot in the PR" or "show the image in the PR" should trigger this skill. Prefers GitHub CLI's native `--attach` flag (gh 2.99.0+), which needs no browser at all, and falls back to browser automation (Chrome DevTools MCP, then Playwright MCP, then agent-browser) only when `gh --attach` is unavailable.
Design, prioritize, and run measurable growth experiments across acquisition, activation, retention, referral, and revenue. Use when a startup needs an experiment backlog, ICE/RICE prioritization, referral or UGC loops, rapid weekly testing, causal measurement, or stop conditions without spam, fake accounts, or dark patterns.
Generate a vetted backlink outreach batch (`seo/outreach-batch-YYYY-MM-DD.md`) with a SEND/CUT prospect table, ranking target URLs, and structurally varied plain-text email drafts for partners, customers, and niche blog authors. Use when writing link-building outreach emails, asking integration partners or customers for backlinks, pitching ranking listicles or guides, or auditing an outreach list for weak prospects
16:9 HTML deck in an editorial minimalist style. Warm cream slides, serif display type with grotesque body text, hairline rules, monospace metadata, generous macro whitespace, and one accent. Distilled from Leonxlnx/taste-skill `minimalist-skill`.
Set up and tweak Meta Movement SDK (MSDK) retargeting for a character model. Use this whenever the user wants to retarget a humanoid FBX/prefab for Meta VR body tracking, generate a retargeting config, or hand-edit the resulting `<asset>.json` (fix known-joint mappings, exclude joints from auto-mapping, rename target joints, adjust per-joint mapping weights, change a mapping behavior to twist/childAlignedTwist, edit T-pose values). The headless entry point is `Meta.XR.Movement.Editor.MSDKUtilityEditor.RunDefaultRetargetingSetup(GameObject asset)` — call it against a live Editor with unity-cli first, then hand-edit if needed. **Skip** if the user is editing runtime retargeting code, the source `OVRSkeletonData.json`, or non-MSDK files.
Жизнь вимарши и отказ по родам: «разбери вимарши», «закрой/оставь вопрос», «отказываемся от направления», «всё это чушь», «забудь это»; вероятно устаревшее чужое — дело забвения. Различить волю и опровержение, сохранить смысл, перевязать зависевших, затем исполнить. Также якорение, разрешение, принятие как есть, вытеснение, кристаллизация, поле вопрошания, «триаж вимарш», work the field of inquiry, resolve the question. Не постановка узла (writing), не сборка графа (assembly). Нужны искрон-тулы.
Используй для задач интеграции и целостности превращения. Триггеры: «интеграция», «интегрировать X с Y», «спецификация интеграции», integrate, integration spec — режим 0: сначала граф; «область интеграции изменения», integration scope, cold review — режим 1: холон + steward + узлы изменения; «проверь бяньхуа на целостность», «что затронет превращение», «кого заденет», integrity check — волновой фронт; «подкреплено ли графом», «не театр ли», claim audit — обратный аудит прозы. Distinct from assembly и design. Нужны iskron_*.
Access and compare Israeli supermarket prices using mandatory Price Transparency Law data feeds. Use when the user asks about “supermarket prices Israel,” “price comparison Shufersal,” “Rami Levy prices,” “grocery prices,” “Price Transparency Law,” “shopping list optimizer,” “food costs Israel,” or “השוואת מחירי סופר.” Covers chain-specific XML feed parsing, cross-chain price comparison, shopping list optimization, price trend tracking, and restaurant ingredient cost analysis. Do NOT use for restaurant operations (use israeli-restaurant-ops) or non-food retail prices.
Drupal security and coding rules from Ivan Grynenko's cursorrules, organised by OWASP Top 10 (2021) category: authentication, access control, injection (SQL, XSS), cryptographic failures, security misconfiguration, vulnerable dependencies, SSRF, insecure design, integrity, and logging, plus database standards and file permissions. Use when writing or reviewing Drupal code for security, handling user input, building queries, handling file uploads, adding permission or access checks, making outbound HTTP requests, or preparing a security review.
Run a structured reflection on how AI is reshaping your skills, career, and leverage. Use this skill for monthly career audits, skill atrophy reviews, understanding what's worth learning vs delegating to AI, or when the user says "career audit", "skills review", "what should I learn", "am I becoming obsolete", "AI impact on my work", "leverage review", "meta reflection". Based on Karpathy 56k-like programmer identity post.
Upgrade LLM outputs from plain text to structured, rendered formats like HTML, Marp slides, or interactive dashboards. Use this skill when the user wants better-formatted output, needs to convert notes into a presentation, wants HTML output from an LLM, needs slides from a document, or says "make this prettier", "render this", "output as HTML", "make slides from this", "structured output", "Marp", "better format". Based on Karpathy 19k-like HTML output post.
Transition from vibe coding (fast prototyping) to agentic engineering (rigorous iteration). Use this skill when the user has a rough prototype and wants to level it up, needs to go from "it kind of works" to production-quality, wants to understand the difference between vibe coding and agentic coding, or says "polish this", "make this production-ready", "level up from prototype", "vibe coded this now what". Based on Karpathy posts 3 and 6.
Investigate a LangSmith experiment with the LangSmith CLI, identify examples with poor evaluator results, explain likely causes using run evidence, and propose targeted fixes. Use when a user asks why an experiment performed badly or which evaluated examples need attention.
A one-stop tool for getting content from the internet—video downloads, audio extraction and transcription, subtitle downloads, comment collection, creator data, web scraping, aggregated search, cross-platform publishing, and analytics, covering 30+ platforms (Douyin/TikTok/YouTube/Bilibili/Xiaohongshu/Zhihu/official accounts/Channels/Weibo/Reddit/HackerNews/Jike/Knowledge Planet/Xueqiu/Tieba/Toutiao/Twitter, etc.). Automatically selects the best tool through a fallback chain. Use when the user says “download,” “get a video,” “grab this,” “crawl,” “read this,” “read this link,” “check this URL,” “transcribe,” “get subtitles,” “comments,” “check comments,” “grab comments,” “creator data,” “creator updates,” “UP主,” “what did so-and-so post recently,” “cover image,” “post to Douyin,” “post to Xiaohongshu,” “schedule a post,” “draft,” “account data,” “follower count,” “take a screenshot,” “webpage text,” or “what is this page about”; provides any URL, short link, BV number, Channels link, or official account article link and asks to retrieve its content; mentions a specific platform such as Douyin/TikTok/YouTube/Bilibili/Xiaohongshu/Zhihu/official accounts/Channels/Weibo and requests downloading or searching content, reading comments, or collecting data; or asks for any operation involving getting content from the internet. Prefer tools in this fallback order: search uses anysearch→opencli→agent-reach; downloads are routed by platform; scraping uses Scrapling→browser-use→web-access; for browser operations (logged-in pages/JS rendering/multi-step interactions/cross-site transfers), prioritize huashu-chrome MCP (since 2026-10-21, real logged-in state + evidence of results, replacing chrome-devtools MCP). Purely technical fact-checking or searches for tutorials and experience (without a platform name and without retrieving content) defer to laohan-sousuo (decided by Jeffrey on 2026-10-02).
When the user wants to build data enrichment workflows, score leads against ICP, set up Clay waterfalls, or improve contact data quality. Also use when the user mentions “enrichment,” “data enrichment,” “Clay,” “waterfall enrichment,” “ICP scoring,” “lead scoring,” “intent data,” “contact verification,” “Apollo,” “ZoomInfo,” or “data quality.” This skill covers lead enrichment waterfalls, ICP scoring frameworks, and contact verification systems. Do NOT use for technical implementation, code review, or software architecture.
Identifies high-quality leads for your product or service by analyzing your business, searching for target companies, and providing actionable contact strategies. Perfect for sales, business development, and marketing professionals.
Expert-level Linkerd service mesh management, traffic control, reliability, and production operations. Use when the user mentions service mesh, Kubernetes, microservices, mTLS, or observability, or when the task involves Linkerd Architecture, Mesh Injection, Traffic Management, or Reliability Features.
Queries patent citation data from PatSnap, including citation counts and details of citing patents. Triggered when users mention patent citations, citation analysis, patent influence, citation frequency, citations of a patent family, forward citations, or ask which patents cite a given patent; also for patent citations, citation count, patent influence, citation analysis, or PatSnap. Use even if “PatSnap” is not explicitly mentioned, as long as the user wants to find how often a patent is cited or which patents cite it.
Retrieve translated patent claims from the 智慧芽 patent database. Trigger this skill when the user asks about patent claims or claim translations, wants to view claims in a specific language (Chinese, English, or Japanese), looks up patent claims by patent ID or publication number, analyzes claim text, or mentions claim translation, patent claim translation, PatSnap, or patent translation. Trigger it even if the user does not explicitly mention “patent claim translation,” as long as they need patent claims in a specific language.
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.