From an empty folder
to the catalog

Step by step

1. 1

   Pick the section

   A plugin belongs to exactly one section, and the section decides where it appears and what it may ask for. If you connect a service, choose by what you bring in: tasks, pull requests, tables, quotas, documents, messages. If you build a tool with its own screen, choose pages. The sections are described one by one below.

2. 2

   Get the templates and open the playground

   The repository holds one working plugin per section and a playground that draws it the way PromptOps does. It binds to your machine only and needs nothing installed.

   Copy

   git clone https://github.com/shellonback/promptops-plugin-templates
   cd promptops-plugin-templates
   node playground/server.mjs

3. 3

   Copy the template of your section

   This creates your own folder, outside the templates repository, with a manifest, the source file, sample data and a README. Then point the playground at it. The first argument is the section, the third is your id: your-handle.plugin-slug, lowercase, permanent.

   Copy

   node tools/new-plugin.mjs tasks ../my-plugin your-handle.my-plugin "My Plugin"
   node playground/server.mjs --plugin ../my-plugin

4. 4

   Declare what you need in the manifest

   promptops-plugin.json names your plugin and lists its permissions. Ask only for what you use: people read this list before installing, and a new permission in an update needs their approval again. Hosts are named one by one, net:api.example.com. Optionally list the AI providers you tried it with under providers: the catalog shows the first three as small icons.

   Copy

   {
     "schemaVersion": 1,
     "id": "your-handle.my-plugin",
     "name": "My Plugin",
     "version": "0.1.0",
     "category": "tasks",
     "entry": "src/plugin.js",
     "permissions": ["net:api.example.com", "secrets", "tasks:read"],
     "providers": ["claude-code-cli"]
   }

5. 5

   Write src/plugin.js

   You register the contract of your section and return data. PromptOps draws it: no HTML, CSS or script ever comes from a plugin. The only way out is the sdk object. For a token you write a placeholder, {{secret:token}}, and PromptOps fills it in when the request leaves, only towards a host you declared.

   Copy

   promptops.tasks.registerSource({
     async validate(sdk) {
       const res = await sdk.http.fetch('https://api.example.com/me', {
         headers: { Authorization: 'Bearer {{secret:token}}' },
       });
       return { ok: res.ok };
     },
     async listTasks({ containerId }, sdk) { /* return tasks as data */ },
   });

6. 6

   Test it, offline first

   The playground starts in Fixtures mode: answers come from fixtures.json, so it works on a train. Switch to Live to call the real service. Every call your plugin makes shows in the activity log, and a denied one is red with the reason. Press Reload plugin after each change.

7. 7

   Validate

   The validator applies the same rules as the app and the registry: manifest, permissions, readable code. It also prints the three values you need to submit.

   Copy

   node tools/validate.mjs ../my-plugin

8. 8

   Publish your repository

   Push your folder to a public GitHub repository under your account. Keep the code in src/ and unminified: what people read must be what runs. If you use a bundler, commit your sources next to its output.

9. 9

   Submit it for review

   In PromptOps open Plugins › Create plugin, choose whether you publish as yourself or as your team, and paste the version, the commit SHA, the SHA-256 of your file and the manifest. PromptOps downloads that exact commit, scans it and a person reviews it. Once approved it appears in the catalog and here. To update, submit a higher version: people are never updated silently.