菜单
Use when reviewing a plugin for the rosetta catalog or registering it in marketplace.json — the quality bar the validator can't fully check, the required manifest/component fields, and how category metadata works. Apply during contribution review or before merging a new plugin.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when designing memory or persistent context for an agent — deciding what to persist vs. recompute, how to retrieve only what's relevant, and how to summarize/compact history to fit the context window. Use when an agent forgets, bloats its context, or repeats work.
Interactive installer for Rosetta. Guides users through selecting and installing skills and language-specific rules at user-level or project-level, verifies paths, and optionally optimizes installed files.
Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills, commands, and agents.
Use when building or reviewing an evaluation for an LLM feature — assembling a representative test set, choosing pass criteria (exact match, programmatic checks, rubric, or LLM-as-judge), and catching regressions. Use when asking "how do I know this prompt or model change is better?"
Use when writing or reviewing a prompt for an LLM — making it specific, structured, and testable (clear task, role/context, examples, an explicit output contract, decomposition, room to reason) and avoiding the anti-patterns that make prompts brittle. Provider-agnostic.
Pattern for progressively refining context retrieval to solve the subagent context problem.
| name | catalog-quality-bar |
| description | Use when reviewing a plugin for the rosetta catalog or registering it in marketplace.json — the quality bar the validator can't fully check, the required manifest/component fields, and how category metadata works. Apply during contribution review or before merging a new plugin. |
The catalog earns trust by curation, not volume. The validator checks structure; this skill covers the judgment a reviewer brings on top.
plugin.json: name (kebab-case), description, SemVer version, author.name, license;
keywords recommended.README.md is present.name + description; commands have description.CLAUDE_PLUGIN_ROOT variable instead).marketplace.json category is one of the names in catalog/categories.json.name/version agree between plugin.json and the marketplace.json entry; names are unique.allowed-tools / tools should be the minimum the component needs.marketplace.jsonAdd an entry with name, source (e.g. ./plugins/<name>), description, a category from
the taxonomy, and version (matching plugin.json). Category is catalog-side metadata — it
lives here, not in plugin.json. Then run the validator and fix every error before merging.