Skills
101,174 packaged capabilities and playbooks for agents. Install any of them with one command.
All
Query BingX spot market data including ticker prices, order book depth, recent trades, klines/candlesticks, and trading symbol info. Use when the user asks about BingX spot prices, order books, candlestick charts, recent trades, or spot market statistics.
Filing gate for ALL brain writes. Consulted before creating any new brain page to determine the correct path. Reads the ACTIVE schema pack via `gbrain schema show --json` — no hardcoded directory table. Also runs periodic taxonomy drift detection via `gbrain schema review-orphans`.
Pre-implementation exploration: deep interview, approach comparison, design doc. Use when exploring a vague feature idea, clarifying ambiguous requirements, or comparing approaches before coding. For the full workflow, use the ia-brainstorm command (Claude Code)
Expert assistant for BuilderBot (v1.4.0) — a TypeScript/JavaScript framework for building multi-platform chatbots (WhatsApp, Telegram, Instagram, Email, etc.). Use when creating or editing flows (addKeyword, addAnswer, addAction), wiring EVENTS, managing per-user state or globalState, configuring providers (Baileys, Meta, Telegram, Evolution, etc.) or databases (Mongo, Postgres, MySQL, JSON), implementing REST API endpoints (handleCtx, httpServer), debugging flow control (gotoFlow, endFlow, fallBack, idle, capture, flowDynamic), or handling blacklist logic. Architecture: Provider + Database + Flow.
Builds AI agents on Cloudflare using the Agents SDK with state management, real-time WebSockets, scheduled tasks, tool integration, and chat capabilities. Generates production-ready agent code deployed to Workers. Use when: user wants to "build an agent", "AI agent", "chat agent", "stateful agent", mentions "Agents SDK", needs "real-time AI", "WebSocket AI", or asks about agent "state management", "scheduled tasks", or "tool calling". Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
Implement a vulnerability aging dashboard and SLA tracking system that measures time-to-remediation against severity-based deadlines (e.g. 14 days critical, 30 days high, 60 days medium, 90 days low), with automated escalations and compliance metrics reporting. Use when designing SLA policies, building aging/remediation dashboards, or proving compliance with remediation timelines.
dontbesilent personal decision system. Turn any domain that requires long-term tracking (business, relationships, health, career, learning, investing…) into a local knowledge project: a four-layer structure, source tags, immutable snapshots, and a concept library that can distill patterns. Triggers: /dbs-decision, /决策系统, /决策立案, /结果回填, /状态画像
dontbesilent business model diagnosis. Two modes: consultation (dissolve your question) and checkup (analyze your business model). Triggers: /dbs-diagnosis, /问诊, “help me review my business model”, “diagnose my business”, “I have a business question”
dontbesilent goal clarification. Uses Wittgenstein’s philosophy of language to audit fuzzy goals into checkable deliverables. Triggers: /dbs-goal, /目标, “help me clarify my goal”, “I want to build a personal brand”, “my goal is to become…”, “I want to become more…”
dontbesilent good-question generator. Turns fuzzy problems into briefs that an Agent can reason about, critique, and verify, and assesses how much of the problem can be solved automatically. Triggers: /dbs-good-question, /好问题, /问题说明书, /Agent可解性, “can this problem be solved automatically”, “help me clarify the problem”
Communication psychology decoder. Given a piece of content, uses five classic communication theories to explain why it resonates with an audience, analyze the audience’s underlying emotions and effective stance, and suggest discussion directions for a chatroom. Triggers: /dbs-spread, “communication psychology decoder”, “why does this go viral”, “what does the audience want to hear”, “what emotion does this content hit”
Structured approach to workplace conflicts, performance discussions, and challenging feedback using preparation-delivery-followup framework. Use when preparing for tough conversations, addressing conflicts, giving critical feedback, or navigating sensitive workplace discussions.
Lightweight shared entry point for the DingTalk MultiSkill. Use when the user refers generically to DWS/DingTalk operations without naming a product, requests cross-product orchestration, needs URL type pre-checks, or requires disambiguation of product boundaries. Clear single-product operations should prefer the corresponding dingtalk-* sub-skill; this skill only provides the global execution contract and on-demand reference navigation, not the full set of product commands.
Manages project directory setup and artifact organization. Use when starting a new project, resuming an existing one, or when a PLAN.md needs to be associated with a project directory. Creates the project folder structure (specs/, scripts/, notebooks/, manifests/, agent_memory/) and resolves project naming.
End-to-end orchestration for non-trivial software feature development. Use this skill whenever the user asks to implement a PR-sized feature, break down a plan, have subagents review a plan, run a plan-review-development-acceptance loop, coordinate multiple review perspectives, produce an acceptance report, or generate an HTML PR summary. Prefer this skill for multi-step code changes even if the user only says "build this feature" and the task is not a tiny one-file edit.
Install and wire registry blocks and components into FrameVideo compositions. Use when running framevideo add, installing a block or component, wiring an installed item into index.html, or working with framevideo.json. Covers the add command, install locations, block sub-composition wiring, component snippet merging, and registry discovery.
Review design specification documents for Go programs before implementation begins. Use this skill when a user has a Go spec, design doc, RFC, or PRD to review, wants feedback on a planned feature in a Go codebase, is about to start implementing from a spec, or asks “is this spec ready?” or “review this before I build it”. Applies Go philosophy—simplicity, composition, explicit errors, context propagation—plus Cobra/Viper CLI conventions where applicable.
In-depth competitor scanning and research into evidence of early paying customers; delivers industry profile hypotheses and actionable requirement handoffs. Batch-scrapes competitors’ landing pages (title/h1/intro/pricing), pricing pages, top 10 blog posts, and change history (Wayback). Powered by actionbook (30 concurrent tabs + 90% token savings). Invoke when the user says “analyze competitors,” “see what competitors are doing,” “find benchmarks,” or “scan the top 10.”
Ask about and record decisions on substantive unresolved user choices in plans, product specifications, design, technical solutions, implementation, or release. Applies to scope, priorities, trade-offs, risks, acceptance, dependencies, visual direction, or release authorization that cannot be resolved from code, configuration, authoritative artifacts, or deterministic execution. It is not triggered automatically by a new phase or module.
GSAP animation reference for FrameVideo. Covers gsap.to(), from(), fromTo(), easing, stagger, defaults, timelines (gsap.timeline(), position parameter, labels, nesting, playback), and performance (transforms, will-change, quickTo). Use when writing GSAP animations in FrameVideo compositions.
Dark-terminal honest-review deck — #0a0c10 black background + 56px cyber grid + CRT vignette + scanlines, window traffic-light chrome, `$ prompt` command-line title, mint-green #7ed3a4 headlines, JetBrains Mono, stroke-only bar charts, blinking cursor, amber/green/red tier tags, dark code blocks. For CLI / agent / dev tool reviews (including trace, diff, benchmark).
Huawei Cloud SWR (Software Repository for Container) image governance skill using hcloud CLI. Use when the user wants to: (1) manage SWR namespace permissions—grant/query/modify/revoke; (2) manage repository permissions—grant/query/modify/revoke; (3) manage image retention rules—create/list/update/delete; (4) manage shared download domains—create/list/update/delete; (5) manage image sharing—list shared repos/query feature gates; (6) check SWR agency status and create agency delegation; (7) list repo accessories and references. Trigger: user mentions “SWR image governance,” “SWR 镜像治理,” “SWR 权限管理,” “SWR retention,” “SWR 保留策略,” “SWR 共享域名,” “SWR 共享镜像,” “SWR 委托,” “SWR agency,” “namespace permissions,” “repository permissions,” “镜像权限,” “保留规则,” “共享下载,” or “镜像分享.”
Guide to building static websites with the Hugo static site generator: blogs, documentation sites, landing pages and portfolios. Covers scaffolding new sites, choosing Hugo Extended over Standard, hugo.yaml and hugo.toml configuration, themes such as PaperMod via Git submodules or Hugo Modules, Go templates and Goldmark, Tailwind CSS v4 through Hugo Pipes and PostCSS, headless CMS integration with Sveltia CMS or TinaCMS, multilingual sites, GitHub Actions CI/CD, and deployment to Cloudflare Workers Static Assets or Pages with wrangler. Documents 15 pitfalls: Hugo version mismatch, baseURL errors, theme not found, YAML versus TOML frontmatter, and date-related build failures. Use when creating, styling, adding a CMS to, deploying or troubleshooting a Hugo site.
This skill should be used when writing, enhancing, or evaluating the launch prompt for a long-running autonomous agent or a parallel multi-agent orchestration attacking a hard problem: pseudo-formal task briefs that define terms and an exact success predicate linguistically, enumerate non-counting outcomes, set persistence rules with explicit stop and return conditions and effort floors, manage a diverse portfolio of parallel approaches with an approach registry and blocked-route bookkeeping, and gate the return on adversarial audit. Route agent topology and coordination protocols to multi-agent-patterns, runtime control surfaces and loop governance to harness-engineering, evaluator and quality-gate construction to evaluation, judge design to advanced-evaluation, and compaction or memory mechanics to context-compression and memory-systems.
Review MATLAB code for quality, performance, maintainability, and adherence to MathWorks coding standards. Uses check_matlab_code and matlab_coding_guidelines. Use when reviewing code, checking style, finding code smells, assessing quality, or preparing code for handoff or publication.
(NS) Gated PM: clarify, RICE/WSJF, sprint, PERT/Monte Carlo; PRD (product discovery doc); product/project roadmap (multi-version); version handoff; release delivery report for leadership (relatório de entrega da versão, deploy report para diretoria, o que vai para produção); risk/status/OKR; orçamento, Function Points, proposta comercial, preço do ponto de função, quanto custa o PF; cronograma P100/P85/P50. Use on transcripts, backlog, timeline, delivery date, status, roadmap, roadmap do projeto, roadmap de produto, PRD, product requirements document, documento de requisitos de produto, versões entregues/planejadas, orçamento, cotação, cronograma, handoff, fecha a versão, valor do PF, não sei o preço do ponto de função, dúvidas do dev, perguntas da equipe sobre o PRD — even if PM unnamed. Do NOT use for coding, SDD requirements.md, GitLab issue execution, or `/ns-requirements-enricher`.
Creates an ALM (Application Lifecycle Management) plan for deploying a Power Pages site across environments. Gathers your promotion strategy, target environments, and approval requirements upfront, then generates a visual HTML plan document for your review and approval. **plan-alm does not deploy anything itself** — it is a planner. After you approve the plan, run the individual ALM skills (setup-solution, setup-pipeline, deploy-pipeline, or export-solution/import-solution); each detects the approved plan and executes the right step in order, keeping the plan updated as it runs. Use when asked to: "plan my alm", "set up alm", "create deployment plan", "plan my deployments", "help me deploy to multiple environments", "set up promotion strategy", "create cicd plan", "plan site promotion", "help me go to production", "set up pipeline for my site".
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.