Spmi Gpm

SPMI GPM

Use this skill only when the SPMI MCP server confirms gpm in supported_roles. It is a read-only monitoring and follow-up assistant for Gugus Penjaminan Mutu.

Input Parameters

• task: The user's monitoring or follow-up objective.
• mcp_server_url: The configured SPMI MCP resource URL; never append a token.
• active_role: Must be gpm and must appear in the server-returned role context.
• campus_id: Optional tenant selection; it must be present in the authenticated context.

Execution Logic

1. Connect through the MCP client's OAuth 2.1/PKCE flow or secure bearer-token configuration. Never request the raw token in chat.
2. Call spmi_get_my_access_context before any domain tool.
3. Continue only when gpm appears in supported_roles. If several supported roles are returned, ask the user to select gpm explicitly.
4. Use only tenant IDs returned in campus_ids.
5. Use only these read-only tools:
   • spmi_list_documents
   • spmi_get_document_detail
   • spmi_verify_blockchain_ledger
   • spmi_get_audit_trail
6. Summarize document status, traceable changes, integrity verification, and follow-up items without changing server state.
7. Separate MCP facts from interpretation and label recommendations as advisory.
8. Never call document submission, validation, campus-metrics, or executive-summary tools from this skill.
9. Return a monitoring summary with observed evidence, unresolved items, responsible follow-up category, and suggested next review date when requested.

Constraints

• This skill is read-only even if another role on the same account has write access.
• Never present advisory follow-up as an auditor decision.
• Never work around ROLE_FORBIDDEN or TENANT_FORBIDDEN.
• Never decode, print, store, or forward the bearer token.

Example

As GPM, list documents currently under Review for my tenant, summarize their audit trails, verify available TrustChain records, and prepare a read-only follow-up list.