getprobo/probo

Run a semi-automated Probo access review campaign. Use when the user wants to review access entries, decide approve/revoke/escalate, or resume an in-progress campaign with MCP and .probo/access-reviews/ notes.

Create or update the public commitments (commitment groups and their commitments) shown on a Probo compliance portal, grounded strictly in the organization's own published Probo policies and written in a factual, understated engineering voice. Use this skill whenever the user wants to add, write, draft, edit, rewrite, curate, trim, or publish compliance portal commitments, "security commitments", or a compliance portal security section for a company on Probo; asks what commitments to show for a company doing SOC 2 or ISO 27001; gives an organization name or ID and asks to build out its compliance portal commitments; or wants existing commitments reworded to sound less like marketing. Always pull the real published policies first, surface only the specific and differentiating controls a skeptical security reviewer would find useful, and create or update them through the Probo MCP. Never invent controls that are not in the published policies.

Report who is missing document signatures or quorum approvals in Probo. Use when the user wants a per-person recap of unsigned signature requests, pending approval decisions, or document signing compliance status.

This skill should be used when the user wants to assess, track, or automate open-source compliance work in Probo — vendor reviews, control mapping, evidence collection, risk registers, or policy workflows using Probo MCP tools.