AGagentsky

Export a plugin as a Codex package [read]

Changed on

One plugin, by the id GET /plugins shows, as a Codex portable plugin package: root plugin.json (with extensions["com.openai"].interface), skills/<name>/ and root mcp.json (Agent Plugins 1.0.0: each server {type: streamable-http, url}) for the servers that need no key or sign in with OAuth. A server that signs in with an API key, which a plugin cannot carry, is named instead in an api-key-setup onboarding skill that adds it with codex mcp add … --bearer-token-env-var. No token is ever written. A bundle keeps its skills (its commands were installed as skills) and remote MCP servers; a skill is one plugin; a custom MCP server is a plugin with that server. Apps, tools, chat apps, Mac features and browser logins export the AgentSky plugin, AgentSky's own MCP server (API key) and help server, because Codex reaches them only through it. Write each file to path under one folder (base64 when encoding is base64, made executable when executable). 400 invalid_request without format=codex; 404 not_found for a bundle or MCP server the workspace has not added; 409 skill_empty for a skill with no saved version.

get/plugins/{name}/export

Request

  • Base URL
    https://api.agentsky.dev/v1
  • URL
    https://api.agentsky.dev/v1/plugins/{name}/export
  • Auth
    HTTP bearer

Path parameters

namestring required

Plugin id, e.g. bundle:review-kit, skill:skl_…, mcp:1a2b3c4d, app:gmail

Query parameters

format'codex' required

Response

The package

format'codex' required
plugin_idstring required
namestring required

The package's kebab-case name

Example response

{
  "files": [
    {
      "path": "skills/review/SKILL.md"
    }
  ]
}

Changes