@probo/skills 0.3.2 → 0.4.1

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "probo",
-  "version": "0.3.2",
+  "version": "0.4.1",
   "description": "Open-source compliance workflows powered by Probo MCP (Claude Code, Codex, OpenCode)",
   "author": {
     "name": "Probo Inc",

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "probo",
-  "version": "0.3.2",
+  "version": "0.4.1",
   "description": "Open-source compliance workflows powered by Probo MCP (Codex, OpenCode, Claude Code)",
   "author": {
     "name": "Probo Inc",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@probo/skills",
-  "version": "0.3.2",
+  "version": "0.4.1",
   "description": "Multi-agent compliance skills for open-source GRC (Claude Code, Codex, OpenCode) powered by Probo MCP",
   "private": false,
   "scripts": {

package/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
   "name": "probo",
-  "version": "0.3.2",
+  "version": "0.4.1",
   "description": "Open-source compliance workflows powered by the Probo MCP API",
   "author": {
     "name": "Probo Inc",

package/skills/access-review/references/mcp-tools.md

@@ -22,6 +22,10 @@ required input, so it serves two distinct purposes:
 Either way the organization must be resolved before `listAccessReviewCampaigns`,
 which requires `organization_id`.
 
+Each organization includes `name` (operating name) and `legal_name` (registered
+legal name, null when unset). Match the organization the user named against
+`name`. Use `legal_name` when a note or report must name the legal entity.
+
 ## Read
 
 ### `listAccessReviewCampaigns`

package/skills/compliance-portal-commitments/SKILL.md

@@ -50,7 +50,9 @@ Commitments must trace to controls the company genuinely has. The source of trut
 1. **Find the Probo MCP and the organization.** This environment may expose more than one Probo MCP
    server (the plugin ships hosted `probo-us` and `probo-eu`, and self-hosted instances add their own).
    Call `listOrganizations` on each until you find the one that returns the target company, and use that
-   server for every later call. Match the organization the user named and capture its `id`.
+   server for every later call. Match the organization the user named on `name` (the operating name) and
+   capture its `id`. `legal_name` is the registered legal name when set. The public group title still uses
+   the operating name. Use `legal_name` only when a commitment must name the legal entity.
 2. **List the published policies.** Call `listDocuments` with `document_types: ["POLICY"]`. Policies with
    a `current_published_major` are published.
 3. **Read the actual content.** `getDocument` returns metadata only. To get the text, call

package/skills/missing-signatures/references/mcp-tools.md

@@ -8,7 +8,9 @@ server configured in the agent). Read each tool schema before calling.
 ### `listOrganizations`
 
 List organizations the caller can access. Use to resolve `$ARGUMENTS` when the
-user provides a name instead of a GID.
+user provides a name instead of a GID. Match on `name` (operating name).
+`legal_name` is the registered legal name when set; use it in the report title
+when the document should name the legal entity, and `name` otherwise.
 
 ### `listUsers`
 

package/skills/open-source-compliance/SKILL.md

@@ -17,7 +17,10 @@ first.
    `claude mcp login probo-us` to complete the OAuth 2.0 sign-in.
 2. Identify the target organization. List organizations if the user did not
    provide one, and when several servers are connected use the one that returns
-   the target organization.
+   the target organization. `listOrganizations` returns `name` (the operating
+   name) and `legal_name` (the registered legal name, null when unset). Match
+   the organization on `name`. When a policy, contract, or other legal document
+   must name the company, use `legal_name` when it is set and `name` otherwise.
 3. Prefer MCP tools over manual API calls. The Probo MCP API mirrors the
    platform's GraphQL surface.
 
@@ -32,7 +35,7 @@ first.
 
 ### Control and obligation tracking
 
-1. List controls, measures, or obligations relevant to the user's question.
+1. List controls, internal controls, or obligations relevant to the user's question.
 2. Link evidence (documents, audits) where appropriate.
 3. Report gaps between required and implemented controls.