shellonback/ClickUp
Tasks & projects · v0.1.1Source
Brings the tasks of your ClickUp lists into the Teams board and keeps their status in sync.
net:api.clickup.comsecretstasks:readtasks:writeprompt:proposeCompany
Connect PromptOps
to everything you use
Plugins bring your tools into PromptOps: tasks from your tracker, pull requests, usage of your AI providers, notifications, and whole new pages in the menu. Anyone can write one. Every plugin runs in a sandbox and is reviewed before it is listed.
Plugins are in preview: they run in the development build today and arrive with an upcoming desktop release.
What they are for
Your work lives in many tools. Your agents should see it.
A plugin is a small piece of JavaScript that connects one service, or adds one tool, to one part of PromptOps.
Bring your data in
Tasks, pull requests, documents and quotas show up where you already work, next to your sessions, instead of in another browser tab.
Add your own tools
A plugin can own a page in the menu: a writer, a report, a benchmark. You describe the page as data and PromptOps draws it.
Share know-how
Skills and quick prompts for your agents, packaged once and installed by the whole team.
Stay in control
A plugin asks for named permissions. Anything that runs a model or writes a file shows you the full content first.
Sections
Eight kinds of plugin, one for each part of PromptOps
A plugin belongs to exactly one section. The section decides where it appears and what it can ask for.
Pages & tools
Works in the appA tool with its own page: a form, a result, your logic.
- Turn git activity into an email, a changelog or a handover.
- Measure how fast your models answer today against what is normal for you.
- Build the internal tool your team keeps asking for, without forking the app.
- Where it appears
- Its own entry in the sidebar menu
- Typical services
- Writers, reports, benchmarks, checklists, generators
Tasks & projects
Screen being connectedThe tasks of your tracker as cards on the board, with their status in sync.
- Pick a card and hand it to an agent with its full description.
- Move the card and the status changes in your tracker too.
- One board for the whole team, whatever tracker each project uses.
- Where it appears
- Teams › Board
- Typical services
- ClickUp, Linear, Jira, Trello, GitHub Issues
Code & repos
Screen being connectedPull requests and CI checks of your code host, next to the repository you are working on.
- See which pull requests wait for you without leaving the session.
- Read why a check failed and propose the fix to an agent.
- Works with the host your company uses, not only the big ones.
- Where it appears
- Sessions › Git Explorer
- Typical services
- GitHub, GitLab, Bitbucket, Gitea, your CI
Data & infra
Screen being connectedTables from an API or a database service, to look at while an agent works.
- Check the rows an agent just changed.
- Keep error rates or queue sizes in view during a fix.
- Read-only by design: a panel, not a console.
- Where it appears
- Sessions › side panel
- Typical services
- Supabase, PlanetScale, Sentry, Grafana, internal APIs
AI providers
Screen being connectedCredit and quota of an AI provider, in the same place as the others.
- Know before a long run whether you have the budget.
- One screen for every account your team pays for.
- Add the provider PromptOps does not know yet.
- Where it appears
- Usage
- Typical services
- OpenRouter, Together, Groq, your gateway
Context
Works in the appSearch your documents and hand one to an agent as context. You read it first.
- The spec, the ADR or the runbook reaches the agent without copy and paste.
- The agent works from the current version, not from memory.
- Every document is proposed to you, never sent on its own.
- Where it appears
- Prompts › Project Brief
- Typical services
- Notion, Confluence, Google Docs, your wiki
Notifications
Screen being connectedA message where your team already talks, when an agent finishes or needs you.
- Start a long task and walk away: you are told when it is done.
- Approvals do not wait for someone to look at the screen.
- Only metadata leaves: session name, status, duration. Never prompts or code.
- Where it appears
- Notifications, session events
- Typical services
- Slack, Discord, Telegram, Teams, any webhook
Agent extensions
Playground only for nowSkills and quick prompts for your agents. No code at all, only text in the manifest.
- The house style of your team, applied by every agent.
- A review checklist one click away.
- The full text is shown before anyone installs it.
- Where it appears
- Spawn composer
- Typical services
- Checklists, routines, house style
Catalog
Plugins you can install
The same list you find in PromptOps under Plugins. Every entry points to its public source code.
You install them from the desktop app, under Plugins › Catalog. Here you can read what each one asks for and open its code.
shellonback/AI Git Writer
Pages & tools · v0.1.2Source
Turns your notes and the git activity of a repository into an email, documentation, a changelog, a status report or a handover, and saves it in docs/.
git:readworkspace:writeai:generatestorageCompany
shellonback/AI Agent Evals
Pages & tools · v0.1.1Source
Measures how fast your AI models really answer, through the same CLI you use every day, and compares each one with its expected range and with your own history.
ai:benchmarkstorageCompany
shellonback/Trello
Tasks & projects · v0.1.0Source
Brings the cards of your Trello boards into the Teams board. Lists become columns, and moving a card moves it in Trello too.
net:api.trello.comsecretstasks:readtasks:writeprompt:proposeCompany
shellonback/Jira
Tasks & projects · v0.1.0Source
Brings the issues of your Jira Cloud projects into the Teams board. Statuses become columns, and moving a card runs the matching Jira transition.
net:api.atlassian.comsecretstasks:readtasks:writeprompt:proposeCompany
Safe by construction
Plugins come from other people, so PromptOps never trusts them.
- JavaScript only, in a sandbox with no network, no files and no access to the app.
- One way out: a broker that allows only what the manifest declares, HTTPS and named hosts only.
- Your credentials never reach the plugin: PromptOps fills them in when a request leaves.
- A plugin never writes to an agent. It proposes, you confirm.
- Public code, reviewed at an exact commit, with the hash of the file checked on every load.
Contribute
Write one. It takes an afternoon.
Start from a working example of your section, try it in a graphical playground, push it to your public GitHub repository and submit it for review.
- 1
Start from a template
One working plugin per section, with sample data, so you change a real thing instead of reading a spec.
- 2
Try it in the playground
A local page that draws your plugin as PromptOps would, with the same rules and an activity log. No account, no dependencies.
- 3
Publish and submit
Your code stays in your repository. PromptOps reviews an exact commit and lists it in the catalog.
