Read the workspace at a glance: spend, request volume, agent performance, tool reliability, sessions, and conversations - all rolled up over a time window. This is the fleet view; for drilling into one request use inspectairequests, and for one conversation use inspectconversation.
Drive every stage of the governance pipeline end to end, then prove that each decision was audited. This is the guided tour of the enforcement spine: the same four stages run on every tool call in the workspace.
Work with the agents in the workspace: list them, check their configuration and the MCP tools they can reach, send one a message over the A2A protocol, and read the artifacts and traces it produces.
Follow one inference request through the AI gateway: from the client's /v1/messages call, through model routing and the governance pipeline, to the provider and back. Use it to debug a single request - routing, denials, latency, cost, or the tool calls it spawned.
Show the structured data behind a conversation that is happening right now. When a client like Claude Desktop talks to the gateway, every message, AI request, tool call, governance decision, and cost lands in the database keyed to one session. This skill reconstructs that whole picture from a single starting id.
Discover and exercise the MCP plugin surface - especially the admin-only systemprompt MCP server that runs CLI commands as a tool - and keep the skills catalogue in sync.
Change what a user is allowed to do, then watch the governance pipeline honour the change on the very next call - no restart, no new token. This is the live proof that authority is data, not a baked-in constant.
A deliberately dangerous capability that the platform refuses. It exists in the catalog to prove that governance stops unsafe actions on two independent layers - access control and runtime secret scanning - rather than trusting the agent to behave.
Answer questions about AI spend and adoption on this platform - "what did we spend on AI this week", "top users by cost", "which skills / models / plugins are used most", "were there failed or denied requests", "how does this week compare to last". For what a person or team has been working on, use adminpersonactivity.
Answer "what has been working on", "how much is using the platform", "who in is active", "how intensively", or "whose work relates to ". Reads conversations, skills used and active days, not raw requests.
Use when someone asks who they are on this instance, what they have access to, why a skill or connector they expected is missing, or what they are allowed to do here. It is the first thing a new user runs and the fastest answer to "why can't I see X".
CRM and sales pipeline management for systemprompt.io. Tracks leads from first touch through conversion, manages deals and pipeline stages, drafts and sends emails via Resend API (human-approved, never automatic), produces daily sales strategy briefs, and logs every action as a falsifiable hypothesis. Includes…
Content creation and publishing: three writer+optimiser pairs (guides, features, documentation) with research-first workflows, per-content reports, and deterministic audit scoring. Feature writer+optimiser now enforce Technical-Marketing Synthesis (Rule 6: ten sub-checks including coined terminology, dropdown…
Search engine optimisation: daily SEO brief (renamed from seo-monitor), DataForSEO keyword tracking, hypothesis-driven SEO testing (S-### ledger), AI agent answer-engine optimisation (AEO), and living strategy document maintenance.
Social media engagement: LinkedIn posting and DM outreach, three-skill Reddit pipeline (audience-finder for subreddit qualification, monitor for daily opportunity scanning, post-composer for genuine non-marketing posts), X/Twitter threads, cross-platform coordination, and daily social brief.
★not rated 2 9d agoA
tokens not measured
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: