Repository navigation
chore(plugin): Add the OpenAI review metadata and release notes to plugin.json - #113
Conversation
…ugin.json Add review.test_cases, review.commerce and publication.release_notes under extensions["com.openai"], as uploaded to the OpenAI plugin portal. Remove the plan sentence from the OpenAI longDescription only, because the portal flags pricing text in the description.
|
|
Impact: the OpenAI plugin portal reads the review test cases, the commerce flag and the release notes from the ZIP, and it does not let us edit imported test cases in the dashboard. Before this PR, those fields lived only in the uploaded ZIP, so the next ZIP from Before: After:
|
There was a problem hiding this comment.
🟢 Approval recommended
The metadata-only changes match the stated scope, with no identified blocking issues.
No open issues 🎉
What changed in this PR
Aligns the root plugin manifest with the OpenAI portal submission so future packages retain review metadata and release notes.
Changes:
- Adds the commerce flag, five positive test cases, and three negative test cases.
- Adds publication release notes.
- Removes the paid-plan sentence only from the OpenAI listing description.
| File | Description |
|---|---|
plugin.json |
Adds OpenAI review and publication metadata and adjusts the listing text. |
Review effort: Balanced
Summary
This PR makes the root
plugin.jsonmatch the package that we uploaded to the OpenAI plugin portal. It adds the review metadata and the release notes underextensions["com.openai"]. It also removes one plan sentence from the OpenAI listing text, because the portal flags it.Why
reviewandpublicationdirectly underextensions.com.openai, next tointerface("Configure onboarding, review, and publication", https://developers.openai.com/plugins/deploy/submission#automatically-provide-submission-and-review-information).maindrops the test cases and the release notes.longDescription.What changes
plugin.jsonextensions["com.openai"].review.commerce(false),review.test_cases.positive(5 cases withdescription,prompt,tools_triggered,expected_behavior),review.test_cases.negative(3 cases withdescriptionandprompt) andpublication.release_notes. The values are the same as the uploaded file.plugin.jsonextensions["com.openai"].interface.longDescriptiononly. The rootdescription,.claude-plugin/plugin.json,.cursor-plugin/plugin.jsonand the README keep the plan rule.Every tool name in
tools_triggeredis a hosted User MCP tool on taskade/taskcade master:list_spaces,list_projects,create_task,set_task_date,read_project,list_agents,prompt_agent,list_automations,run_flow,get_flow_runs.No package code, no
server.jsonand nomcp.jsonchange, so this PR has no changeset.Checks
python3 -m json.tool plugin.jsonplugin.jsonandmcp.jsonagainst the agent-plugins.org 1.0.0 schemas (ajv, draft 2020-12, the check from #105)schema ok plugin.json,schema ok mcp.jsonclaude plugin validate .✔ Validation passed(marketplace)claude plugin validate .claude-plugin/plugin.json✔ Validation passedrg -n "[\x{2014}\x{2013}]" plugin.jsongit archiveofplugin.json,mcp.json,skills/,assets/,README.md,LICENSE) against the uploaded ZIPplugin.json, the parsed JSON differs only in the removed sentence. The uploaded file used expanded arrays, and this branch keeps the compact layout ofmain.yarn lint.js,.jsx,.ts,.tsxonly, so it does not read JSONOwner decision
The guide marks
review.demo_recording_urlas "Optional in ZIP; required for MCP review". The uploaded file has no demo URL, and this PR does not add one. Give the URL in the dashboard, or send it and a follow-up PR adds it toplugin.json.Rollback
Revert this PR. No host reads
revieworpublicationat install time, so a revert changes only the next ZIP that we upload.QA steps
plugin.json,mcp.json,skills/,assets/,README.mdandLICENSEfrom this branch.claude plugin validate ..✔ Validation passedRefs taskade/taskcade#32572