marketplace-release-handoff
Skill0 starsChanged 4 months agoMITView on GitHub
Prepare or resume an Apple Mail Marketplace update from a signed source tag. Use when a source release needs promotion, Marketplace admission, plugin refresh, or concise release handoff guidance.
- Commits and pushes
In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- apple-mail-mcpb/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .claude-plugin/CLAUDE.mdCLAUDE.md
- docs/CLAUDE.mdCLAUDE.md
- tasks/CLAUDE.mdCLAUDE.md
- tests/CLAUDE.mdCLAUDE.md
- tools/CLAUDE.mdCLAUDE.md
- apple-mail-archive-exportSkill
- context-guidance-auditSkill
- cowork-plugin-customizerSkill
- create-cowork-pluginSkill
- finalize-apple-mail-mcpSkill
- find-skillsSkill
- mail-scripting-dictionarySkill
- mcp-builderSkill
- plugin-creatorSkill
- plugin-settingsSkill
- plugin-structureSkill
- python-performance-optimizationSkill
- reviewing-codeSkill
- testing-pythonSkill
- thermo-nuclear-code-quality-reviewSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill only after the source change is merged and the source release gate has passed.
- Distinctive: line 23
Treat the handoff output as the only source of the tag, commit, signed source inventory hash, target, and selector.
- Distinctive: line 36
After the Marketplace PR merges, return to this repository and run:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Marketplace release handoff
Use this skill only after the source change is merged and the source release gate has passed. It keeps the source and Marketplace responsibilities separate without rediscovering the release process.
Fast path
From clean source
main, run:bash tools/gates/source-release-gate.sh bash tools/gates/create-release-tag.sh --confirm-create git push origin vX.Y.Z bash tools/gates/marketplace-handoff.sh vX.Y.Z- Treat the handoff output as the only source of the tag, commit, signed source inventory hash, target, and selector. Do not transcribe these values manually. The Marketplace tool calculates the separate candidate payload digest.
- In a clean
chore/*branch of the central Marketplace, run the printed command — currentlypython3 tools/prepare_plugin_update.py --plugin apple-mail --prepare --next-steps, run from the Marketplace checkout root (that script lives in the Marketplace repository, not in this one). Complete its candidate-specific evidence, admission, attestation, release gate, and reviewed PR steps there. Commit and push the candidate plus redacted proof files before admission, because its evidence URLs must be reachable fromorigin. After the Marketplace PR merges, return to this repository and run:
bash tools/gates/refresh-central-marketplace.shRestart Claude Code and Codex so their MCP schemas reload.
Boundaries
- The handoff command is read-only and verifies the signed remote source tag.
- It does not create a tag, publish a package, update a Marketplace checkout, merge a PR, or claim untested client support.
- The Marketplace owns evidence, admission, and attestation. Do not edit its promoted Apple Mail payload directly.
- Cursor direct runtime proof and Cursor Team Marketplace UI admission are distinct facts. Do not substitute one for the other.
For the concise human reference, read docs/marketplace-release-handoff.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

