[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7902E4KKFWD5KPD2GN8ZQJN":3,"skill-same:01M7902E4KKFWD5KPD2GN8ZQJN":76},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":14,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M7902E4KKFWD5KPD2GN8ZQJN","fsi-compliance-checker",null,"Maps code, architecture, and infrastructure changes to specific control IDs in PCI-DSS v4.0 and MAS TRM (Singapore financial regulator), producing an audit-traceable findings report with per-control remediation.","Elogic360\u002Fsoftware-factory","Elogic360","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F156535519?v=4","01M74NH3F0RB13PWB7JZDE2V80","elogic360","01M74NH3FPC65082MDZVMFHDM3",0,"MIT","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fintegrations\u002Fantigravity-skills\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Ffsi-compliance-checker\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: fsi-compliance-checker\ndescription: \"Maps code, architecture, and infrastructure changes to specific control IDs in PCI-DSS v4.0 and MAS TRM (Singapore financial regulator), producing an audit-traceable findings report with per-control remediation.\"\ncategory: security\nrisk: safe\nsource: community\nsource_repo: timwukp\u002Fagent-skills-best-practice\nsource_type: community\ndate_added: \"2026-06-12\"\nauthor: timwukp\ntags: [compliance, pci-dss, mas-trm, fintech, banking, security-review, audit, financial-services]\ntools: [claude, cursor, gemini, codex, antigravity]\nlicense: \"MIT\"\nlicense_source: \"https:\u002F\u002Fgithub.com\u002Ftimwukp\u002Fagent-skills-best-practice\u002Fblob\u002Fmain\u002FLICENSE\"\n---\n\n# FSI Compliance Checker\n\n## Overview\n\nMaps a concrete change (code diff, architecture design, IaC, pipeline config) to the specific controls it touches in financial services compliance frameworks — PCI-DSS v4.0 for payment card data and MAS TRM for Singapore-regulated institutions — and reports gaps with actionable remediation. This is engineering-level compliance triage: it helps teams catch violations before audit, but it does not replace a qualified assessor (QSA) or the institution's compliance function. Say so in every report.\n\n## When to Use This Skill\n\n- Use when a change touches payment card data (PAN, CVV, track data) and needs a PCI-DSS check\n- Use when reviewing changes at a Singapore-regulated financial institution against MAS TRM expectations\n- Use when someone asks \"is this compliant\", \"does logging this violate PCI\", or requests a banking-regulation review of a diff, design, or Terraform change\n- Do NOT use for generic security review (no framework involved), GDPR\u002FSOC2\u002FHIPAA (out of bundled scope), or legal advice\n\n## How It Works\n\n### Step 1: Select the framework\n\nLoad only the reference file(s) the engagement needs:\n\n| Situation | Load |\n|-----------|------|\n| Payment card data is stored, processed, or transmitted | [pci-dss.md](pci-dss.md) |\n| Singapore-regulated financial institution (bank, insurer, capital markets, major payment institution) | [mas-trm.md](mas-trm.md) |\n| Both apply (e.g. Singapore bank handling cards) | Both files |\n| Other jurisdictions\u002Fframeworks (SOX, GDPR, HKMA, APRA) | State they are out of scope; offer general secure-engineering review instead |\n\nIf the user hasn't said which applies, ask one question: what data does the change touch, and is the institution Singapore-regulated?\n\n### Step 2: Scope the change\n\nIdentify what the diff\u002Fdesign actually touches: data elements (card data? customer PII? credentials?), trust boundaries, environments (production? DR?), and third parties.\n\n### Step 3: Assess applicable controls\n\nSelect the applicable controls from the loaded reference file(s) — typically 5-15 controls, not the whole framework. List what you ruled out and why (one line each) so the scoping is auditable. Assess each as `Compliant` \u002F `Gap` \u002F `Needs evidence` (can't tell from the artifact — name the evidence required).\n\n### Step 4: Report\n\nEvery Gap gets: the control ID, what's wrong in this specific change, concrete remediation, and severity (Critical = violation involving live regulated data; High = control absent; Medium = control partial\u002Fundocumented).\n\n```markdown\n# Compliance Review: [change title]\n**Frameworks:** [PCI-DSS v4.0 \u002F MAS TRM 2021] · **Date:** [YYYY-MM-DD]\n**Scope:** [what was reviewed: files, design doc, pipeline]\n> Engineering triage only — not a substitute for QSA assessment or the compliance function.\n\n## Data & Boundary Analysis\n- Data elements touched: [e.g. PAN (masked), customer NRIC, none]\n- Environments\u002Fboundaries: [e.g. CDE-adjacent service, public API]\n\n## Findings\n| # | Control | Status | Severity | Finding | Remediation |\n|---|---------|--------|----------|---------|-------------|\n| 1 | [PCI 3.5.1] | Gap | Critical | [specific issue in this change] | [specific fix] |\n\n## Ruled Out (not applicable)\n- [Control area] — [one-line reason]\n\n## Evidence Needed\n- [Control]: [what artifact would demonstrate compliance]\n```\n\n### Step 5: Offer story conversion\n\nOffer to turn findings into backlog items with the control ID in each story for traceability.\n\n## Examples\n\n### Example 1: Logging review\n\n**User**: \"Is this PCI-DSS compliant: we log the full request body of card authorization calls for debugging?\"\n\n**Skill**: Loads pci-dss.md → Critical findings against 3.3.1 (CVV must never be stored post-authorization — logs are storage), 3.4.1 (PAN display masking), 3.5.1 (PAN unreadable at rest); remediation: remove the log line or apply a field-allowlist redaction filter; flags downstream log-pipeline scoping (10.3.x); QSA disclaimer included.\n\n### Example 2: Cloud migration\n\n**User**: \"Our Singapore bank is moving the customer notification service to a cloud region in another country. MAS TRM implications?\"\n\n**Skill**: Loads mas-trm.md → reviews against §11.5 (cloud: due diligence, data residency, exit strategy), flags the MAS Outsourcing Guidelines as a related instrument, asks what customer data the service touches before rating severity.\n\n## Common FSI Engineering Triggers\n\nChanges that almost always have compliance impact — check proactively when they appear in a diff:\n\n- Logging statements near payment or authentication flows (PAN\u002FCVV must never be logged; MAS TRM requires security event logging — both directions matter)\n- New data stores or caches receiving customer or card data (encryption at rest, retention, residency)\n- Authentication\u002Fsession changes (MFA requirements, session timeout, credential storage)\n- New third-party SDKs or API integrations (outsourcing\u002Fvendor controls, data flows leaving the boundary)\n- Infrastructure changes touching network segmentation, security groups, or public exposure\n- CI\u002FCD changes that alter who\u002Fwhat can deploy to production (change management, segregation of duties)\n\n## Guardrails\n\n- Cite control IDs precisely (e.g. \"PCI-DSS 8.3.6\", \"MAS TRM 9.1.1\") so findings are traceable in audit tooling; the bundled reference files carry the ID schemes.\n- Severity discipline: don't inflate. A missing comment is not a Critical; unencrypted PAN at rest is.\n- When the change is compliant, say so affirmatively per control — \"no findings\" plus the checked-control list is a useful audit artifact.\n- Never output real card numbers, even as examples; use the standard test PANs (e.g. 4111 1111 1111 1111) when illustrating.\n- Read-only: this skill reviews and reports; it never modifies code, infrastructure, or configuration.\n\n## Limitations\n\n- Covers only the bundled PCI-DSS v4.0 and MAS TRM engineering summaries; other frameworks or local policy overlays need separate review.\n- Provides engineering triage, not legal advice, QSA assessment, or formal compliance sign-off.\n- Requires concrete evidence such as diffs, designs, IaC, logs, or control artifacts; incomplete evidence should be marked `Needs evidence`.\n- The bundled references are concise control maps, not substitutes for reading the official standards.\n\n## Credits\n\nAdapted from [timwukp\u002Fagent-skills-best-practice](https:\u002F\u002Fgithub.com\u002Ftimwukp\u002Fagent-skills-best-practice) (MIT), where the skill ships with evals and a documented 4-layer test methodology (see the repo's TESTING.md).\n","# FSI Compliance Checker\n\n## Overview\n\nMaps a concrete change (code diff, architecture design, IaC, pipeline config) to the specific controls it touches in financial services compliance frameworks — PCI-DSS v4.0 for payment card data and MAS TRM for Singapore-regulated institutions — and reports gaps with actionable remediation. This is engineering-level compliance triage: it helps teams catch violations before audit, but it does not replace a qualified assessor (QSA) or the institution's compliance function. Say so in every report.\n\n## When to Use This Skill\n\n- Use when a change touches payment card data (PAN, CVV, track data) and needs a PCI-DSS check\n- Use when reviewing changes at a Singapore-regulated financial institution against MAS TRM expectations\n- Use when someone asks \"is this compliant\", \"does logging this violate PCI\", or requests a banking-regulation review of a diff, design, or Terraform change\n- Do NOT use for generic security review (no framework involved), GDPR\u002FSOC2\u002FHIPAA (out of bundled scope), or legal advice\n\n## How It Works\n\n### Step 1: Select the framework\n\nLoad only the reference file(s) the engagement needs:\n\n| Situation | Load |\n|-----------|------|\n| Payment card data is stored, processed, or transmitted | [pci-dss.md](pci-dss.md) |\n| Singapore-regulated financial institution (bank, insurer, capital markets, major payment institution) | [mas-trm.md](mas-trm.md) |\n| Both apply (e.g. Singapore bank handling cards) | Both files |\n| Other jurisdictions\u002Fframeworks (SOX, GDPR, HKMA, APRA) | State they are out of scope; offer general secure-engineering review instead |\n\nIf the user hasn't said which applies, ask one question: what data does the change touch, and is the institution Singapore-regulated?\n\n### Step 2: Scope the change\n\nIdentify what the diff\u002Fdesign actually touches: data elements (card data? customer PII? credentials?), trust boundaries, environments (production? DR?), and third parties.\n\n### Step 3: Assess applicable controls\n\nSelect the applicable controls from the loaded reference file(s) — typically 5-15 controls, not the whole framework. List what you ruled out and why (one line each) so the scoping is auditable. Assess each as `Compliant` \u002F `Gap` \u002F `Needs evidence` (can't tell from the artifact — name the evidence required).\n\n### Step 4: Report\n\nEvery Gap gets: the control ID, what's wrong in this specific change, concrete remediation, and severity (Critical = violation involving live regulated data; High = control absent; Medium = control partial\u002Fundocumented).\n\n```markdown\n# Compliance Review: [change title]\n**Frameworks:** [PCI-DSS v4.0 \u002F MAS TRM 2021] · **Date:** [YYYY-MM-DD]\n**Scope:** [what was reviewed: files, design doc, pipeline]\n> Engineering triage only — not a substitute for QSA assessment or the compliance function.\n\n## Data & Boundary Analysis\n- Data elements touched: [e.g. PAN (masked), customer NRIC, none]\n- Environments\u002Fboundaries: [e.g. CDE-adjacent service, public API]\n\n## Findings\n| # | Control | Status | Severity | Finding | Remediation |\n|---|---------|--------|----------|---------|-------------|\n| 1 | [PCI 3.5.1] | Gap | Critical | [specific issue in this change] | [specific fix] |\n\n## Ruled Out (not applicable)\n- [Control area] — [one-line reason]\n\n## Evidence Needed\n- [Control]: [what artifact would demonstrate compliance]\n```\n\n### Step 5: Offer story conversion\n\nOffer to turn findings into backlog items with the control ID in each story for traceability.\n\n## Examples\n\n### Example 1: Logging review\n\n**User**: \"Is this PCI-DSS compliant: we log the full request body of card authorization calls for debugging?\"\n\n**Skill**: Loads pci-dss.md → Critical findings against 3.3.1 (CVV must never be stored post-authorization — logs are storage), 3.4.1 (PAN display masking), 3.5.1 (PAN unreadable at rest); remediation: remove the log line or apply a field-allowlist redaction filter; flags downstream log-pipeline scoping (10.3.x); QSA disclaimer included.\n\n### Example 2: Cloud migration\n\n**User**: \"Our Singapore bank is moving the customer notification service to a cloud region in another country. MAS TRM implications?\"\n\n**Skill**: Loads mas-trm.md → reviews against §11.5 (cloud: due diligence, data residency, exit strategy), flags the MAS Outsourcing Guidelines as a related instrument, asks what customer data the service touches before rating severity.\n\n## Common FSI Engineering Triggers\n\nChanges that almost always have compliance impact — check proactively when they appear in a diff:\n\n- Logging statements near payment or authentication flows (PAN\u002FCVV must never be logged; MAS TRM requires security event logging — both directions matter)\n- New data stores or caches receiving customer or card data (encryption at rest, retention, residency)\n- Authentication\u002Fsession changes (MFA requirements, session timeout, credential storage)\n- New third-party SDKs or API integrations (outsourcing\u002Fvendor controls, data flows leaving the boundary)\n- Infrastructure changes touching network segmentation, security groups, or public exposure\n- CI\u002FCD changes that alter who\u002Fwhat can deploy to production (change management, segregation of duties)\n\n## Guardrails\n\n- Cite control IDs precisely (e.g. \"PCI-DSS 8.3.6\", \"MAS TRM 9.1.1\") so findings are traceable in audit tooling; the bundled reference files carry the ID schemes.\n- Severity discipline: don't inflate. A missing comment is not a Critical; unencrypted PAN at rest is.\n- When the change is compliant, say so affirmatively per control — \"no findings\" plus the checked-control list is a useful audit artifact.\n- Never output real card numbers, even as examples; use the standard test PANs (e.g. 4111 1111 1111 1111) when illustrating.\n- Read-only: this skill reviews and reports; it never modifies code, infrastructure, or configuration.\n\n## Limitations\n\n- Covers only the bundled PCI-DSS v4.0 and MAS TRM engineering summaries; other frameworks or local policy overlays need separate review.\n- Provides engineering triage, not legal advice, QSA assessment, or formal compliance sign-off.\n- Requires concrete evidence such as diffs, designs, IaC, logs, or control artifacts; incomplete evidence should be marked `Needs evidence`.\n- The bundled references are concise control maps, not substitutes for reading the official standards.\n\n## Credits\n\nAdapted from [timwukp\u002Fagent-skills-best-practice](https:\u002F\u002Fgithub.com\u002Ftimwukp\u002Fagent-skills-best-practice) (MIT), where the skill ships with evals and a documented 4-layer test methodology (see the repo's TESTING.md).\n",{"name":5,"risk":24,"tags":25,"tools":34,"author":40,"source":41,"license":15,"category":42,"date_added":43,"description":7,"source_repo":44,"source_type":41,"license_source":45},"safe",[26,27,28,29,30,31,32,33],"compliance","pci-dss","mas-trm","fintech","banking","security-review","audit","financial-services",[35,36,37,38,39],"claude","cursor","gemini","codex","antigravity","timwukp","community","security","2026-06-12","timwukp\u002Fagent-skills-best-practice","https:\u002F\u002Fgithub.com\u002Ftimwukp\u002Fagent-skills-best-practice\u002Fblob\u002Fmain\u002FLICENSE","main","c475fc64e94e803b50d14a791dfee8853fbb2c5c","integrations\u002Fantigravity-skills\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Ffsi-compliance-checker","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory","https:\u002F\u002Fgithub.com\u002FElogic360","2026-11-08 22:21:22",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add Elogic360\u002Fsoftware-factory --skill fsi-compliance-checker",{"tool":58,"command":59},"bunx","bunx skills add Elogic360\u002Fsoftware-factory --skill fsi-compliance-checker",{"tool":61,"command":62},"pnpm","pnpm dlx skills add Elogic360\u002Fsoftware-factory --skill fsi-compliance-checker","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fintegrations\u002Fantigravity-skills\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Ffsi-compliance-checker\u002FSKILL.md",true,[66,72],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"mas-trm.md","REFERENCE","参考文档",8125,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fintegrations\u002Fantigravity-skills\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Ffsi-compliance-checker\u002Fmas-trm.md",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"pci-dss.md",6577,"https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fintegrations\u002Fantigravity-skills\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Ffsi-compliance-checker\u002Fpci-dss.md",[77,85,92,99,106,113],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M79G206MT3J6S0GY3C45P2KV","vss-summarize-video","Use to summarize a recorded video via the LVS summarization microservice (HITL-gated) with a VLM fallback. Not for report generation or live RTSP captioning.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-summarize-video\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M79G1WN63PGRE8CKD47WEBQ5","vss-setup-video-analytics-api","Use to deploy the vss-video-analytics-api REST service standalone (config-source, data-log bind, Elasticsearch, optional Kafka). Not for full warehouse deploy.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-setup-video-analytics-api\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M79G1S9F7VY3EF6H53PRP5AN","vss-setup-behavior-analytics","Use to deploy the vss-behavior-analytics service standalone (entrypoint, config-source, optional calibration). Not for the full warehouse deploy.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-setup-behavior-analytics\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M79G1N1S1Y27PFZPYMNK1MTQ","vss-search-archive","Use this skill to run top-level VSS fusion search on archived video, or to ingest video files \u002F RTSP streams for search. Do NOT use for ad-hoc visual Q&A (use vss-ask-video), live captioning (use vss-deploy-dense-captioning), or video summarization and reports (use vss-summarize-video).","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-search-archive\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M79G1H6WN0Q6C0VCAXCZX6B7","vss-query-analytics","Use this skill when reading video-analytics metrics, incidents, alerts, and sensor data via the VA-MCP server (port 9901). Not for live VLM or incident-range narrative reports.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-query-analytics\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":19},"01M79G1DYPNXQS7QHZ0AAF5FX5","vss-manage-video-io-storage","Use to call the VIOS REST API (sensor list, timelines, clip extraction, snapshots, add\u002Fdelete sensors and streams). Not for VLM inference or search.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-manage-video-io-storage\u002FSKILL.md",[],[]]