How do I install the Staffdeck API Manage Sops skill?

Run npx skillmds@latest add openbmb/staffdeck-api-manage-sops in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Staffdeck API Manage Sops safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Staffdeck API Manage Sops?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Staffdeck API Manage Sops free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Staffdeck API Manage Sops?

OpenBMB (@openbmb) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Staffdeck API Manage Sops by openbmb

Name: Staffdeck API Manage Sops
Author: OpenBMB

Staffdeck API Manage Sops

Manage a StaffDeck employee's SOP lifecycle through Open API v1, including listing published SOPs and drafts, generating from source text, rewriting selected fields, replacing or JSON-patching drafts, validating, publishing, archiving, comparing versions, and creating rollback drafts. Use for controlled SOP authoring and release automation.

OpenBMB 3a4e407 3 files · 3.7 KB Updated Sep 17, 2026

File contents

Manage StaffDeck SOPs

Preserve the draft boundary

Generate, rewrite, structured create, patch, and rollback as drafts. Never publish a draft unless the user explicitly requests publication. Unpublished drafts must not be treated as runtime-active SOPs.

Workflow

Verify the credential can write the target employee and has the required sops:* scopes.
List current published SOPs and drafts with GET /agents/{agent_id}/sops.
Choose one authoring path from references/sop-api.md: structured create, generate, rewrite, replace, or JSON Patch.
For asynchronous generate or rewrite, poll the returned /jobs/{job_id} and read /jobs/{job_id}/result only after success.
Preserve the returned draft_id, sop_id, and ETag.
Validate the exact draft before publication.
Publish only the validated draft ID requested by the user.
Re-read the published SOP and report its version.

Concurrency and edits

Send If-Match on draft replacement and JSON Patch. On 412, fetch the latest draft and reconcile; never overwrite blindly.
Use application/json-patch+json for PATCH operations.
Keep skill_id immutable.
Prefer targeted rewrite paths or JSON Patch for small changes; use full replacement only when the complete SkillCard is authoritative.
Treat rollback as creation of a new draft, not immediate runtime rollback.

Capability safety

Before publishing, confirm every referenced skill, knowledge base, and tool belongs to the employee's available capability set. A sop_specific capability must be explicitly referenced by an SOP node to become executable.

---name: staffdeck-api-manage-sopsdescription: Manage a StaffDeck employee's SOP lifecycle through Open API v1, including listing published SOPs and drafts, generating from source text, rewriting selected fields, replacing or JSON-patching drafts, validating, publishing, archiving, comparing versions, and creating rollback drafts. Use for controlled SOP authoring and release automation.---# Manage StaffDeck SOPs## Preserve the draft boundaryGenerate, rewrite, structured create, patch, and rollback as drafts. Never publish a draft unless the user explicitly requests publication. Unpublished drafts must not be treated as runtime-active SOPs.## Workflow1. Verify the credential can write the target employee and has the required `sops:*` scopes.2. List current published SOPs and drafts with `GET /agents/{agent_id}/sops`.3. Choose one authoring path from [references/sop-api.md](references/sop-api.md): structured create, generate, rewrite, replace, or JSON Patch.4. For asynchronous generate or rewrite, poll the returned `/jobs/{job_id}` and read `/jobs/{job_id}/result` only after success.5. Preserve the returned `draft_id`, `sop_id`, and `ETag`.6. Validate the exact draft before publication.7. Publish only the validated draft ID requested by the user.8. Re-read the published SOP and report its version.## Concurrency and edits- Send `If-Match` on draft replacement and JSON Patch. On `412`, fetch the latest draft and reconcile; never overwrite blindly.- Use `application/json-patch+json` for PATCH operations.- Keep `skill_id` immutable.- Prefer targeted rewrite paths or JSON Patch for small changes; use full replacement only when the complete SkillCard is authoritative.- Treat rollback as creation of a new draft, not immediate runtime rollback.## Capability safetyBefore publishing, confirm every referenced skill, knowledge base, and tool belongs to the employee's available capability set. A `sop_specific` capability must be explicitly referenced by an SOP node to become executable.

Frequently asked questions