1---2name: sg-ai-governance-tabular-review3description: Review Singapore AI governance, agency calibration, testing evidence and sector overlays against identified current sources.4license: MIT5metadata:6 source: https://skillmd.com/skills/open-legal-products/sg-ai-governance-tabular-review7 version: 1.0.08 author: Si Han Xu9 language: English10 mike-display-name: SG AI Governance Tabular Review11 mike-type: tabular12 mike-availability: add-on13 practice: AI Governance14 jurisdictions: Singapore15---1617# AI Governance Assessment — Singapore (IMDA Model Frameworks + AI Verify)1819## Instructions2021- Apply each column prompt in `table-columns.yaml` to each document independently.22- Extract only information supported by the document text.23- Include clause references, section names, dates, amounts, party names, and defined terms where available.24- If responsive information is not found, return an empty value or a concise "Not found" response.25- Keep cell outputs concise while including enough context to make each extracted value useful.26- Do not invent citations, facts, parties, dates, rights, obligations, or financial consequences.27- Render the completed results as an exportable Excel (`.xlsx`) file. If Excel output is not possible, render the results as a Markdown table.28## Scope and legal anchors2930- Identify the applicable traditional, generative and agentic Model AI Governance Framework versions and cite the relevant passages. Determine agency taxonomy and pathways from the identified text, not display tags.31- Determine AI Verify coverage, limitations, evidence requirements and assurance/certification claims from the identified current scheme source. Determine chatbot disclosures from the identified dated Transparency Guidelines for Generative AI Chatbots and cite each relevant passage.32- Distinguish source-backed framework recommendations, sector requirements and market expectations (for example, MAS, MOH, PDPC or IMDA sources). Compare supplied system and governance evidence; do not presume controls or approvals.33- Use supplied system inventories, architecture, risk assessments, evaluation records, governance policies and approval records; do not treat a single system document as an organisation-wide inventory. Distinguish document facts (cite the reviewed passage), operational facts (cite supplied organisational materials), external law or guidance (identify the current source/version and pinpoint provision), and labelled assessments or proposals. Return Not found for missing facts and Not assessed for unsupported analysis; do not infer consent, ownership, approval, deadlines, prior positions or deployed controls from silence.34- Keep all drafts and proposed actions subject to human review. Do not submit, publish, approve deployment or accept residual risk without human approval.