Skip to content

feat(skills): default plugin creator to personal share flow#22221

Merged
efrazer-oai merged 4 commits into
mainfrom
efrazer/plugin-creator-deeplink-handoff
May 12, 2026
Merged

feat(skills): default plugin creator to personal share flow#22221
efrazer-oai merged 4 commits into
mainfrom
efrazer/plugin-creator-deeplink-handoff

Conversation

@efrazer-oai
Copy link
Copy Markdown
Contributor

@efrazer-oai efrazer-oai commented May 11, 2026

Summary

Plugin creation now defaults to the personal marketplace path and ends with a readable handoff back into Codex after a marketplace-backed scaffold.

Before this change, plugin-creator centered repo-local marketplace updates and did not clearly guide the agent to return the user to the created plugin afterward. This PR updates the bundled system skill so marketplace-backed scaffolds default to ~/plugins/<plugin-name> plus ~/.agents/plugins/marketplace.json, ask for user intent only when an existing repo marketplace makes personal vs team scope ambiguous, and end with named Markdown deeplinks labeled View <plugin-name> and Share <plugin-name>.

What changed

  • default marketplace-backed creation to the personal plugin location
  • document the explicit repo/team override path for codebases that should own the plugin entry
  • ask personal vs team only when the current Git repo already has .agents/plugins/marketplace.json and the user has not stated scope
  • require named Markdown deeplinks after marketplace-backed creation so the final response returns the user to the exact plugin cleanly
  • keep the deeplink targets precise with real absolute marketplacePath and normalized pluginName values
  • align the bundled prompt, scaffold help text, and marketplace reference spec with the new default

Testing

Tests: targeted skill validation, Python compile checks, personal-default scaffold smoke, repo-override scaffold smoke, and whitespace checks.

@efrazer-oai efrazer-oai changed the title feat(skills): require plugin creator deeplink handoff feat(skills): default plugin creator to personal share flow May 12, 2026
@efrazer-oai efrazer-oai marked this pull request as ready for review May 12, 2026 00:38
- Keep marketplace `source.path` relative to the selected marketplace root as `./plugins/<plugin-name>`.
- When the workflow created or updated a marketplace-backed plugin, end the final user-facing
response with these two Markdown links, in this order, and do not add any text after them:
- `[View <normalized plugin name>](codex://plugins/view-local?marketplacePath=<absolute marketplace.json path>&pluginName=<normalized plugin name>)`
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should already support codex://plugins/plugin_name@workspace_name

@efrazer-oai efrazer-oai merged commit fd24c00 into main May 12, 2026
27 checks passed
@efrazer-oai efrazer-oai deleted the efrazer/plugin-creator-deeplink-handoff branch May 12, 2026 00:58
@github-actions github-actions Bot locked and limited conversation to collaborators May 12, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

2 participants