[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BNK79MT32F0YS1R7SW7NCM":3,"skill-same:01M7BNK79MT32F0YS1R7SW7NCM":54},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":14,"categories":15,"keywords":16,"publishedAt":17,"linkOnly":18,"markdownContent":19,"markdownBody":20,"frontMatter":21,"refName":22,"commitSha":23,"skillDirectory":24,"forksCount":12,"repositoryHtmlUrl":25,"repositoryHomepageUrl":6,"ownerHtmlUrl":26,"ownerBlogUrl":27,"ownerDescription":28,"updatedAt":29,"install":30,"resources":43},"01M7BNK79MT32F0YS1R7SW7NCM","release",null,"zjykzj\u002Fclaude-skills","zjykzj","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F69463217?v=4","01M7BNJKR5W098EGBTX0PPRFHV","01M7BNJKRZHHP642XYS58QJT5H",0,"MIT","https:\u002F\u002Fgithub.com\u002Fzjykzj\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fmaestro\u002Fskills\u002Frelease\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: release\ndescription: Bump the project version and publish a GitHub release in two phases: local (bump, commit, tag) then optional remote (push, GitHub release). Use when releasing a new version — locally or published — and whenever the user asks anything about the release process — which semver bump to pick from the commit history, version bump locations, the release commit message format, tagging and pushing the release, local-only releases, or renaming the CHANGELOG [Unreleased] section — even if they only ask a question rather than request a release.\nallowed-tools: Bash, Read, Edit, Grep, Write\n---\n\n# Release Skill\n\nUse this skill when bumping the project version and publishing a GitHub release.\n\nThe release has two phases: **Phase A — Local** (Steps 0-3: determine, bump, commit, tag) needs no network access and always runs; **Phase B — Remote** (Steps 4-5: push, GitHub release) runs only after an explicit user choice at the gate between the phases. Phase B can also run standalone later, after a local-only release.\n\n## Phase A — Local\n\n### Step 0: Determine Version Number\n\nReview `git log` since the last tag. Classify each commit's conventional commit type into semver:\n\n| Commit Type(s) | Semver | Example |\n|---------------|--------|---------|\n| `fix:`, `docs:`, `refactor:`, `style:`, `perf:`, `chore:`, `test:`, `ci:`, `build:` | **PATCH** (1.6.1 → 1.6.2) | Bug fix, doc update, internal restructure |\n| `feat:` | **MINOR** (1.6.2 → 1.7.0) | New public API, new CLI flag, new feature |\n| `feat!:` \u002F `fix!:` or `BREAKING CHANGE` in the commit body | **MAJOR** (1.7.0 → 2.0.0) | Remove public API, change default behavior |\n\n**Rule:** the highest-severity commit wins. If all commits are `docs`\u002F`refactor`\u002F`chore` → PATCH. If any `feat` → MINOR. If any breaking change → MAJOR.\n\n**Concrete check:** before picking a version, look at the `## [Unreleased]` section you're about to rename. If `### Added` is empty (no new features) → PATCH. If any entry is marked `(breaking)` → MAJOR.\n\n### Step 1: Bump Version\n\nUpdate **all** version locations configured for this project. See the `### Version Bump Locations` table in the `## Maestro Configuration` section of CLAUDE.md for the exact file paths — typical patterns include:\n\n| Pattern | Example File | Field |\n|---------|-------------|-------|\n| Package init | `{{PACKAGE_NAME}}\u002F__init__.py` | `__version__ = \"X.Y.Z\"` |\n| Project config | `pyproject.toml` | `version = \"X.Y.Z\"` |\n| Version file | `VERSION` | `X.Y.Z` (bare string, no field syntax) |\n| Changelog | `CHANGELOG.md` | Rename `## [Unreleased]` → `## [X.Y.Z] - YYYY-MM-DD`, then add a fresh empty `## [Unreleased]` at the top |\n\nThe `{{PACKAGE_NAME}}` variable is defined in CLAUDE.md — `none` for projects without a Python package (bare `VERSION` file projects).\n\n**CHANGELOG rename, not rewrite**: the commit skill maintains `## [Unreleased]` on every commit, so the release does not write new entries. Rename the section header and reset it — the section content flows unchanged into the GitHub Release body (Step 5), while the bump commit (Step 2) carries a curated digest of it.\n\n### Step 2: Commit\n\nUse the version bump commit format — the body is a **digest** of the `[X.Y.Z]` section, not a transcription of it (keep it under ~120 words):\n\n```bash\ngit commit -m \"$(cat \u003C\u003C'EOF'\nchore: bump version to X.Y.Z\n\n\u003C1-2 sentence theme summary drawn from the section>\n\nHighlights:\n- \u003Cone curated bullet per line, 3-6 total>\n\nFull release notes: CHANGELOG.md\n\nCo-Authored-By: {{AI_MODEL_NAME}} \u003C{{AI_MODEL_EMAIL}}>\nCo-Authored-By: Claude Code \u003Cnoreply@anthropic.com>\nEOF\n)\"\n```\n\n**Digest selection rules** (cap the Highlights list at 6 bullets; when more candidates exist, keep the most user-visible — `(breaking)` entries are exempt and must all be included):\n\n| Include | Skip |\n|---------|------|\n| `(breaking)` entries — always | `### Fixed` minutiae |\n| New user-facing features (`### Added`) | Internal refactors and optimization details |\n| Default-behavior changes (affect existing users) | Recipe transcriptions (\"records ... values\") |\n| 1-2 representative performance numbers | Docs reorganization entries |\n\n**Worked example** — a 31-entry section (flash-yolo 0.7.0) compresses to:\n\n```text\n0.7.0 completes end-to-end segmentation training: YOLO26-seg and\nFlash-YOLO-seg now train, validate, export and eval from COCO polygons.\n\nHighlights:\n- Seg verified against official weights (box 39.67 \u002F mask 33.67 mAP50-95)\n- Fine-tuning from a different class count (O365 365-class → COCO 80)\n- mask_ratio=1 mask-loss peak: 12.0 → 1.1 GB\n- Default MuSGD blend changed to 0.2\u002F1.0 (official recipes keep their\n  per-scale values)\n\nFull release notes: CHANGELOG.md\n```\n\nTwenty-five `### Added` entries collapse into two representative bullets; the default-behavior change stays because it affects existing users; the memory fix contributes one number. Recipe transcriptions and docs-reorganization entries are skipped entirely.\n\nThe digest budget is mechanically enforced: a PreToolUse hook (`skills\u002Frelease\u002Fscripts\u002Fdigest-check.sh`) blocks `git commit` invocations whose bump body exceeds 150 words.\n\nThe tag points at this commit, so `git log vX.Y.Z -1` shows each release's headlines at a glance; the full section stays in `CHANGELOG.md` and goes verbatim into the GitHub Release body (Step 5).\n\n### Step 3: Tag (Local)\n\nCreate an annotated tag locally with a minimal message — do not push:\n\n```bash\ngit tag -a vX.Y.Z -m \"vX.Y.Z\"\n```\n\nIn plugin-marketplace repos with per-plugin versioning (like this one), use the tool-native tag instead: `claude plugin tag plugins\u002F\u003Cplugin>` (without `--push`) — it generates the `\u003Cplugin>--vX.Y.Z` format and validates the manifest.\n\n## Gate: Local or Remote?\n\nAfter Phase A completes, **always pause and ask the user how to proceed** — regardless of permission mode (including auto\u002FacceptEdits). Pushing and publishing are outward-facing and hard to reverse, and the user's environment may be offline; the local phase must never auto-continue into remote actions. Use AskUserQuestion:\n\n| Option | Action |\n|--------|--------|\n| Push and publish | Run Phase B, Steps 4-5 |\n| Push only | Run Step 4, skip Step 5 |\n| Local only | Stop here — Phase B can run later from the gate |\n\n**Phase B runs standalone**: if the bump commit and tag already exist from a previous local-only release, skip Phase A and start directly at the gate.\n\n## Phase B — Remote\n\nRuns only for \"Push and publish\" or \"Push only\".\n\n### Step 4: Push\n\n```bash\ngit push && git push --tags\n```\n\nFor plugin-marketplace repos that tagged with `claude plugin tag plugins\u002F\u003Cplugin>` in Step 3, the tag already exists locally, so re-running the command with `--push` fails with \"Tag ... already exists locally\". Push the tag with the exact command the tagger prints instead: `git push origin refs\u002Ftags\u002F\u003Cplugin>--vX.Y.Z` (or `git push --tags`; `--force` is only for moving a wrongly-placed tag). If the push fails (e.g. no network), Phase A's work stays intact — retry Phase B later.\n\n### Step 5: Create GitHub Release\n\nGo to the repository's Releases page, select tag `vX.Y.Z`, and fill in:\n\n| Field | Content |\n|-------|---------|\n| **Title** | `vX.Y.Z: \u003Cone-line summary>` — draw the key theme(s) from the CHANGELOG entries. Keep it concise (~5-10 words). Examples: `v1.5.0: Industry-Standard Label Positioning`, `v1.6.1: Specs Purge & Code-Spec Compliance` |\n| **Body** | CHANGELOG.md `[X.Y.Z]` section content, with citation link appended at the end |\n\nBody template:\n\n```markdown\n\u003CCHANGELOG.md [X.Y.Z] section content, including ### Added\u002FChanged\u002FDeprecated\u002FRemoved\u002FFixed\u002FSecurity headings>\n\n---\n\n*See [CHANGELOG.md]({{REPO_URL}}\u002Fblob\u002Fmain\u002FCHANGELOG.md) for the full change history.*\n```\n\n**Rationale**: Full changelog content on the Release page lets readers see all changes without navigating away. The citation link at the bottom serves as an attribution reference.\n\n## Bootstrap (First Use in a New Project)\n\nConfiguration lives in the unified `## Maestro Configuration` section of the project's CLAUDE.md, shared with the other maestro skills. On first use in a project:\n\n1. Grep CLAUDE.md for `## Maestro Configuration` and for `{{AI_MODEL_NAME}}`, `{{AI_MODEL_EMAIL}}`, `{{PACKAGE_NAME}}`, `{{REPO_URL}}` definition lines and the `### Version Bump Locations` table.\n2. If the section or the lines are missing, add what's missing — create the section at the end of CLAUDE.md containing just the lines below, or append the lines inside an existing section (table last). If CLAUDE.md does not exist, create it with just this section. In either case, detect what you can from the project: `git remote get-url origin` for the repo URL; `pyproject.toml` with a package directory → `{{PACKAGE_NAME}} = \u003Cpackage>`, otherwise `{{PACKAGE_NAME}} = none`; `grep -rn 'X.Y.Z' pyproject.toml \u003Cpackage>\u002F` or a bare `VERSION` file for version locations. Ask the user for `{{AI_MODEL_NAME}}` \u002F `{{AI_MODEL_EMAIL}}` rather than guessing, and tell the user what was detected.\n3. If the lines are present — inside or outside the section (legacy `## Release Configuration` format) — use the existing values unchanged. If they sit outside the section, tell the user to merge them into `## Maestro Configuration`.\n\n```markdown\n{{AI_MODEL_NAME}} = \u003Cmodel-name>\n{{AI_MODEL_EMAIL}} = \u003Cmodel-email>\n{{REPO_URL}} = \u003Crepo-url>\n{{PACKAGE_NAME}} = \u003Cpackage-name|none>\n\n### Version Bump Locations\n\n| # | File | Field |\n|---|------|-------|\n| 1 | `pyproject.toml` | `version = \"X.Y.Z\"` |\n| 2 | `\u003Cpackage>\u002F__init__.py` | `__version__ = \"X.Y.Z\"` |\n| 3 | `CHANGELOG.md` | `## [X.Y.Z] - YYYY-MM-DD` section header |\n```\n\n**Degraded mode**: if configuration cannot be added, use the detected values per-invocation and state them in the output. Never block the release over missing configuration.\n\n## Required Configuration\n\nDefined in the project's CLAUDE.md, `## Maestro Configuration` section (unified with the other maestro skills — shared variables are defined once at the section top):\n\n| Item | Purpose | Example |\n|------|---------|---------|\n| `{{AI_MODEL_NAME}}` \u002F `{{AI_MODEL_EMAIL}}` | `Co-Authored-By` model line in bump commit; the agent-tool line is fixed to `Claude Code \u003Cnoreply@anthropic.com>` | `DeepSeek-V4-Pro` \u002F `noreply@deepseek.com` |\n| `{{PACKAGE_NAME}}` | Locate `__init__.py` version field; `none` for projects without a Python package | `dataflow` |\n| `{{REPO_URL}}` | CHANGELOG citation link in Release body | `https:\u002F\u002Fgithub.com\u002Fowner\u002Frepo` |\n| Version bump locations table | Which files carry the version string | `### Version Bump Locations` subsection of `## Maestro Configuration` |\n","# Release Skill\n\nUse this skill when bumping the project version and publishing a GitHub release.\n\nThe release has two phases: **Phase A — Local** (Steps 0-3: determine, bump, commit, tag) needs no network access and always runs; **Phase B — Remote** (Steps 4-5: push, GitHub release) runs only after an explicit user choice at the gate between the phases. Phase B can also run standalone later, after a local-only release.\n\n## Phase A — Local\n\n### Step 0: Determine Version Number\n\nReview `git log` since the last tag. Classify each commit's conventional commit type into semver:\n\n| Commit Type(s) | Semver | Example |\n|---------------|--------|---------|\n| `fix:`, `docs:`, `refactor:`, `style:`, `perf:`, `chore:`, `test:`, `ci:`, `build:` | **PATCH** (1.6.1 → 1.6.2) | Bug fix, doc update, internal restructure |\n| `feat:` | **MINOR** (1.6.2 → 1.7.0) | New public API, new CLI flag, new feature |\n| `feat!:` \u002F `fix!:` or `BREAKING CHANGE` in the commit body | **MAJOR** (1.7.0 → 2.0.0) | Remove public API, change default behavior |\n\n**Rule:** the highest-severity commit wins. If all commits are `docs`\u002F`refactor`\u002F`chore` → PATCH. If any `feat` → MINOR. If any breaking change → MAJOR.\n\n**Concrete check:** before picking a version, look at the `## [Unreleased]` section you're about to rename. If `### Added` is empty (no new features) → PATCH. If any entry is marked `(breaking)` → MAJOR.\n\n### Step 1: Bump Version\n\nUpdate **all** version locations configured for this project. See the `### Version Bump Locations` table in the `## Maestro Configuration` section of CLAUDE.md for the exact file paths — typical patterns include:\n\n| Pattern | Example File | Field |\n|---------|-------------|-------|\n| Package init | `{{PACKAGE_NAME}}\u002F__init__.py` | `__version__ = \"X.Y.Z\"` |\n| Project config | `pyproject.toml` | `version = \"X.Y.Z\"` |\n| Version file | `VERSION` | `X.Y.Z` (bare string, no field syntax) |\n| Changelog | `CHANGELOG.md` | Rename `## [Unreleased]` → `## [X.Y.Z] - YYYY-MM-DD`, then add a fresh empty `## [Unreleased]` at the top |\n\nThe `{{PACKAGE_NAME}}` variable is defined in CLAUDE.md — `none` for projects without a Python package (bare `VERSION` file projects).\n\n**CHANGELOG rename, not rewrite**: the commit skill maintains `## [Unreleased]` on every commit, so the release does not write new entries. Rename the section header and reset it — the section content flows unchanged into the GitHub Release body (Step 5), while the bump commit (Step 2) carries a curated digest of it.\n\n### Step 2: Commit\n\nUse the version bump commit format — the body is a **digest** of the `[X.Y.Z]` section, not a transcription of it (keep it under ~120 words):\n\n```bash\ngit commit -m \"$(cat \u003C\u003C'EOF'\nchore: bump version to X.Y.Z\n\n\u003C1-2 sentence theme summary drawn from the section>\n\nHighlights:\n- \u003Cone curated bullet per line, 3-6 total>\n\nFull release notes: CHANGELOG.md\n\nCo-Authored-By: {{AI_MODEL_NAME}} \u003C{{AI_MODEL_EMAIL}}>\nCo-Authored-By: Claude Code \u003Cnoreply@anthropic.com>\nEOF\n)\"\n```\n\n**Digest selection rules** (cap the Highlights list at 6 bullets; when more candidates exist, keep the most user-visible — `(breaking)` entries are exempt and must all be included):\n\n| Include | Skip |\n|---------|------|\n| `(breaking)` entries — always | `### Fixed` minutiae |\n| New user-facing features (`### Added`) | Internal refactors and optimization details |\n| Default-behavior changes (affect existing users) | Recipe transcriptions (\"records ... values\") |\n| 1-2 representative performance numbers | Docs reorganization entries |\n\n**Worked example** — a 31-entry section (flash-yolo 0.7.0) compresses to:\n\n```text\n0.7.0 completes end-to-end segmentation training: YOLO26-seg and\nFlash-YOLO-seg now train, validate, export and eval from COCO polygons.\n\nHighlights:\n- Seg verified against official weights (box 39.67 \u002F mask 33.67 mAP50-95)\n- Fine-tuning from a different class count (O365 365-class → COCO 80)\n- mask_ratio=1 mask-loss peak: 12.0 → 1.1 GB\n- Default MuSGD blend changed to 0.2\u002F1.0 (official recipes keep their\n  per-scale values)\n\nFull release notes: CHANGELOG.md\n```\n\nTwenty-five `### Added` entries collapse into two representative bullets; the default-behavior change stays because it affects existing users; the memory fix contributes one number. Recipe transcriptions and docs-reorganization entries are skipped entirely.\n\nThe digest budget is mechanically enforced: a PreToolUse hook (`skills\u002Frelease\u002Fscripts\u002Fdigest-check.sh`) blocks `git commit` invocations whose bump body exceeds 150 words.\n\nThe tag points at this commit, so `git log vX.Y.Z -1` shows each release's headlines at a glance; the full section stays in `CHANGELOG.md` and goes verbatim into the GitHub Release body (Step 5).\n\n### Step 3: Tag (Local)\n\nCreate an annotated tag locally with a minimal message — do not push:\n\n```bash\ngit tag -a vX.Y.Z -m \"vX.Y.Z\"\n```\n\nIn plugin-marketplace repos with per-plugin versioning (like this one), use the tool-native tag instead: `claude plugin tag plugins\u002F\u003Cplugin>` (without `--push`) — it generates the `\u003Cplugin>--vX.Y.Z` format and validates the manifest.\n\n## Gate: Local or Remote?\n\nAfter Phase A completes, **always pause and ask the user how to proceed** — regardless of permission mode (including auto\u002FacceptEdits). Pushing and publishing are outward-facing and hard to reverse, and the user's environment may be offline; the local phase must never auto-continue into remote actions. Use AskUserQuestion:\n\n| Option | Action |\n|--------|--------|\n| Push and publish | Run Phase B, Steps 4-5 |\n| Push only | Run Step 4, skip Step 5 |\n| Local only | Stop here — Phase B can run later from the gate |\n\n**Phase B runs standalone**: if the bump commit and tag already exist from a previous local-only release, skip Phase A and start directly at the gate.\n\n## Phase B — Remote\n\nRuns only for \"Push and publish\" or \"Push only\".\n\n### Step 4: Push\n\n```bash\ngit push && git push --tags\n```\n\nFor plugin-marketplace repos that tagged with `claude plugin tag plugins\u002F\u003Cplugin>` in Step 3, the tag already exists locally, so re-running the command with `--push` fails with \"Tag ... already exists locally\". Push the tag with the exact command the tagger prints instead: `git push origin refs\u002Ftags\u002F\u003Cplugin>--vX.Y.Z` (or `git push --tags`; `--force` is only for moving a wrongly-placed tag). If the push fails (e.g. no network), Phase A's work stays intact — retry Phase B later.\n\n### Step 5: Create GitHub Release\n\nGo to the repository's Releases page, select tag `vX.Y.Z`, and fill in:\n\n| Field | Content |\n|-------|---------|\n| **Title** | `vX.Y.Z: \u003Cone-line summary>` — draw the key theme(s) from the CHANGELOG entries. Keep it concise (~5-10 words). Examples: `v1.5.0: Industry-Standard Label Positioning`, `v1.6.1: Specs Purge & Code-Spec Compliance` |\n| **Body** | CHANGELOG.md `[X.Y.Z]` section content, with citation link appended at the end |\n\nBody template:\n\n```markdown\n\u003CCHANGELOG.md [X.Y.Z] section content, including ### Added\u002FChanged\u002FDeprecated\u002FRemoved\u002FFixed\u002FSecurity headings>\n\n---\n\n*See [CHANGELOG.md]({{REPO_URL}}\u002Fblob\u002Fmain\u002FCHANGELOG.md) for the full change history.*\n```\n\n**Rationale**: Full changelog content on the Release page lets readers see all changes without navigating away. The citation link at the bottom serves as an attribution reference.\n\n## Bootstrap (First Use in a New Project)\n\nConfiguration lives in the unified `## Maestro Configuration` section of the project's CLAUDE.md, shared with the other maestro skills. On first use in a project:\n\n1. Grep CLAUDE.md for `## Maestro Configuration` and for `{{AI_MODEL_NAME}}`, `{{AI_MODEL_EMAIL}}`, `{{PACKAGE_NAME}}`, `{{REPO_URL}}` definition lines and the `### Version Bump Locations` table.\n2. If the section or the lines are missing, add what's missing — create the section at the end of CLAUDE.md containing just the lines below, or append the lines inside an existing section (table last). If CLAUDE.md does not exist, create it with just this section. In either case, detect what you can from the project: `git remote get-url origin` for the repo URL; `pyproject.toml` with a package directory → `{{PACKAGE_NAME}} = \u003Cpackage>`, otherwise `{{PACKAGE_NAME}} = none`; `grep -rn 'X.Y.Z' pyproject.toml \u003Cpackage>\u002F` or a bare `VERSION` file for version locations. Ask the user for `{{AI_MODEL_NAME}}` \u002F `{{AI_MODEL_EMAIL}}` rather than guessing, and tell the user what was detected.\n3. If the lines are present — inside or outside the section (legacy `## Release Configuration` format) — use the existing values unchanged. If they sit outside the section, tell the user to merge them into `## Maestro Configuration`.\n\n```markdown\n{{AI_MODEL_NAME}} = \u003Cmodel-name>\n{{AI_MODEL_EMAIL}} = \u003Cmodel-email>\n{{REPO_URL}} = \u003Crepo-url>\n{{PACKAGE_NAME}} = \u003Cpackage-name|none>\n\n### Version Bump Locations\n\n| # | File | Field |\n|---|------|-------|\n| 1 | `pyproject.toml` | `version = \"X.Y.Z\"` |\n| 2 | `\u003Cpackage>\u002F__init__.py` | `__version__ = \"X.Y.Z\"` |\n| 3 | `CHANGELOG.md` | `## [X.Y.Z] - YYYY-MM-DD` section header |\n```\n\n**Degraded mode**: if configuration cannot be added, use the detected values per-invocation and state them in the output. Never block the release over missing configuration.\n\n## Required Configuration\n\nDefined in the project's CLAUDE.md, `## Maestro Configuration` section (unified with the other maestro skills — shared variables are defined once at the section top):\n\n| Item | Purpose | Example |\n|------|---------|---------|\n| `{{AI_MODEL_NAME}}` \u002F `{{AI_MODEL_EMAIL}}` | `Co-Authored-By` model line in bump commit; the agent-tool line is fixed to `Claude Code \u003Cnoreply@anthropic.com>` | `DeepSeek-V4-Pro` \u002F `noreply@deepseek.com` |\n| `{{PACKAGE_NAME}}` | Locate `__init__.py` version field; `none` for projects without a Python package | `dataflow` |\n| `{{REPO_URL}}` | CHANGELOG citation link in Release body | `https:\u002F\u002Fgithub.com\u002Fowner\u002Frepo` |\n| Version bump locations table | Which files carry the version string | `### Version Bump Locations` subsection of `## Maestro Configuration` |\n",{},"main","3a702d84c03af43058449a75b3c1999d579c5ff0","plugins\u002Fmaestro\u002Fskills\u002Frelease","https:\u002F\u002Fgithub.com\u002Fzjykzj\u002Fclaude-skills","https:\u002F\u002Fgithub.com\u002Fzjykzj","https:\u002F\u002Fwww.zjykzj.cn","Multimodal & LLM & AIGC","2026-10-25 19:44:12",{"source":7,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add zjykzj\u002Fclaude-skills --skill release",{"tool":36,"command":37},"bunx","bunx skills add zjykzj\u002Fclaude-skills --skill release",{"tool":39,"command":40},"pnpm","pnpm dlx skills add zjykzj\u002Fclaude-skills --skill release","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzjykzj\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fmaestro\u002Fskills\u002Frelease\u002FSKILL.md",true,[44,50],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"scripts\u002Fdigest-check.py","SCRIPT","脚本",2277,"https:\u002F\u002Fgithub.com\u002Fzjykzj\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fmaestro\u002Fskills\u002Frelease\u002Fscripts\u002Fdigest-check.py",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"scripts\u002Fdigest-check.sh",692,"https:\u002F\u002Fgithub.com\u002Fzjykzj\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fmaestro\u002Fskills\u002Frelease\u002Fscripts\u002Fdigest-check.sh",[55,62,69,76],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":17},"01M7BNK92FNP682W39436HRPR0","spec","Create or modify spec files following project methodology, and drive SDD (spec-first development). Use when writing, editing, or reviewing specs\u002F files; before implementing any feature or behavior change that affects a contract documented in specs\u002F; and whenever the user asks anything about spec-first development — the SDD workflow, spec versioning rules, impact analysis, or what belongs in specs\u002F vs CLAUDE.md — even if they only ask a question rather than request an edit. Do not use for writing or debugging tests, including contract tests.","https:\u002F\u002Fgithub.com\u002Fzjykzj\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fmaestro\u002Fskills\u002Fspec\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":17},"01M7BNK2DX74S6QYJVFQD3Q6YH","commit","Create git commits following project conventions. Use when committing code or preparing a commit message, and whenever the user asks anything about commit conventions — the commit message format, Conventional Commit type classification, the mandatory Co-Authored-By lines, or CHANGELOG maintenance rules (subsections, breaking-change marking, what to skip) — even if they only ask a question rather than request a commit.","https:\u002F\u002Fgithub.com\u002Fzjykzj\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fmaestro\u002Fskills\u002Fcommit\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":17},"01M7BNJXQXNSXSRGFH1MEBTNE1","claude","Write or update CLAUDE.md following project conventions. Use when adding gotchas, restructuring CLAUDE.md, or updating project documentation.","https:\u002F\u002Fgithub.com\u002Fzjykzj\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fmaestro\u002Fskills\u002Fclaude\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":6,"repositoryNo":11,"starsCount":12,"licenseSpdxId":13,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":17},"01M7BNJN61SE3MZ3Y9G89RKYQ5","dataflow-cv","Use the dataflow-cv library (v3.0.0+) — CLI commands (analyse stats\u002Fsplit\u002Ffilter\u002Fpartition\u002Fsample, convert yolo2coco\u002Fyolo2labelme\u002Flabelme2yolo\u002Flabelme2coco\u002Fcoco2yolo\u002Fcoco2labelme, visualize yolo\u002Flabelme\u002Fcoco, evaluate detection\u002Fsegmentation with --prf1) and Python API (label handlers, 5 analysers, 3 converters, 3 visualizers, 2 evaluators, compute_pr_f1, LogConfig\u002FLogManager). Use when working with dataflow-cv — building dataset pipelines, converting YOLO\u002FLabelMe\u002FCOCO annotations, evaluating detections, debugging dataflow-cv errors — and whenever the user asks anything about dataflow-cv — CLI usage, API signatures, metric computation, format conversion rules, or install extras — even if they only ask a question rather than request an action. Do not use for other CV libraries, generic OpenCV usage, or general numpy questions.","https:\u002F\u002Fgithub.com\u002Fzjykzj\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fdataflow\u002Fskills\u002Fdataflow-cv\u002FSKILL.md",[],[]]