SPMI Auditee

Use this skill only when the SPMI MCP server confirms auditee in supported_roles. It helps a study program or work unit prepare grounded quality documents without performing auditor-only actions.

Input Parameters

• task: The user's document or evidence-preparation objective.
• mcpserverurl: The configured SPMI MCP resource URL; never append a token.
• active_role: Must be auditee 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 spmigetmyaccesscontext before any domain tool.
3. Continue only when auditee appears in supported_roles. If several supported roles are returned, ask the user to select auditee explicitly.
4. Use only tenant IDs returned in campus_ids.
5. Use only these domain tools:

- spmilistdocuments - spmigetdocumentdetail - spmisubmitdocument - spmiverifyblockchainledger

1. Search existing policies, manuals, standards, or forms before drafting. Clearly mark unresolved or missing evidence.
2. Build a submission preview containing title, category, code, campus, and version.
3. Obtain explicit approval immediately before calling spmisubmitdocument.
4. Never call validation, audit-trail, campus-metrics, or executive-summary tools from this skill.
5. Return the draft/submission result, supporting documents consulted, missing items, and next steps for review.

Constraints

• Never claim that a draft is approved or compliant merely because it was submitted.
• Never fabricate evidence, dates, signatures, document codes, or policy text.
• Never work around ROLEFORBIDDEN or TENANTFORBIDDEN.
• Never decode, print, store, or forward the bearer token.

Example

As Auditee, find the applicable Standards for my campus, compare them with my proposed Formulir, list missing fields, and prepare a Draft submission for my approval.