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.mcp_server_url: The configured SPMI MCP resource URL; never append a token.active_role: Must beauditeeand must appear in the server-returned role context.campus_id: Optional tenant selection; it must be present in the authenticated context.
Execution Logic
- Connect through the MCP client's OAuth 2.1/PKCE flow or secure bearer-token configuration. Never request the raw token in chat.
- Call
spmi_get_my_access_contextbefore any domain tool. - Continue only when
auditeeappears insupported_roles. If several supported roles are returned, ask the user to selectauditeeexplicitly. - Use only tenant IDs returned in
campus_ids. - Use only these domain tools:
spmi_list_documentsspmi_get_document_detailspmi_submit_documentspmi_verify_blockchain_ledger
- Search existing policies, manuals, standards, or forms before drafting. Clearly mark unresolved or missing evidence.
- Build a submission preview containing title, category, code, campus, and version.
- Obtain explicit approval immediately before calling
spmi_submit_document. - Never call validation, audit-trail, campus-metrics, or executive-summary tools from this skill.
- 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
ROLE_FORBIDDENorTENANT_FORBIDDEN. - 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.