review-plugin-submission

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Review plugin submission

插件提交审核

Trigger

触发场景

A plugin is implemented and needs a final quality check before submission or release.
插件已开发完成,在提交或发布前需要进行最终质量检查。

Workflow

工作流程

  1. Verify manifest validity:
    • .cursor-plugin/plugin.json
      exists
    • name
      is valid lowercase kebab-case
    • metadata fields are coherent (
      description
      ,
      version
      ,
      author
      ,
      license
      )
  2. Verify component discoverability:
    • Skills in
      skills/*/SKILL.md
    • Rules in
      rules/
      as
      .mdc
      or markdown variants
    • Agents in
      agents/
      markdown files
    • Commands in
      commands/
      markdown or text files
    • Hooks in
      hooks/hooks.json
    • MCP config in
      mcp.json
      (or
      mcpServers
      override)
  3. Verify component metadata:
    • Skills include
      name
      and
      description
      frontmatter
    • Rules include valid frontmatter and clear guidance
    • Agents and commands include
      name
      and
      description
  4. Verify repository integration:
    • For marketplace repos, plugin entry exists in
      .cursor-plugin/marketplace.json
    • source
      resolves to plugin directory and names are unique
  5. Verify documentation quality:
    • README.md
      states purpose, installation, and component coverage
    • optional logo path is valid and repository-hosted
  1. 验证清单有效性:
    • .cursor-plugin/plugin.json
      文件存在
    • name
      为有效的小写短横线命名格式(kebab-case)
    • 元数据字段(
      description
      、
      version
      、
      author
      、
      license
      )内容连贯合理
  2. 验证组件可发现性:
    • 技能文件位于
      skills/*/SKILL.md
    • 规则文件位于
      rules/
      目录,格式为
      .mdc
      或 Markdown 变体
    • Agent 文件位于
      agents/
      目录,为 Markdown 文件
    • 命令文件位于
      commands/
      目录,为 Markdown 或文本文件
    • 钩子配置位于
      hooks/hooks.json
    • MCP 配置位于
      mcp.json
      (或通过
      mcpServers
      覆盖)
  3. 验证组件元数据:
    • 技能文件包含
      name
      和
      description
      前置元数据
    • 规则文件包含有效的前置元数据和清晰的指引
    • Agent 和命令文件包含
      name
      和
      description
  4. 验证仓库集成:
    • 对于市场仓库,
      .cursor-plugin/marketplace.json
      中存在插件条目
    • source
      指向插件目录且名称唯一
  5. 验证文档质量:
    • README.md
      说明插件用途、安装方法及组件覆盖范围
    • 可选的 Logo 路径有效且托管在仓库内

Checklist

检查清单

  • Manifest exists and parses as valid JSON
  • All declared paths exist and are relative
  • No broken file references
  • No missing frontmatter on skills/rules/agents/commands
  • Plugin scope is clear and focused
  • Marketplace registration complete (if multi-plugin repo)
  • 清单文件存在且可解析为有效的 JSON
  • 所有声明的路径均存在且为相对路径
  • 无损坏的文件引用
  • 技能/规则/Agent/命令文件无缺失的前置元数据
  • 插件范围清晰且聚焦
  • 市场注册完成(若为多插件仓库)

Output

输出

  • Pass/fail report by section
  • Prioritized fix list
  • Final submission recommendation
  • 按模块划分的通过/失败报告
  • 优先级排序的修复列表
  • 最终提交建议