@probo/skills 0.2.0 → 0.2.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/skills/compliance-portal-commitments/references/portal-mechanics.md +3 -4
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@probo/skills",
3
- "version": "0.2.0",
3
+ "version": "0.2.1",
4
4
  "description": "Multi-agent compliance skills for open-source GRC (Claude Code, Codex, OpenCode) powered by Probo MCP",
5
5
  "private": false,
6
6
  "scripts": {
package/skills/compliance-portal-commitments/references/portal-mechanics.md CHANGED
@@ -8,13 +8,12 @@ varies by environment (there may be more than one Probo server, e.g. US and EU).
8
8
 
9
9
  1. **Resolve the organization** — `listOrganizations`, match by name, keep the `id`.
10
10
  2. **Resolve the compliance portal** — `getCompliancePortal` with `organization_id`. Keep
11
- `compliance_portal.id`; every group call still takes it as the `trust_center_id` argument (the resource
12
- was renamed from "trust center" to "compliance portal" but the ID parameter kept its old name).
13
- 3. **Read what already exists** — `listCommitmentGroups` with the `trust_center_id`, and
11
+ `compliance_portal.id`; every group call takes it as the `compliance_portal_id` argument.
12
+ 3. **Read what already exists** — `listCommitmentGroups` with the `compliance_portal_id`, and
14
13
  `listCommitments` with a `group_id`. Do this so you reuse the existing group instead of duplicating it.
15
14
  Order by `{field: "RANK", direction: "ASC"}`.
16
15
  4. **Create the single group** — all commitments live under one group titled "Security at <company name>".
17
- If it does not exist yet, `addCommitmentGroup` with `trust_center_id`, `title`, `description`; if it (or
16
+ If it does not exist yet, `addCommitmentGroup` with `compliance_portal_id`, `title`, `description`; if it (or
18
17
  any other group) already exists, reuse it. Capture the returned `commitment_group.id`. You need it to
19
18
  attach commitments.
20
19
  5. **Add commitments** — `addCommitment` with `group_id`, `icon`, `eyebrow`, `title`, `description`. These