You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Unkey team - would you be open to a small PR that packages Unkey operational workflows as an installable agent plugin?
What I have in mind:
a plugins/unkey-ops-operator/ package with Codex/Claude-compatible plugin metadata
one focused Skill inside the plugin for safe API-key operations: key inventory review, rollout planning, rate-limit investigation, permission/scope checks, incident triage, and approval-gated changes
a few JSONL eval cases that verify the agent reads context first, asks for approval before mutating keys or policies, and avoids exposing key material, customer identifiers, tool arguments, or model outputs in telemetry
I am using "plugin" as the installable package and "Skill" as a focused workflow inside that plugin. The goal would be to make Unkey easier to add to agent workspaces while keeping credential and customer-data boundaries explicit.
If this sounds useful, I can open a scoped PR with docs/metadata/evals only and follow any preferred naming or location convention.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi Unkey team - would you be open to a small PR that packages Unkey operational workflows as an installable agent plugin?
What I have in mind:
plugins/unkey-ops-operator/package with Codex/Claude-compatible plugin metadataI am using "plugin" as the installable package and "Skill" as a focused workflow inside that plugin. The goal would be to make Unkey easier to add to agent workspaces while keeping credential and customer-data boundaries explicit.
If this sounds useful, I can open a scoped PR with docs/metadata/evals only and follow any preferred naming or location convention.
All reactions