Skip to content

feat(plugin-creator): default to personal marketplace handoff#237

Merged
efrazer-oai merged 2 commits into
mainfrom
efrazer/plugin-creator-personal-marketplace-default
May 12, 2026
Merged

feat(plugin-creator): default to personal marketplace handoff#237
efrazer-oai merged 2 commits into
mainfrom
efrazer/plugin-creator-personal-marketplace-default

Conversation

@efrazer-oai
Copy link
Copy Markdown
Contributor

Summary

Plugin creation now defaults to the personal marketplace path that Codex can render and share directly.

Before this change, the curated plugin-creator skill centered repo-local plugin scaffolds and repo-root marketplace updates. That made the common personal-plugin path less explicit, and the public skill copy did not include the final deeplink handoff back into Codex after marketplace-backed creation.

This PR makes personal plugins the default flow. Marketplace-backed scaffolds now default to ~/plugins/<plugin-name> plus ~/.agents/plugins/marketplace.json. If the current Git repo already has .agents/plugins/marketplace.json and the user has not said whether the plugin is personal or team-shared, the skill asks which marketplace to update. The skill also ends marketplace-backed creation with named View <plugin-name> and Share <plugin-name> deeplinks.

What changed

  • default scaffold and marketplace paths to the personal plugin location
  • document the explicit repo/team override path for shared codebases
  • ask for user intent only in the ambiguous existing-repo-marketplace case
  • add the final named Codex deeplink handoff after marketplace-backed creation
  • refresh the marketplace reference sample to the policy.installation and policy.authentication shape

Design decisions

  • Personal plugins are the default because they are the path users can create, open, and share without first deciding to commit plugin code into a team repo.
  • Existing repo marketplaces are the one ambiguous case worth interrupting for. They can mean “add this to the codebase” rather than “make something for me personally.”
  • The deeplink labels include the plugin name so the assistant can present readable links instead of raw codex://... URLs.

Testing

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

@efrazer-oai efrazer-oai marked this pull request as ready for review May 12, 2026 00:37
@efrazer-oai efrazer-oai requested a review from a team May 12, 2026 00:37
@efrazer-oai efrazer-oai requested review from a team and gverma-openai May 12, 2026 00:54
@efrazer-oai efrazer-oai merged commit 1141b76 into main May 12, 2026
@efrazer-oai efrazer-oai deleted the efrazer/plugin-creator-personal-marketplace-default branch May 12, 2026 00:59
xl-openai pushed a commit that referenced this pull request May 13, 2026
## Summary

Plugin Creator now documents the shorter local-plugin handoff URL that
the app can interpret directly.
[#237](#237) teaches the skill to
end marketplace-backed creation flows with named View and Share links;
this follow-up updates those examples so the skill only emits the
normalized plugin name, the absolute marketplace path, and optional
share mode.

The documented shape is:

```txt
codex://plugins/<normalized-plugin-name>?marketplacePath=<absolute-marketplace-json-path>
codex://plugins/<normalized-plugin-name>?marketplacePath=<absolute-marketplace-json-path>&mode=share
```

The skill text now states exactly where the normalized plugin name
belongs, exactly where the absolute marketplace path belongs, and that
it should not add `pluginName` or `hostId` query parameters.

## Testing

Tests: plugin-creator skill validation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants