content-marketing
撰写能转化并优化排名的博客、简报、案例与社媒文案。
▸ 推荐理由结合经典与现代分发策略，适合增长与品牌团队使用。
全部收录
相关性达标的全量 Skills（含未精选长尾）· 共 5090 个
comprehensive-review
使用并行子代理从架构到安全进行全面的代码审查并合并结果。
▸ 推荐理由覆盖多维度审查并能直接对 PR 发表评论，适合关键变更审查。
▸ 风险提示会访问仓库并可能发表评论，需提供访问令牌
component-forge
为 React/Vue/Svelte 生成生产级组件模板，涵盖所有状态与无障碍。
▸ 推荐理由包含脚手架与范式，减少重复工作并兼顾 RSC 与 WCAG 要求。
communication
起草专业邮件、反馈、会议记录与跨文化沟通模板。
▸ 推荐理由提供语气矩阵与多场景模板，适合职场日常沟通需求。
code-review
对 diff 或提交进行正确性、安全性与可维护性的详尽审查。
▸ 推荐理由支持粘贴 diff 或从 commit 提取，便于自动化与人工复审结合。
ci-cd
为 GitHub Actions/GitLab CI/CircleCI 设计高效安全的 CI/CD 流水线。
▸ 推荐理由覆盖矩阵构建、缓存与自动回滚等企业级实践，适合生产环境。
▸ 风险提示可能需要仓库与部署权限及凭据才能完整运行
chromadb
Manage the ChromaDB vector database that stores the ecosystem's persistent memory. Use when user asks to check memory storage, backup memory, search stored entries, delete entries, or reset the vector database. Do NOT use for general question answering about past sessions (use the memory skill for that).
business-proposals
生成销售外联、提案书、SOW、投融资演示文稿与 RFP 回复模板。
▸ 推荐理由快速产出标准化商务文档，提升商务沟通与获客效率。
brand-design
生成品牌识别、设计系统与设计代币，并产出创意方向与设计简报。
▸ 推荐理由流程化产出品牌与设计系统文档，便于跨团队执行与落地。
auth-architect
按 OWASP/NIST 标准实现生产级认证与授权（OAuth/OIDC、WebAuthn、会话、RBAC）。
▸ 推荐理由覆盖现代认证场景与合规要点，适合构建安全登录/权限体系的团队。
▸ 风险提示安全相关建议需专业审计，示例不可盲目直接投入生产
api-forge
根据需求设计 REST/GraphQL 接口，并生成符合 OpenAPI 3.1 的规范与最佳实践。
▸ 推荐理由基于成熟产品模式生成可交付的 API 规范，利于开发与文档对齐。
agent-tools
通过 inference.sh CLI 在云端运行多种 AI 应用与模型（图像、视频、LLM 等）。
▸ 推荐理由一键接入上百种模型与应用，适合需要多模型快速试验的工程/产品团队。
▸ 风险提示安装示例使用 curl | sh 拉取外部脚本，存在安全与信任链风险
agent-browser
为 AI agent 提供浏览器自动化能力：导航、填表、点击、截图与数据提取。
▸ 推荐理由把繁琐的网页交互交给 agent 自动完成，适合测试与数据抓取场景。
▸ 风险提示会自动访问并操作外部网站，可能需要凭证且有滥用或隐私风险
Aesthetic Web Design
按专业UI/UX规范为网页、界面或组件提供美学设计指导与方案。
▸ 推荐理由系统化区分品牌与产品设计，适合需要高辨识度界面的场景。
story
网文工具箱路由入口，根据意图分发到具体技能
▸ 推荐理由方便模糊需求自动匹配技能，提升交互体验
story-short-write
从构思到成稿生成短篇小说，侧重情绪与节奏
▸ 推荐理由适合短篇创作者快速产出与迭代
▸ 风险提示可能生成具争议性情节，注意合规与审查
story-short-scan
扫榜分析短篇网文趋势并给出题材与情绪方向
▸ 推荐理由快速发现短篇风口，便于选题与验证
▸ 风险提示可能依赖第三方平台数据，需注意采集合规
story-short-analyze
对短篇网文进行结构化拆解，输出拆文报告与元数据
▸ 推荐理由适合作者和编辑快速复用爆款结构
▸ 风险提示可能涉及版权内容处理，须确保拥有使用权
story-setup
在项目目录部署写作工具集的 hooks、rules、agents 与配置文件。
▸ 推荐理由一键搭建写作工程基础设施，合并配置且避免覆盖用户已有文件。
▸ 风险提示会在项目目录写入配置并可能执行脚本或拉取远程资源，需备份并确认来源可信。
story-review
以多视角并行或单独模式审查小说并给出可执行修改建议。
▸ 推荐理由支持 full/lean 模式并能自动降级，适合编辑把关与质量审查流程。
▸ 风险提示审查过程可能并行 spawn 多个子代理并调用外部模型，注意权限与数据流向。
story-long-write
从选题、大纲到正文全流程辅助长篇网文创作与情节管理。
▸ 推荐理由覆盖日更、续写与章节管理，适合系统写长篇的作者团队。
▸ 风险提示会调用子代理与外部模型，需配置 API Key 并注意数据外发权限。
story-long-scan
分析起点、番茄等平台排行榜，提炼热门题材与市场信号。
▸ 推荐理由快速把握多平台题材趋势，辅助选题与运营决策。
▸ 风险提示可能需抓取第三方榜单或调用平台 API，存在合规与速率限制风险。
story-long-analyze
深度拆解长篇小说的黄金三章、人设、爽点与节奏控制。
▸ 推荐理由系统还原爆款结构，适合想模仿与学习作品构造的作者。
▸ 风险提示可能分析受版权保护的作品，使用时需注意版权合规。
story-import
把已有小说文本解析为标准写作项目目录与续写资产。
▸ 推荐理由把散乱文本变为可接入写作流水线的工程，便于续写与管理。
▸ 风险提示处理用户文件并可能调用外部 Agent，注意隐私与权限控制。
story-deslop
将过于AI化的网文改写为更自然、口语化且不模板化的文本。
▸ 推荐理由针对网文常见的AI化问题，保留剧情同时增强生活化语感。
story-cover
根据书名与题材风格生成带书名与署名的网文封面图。
▸ 推荐理由自动产出可发布的带字封面，适合作者快速出图与封面迭代。
▸ 风险提示需配置外部图像 API Key，可能将封面文本或素材发送到第三方服务。
browser-cdp
通过 Chrome DevTools Protocol 控制本地 Chrome，执行自动化与登录复用。
▸ 推荐理由适合需要复用真实浏览器会话或执行 JS 的自动化任务。
▸ 风险提示首次启动会终止用户 Chrome 进程，需征得许可并有本地高权限。
project-canon
Maintain a project's canonical truth across long-running AI collaboration. Discover authoritative project documents, identify the current valid plan, audit conflicts and duplicates, absorb external materials through Preview and confirmation, route decisions and changes to the right files, separate design acceptance from implementation and verification, archive processed sources safely, and resume after context loss. Use when users ask which plan is current, want to take over or organize project docs, update current/decisions/changes/delivery/evidence, reconcile docs with code, archive reviewed materials, or continue without re-deciding settled issues. Do not use for generic Markdown formatting or one-time mass document summarization.
ai-application-design-review
Pre-implementation kill-criteria review for AI apps, Agents, or Workflows. Finds at most two blocking failure modes and designs one falsifiable minimal experiment. When multiple independent blockers compete, applies conditional decision-priority scoring and experiment-coverage declarations. Use when the user invokes /ai-application-design-review, or asks for design-stage blocking-risk / kill-criteria review before building. Do not use for code review, runtime debugging, UI taste, pure brainstorming, model-picker advice alone, or full system redesign.
pre-commit-review
在提交前对未暂存的 git diff 启动多位专责审查代理，汇总问题提示开发者修正。
▸ 推荐理由把多种审查器并行运行在本地 diff 上，能在提交前一次性发现质量与覆盖问题。
▸ 风险提示需要读取仓库代码并可能执行本地分析脚本，注意本地执行风险与敏感代码暴露。
ctxinit
Initialize a project's engineering foundation and knowledge hub, and manage its Architecture Decision Records (ADRs). Use whenever the user types /ctxinit, or asks to bootstrap/scaffold a new project's structure, set up a context/ knowledge folder, engineering rules, or security rules. /ctxinit interviews the user about the project's surfaces (admin panel, portal, landing, mobile app, API), then generates a complete context/ hub — rules, docs, plans, decisions (ADR), technical-debt registry, map — plus thin agent entry-point files (CLAUDE.md, AGENTS.md, .cursor stubs) that REFERENCE context/ instead of copying it. /ctxinit --sync (re)generates context/map.md and the component-reuse registry by scanning the current codebase — also use --sync when the user says "update the map", "sync the context", or "list the components". Once a project has a context/decisions/ log, this skill also RECORDS, QUERIES, and SUPERSEDES its ADRs — trigger on "record this decision", "why did we decide X", "di
ratemyharness
Use this skill to rate, audit, red-team, or release-gate a concrete AI agent harness, runtime, orchestrator, runner, repository, deployment, trace set, or configuration. Use for loop correctness, tool dispatch and result correlation, context and memory isolation, permissions and sandboxing, approvals, retry and idempotency, timeouts, cancellation, budgets, termination, observability, cost, recovery, author defense, and same-rubric re-reviews. Trigger for wording such as rate my harness, audit this agent runtime, review my agent loop, red-team this orchestrator, is this agent production ready, harness 上线前挑刺, 给 agent harness 打分, or 这个智能体运行时能上线吗. Require an actual harness artifact or runtime evidence, including one in the current workspace. Do not use for generic agent architecture advice, ordinary code review, reviewing a standalone Skill or prompt, validating only a plugin manifest, debugging one model response, or evaluating a model without its runtime.
ratemyharness
Use this skill to rate, audit, red-team, or release-gate a concrete AI agent harness, runtime, orchestrator, runner, repository, deployment, trace set, or configuration. Use for loop correctness, tool dispatch and result correlation, context and memory isolation, permissions and sandboxing, approvals, retry and idempotency, timeouts, cancellation, budgets, termination, observability, cost, recovery, author defense, and same-rubric re-reviews. Trigger for wording such as rate my harness, audit this agent runtime, review my agent loop, red-team this orchestrator, is this agent production ready, harness 上线前挑刺, 给 agent harness 打分, or 这个智能体运行时能上线吗. Require an actual harness artifact or runtime evidence, including one in the current workspace. Do not use for generic agent architecture advice, ordinary code review, reviewing a standalone Skill or prompt, validating only a plugin manifest, debugging one model response, or evaluating a model without its runtime.
write-mermaid
Write mermaid diagrams that actually render on the target platform. Covers all 31 diagram types in mermaid 11.16.0 — flowchart, sequence, class, state, ER, gantt, gitGraph, C4, architecture, mindmap, and the long tail — with per-diagram syntax, node shapes, and worked examples. Use when writing or fixing any ```mermaid block, choosing which diagram type fits, debugging a diagram that renders as a broken box on GitHub, or deciding whether a diagram type is supported by the renderer you are targeting.
write-agent-skill
Extracts user workflows into self-contained agent skills by interviewing for intent and edge cases, designing modular packages with progressive disclosure (lean SKILL.md body, on-demand references/), writing step-by-step instructions with gotchas and validation loops, structuring directory trees (references/, assets/, scripts/), and enforcing the full spec checklist before deployment. Use whenever the user asks to create a new agent skill, extract expertise into a skill package, build a reusable workflow, audit an existing skill for compliance, or convert rough notes into a structured SKILL.md.
write-agent-card
Writes and audits A2A-compliant agent-card.json files: the machine-readable discovery metadata that lets other agents find, route to, and invoke an agent's skills. Covers all required and optional JSON fields, skill declaration quality (description, examples, tags), capability flags, security schemes, and alignment between the card and the agent's runtime SKILL.md. Use when creating a new agent, auditing an existing agent-card.json, or adding/modifying skills declared in a card.
review-code
The repeatable process for reviewing a code change: understand the change's intent before critiquing, read the diff AND the surrounding code, verify the change's claims and tests rather than trusting them, categorize each finding by severity, and structure the written review. Load whenever the task is to review a pull request, diff, branch, or proposed code change - before you start reading the diff.
research-git-repos
How to research a git repository's code, structure, or conventions: clone it shallowly and read it locally with your filesystem tools instead of fetching github.com pages over the web. Load when a task involves understanding a codebase, a repo's layout, its conventions, how a feature is implemented, or anything answerable from the repository's own files.
pr-authoring
How to write a pull request - a title and a description that tell the reviewer what changed, why, and how to verify it, scaled to the size of the change. Use when composing a PR for delivery.
format-markdown
Reformats a Markdown document for clean visual rendering - consistent whitespace, heading hierarchy, scannability, and formatting consistency. Preserves all content and links exactly. Use before returning any Markdown document to the user, or when asked to clean up, format, or tidy Markdown output.