Skills
97,905 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Evaluate scientific claims and evidence quality. Use for assessing experimental design validity, identifying biases and confounders, applying evidence grading frameworks (GRADE, Cochrane Risk of Bias), or teaching critical analysis. Best for understanding evidence quality, identifying flaws. For formal peer review writing use peer-review.
Given your SDK or library name, searches GitHub code search for public repos that import or require it, classifies each repo as company org, affiliated developer, solo developer, or tutorial noise, scores by adoption signal strength, detects new adopters by date, and outputs a ranked list of who is building on you with outreach context per high-signal company. Use when asked to find who uses your SDK, track SDK adoption, find companies building on your library, identify warm leads from existing SDK users, or see which orgs import your package. Trigger when a user says "who is using my SDK", "find repos that import my library", "track adoption of my package", "which companies are building on my SDK", "find my SDK users on GitHub", or "show me who imports my package".
Integrate Seam Access Grants for per-entrance, per-credential control over smart lock access. Create access grants specifying who gets access to which doors, when, and how (PIN code, mobile key, Instant Key). Use this skill when someone needs to control which access methods each guest or member gets, issue both PIN codes and mobile keys, manage access per-door (room + lobby + gym), or deliver Instant Key links. Works with August, Yale, Schlage, Kwikset, and other smart locks. Common use cases: hotel guest apps, gym/fitness access, office visitor management.
Use when hunting for exposed secrets and auditing how an app you own manages them — API keys, tokens, passwords, and private keys in source, git history, binaries, logs, config, and CI; plus vaulting, rotation, and least-privilege of the secrets themselves.
Secure an API by applying a policy from the catalog. Handles multiple starting points: from an existing API Manager instance, from an Exchange asset that needs an instance, or from scratch. Use when the user wants to secure an API, add rate limiting, apply OAuth2, enforce IP allowlisting, or protect any API with a policy — regardless of where they are in the setup process.
Audit mobile app source code for insecure data storage vulnerabilities per MASVS-STORAGE controls and MASTG tests. Use when reviewing how an app stores sensitive data locally, checks for data leakage, or assesses data-at-rest protection on Android or iOS.
Security audit orchestrator - parallel dependency, SAST and auth/config agents consolidated into an OWASP-mapped severity report, plus PHP 8, Twig and Craft CMS hardening references. Triggers on: security review, security audit, OWASP, XSS, SQL injection, CSRF, authentication, authorization, secrets management, input validation, vulnerability scan, dependency audit, composer audit, PHP security, Twig escaping, template injection, Craft CMS security, devMode, allowAnonymous, security key, DDEV. Use when auditing or hardening an app before release - e.g. 'security review this PR', 'is this Twig |raw safe?', 'audit our Craft config for production', 'does this controller need allowAnonymous?', 'triage composer audit output', 'diff DDEV against production PHP settings'.
Use when you want to security-test, pentest, audit, or find vulnerabilities in an application you own or are authorized to test — entry point that confirms authorization and routes to the right phase (threat model, code audit, active test, or hardening).
Design and build web pages and product screens at studio quality, not AI-template quality. Use for a new landing page, site, dashboard, pricing or app shell, a redesign or visual polish, a page made like a named site, and changes to screens in an existing app. Designs the brand's identity first, researches real leaders and studio work in Seenry MCP, builds on a token system with purposeful motion, and does not finish until the check script's slop board and a blind critic have reviewed the page. Native app screens go to seenry-apps, motion alone to seenry-motion, review alone to seenry-review.
Answer business questions about the org's RevOS data directly in chat by querying its live semantic model over MCP — "how many orders…", "revenue by…", "top N…", "trend over time…", "compare X to Y…" — and schema-discovery questions like "what's in my semantic model", "what can I query", "list cubes/datasets/fields", "describe a cube" — or when explicitly asked to "query the semantic model", "run a cube query", "show me a chart", "plot…", "graph…". Use this whenever you would otherwise call the RevOS api_read tool against the `cubes` resource directly — this skill is what turns its raw JSON into a rendered table, a chart when the shape fits, a safe choice of join path when a query spans multiple cubes, and a plain-English explanation, instead of a dumped tool result. This applies even when the question names a specific source system (HubSpot, Zammad, Exact Online, …) — answer aggregate/analytical questions from the semantic model, not a direct source connector.
Run a comprehensive SEO audit of the entire project, scanning all pages and components to produce a prioritized issue list and fix recommendations. Covers technical SEO, content SEO, E-E-A-T authority, content strategy, and performance. Provides a 0-100 SEO scoring system (6 dimensions). Supports both Chinese and English.
Settle disputes, resolve conflicts, mediate fights, negotiate agreements, run debates, and arbitrate disagreements between any parties — humans, AI agents, teams, roommates, co-founders, colleagues, or organizations. Use this skill whenever the user has a complaint, grievance, argument, or disagreement with ANYONE or ANYTHING — including with you (the AI agent), with another person, with a company, with a coworker, with a roommate, with a partner, or with another AI. Also use this when the user wants to debate a topic, argue for or against a position, do a mock trial, play devil's advocate, have a structured argument, or roleplay an opposing side. Also use this when parties need to establish shared rules, contracts, household agreements, team norms, community guidelines, or any kind of binding or non-binding consensus. Covers: conflict resolution, dispute resolution, arbitration, mediation, negotiation, litigation alternative, fair division, binding rulings, relationship conflicts, workplace disputes, collaborative agreement-making, structured debates, mock trials, devil's advocate exercises, and adversarial discussions.
Servd (servd.host) — Craft-specialised managed hosting for Craft CMS. Covers git push-to-deploy with the optional servd.yaml build config, local → staging → production environments with uni-directional Project Config sync, the servd/craft-asset-storage plugin (S3-backed Flysystem volumes on the svdcdn.com CDN, off-server image transforms, Imager-X/ImageOptimize integrations), Servd's static caching (full vs tag-based purge, {% dynamicInclude %}, CSRF injection, cache-busting) and running Blitz alongside it in reverse-proxy mode, MariaDB/MySQL databases over an SSH tunnel, automatic + manual backups, the Dedicated Queue Runner, environment variables and secrets, the ephemeral load-balanced filesystem (Redis + remote volumes for runtime files), plugin/feature constraints, and Servd-vs-Craft-Cloud differences.
Use when asked to audit, measure, or re-check how agent sessions are using the Bash tool — command chaining (&&, ;, |), cd into the session's own repo, head/tail truncation, sed -n/cat/heredoc instead of Read/Edit, git commit/push inside chains or behind git -C — or when deciding whether a permission prompt, an allowlist rule, a ~/.agents/AGENTS.md Bash rule, or the permission mode (acceptEdits vs auto) needs changing and wants evidence from real transcripts rather than a hunch. Runs a stdlib script over ~/.claude/projects/*.jsonl, prints per-model and per-session rates plus samples, and carries the dated research that explains why each pattern happens and where the fix belongs. Also the place to record a newly noticed Bash anti-pattern so the next audit measures it.
When the user wants to solve set covering problems, determine minimum coverage sets, or optimize facility coverage. Also use when the user mentions "set cover," "minimum set cover," "coverage optimization," "facility coverage problem," "service coverage," "location set covering," "maximal covering location problem," or "covering design." For general facility location, see facility-location-problem. For specific applications, see warehouse-location-optimization or hub-location-problem.
在專案中建立並維護 Zeabur 部署規範，會在專案根目錄的 AGENTS.md 寫入一段部署約束（Zeabur 只支援 Dockerfile、不支援 docker-compose；compose 僅供本地開發測試）。僅在使用者明確指定專案要部署到 Zeabur 時才使用 — 例如使用者明說「這個專案要部署到 Zeabur」「要上 Zeabur」「設定 Zeabur 部署」，或直接呼叫此 skill。不要在僅僅提到 Docker、寫 Dockerfile、討論部署平台、或泛泛談到 Zeabur 時觸發；必須有明確的「部署到 Zeabur」意圖。This skill MUST be used only when the user explicitly states the project deploys to Zeabur, and MUST NOT be triggered by Docker usage, Dockerfile work, or general deployment talk.
View and configure settings for coding agents (Claude Code, Codex CLI, OpenCode, Devin CLI/Desktop, and others). Covers JSON settings for Claude Code and Devin, TOML for Codex CLI, and JSON/JSONC for OpenCode, including permissions, sandbox, model selection, profiles, feature flags, providers, hooks, subagents, and skills.
Set up git guardrails that make coding agents ask or stop before commands that lose work or rewrite shared history, at a guard level the user picks, for whichever agent harnesses they use. Use when the user wants to guard against destructive git operations by coding agents.
Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.
SHARK v3.0 — SM Conviction + Liquidation Cascade Hunter. Consolidated from v1.0's 8-cron pipeline into a single scanner. 4-gate entry: SM concentration (30+ traders, 5%+) → top 5 trader alignment → price momentum → funding structure. Score 8+ to enter. DSL manages all exits. No thesis exit. DSL exit managed by plugin runtime via runtime.yaml.
Load this skill before shipping a UI change, to statically review the diff for design-craft regressions (accessibility, motion, responsive, and visual or UX drift), correctness and security issues, exposed secrets or credentials, and leftover commented-out code, then write a commit message and pull request description that match the repository's conventions, and offer to commit and push. Triggers on "ship this", "review this", "ready to ship". This is the ship gate at the end of the design → build → ship pipeline.
Scaffold and formally review a new Agent Skill in this marketplace repo. Covers valid SKILL.md generation, directory layout, registry entries, and spec auditing. Use when adding a skill, validating frontmatter, or checking marketplace readiness before a PR.
Build correct, consistent Agent Skills for any compatible agent product. Use when creating, updating, renaming, deleting, or validating a skill, or when improving skill descriptions, structure, safety rules, progressive disclosure, or trigger reliability.
Create new Claude Code Skills with proper YAML frontmatter, progressive disclosure structure, and complete directory organization. Use when you need to build custom skills for specific workflows, generate skill templates, or understand the Claude Skills specification.
Improves Agent Skills via validate → rule-based eval cases → plugin-eval → prompt evals → bounded edits with held-out gates. Use when tuning skill quality, routing, or adopting Chrome/Microsoft T-named quality gates—not for bulk validate-only or SkillOpt automation.
Requires durable citations when authoring or researching Agent Skills—maintain references/sources.md per skill, link external research, and record provenance in PRs. Use when creating skills, updating SKILL.md, doing web research for skills, or auditing missing sources.
Tmux execution support for long-running and persistent commands. Load this skill when you need to: (1) run commands expected to exceed tool timeout (over 60s), (2) start persistent servers or dev processes, (3) run TUI/interactive applications, (4) execute parallel isolated tasks in separate sessions, (5) run remote commands over SSH that must survive disconnection, (6) handle tmux errors like 'capture-pane blocked in interactive_bash'. Trigger phrases: 'run in background', 'start server', 'long-running', 'tmux session', 'keep running', 'persistent process', 'dev server', 'training script', 'git clone large repo', 'docker build', 'capture-pane blocked'.
Administrative workflows for the agent-skills repository. Use when the user wants to contribute a skill, open a pull request, or update an already-installed skill to the latest version. Trigger when users say: "open a PR", "submit my changes", "push this skill", "update my skills", "update the skills repo", or "how do I contribute a skill".
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.