[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79P4MJ1WYNSC2P78690298E":3,"skill-same:01M79P4MJ1WYNSC2P78690298E":92},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":13,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":41,"install":42,"resources":55},"01M79P4MJ1WYNSC2P78690298E","marketplace-development",null,"Converts a Claude Code skills repository (skills\u002F directories with SKILL.md files, no individual plugin.json per skill) into an official plugin marketplace — generates spec-conforming .claude-plugin\u002Fmarketplace.json, validates with `claude plugin validate`, tests real installation, and PRs the upstream repo, encoding hard-won schema\u002Fversion\u002Fdescription anti-patterns. Use when the user mentions marketplace.json, one-click install, auto-update, plugin distribution for a skills collection, or wants a skills repo installable via `claude plugin install`. For plugins that already have plugin.json, plugin-development handles marketplace publishing.","AndreHahm\u002Fandres-cc-marketplace","AndreHahm","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F80748019?v=4","01M79N2VZJT9MAJ7K695C9VXQ4","01M79N2W06PFX8BSCQ592M8K8K",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FAndreHahm\u002Fandres-cc-marketplace\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fmarketplace-development\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: marketplace-development\ndescription: >-\n  Converts a Claude Code skills repository (skills\u002F directories with SKILL.md files,\n  no individual plugin.json per skill) into an official plugin marketplace —\n  generates spec-conforming .claude-plugin\u002Fmarketplace.json, validates with\n  `claude plugin validate`, tests real installation, and PRs the upstream repo,\n  encoding hard-won schema\u002Fversion\u002Fdescription anti-patterns. Use when the user\n  mentions marketplace.json, one-click install, auto-update, plugin distribution\n  for a skills collection, or wants a skills repo installable via `claude plugin install`.\n  For plugins that already have plugin.json, plugin-development handles marketplace publishing.\nallowed-tools: Read Write Glob Bash(scripts\u002Fcheck_marketplace.sh:*) Bash(jq:*) Bash(python3:*) Bash(find:*) Bash(claude:*) Bash(git:*)\n# R19 exception (see .claude\u002Fmarketplace-sync.json's divergence_exceptions): the command paths below\n# intentionally differ from the plugin-devkit canonical copy of this file. This .claude\u002F mirror copy\n# is never distributed -- it exists only for in-repo dogfooding before packaging -- so it uses\n# ${CLAUDE_PROJECT_DIR} with this repo's own path, which reliably resolves here. The canonical\n# plugins\u002Fplugin-devkit\u002F copy is the one distributed via the marketplace and installed into other\n# users' own projects, where ${CLAUDE_PROJECT_DIR} would resolve to *their* project root, not this\n# repo -- so it uses ${CLAUDE_PLUGIN_ROOT} instead (tracks wherever the plugin is actually installed).\nhooks:\n  PostToolUse:\n    - matcher: \"Write|Edit\"\n      hooks:\n        - type: command\n          command: \"${CLAUDE_PROJECT_DIR}\u002F.claude\u002Fskills\u002Fmarketplace-development\u002Fhooks\u002Fpost_edit_validate.sh\"\n          timeout: 30\n        - type: command\n          command: \"${CLAUDE_PROJECT_DIR}\u002F.claude\u002Fskills\u002Fmarketplace-development\u002Fhooks\u002Fpost_edit_sync_check.sh\"\n          timeout: 10\n---\n\n# marketplace-development\n\nConvert a Claude Code skills repository into an official plugin marketplace so users\ncan install skills via `claude plugin marketplace add` and get auto-updates.\n\n**Input**: a repo with `skills\u002F` directories containing SKILL.md files.\n**Output**: `.claude-plugin\u002Fmarketplace.json` + validated + installation-tested + PR-ready.\n\n## Quick Start\n\n1. **Check existing marketplace** — run `bash scripts\u002Fcheck_marketplace.sh`; if `RESULT: PASSED`, jump to Phase 4 (PR) or stop\n2. **New marketplace** — Phases 1 → 2 → 3 → 4 in order\n3. **Adding skills to existing marketplace** — see \"Maintaining an existing marketplace\" below → Phase 3 → Phase 4\n4. **Debugging `claude plugin validate` failures** — see `references\u002Fdebugging-guide.md` for session history mining\n5. **Schema field reference** — `references\u002Fmarketplace-schema.md`; for `source`\u002F`skills` path pitfalls — `references\u002Fcache-and-source-patterns.md`\n\n## When to Use\n\n- Creating `.claude-plugin\u002Fmarketplace.json` for a skills repository\n- Adding new skills to an existing marketplace catalog\n- Bumping plugin versions after SKILL.md content changes\n- Debugging `claude plugin validate` or install failures\n- Preparing a PR for a skills repo to support `claude plugin install` distribution\n\n## When NOT to Use\n\n- For plugins with an existing `plugin.json` — use `plugin-development` instead\n- For local-only skills not intended for distribution\n- **Recording a plugin's lifecycle status, history, or grading rollups** (e.g. \"update the\n  marketplace database\", \"check all plugin inventories for drift\", \"import the latest plugin\n  grades\") — use `marketplace-inventory` instead; this skill only ever writes\n  `.claude-plugin\u002Fmarketplace.json` (the installable catalog), never\n  `marketplace-inventory.json` (the historical status\u002Frollup database).\n\n---\n\n## Phase 0: Evidence Intake\n\nBefore editing an **existing** marketplace, collect evidence first — read\n`references\u002Fdebugging-guide.md` for session history mining patterns and\nevidence-backed rule extraction. For new marketplaces, skip to Phase 1.\n\n---\n\n## Phase 1: Analyze the Target Repo\n\n### Step 1: Discover all skills\n\n```bash\n# Find every SKILL.md\nfind \u003Crepo-path>\u002Fskills -name \"SKILL.md\" -type f 2>\u002Fdev\u002Fnull\n```\n\nFor each skill, extract from SKILL.md frontmatter:\n- `name` — the skill identifier\n- `description` — the ORIGINAL text, do NOT rewrite or translate\n\n### Step 2: Read the repo metadata\n\n- `VERSION` file (if exists) — this becomes `metadata.version`\n- `README.md` — understand the project, author info, categories\n- `LICENSE` — note the license type\n- Git remotes — identify upstream vs fork (`git remote -v`)\n\n### Step 3: Determine categories\n\nGroup skills by function. Categories are freeform strings. Good patterns:\n- `business-diagnostics`, `content-creation`, `thinking-tools`, `utilities`\n- `developer-tools`, `productivity`, `documentation`, `security`\n\nIf grouping is ambiguous, propose a category set and use `AskUserQuestion` — question: \"Does this category grouping look right?\", options: \"Confirm\" \u002F \"Let me revise\" — to confirm before proceeding.\n\n### Step 4: Choose plugin boundaries\n\nClaude Code has three separate levels:\n\n```text\nmarketplace -> plugin -> skill\n```\n\n- Marketplace name is used for install identity: `plugin@marketplace`.\n- Plugin name is the slash namespace: `\u002Fplugin-name:skill-name`.\n- Skill name comes from `SKILL.md` frontmatter when the skill path points to a\n  directory containing `SKILL.md` directly.\n\nChoose each plugin boundary by installation\u002Fupdate\u002Fcache intent:\n\n- **Single-skill plugin**: use when the skill should install, update, and roll back\n  independently with a narrow cache.\n- **Suite plugin**: use when related skills should share one namespace and one\n  install command, for example `\u002Facme-docs:mermaid-tools`.\n\nFor detailed source\u002Fcache patterns and pitfalls, read\n`references\u002Fcache-and-source-patterns.md` before changing `source` or `skills`.\n\n---\n\n## Phase 2: Create marketplace.json\n\n### The official schema (memorize this)\n\nRead `references\u002Fmarketplace-schema.md` for the complete field reference.\nKey rules that are NOT obvious from the docs:\n\n1. **`$schema` field is REJECTED** by `claude plugin validate`. Do not include it.\n2. **`metadata` only has 3 valid fields**: `description`, `version`, `pluginRoot`. Nothing else.\n   `metadata.homepage` does NOT exist — the validator accepts it silently but it's not in the spec.\n3. **`metadata.version`** is the marketplace catalog version, NOT individual plugin versions.\n   It should match the repo's VERSION file (e.g., `\"2.3.0\"`).\n4. **Plugin entry `version`** is independent. For first-time marketplace registration, use `\"1.0.0\"`.\n5. **`strict: false`** is required when there's no `plugin.json` in the repo.\n   With `strict: false`, the marketplace entry IS the entire plugin definition.\n   Having BOTH `strict: false` AND a `plugin.json` with components causes a load failure.\n6. **`source` defines the installed plugin root**. For single-skill plugins, point\n   `source` directly at the skill directory (e.g., `\".\u002Ftunnel-doctor\"`) and omit\n   `skills` entirely — this is the official pattern used by 167\u002F168 plugins in\n   `anthropics\u002Fclaude-plugins-official`. For suite plugins, use\n   `source: \".\u002F\u003Csuite>\"` with explicit `skills` array listing subdirectories.\n   Avoid `source: \".\u002F\"` (installs full repo as cache) and `skills: [\".\u002F\"]`\n   (rejected by Claude Code 2.1.x path-escape validator).\n7. **Reserved marketplace names** that CANNOT be used: `claude-code-marketplace`,\n   `claude-code-plugins`, `claude-plugins-official`, `anthropic-marketplace`,\n   `anthropic-plugins`, `agent-skills`, `knowledge-work-plugins`, `life-sciences`.\n8. **`tags` vs `keywords`**: Both are optional. In the current Claude Code source,\n   `keywords` is defined but never consumed in search. `tags` only has a UI effect\n   for the value `\"community-managed\"` (shows a label). Neither affects discovery.\n   The Discover tab searches only `name` + `description` + `marketplaceName`.\n   Include `keywords` for future-proofing but don't over-invest.\n\n### Generate the marketplace.json\n\nUse the template in `references\u002Fmarketplace-schema.md` (see \"marketplace.json Template\" section).\nKey shape: root fields `name \u002F owner \u002F metadata \u002F plugins[]`; each plugin entry requires `name \u002F source \u002F strict \u002F version`.\n\n### Naming the marketplace\n\nThe `name` field is what users type after `@` in install commands:\n`claude plugin install dbs@\u003Cmarketplace-name>`\n\nChoose a name that is:\n- Short and memorable\n- kebab-case (lowercase, hyphens only)\n- Related to the project identity, not generic\n\n### Description rules\n\n- **Use the ORIGINAL description from each SKILL.md frontmatter**\n- Do NOT translate, embellish, or \"improve\" descriptions\n- If the repo's audience is Chinese, keep descriptions in Chinese\n- If bilingual, use the first language in the SKILL.md description field\n- The `metadata.description` at marketplace level can be a new summary\n\n---\n\n## Maintaining an existing marketplace\n\nWhen adding a new plugin to an existing marketplace.json:\n\n1. **Bump `metadata.version`** — this is the marketplace catalog version.\n   Follow semver: new plugin = minor bump, breaking change = major bump.\n2. **Update `metadata.description`** — append the new skill's summary.\n3. **Set new plugin `version` to `\"1.0.0\"`** — it's new to the marketplace.\n4. **Bump existing plugin `version`** when its SKILL.md content changes.\n   Claude Code uses version to detect updates — same version = skip update.\n5. **Bump existing plugin `version`** when its `source` or `skills` changes.\n   The installed cache path and component resolution changed even if SKILL.md did not.\n6. **Audit `metadata` for invalid fields** — `metadata.homepage` is a common\n   mistake (not in spec, silently ignored). Remove if found.\n7. **Sync human-facing doc lists** — run `python3 scripts\u002Fcheck_doc_skill_lists.py` after\n   adding or removing skills. It verifies that CLAUDE.md, README.md, and README.zh-CN.md\n   skill lists match `marketplace.json` and flags any drift.\n\n---\n\n## Phase 3: Validate\n\n### Step 1: One-shot pre-flight check\n\nRun the bundled validator. It runs four checks in sequence and exits non-zero on\nany required failure:\n\n```bash\nbash scripts\u002Fcheck_marketplace.sh          # validates current repo\nbash scripts\u002Fcheck_marketplace.sh \u002Fpath    # validates a target repo\n```\n\nWhat it checks:\n\n| # | Check | Failure means |\n|---|-------|---------------|\n| 1 | JSON syntax of `.claude-plugin\u002Fmarketplace.json` | file is not parseable JSON |\n| 2 | `claude plugin validate .` (skipped if `claude` CLI missing) | schema-level rejection (e.g. `Unrecognized key: \"$schema\"`, duplicate names) |\n| 3 | `source` + `skills` resolution for every plugin entry | a plugin entry points to a SKILL.md that does not exist on disk |\n| 4 | Reverse sync (disk → manifest) | WARN-only: a SKILL.md on disk is not registered in any plugin entry |\n\nCommon schema failures and fixes:\n- `Unrecognized key: \"$schema\"` → remove the `$schema` field\n- `Duplicate plugin name` → ensure all names are unique\n- `Path contains \"..\"` → use `.\u002F` relative paths only\n- `No manifest found in directory` when validating an installed cache path → validate\n  the marketplace manifest or plugin source, not a `strict: false` cache directory.\n\n### Step 2: Installation test\n\n```bash\n# Add as local marketplace\nclaude plugin marketplace add .\n\n# Install a plugin\nclaude plugin install \u003Cplugin-name>@\u003Cmarketplace-name>\n\n# Verify it appears\nclaude plugin list | grep \u003Cplugin-name>\n\n# Check for updates (should say \"already at latest\")\nclaude plugin update \u003Cplugin-name>@\u003Cmarketplace-name>\n\n# Clean up\nclaude plugin uninstall \u003Cplugin-name>@\u003Cmarketplace-name>\nclaude plugin marketplace remove \u003Cmarketplace-name>\n```\n\n### Step 3: Cache footprint test\n\nAfter installation or update, inspect the actual cache. This is the only way to\nconfirm `source` produced the intended snapshot:\n\n```bash\nPLUGIN=\u003Cplugin-name>\nMARKET=\u003Cmarketplace-name>\nCACHE=$(jq -r --arg id \"$PLUGIN@$MARKET\" '.plugins[$id][0].installPath' ~\u002F.claude\u002Fplugins\u002Finstalled_plugins.json)\nfind \"$CACHE\" -maxdepth 1 -mindepth 1 -exec basename {} \\; | sort\n```\n\nExpected results:\n\n- Single-skill plugin cache: `SKILL.md` plus its own `scripts\u002F`, `references\u002F`,\n  `assets\u002F` as applicable.\n- Suite plugin cache: only the suite member skill directories and suite-scoped\n  resources.\n- If unrelated skill directories appear, `source` is too broad.\n- If cache entries are symlinks, the plugin is not self-contained; use canonical\n  source directories instead of symlink farms.\n\n### Step 4: GitHub installation test (if pushed)\n\n```bash\n# Test from GitHub (requires the branch to be pushed)\nclaude plugin marketplace add \u003Cgithub-user>\u002F\u003Crepo>\nclaude plugin install \u003Cplugin-name>@\u003Cmarketplace-name>\n\n# Verify\nclaude plugin list | grep \u003Cplugin-name>\n\n# Clean up\nclaude plugin uninstall \u003Cplugin-name>@\u003Cmarketplace-name>\nclaude plugin marketplace remove \u003Cmarketplace-name>\n```\n\n---\n\n## Pre-flight Checklist (MUST pass before proceeding to PR)\n\nRun this checklist after every marketplace.json change. Do not skip items.\n\n### Automated checks\n\n```bash\nbash scripts\u002Fcheck_marketplace.sh\n```\n\nAll four checks must pass. Treat the reverse-sync WARN as a real signal: an\nunregistered `SKILL.md` on disk is almost always either an accidentally-dropped\nskill you forgot to register, or dead code that should be removed.\n\n### Metadata check\n\nVerify these by reading marketplace.json:\n\n- [ ] `metadata.version` bumped from previous version\n- [ ] `metadata.description` mentions all skill categories\n- [ ] No `metadata.homepage` (not in spec, silently ignored)\n- [ ] No `$schema` field (rejected by validator)\n\n### Per-plugin check\n\nFor each plugin entry:\n\n- [ ] `description` matches SKILL.md frontmatter EXACTLY (not rewritten)\n- [ ] `version` is `\"1.0.0\"` for new plugins, bumped for changed plugins\n- [ ] `source` points directly at the skill directory (e.g., `\".\u002Fskill-name\"`)\n- [ ] Single-skill plugins omit the `skills` field (auto-discovery from `source`)\n- [ ] Suite plugins list `skills` paths relative to `source`\n- [ ] `strict` is `false` (no plugin.json in repo)\n- [ ] `name` is kebab-case, unique across all entries\n\n### Final validation\n\n```bash\nbash scripts\u002Fcheck_marketplace.sh\n```\n\nMust print `RESULT: PASSED` before creating a PR. A `WARN [4\u002F4]` is acceptable\nonly when you have consciously decided to leave a SKILL.md unregistered.\n\n---\n\n## Phase 4: Create PR\n\n### Principles\n- **Pure incremental**: do NOT modify any existing files (skills, README, etc.)\n- **Squash commits**: avoid binary bloat in git history from iterative changes\n- Only add: `.claude-plugin\u002Fmarketplace.json`, optionally `scripts\u002F`, optionally update README\n\n### README update (if appropriate)\nAdd the marketplace install method above existing install instructions:\n\n```markdown\n## Install\n\n\u003C!-- Add a demo screenshot or gif here if one exists in the repo -->\n\n**Claude Code plugin marketplace (one-click install, auto-update):**\n\n\\`\\`\\`bash\nclaude plugin marketplace add \u003Cowner>\u002F\u003Crepo>\nclaude plugin install \u003Cskill>@\u003Cmarketplace-name>\n\\`\\`\\`\n```\n\n### PR description template\nInclude:\n- What was added (marketplace.json with N skills, M categories)\n- Install commands users will use after merge\n- Design decisions (pure incremental, original descriptions, etc.)\n- Validation evidence (`claude plugin validate .` passed)\n- Test plan (install commands to verify)\n\n---\n\n## Testing & Validation\n\nAfter creating or modifying marketplace.json:\n\n1. **JSON syntax** — `jq empty .claude-plugin\u002Fmarketplace.json && echo \"Valid\"` before anything else\n2. **Schema validation** — `bash scripts\u002Fcheck_marketplace.sh` — must print `RESULT: PASSED`\n3. **Installation test** — `claude plugin marketplace add . && claude plugin install \u003Cname>@\u003Cmarket>` — verify via `claude plugin list`\n4. **Cache footprint** — inspect installed cache to confirm `source` produced the right snapshot (see Phase 3, Step 3)\n5. **Version bump** — if editing an existing plugin, confirm its `version` was incremented\n\n**Quality gates:**\n- [ ] `scripts\u002Fcheck_marketplace.sh` prints `RESULT: PASSED`\n- [ ] All plugin `description` fields match SKILL.md frontmatter exactly\n- [ ] No `$schema` field, no `metadata.homepage` field\n- [ ] New plugins use `version: \"1.0.0\"`, changed plugins have version bumped\n- [ ] `strict: false` on every plugin entry (no plugin.json in repo)\n\n**Verify this skill activates on:**\n- \"create marketplace.json for this skills repo\"\n- \"add these skills to the existing marketplace catalog\"\n- \"bump the plugin version after this SKILL.md change\"\n- \"why is `claude plugin validate`\u002Finstall failing\"\n- \"prepare a PR so this repo installs via `claude plugin install`\"\n\n**Verify it does NOT activate on:**\n- \"this plugin already has a plugin.json, publish it\" → `plugin-development` instead\n- \"update the marketplace database\" \u002F \"check plugin inventories for drift\" → `marketplace-inventory` instead\n- \"these skills are local-only, not for distribution\" → out of scope entirely\n\n**Last dated run record:** 2026-08-30, `evals\u002Fmarketplace-development\u002F` — 3\u002F3 scenarios,\n11\u002F11 assertions passed (Quick Workflow, `with_skill` only — see `evals\u002Fmarketplace-development\u002Fevals.json`).\n1 of 5 declared trigger scenarios isn't yet exercised by an eval (preparing a PR for distribution) —\nsee `evals.json`'s `testing_validation_coverage` field.\n\n---\n\n## Reference Guide\n\n| Resource | Purpose |\n|---|---|\n| `references\u002Fmarketplace-schema.md` | Complete field reference for marketplace.json |\n| `references\u002Fcache-and-source-patterns.md` | `source`\u002F`skills` path patterns, pitfalls, cache behavior |\n| `references\u002Fanti-patterns.md` | Real failures encountered and fixes (NOT theoretical) |\n| `references\u002Fdebugging-guide.md` | Session history mining for debugging existing marketplace failures |\n| `scripts\u002Fcheck_marketplace.sh` | Automated pre-flight validator (4 checks, prints RESULT: PASSED) |\n| `scripts\u002Fcheck_doc_skill_lists.py` | Verify skill lists match documentation |\n| `hooks\u002Fpost_edit_validate.sh` | Auto-runs `claude plugin validate` on marketplace.json writes (auto-activated) |\n| `hooks\u002Fpost_edit_sync_check.sh` | Warns when SKILL.md edited but plugin version not bumped (auto-activated) |\n","# marketplace-development\n\nConvert a Claude Code skills repository into an official plugin marketplace so users\ncan install skills via `claude plugin marketplace add` and get auto-updates.\n\n**Input**: a repo with `skills\u002F` directories containing SKILL.md files.\n**Output**: `.claude-plugin\u002Fmarketplace.json` + validated + installation-tested + PR-ready.\n\n## Quick Start\n\n1. **Check existing marketplace** — run `bash scripts\u002Fcheck_marketplace.sh`; if `RESULT: PASSED`, jump to Phase 4 (PR) or stop\n2. **New marketplace** — Phases 1 → 2 → 3 → 4 in order\n3. **Adding skills to existing marketplace** — see \"Maintaining an existing marketplace\" below → Phase 3 → Phase 4\n4. **Debugging `claude plugin validate` failures** — see `references\u002Fdebugging-guide.md` for session history mining\n5. **Schema field reference** — `references\u002Fmarketplace-schema.md`; for `source`\u002F`skills` path pitfalls — `references\u002Fcache-and-source-patterns.md`\n\n## When to Use\n\n- Creating `.claude-plugin\u002Fmarketplace.json` for a skills repository\n- Adding new skills to an existing marketplace catalog\n- Bumping plugin versions after SKILL.md content changes\n- Debugging `claude plugin validate` or install failures\n- Preparing a PR for a skills repo to support `claude plugin install` distribution\n\n## When NOT to Use\n\n- For plugins with an existing `plugin.json` — use `plugin-development` instead\n- For local-only skills not intended for distribution\n- **Recording a plugin's lifecycle status, history, or grading rollups** (e.g. \"update the\n  marketplace database\", \"check all plugin inventories for drift\", \"import the latest plugin\n  grades\") — use `marketplace-inventory` instead; this skill only ever writes\n  `.claude-plugin\u002Fmarketplace.json` (the installable catalog), never\n  `marketplace-inventory.json` (the historical status\u002Frollup database).\n\n---\n\n## Phase 0: Evidence Intake\n\nBefore editing an **existing** marketplace, collect evidence first — read\n`references\u002Fdebugging-guide.md` for session history mining patterns and\nevidence-backed rule extraction. For new marketplaces, skip to Phase 1.\n\n---\n\n## Phase 1: Analyze the Target Repo\n\n### Step 1: Discover all skills\n\n```bash\n# Find every SKILL.md\nfind \u003Crepo-path>\u002Fskills -name \"SKILL.md\" -type f 2>\u002Fdev\u002Fnull\n```\n\nFor each skill, extract from SKILL.md frontmatter:\n- `name` — the skill identifier\n- `description` — the ORIGINAL text, do NOT rewrite or translate\n\n### Step 2: Read the repo metadata\n\n- `VERSION` file (if exists) — this becomes `metadata.version`\n- `README.md` — understand the project, author info, categories\n- `LICENSE` — note the license type\n- Git remotes — identify upstream vs fork (`git remote -v`)\n\n### Step 3: Determine categories\n\nGroup skills by function. Categories are freeform strings. Good patterns:\n- `business-diagnostics`, `content-creation`, `thinking-tools`, `utilities`\n- `developer-tools`, `productivity`, `documentation`, `security`\n\nIf grouping is ambiguous, propose a category set and use `AskUserQuestion` — question: \"Does this category grouping look right?\", options: \"Confirm\" \u002F \"Let me revise\" — to confirm before proceeding.\n\n### Step 4: Choose plugin boundaries\n\nClaude Code has three separate levels:\n\n```text\nmarketplace -> plugin -> skill\n```\n\n- Marketplace name is used for install identity: `plugin@marketplace`.\n- Plugin name is the slash namespace: `\u002Fplugin-name:skill-name`.\n- Skill name comes from `SKILL.md` frontmatter when the skill path points to a\n  directory containing `SKILL.md` directly.\n\nChoose each plugin boundary by installation\u002Fupdate\u002Fcache intent:\n\n- **Single-skill plugin**: use when the skill should install, update, and roll back\n  independently with a narrow cache.\n- **Suite plugin**: use when related skills should share one namespace and one\n  install command, for example `\u002Facme-docs:mermaid-tools`.\n\nFor detailed source\u002Fcache patterns and pitfalls, read\n`references\u002Fcache-and-source-patterns.md` before changing `source` or `skills`.\n\n---\n\n## Phase 2: Create marketplace.json\n\n### The official schema (memorize this)\n\nRead `references\u002Fmarketplace-schema.md` for the complete field reference.\nKey rules that are NOT obvious from the docs:\n\n1. **`$schema` field is REJECTED** by `claude plugin validate`. Do not include it.\n2. **`metadata` only has 3 valid fields**: `description`, `version`, `pluginRoot`. Nothing else.\n   `metadata.homepage` does NOT exist — the validator accepts it silently but it's not in the spec.\n3. **`metadata.version`** is the marketplace catalog version, NOT individual plugin versions.\n   It should match the repo's VERSION file (e.g., `\"2.3.0\"`).\n4. **Plugin entry `version`** is independent. For first-time marketplace registration, use `\"1.0.0\"`.\n5. **`strict: false`** is required when there's no `plugin.json` in the repo.\n   With `strict: false`, the marketplace entry IS the entire plugin definition.\n   Having BOTH `strict: false` AND a `plugin.json` with components causes a load failure.\n6. **`source` defines the installed plugin root**. For single-skill plugins, point\n   `source` directly at the skill directory (e.g., `\".\u002Ftunnel-doctor\"`) and omit\n   `skills` entirely — this is the official pattern used by 167\u002F168 plugins in\n   `anthropics\u002Fclaude-plugins-official`. For suite plugins, use\n   `source: \".\u002F\u003Csuite>\"` with explicit `skills` array listing subdirectories.\n   Avoid `source: \".\u002F\"` (installs full repo as cache) and `skills: [\".\u002F\"]`\n   (rejected by Claude Code 2.1.x path-escape validator).\n7. **Reserved marketplace names** that CANNOT be used: `claude-code-marketplace`,\n   `claude-code-plugins`, `claude-plugins-official`, `anthropic-marketplace`,\n   `anthropic-plugins`, `agent-skills`, `knowledge-work-plugins`, `life-sciences`.\n8. **`tags` vs `keywords`**: Both are optional. In the current Claude Code source,\n   `keywords` is defined but never consumed in search. `tags` only has a UI effect\n   for the value `\"community-managed\"` (shows a label). Neither affects discovery.\n   The Discover tab searches only `name` + `description` + `marketplaceName`.\n   Include `keywords` for future-proofing but don't over-invest.\n\n### Generate the marketplace.json\n\nUse the template in `references\u002Fmarketplace-schema.md` (see \"marketplace.json Template\" section).\nKey shape: root fields `name \u002F owner \u002F metadata \u002F plugins[]`; each plugin entry requires `name \u002F source \u002F strict \u002F version`.\n\n### Naming the marketplace\n\nThe `name` field is what users type after `@` in install commands:\n`claude plugin install dbs@\u003Cmarketplace-name>`\n\nChoose a name that is:\n- Short and memorable\n- kebab-case (lowercase, hyphens only)\n- Related to the project identity, not generic\n\n### Description rules\n\n- **Use the ORIGINAL description from each SKILL.md frontmatter**\n- Do NOT translate, embellish, or \"improve\" descriptions\n- If the repo's audience is Chinese, keep descriptions in Chinese\n- If bilingual, use the first language in the SKILL.md description field\n- The `metadata.description` at marketplace level can be a new summary\n\n---\n\n## Maintaining an existing marketplace\n\nWhen adding a new plugin to an existing marketplace.json:\n\n1. **Bump `metadata.version`** — this is the marketplace catalog version.\n   Follow semver: new plugin = minor bump, breaking change = major bump.\n2. **Update `metadata.description`** — append the new skill's summary.\n3. **Set new plugin `version` to `\"1.0.0\"`** — it's new to the marketplace.\n4. **Bump existing plugin `version`** when its SKILL.md content changes.\n   Claude Code uses version to detect updates — same version = skip update.\n5. **Bump existing plugin `version`** when its `source` or `skills` changes.\n   The installed cache path and component resolution changed even if SKILL.md did not.\n6. **Audit `metadata` for invalid fields** — `metadata.homepage` is a common\n   mistake (not in spec, silently ignored). Remove if found.\n7. **Sync human-facing doc lists** — run `python3 scripts\u002Fcheck_doc_skill_lists.py` after\n   adding or removing skills. It verifies that CLAUDE.md, README.md, and README.zh-CN.md\n   skill lists match `marketplace.json` and flags any drift.\n\n---\n\n## Phase 3: Validate\n\n### Step 1: One-shot pre-flight check\n\nRun the bundled validator. It runs four checks in sequence and exits non-zero on\nany required failure:\n\n```bash\nbash scripts\u002Fcheck_marketplace.sh          # validates current repo\nbash scripts\u002Fcheck_marketplace.sh \u002Fpath    # validates a target repo\n```\n\nWhat it checks:\n\n| # | Check | Failure means |\n|---|-------|---------------|\n| 1 | JSON syntax of `.claude-plugin\u002Fmarketplace.json` | file is not parseable JSON |\n| 2 | `claude plugin validate .` (skipped if `claude` CLI missing) | schema-level rejection (e.g. `Unrecognized key: \"$schema\"`, duplicate names) |\n| 3 | `source` + `skills` resolution for every plugin entry | a plugin entry points to a SKILL.md that does not exist on disk |\n| 4 | Reverse sync (disk → manifest) | WARN-only: a SKILL.md on disk is not registered in any plugin entry |\n\nCommon schema failures and fixes:\n- `Unrecognized key: \"$schema\"` → remove the `$schema` field\n- `Duplicate plugin name` → ensure all names are unique\n- `Path contains \"..\"` → use `.\u002F` relative paths only\n- `No manifest found in directory` when validating an installed cache path → validate\n  the marketplace manifest or plugin source, not a `strict: false` cache directory.\n\n### Step 2: Installation test\n\n```bash\n# Add as local marketplace\nclaude plugin marketplace add .\n\n# Install a plugin\nclaude plugin install \u003Cplugin-name>@\u003Cmarketplace-name>\n\n# Verify it appears\nclaude plugin list | grep \u003Cplugin-name>\n\n# Check for updates (should say \"already at latest\")\nclaude plugin update \u003Cplugin-name>@\u003Cmarketplace-name>\n\n# Clean up\nclaude plugin uninstall \u003Cplugin-name>@\u003Cmarketplace-name>\nclaude plugin marketplace remove \u003Cmarketplace-name>\n```\n\n### Step 3: Cache footprint test\n\nAfter installation or update, inspect the actual cache. This is the only way to\nconfirm `source` produced the intended snapshot:\n\n```bash\nPLUGIN=\u003Cplugin-name>\nMARKET=\u003Cmarketplace-name>\nCACHE=$(jq -r --arg id \"$PLUGIN@$MARKET\" '.plugins[$id][0].installPath' ~\u002F.claude\u002Fplugins\u002Finstalled_plugins.json)\nfind \"$CACHE\" -maxdepth 1 -mindepth 1 -exec basename {} \\; | sort\n```\n\nExpected results:\n\n- Single-skill plugin cache: `SKILL.md` plus its own `scripts\u002F`, `references\u002F`,\n  `assets\u002F` as applicable.\n- Suite plugin cache: only the suite member skill directories and suite-scoped\n  resources.\n- If unrelated skill directories appear, `source` is too broad.\n- If cache entries are symlinks, the plugin is not self-contained; use canonical\n  source directories instead of symlink farms.\n\n### Step 4: GitHub installation test (if pushed)\n\n```bash\n# Test from GitHub (requires the branch to be pushed)\nclaude plugin marketplace add \u003Cgithub-user>\u002F\u003Crepo>\nclaude plugin install \u003Cplugin-name>@\u003Cmarketplace-name>\n\n# Verify\nclaude plugin list | grep \u003Cplugin-name>\n\n# Clean up\nclaude plugin uninstall \u003Cplugin-name>@\u003Cmarketplace-name>\nclaude plugin marketplace remove \u003Cmarketplace-name>\n```\n\n---\n\n## Pre-flight Checklist (MUST pass before proceeding to PR)\n\nRun this checklist after every marketplace.json change. Do not skip items.\n\n### Automated checks\n\n```bash\nbash scripts\u002Fcheck_marketplace.sh\n```\n\nAll four checks must pass. Treat the reverse-sync WARN as a real signal: an\nunregistered `SKILL.md` on disk is almost always either an accidentally-dropped\nskill you forgot to register, or dead code that should be removed.\n\n### Metadata check\n\nVerify these by reading marketplace.json:\n\n- [ ] `metadata.version` bumped from previous version\n- [ ] `metadata.description` mentions all skill categories\n- [ ] No `metadata.homepage` (not in spec, silently ignored)\n- [ ] No `$schema` field (rejected by validator)\n\n### Per-plugin check\n\nFor each plugin entry:\n\n- [ ] `description` matches SKILL.md frontmatter EXACTLY (not rewritten)\n- [ ] `version` is `\"1.0.0\"` for new plugins, bumped for changed plugins\n- [ ] `source` points directly at the skill directory (e.g., `\".\u002Fskill-name\"`)\n- [ ] Single-skill plugins omit the `skills` field (auto-discovery from `source`)\n- [ ] Suite plugins list `skills` paths relative to `source`\n- [ ] `strict` is `false` (no plugin.json in repo)\n- [ ] `name` is kebab-case, unique across all entries\n\n### Final validation\n\n```bash\nbash scripts\u002Fcheck_marketplace.sh\n```\n\nMust print `RESULT: PASSED` before creating a PR. A `WARN [4\u002F4]` is acceptable\nonly when you have consciously decided to leave a SKILL.md unregistered.\n\n---\n\n## Phase 4: Create PR\n\n### Principles\n- **Pure incremental**: do NOT modify any existing files (skills, README, etc.)\n- **Squash commits**: avoid binary bloat in git history from iterative changes\n- Only add: `.claude-plugin\u002Fmarketplace.json`, optionally `scripts\u002F`, optionally update README\n\n### README update (if appropriate)\nAdd the marketplace install method above existing install instructions:\n\n```markdown\n## Install\n\n\u003C!-- Add a demo screenshot or gif here if one exists in the repo -->\n\n**Claude Code plugin marketplace (one-click install, auto-update):**\n\n\\`\\`\\`bash\nclaude plugin marketplace add \u003Cowner>\u002F\u003Crepo>\nclaude plugin install \u003Cskill>@\u003Cmarketplace-name>\n\\`\\`\\`\n```\n\n### PR description template\nInclude:\n- What was added (marketplace.json with N skills, M categories)\n- Install commands users will use after merge\n- Design decisions (pure incremental, original descriptions, etc.)\n- Validation evidence (`claude plugin validate .` passed)\n- Test plan (install commands to verify)\n\n---\n\n## Testing & Validation\n\nAfter creating or modifying marketplace.json:\n\n1. **JSON syntax** — `jq empty .claude-plugin\u002Fmarketplace.json && echo \"Valid\"` before anything else\n2. **Schema validation** — `bash scripts\u002Fcheck_marketplace.sh` — must print `RESULT: PASSED`\n3. **Installation test** — `claude plugin marketplace add . && claude plugin install \u003Cname>@\u003Cmarket>` — verify via `claude plugin list`\n4. **Cache footprint** — inspect installed cache to confirm `source` produced the right snapshot (see Phase 3, Step 3)\n5. **Version bump** — if editing an existing plugin, confirm its `version` was incremented\n\n**Quality gates:**\n- [ ] `scripts\u002Fcheck_marketplace.sh` prints `RESULT: PASSED`\n- [ ] All plugin `description` fields match SKILL.md frontmatter exactly\n- [ ] No `$schema` field, no `metadata.homepage` field\n- [ ] New plugins use `version: \"1.0.0\"`, changed plugins have version bumped\n- [ ] `strict: false` on every plugin entry (no plugin.json in repo)\n\n**Verify this skill activates on:**\n- \"create marketplace.json for this skills repo\"\n- \"add these skills to the existing marketplace catalog\"\n- \"bump the plugin version after this SKILL.md change\"\n- \"why is `claude plugin validate`\u002Finstall failing\"\n- \"prepare a PR so this repo installs via `claude plugin install`\"\n\n**Verify it does NOT activate on:**\n- \"this plugin already has a plugin.json, publish it\" → `plugin-development` instead\n- \"update the marketplace database\" \u002F \"check plugin inventories for drift\" → `marketplace-inventory` instead\n- \"these skills are local-only, not for distribution\" → out of scope entirely\n\n**Last dated run record:** 2026-08-30, `evals\u002Fmarketplace-development\u002F` — 3\u002F3 scenarios,\n11\u002F11 assertions passed (Quick Workflow, `with_skill` only — see `evals\u002Fmarketplace-development\u002Fevals.json`).\n1 of 5 declared trigger scenarios isn't yet exercised by an eval (preparing a PR for distribution) —\nsee `evals.json`'s `testing_validation_coverage` field.\n\n---\n\n## Reference Guide\n\n| Resource | Purpose |\n|---|---|\n| `references\u002Fmarketplace-schema.md` | Complete field reference for marketplace.json |\n| `references\u002Fcache-and-source-patterns.md` | `source`\u002F`skills` path patterns, pitfalls, cache behavior |\n| `references\u002Fanti-patterns.md` | Real failures encountered and fixes (NOT theoretical) |\n| `references\u002Fdebugging-guide.md` | Session history mining for debugging existing marketplace failures |\n| `scripts\u002Fcheck_marketplace.sh` | Automated pre-flight validator (4 checks, prints RESULT: PASSED) |\n| `scripts\u002Fcheck_doc_skill_lists.py` | Verify skill lists match documentation |\n| `hooks\u002Fpost_edit_validate.sh` | Auto-runs `claude plugin validate` on marketplace.json writes (auto-activated) |\n| `hooks\u002Fpost_edit_sync_check.sh` | Warns when SKILL.md edited but plugin version not bumped (auto-activated) |\n",{"name":5,"hooks":23,"description":7,"allowed-tools":35},{"PostToolUse":24},[25],{"hooks":26,"matcher":34},[27,31],{"type":28,"command":29,"timeout":30},"command","${CLAUDE_PROJECT_DIR}\u002F.claude\u002Fskills\u002Fmarketplace-development\u002Fhooks\u002Fpost_edit_validate.sh",30,{"type":28,"command":32,"timeout":33},"${CLAUDE_PROJECT_DIR}\u002F.claude\u002Fskills\u002Fmarketplace-development\u002Fhooks\u002Fpost_edit_sync_check.sh",10,"Write|Edit","Read Write Glob Bash(scripts\u002Fcheck_marketplace.sh:*) Bash(jq:*) Bash(python3:*) Bash(find:*) Bash(claude:*) Bash(git:*)","main","1bf12900cac6f28e346abd2912bdb78d306de723",".claude\u002Fskills\u002Fmarketplace-development","https:\u002F\u002Fgithub.com\u002FAndreHahm\u002Fandres-cc-marketplace","https:\u002F\u002Fgithub.com\u002FAndreHahm","2026-11-15 04:26:16",{"source":8,"skillName":5,"commands":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add AndreHahm\u002Fandres-cc-marketplace --skill marketplace-development",{"tool":48,"command":49},"bunx","bunx skills add AndreHahm\u002Fandres-cc-marketplace --skill marketplace-development",{"tool":51,"command":52},"pnpm","pnpm dlx skills add AndreHahm\u002Fandres-cc-marketplace --skill marketplace-development","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAndreHahm\u002Fandres-cc-marketplace\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fmarketplace-development\u002FSKILL.md",true,[56,62,66,72,76,80,84,88],{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"hooks\u002Fpost_edit_sync_check.sh","SCRIPT","脚本",2780,"https:\u002F\u002Fgithub.com\u002FAndreHahm\u002Fandres-cc-marketplace\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fmarketplace-development\u002Fhooks\u002Fpost_edit_sync_check.sh",{"path":63,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":64,"sourceHtmlUrl":65},"hooks\u002Fpost_edit_validate.sh",1386,"https:\u002F\u002Fgithub.com\u002FAndreHahm\u002Fandres-cc-marketplace\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fmarketplace-development\u002Fhooks\u002Fpost_edit_validate.sh",{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fanti-patterns.md","REFERENCE","参考文档",7269,"https:\u002F\u002Fgithub.com\u002FAndreHahm\u002Fandres-cc-marketplace\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fmarketplace-development\u002Freferences\u002Fanti-patterns.md",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fcache-and-source-patterns.md",4671,"https:\u002F\u002Fgithub.com\u002FAndreHahm\u002Fandres-cc-marketplace\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fmarketplace-development\u002Freferences\u002Fcache-and-source-patterns.md",{"path":77,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fdebugging-guide.md",1297,"https:\u002F\u002Fgithub.com\u002FAndreHahm\u002Fandres-cc-marketplace\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fmarketplace-development\u002Freferences\u002Fdebugging-guide.md",{"path":81,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fmarketplace-schema.md",4572,"https:\u002F\u002Fgithub.com\u002FAndreHahm\u002Fandres-cc-marketplace\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fmarketplace-development\u002Freferences\u002Fmarketplace-schema.md",{"path":85,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":86,"sourceHtmlUrl":87},"scripts\u002Fcheck_doc_skill_lists.py",4318,"https:\u002F\u002Fgithub.com\u002FAndreHahm\u002Fandres-cc-marketplace\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fmarketplace-development\u002Fscripts\u002Fcheck_doc_skill_lists.py",{"path":89,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":90,"sourceHtmlUrl":91},"scripts\u002Fcheck_marketplace.sh",4467,"https:\u002F\u002Fgithub.com\u002FAndreHahm\u002Fandres-cc-marketplace\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fmarketplace-development\u002Fscripts\u002Fcheck_marketplace.sh",[93,100,107,114,121,128],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":18},"01M79R0K918Z0XDM74R0EY5H3P","demo","Fixture skill used by scripts.marketplace_ci sync tests.","https:\u002F\u002Fgithub.com\u002FAndreHahm\u002Fandres-cc-marketplace\u002Fblob\u002Fmain\u002Ftests\u002Fmarketplace_ci\u002Ffixtures\u002Fplugins\u002Fsample-kit\u002Fskills\u002Fdemo\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":18},"01M79R08VMDJA2FPJKH3ZM309K","export-demo","Fixture skill used by scripts.marketplace_ci export tests.","https:\u002F\u002Fgithub.com\u002FAndreHahm\u002Fandres-cc-marketplace\u002Fblob\u002Fmain\u002Ftests\u002Fmarketplace_ci\u002Ffixtures\u002Fclaude\u002Fskills\u002Fexport-demo\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":18},"01M79R042FS581DS2JNW5AZ1MK","work-to-development","Validate an accepted Linear Issue's readiness for implementation (criteria, dependencies, duplicate\u002Fexisting artifacts) and request governed branch\u002Fworktree creation through git-kit:starting-work — recording work-started Git\u002FGitHub evidence and a deliberate Linear Started transition only after Git identity is read back and verified. Use when asked to start work on a Linear issue, begin development for an accepted issue, or prepare an accepted issue for implementation. Never creates a branch directly — always delegates to git-kit.","https:\u002F\u002Fgithub.com\u002FAndreHahm\u002Fandres-cc-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fworkmanagement-kit\u002Fskills\u002Fwork-to-development\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":18},"01M79QZZD4EHB82P72P4N92BKT","work-linking","Create and maintain stable cross-system links and authority labels between Notion and Linear records, and detect\u002Frepair drift between them. Use when asked to link a Notion record to a Linear record, check for drift between Notion and Linear, or repair a broken\u002Fstale link. Repairs only the bounded non-authoritative copy or link — never chooses by newest timestamp, and never creates a reverse-write loop against either system's own authority.","https:\u002F\u002Fgithub.com\u002FAndreHahm\u002Fandres-cc-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fworkmanagement-kit\u002Fskills\u002Fwork-linking\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":18},"01M79QZVFA3GTVNZMJ51NESVSP","status-and-learning","Produce a dated, explicitly non-live Linear-to-Notion progress summary, or capture an outcome\u002Flearning after work completes. Use when asked to summarize progress to Notion, report portfolio status, or capture what was learned from a completed piece of work — not to disposition open follow-up items (see open-item-management for that). Never runs automatically or continuously — every summary is a deliberate, approved snapshot, not a live sync.","https:\u002F\u002Fgithub.com\u002FAndreHahm\u002Fandres-cc-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fworkmanagement-kit\u002Fskills\u002Fstatus-and-learning\u002FSKILL.md",[],[],{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":18},"01M79QZNSKSABK7X2PT93X8QT5","repository-gates","Discover, delegate, record, and invalidate this repository's actual Git\u002FGitHub lifecycle gates (pre-commit, pre-push, PR required checks, Codex delta review, review requirements, merge rights) and the repository-policy provider profile that maps governed operations to git-kit. Use when asked what gates apply to this repository, to discover repository policy before starting Wave 2 work, or to check whether prior gate evidence is still valid after new commits. Discovery and delegation only — never executes a gate's own internal logic, and never invents a gate the repository doesn't actually define (in particular, never assumes a \"Review Changes\" gate exists).","https:\u002F\u002Fgithub.com\u002FAndreHahm\u002Fandres-cc-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fworkmanagement-kit\u002Fskills\u002Frepository-gates\u002FSKILL.md",[],[]]