adminbot-workflows

Routes lab administration requests to focused AdminBot skills and approval-gated proposal tools.

1|3|Updated Jul 14, 2026
One-click install
npx skills add https://github.com/akhkim/adminbot --skill adminbot-workflows-akhkim
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: adminbot-workflows
Source: https://github.com/akhkim/adminbot/tree/main/openclaw-adminbot/extensions/adminbot/skills/adminbot-workflows
Command: npx skills add https://github.com/akhkim/adminbot --skill adminbot-workflows-akhkim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Lab administrators handle many sensitive workflows—reimbursements, Slack invites, recommendation letters, social posts, calendar/email, and paper publishing—and choosing the wrong tool or skipping approval steps risks unauthorized external actions. This Skill acts as the routing layer that picks the right focused skill and enforces a universal safety loop before any real-world mutation. ## Core Features & Use Cases - Skill Router: Maps each admin request type (join-form triage, reimbursements, access invites, Slack management, letters, social posts, calendar/email, paper publishing) to the correct focused skill and its typed tools. - Universal Safety Loop: Enforces privacy-aware reasoning via adminbot_reason, evidence gathering, risk-tier identification, and proposal creation with adminbot_propose_action. - Approval-Gated Execution: Requires every external action to be reviewed and approved in the Control UI Pending Actions section, with immutable payloads and re-approval on any change. - Use Case: A lab admin asks to accept a candidate, invite them to Slack, and schedule onboarding; the Skill splits this into three separate proposals, each with its own evidence and approval. ## Quick Start Ask AdminBot to prepare a reimbursement or draft a Slack invite, and it will route the request to the right workflow and create a pending proposal for approval in the Control UI.

Frequently Asked Questions about adminbot-workflows

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route an admin request to the right AdminBot skill?▼

Use the Skill Router table in this workflow skill: match the request type (reimbursements, Slack invites, letters, social posts, calendar/email, paper publishing) to the listed focused skill, then follow that skill's playbook and create a proposal with the narrowest typed tool.

How do I approve or execute a pending AdminBot action?▼

Approve actions only in the Control UI's Pending Actions section, where one click both approves and executes the immutable proposal. Chat-based approval commands are never accepted, and any payload change requires a new proposal and new approval.

Can AdminBot handle requests spanning multiple workflows?▼

Yes, but multi-part requests must be split into separate proposals. For example, accepting a candidate, inviting them to Slack, and scheduling onboarding become three distinct actions, each with its own evidence and approval.

How does AdminBot protect private information in admin requests?▼

Substantive reasoning goes through adminbot_reason with privacy set to private for sensitive requests, and user-named private values are passed in sensitiveTerms. Raw private text is never delegated directly, and remote models only see sanitized content.

When should I use adminbot_propose_action instead of a specialized tool?▼

Use adminbot_propose_action only when no specialized typed tool fits the request. Draft and classification tools are preferred for T0/T1 work, and settings changes go through adminbot_get_settings and adminbot_update_settings.