[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMMQT94V9K02FSAK36WH8P":3,"skill-same:01M7EMMQT94V9K02FSAK36WH8P":47},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EMMQT94V9K02FSAK36WH8P","compliance-mapper",null,"Map security controls across frameworks — one control set satisfying ISO 27001, SOC 2, NIST, PCI DSS, and more.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-compliance-mapper\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: compliance-mapper\ndescription: Map security controls across frameworks — one control set satisfying ISO 27001, SOC 2, NIST, PCI DSS, and more.\ncategory: security\n---\n\n## Overview\n\nMost organizations face multiple compliance frameworks simultaneously — ISO 27001, SOC 2, PCI DSS, NIST CSF, plus sector and regional rules — and auditing each separately multiplies cost and fatigue. Control mapping solves this: build one unified control set, map each control to every framework's requirements, and test once to satisfy many.\n\nThis skill covers building and operating the mapping: framework analysis, unified control design, evidence reuse, and keeping the mapping current as frameworks evolve.\n\nMap to the strongest requirement, not the average: when frameworks differ on a control (e.g., review frequency), implement the strictest version once. A single control that satisfies the toughest framework automatically satisfies the lenient ones — this is where the efficiency comes from.\n\n## When to use\n\n- Facing 2+ frameworks and drowning in duplicate audit work.\n- Building the initial control set for a growing company.\n- Preparing for a new certification while maintaining existing ones.\n- Rationalizing controls after mergers or rapid growth.\n- Responding to customer questionnaires efficiently.\n\n## Core concepts\n\n- **Unified control framework.** One set of controls with clear ownership, each mapped to the relevant clauses of every applicable framework (ISO 27001 Annex A, SOC 2 criteria, PCI DSS requirements, NIST CSF subcategories).\n- **Map once, test once, use many times.** A single test of access reviews produces evidence usable for ISO A.5.17, SOC 2 CC6.2, and PCI DSS 7.x — the mapping is what makes reuse legitimate.\n- **Gap analysis per framework.** The unified set reveals exactly what each new framework adds — usually 10–20% net-new controls, not a whole new program. Scope new certifications precisely.\n- **Authoritative sources.** Use official mappings where they exist (framework crosswalks published by the bodies) and validate custom mappings with auditors before relying on them.\n- **Evidence architecture.** Centralized evidence repository tagged by control — when the SOC 2 auditor asks, you pull the same tested evidence the ISO auditor saw, with the mapping as the bridge.\n- **Framework versioning.** Frameworks update (ISO 27001:2022, PCI DSS v4.0, NIST CSF 2.0) — track versions in the mapping and run delta analyses on each release.\n- **Control inheritance.** Cloud providers and shared services provide some controls (physical security, hypervisor patching) — document inheritance explicitly rather than re-testing what you cannot test.\n\n- **Control inheritance documentation.** For cloud\u002Fshared-service inherited controls, document exactly what is inherited, from whom, and the evidence source — vague inheritance claims fail audits.\n- **Mapping maintenance ownership.** Assign an owner to the mapping itself with a review cadence; unowned mappings rot silently as frameworks evolve.\n\n## Practical workflow\n\n1. **Inventory obligations:** list every framework, regulation, and customer requirement in scope, with versions and audit cycles. This is the demand side.\n2. **Build the unified set:** draft controls covering the union of requirements, mapped clause-by-clause. Start from the strictest requirements; consolidate duplicates ruthlessly.\n3. **Assign ownership and evidence:** every control gets an owner, a defined evidence artifact, and a testing cadence. Unowned controls are unimplemented controls.\n4. **Run gap analyses:** for each framework, show mapped vs missing. New certifications become scoped projects (the 15% delta), not new programs.\n5. **Test once:** execute the control testing program on its own cadence; tag evidence to controls; auditors across frameworks consume the same tested evidence via the mapping.\n6. **Maintain:** update mappings on framework revisions; review control effectiveness annually; prune controls that no framework or risk requires.\n\n### Quick wins\n\n- Pick your two heaviest frameworks and map their overlap this quarter\n- Centralize audit evidence in one tagged repository before the next audit cycle\n- Run a delta analysis on the most recent framework version update\n\n### Sustaining the practice\n\n- Review framework updates within 90 days of publication; run delta mappings\n- Re-validate custom mappings with auditors annually\n- Audit the evidence repository for completeness before each audit cycle\n- Retire controls that have lost their framework or risk justification\n\n### Metrics that prove it works\n\n- Audit effort hours per framework, trending down with reuse\n- % of controls with current, tested evidence\n- Time to onboard a new framework (should shrink with each addition)\n- Audit finding recurrence across frameworks (same root cause, multiple reports)\n\n## Common pitfalls\n\n- **Mapping without testing.** A beautiful spreadsheet of mappings with untested controls is fiction. The mapping's value comes from tested evidence behind it.\n- **Framework-of-the-month controls.** Bolting on controls per audit creates sprawl. Route every new requirement through the unified set first.\n- **Ignoring version drift.** Auditing against ISO 27001:2013 mappings two years after 2022 published. Track versions explicitly.\n- **Over-mapping.** Mapping every control to every framework \"just in case\" creates maintenance hell. Map where genuine overlap exists; keep the rest framework-specific.\n- **No auditor buy-in.** Custom mappings the auditor rejects waste the effort. Validate mapping approaches with auditors early.\n- **Evidence silos.** Each audit team collecting its own evidence destroys the reuse model. Centralize the repository and enforce tagging.\n- **Confusing mapping with compliance.** The map shows coverage; only implemented, tested controls provide it. Report control effectiveness, not mapping completeness.\n- **Static mapping.** Frameworks, products, and risks change. An unmaintained mapping quietly becomes wrong — schedule its maintenance like any control.\n- **Mapping at the wrong granularity.** One-to-one clause mapping where many-to-many is the reality (or vice versa) produces misleading coverage claims. Map honestly.\n- **Letting consultants own the mapping.** External mappings you cannot maintain internally decay the day the engagement ends. Build internal ownership from the start.\n","## Overview\n\nMost organizations face multiple compliance frameworks simultaneously — ISO 27001, SOC 2, PCI DSS, NIST CSF, plus sector and regional rules — and auditing each separately multiplies cost and fatigue. Control mapping solves this: build one unified control set, map each control to every framework's requirements, and test once to satisfy many.\n\nThis skill covers building and operating the mapping: framework analysis, unified control design, evidence reuse, and keeping the mapping current as frameworks evolve.\n\nMap to the strongest requirement, not the average: when frameworks differ on a control (e.g., review frequency), implement the strictest version once. A single control that satisfies the toughest framework automatically satisfies the lenient ones — this is where the efficiency comes from.\n\n## When to use\n\n- Facing 2+ frameworks and drowning in duplicate audit work.\n- Building the initial control set for a growing company.\n- Preparing for a new certification while maintaining existing ones.\n- Rationalizing controls after mergers or rapid growth.\n- Responding to customer questionnaires efficiently.\n\n## Core concepts\n\n- **Unified control framework.** One set of controls with clear ownership, each mapped to the relevant clauses of every applicable framework (ISO 27001 Annex A, SOC 2 criteria, PCI DSS requirements, NIST CSF subcategories).\n- **Map once, test once, use many times.** A single test of access reviews produces evidence usable for ISO A.5.17, SOC 2 CC6.2, and PCI DSS 7.x — the mapping is what makes reuse legitimate.\n- **Gap analysis per framework.** The unified set reveals exactly what each new framework adds — usually 10–20% net-new controls, not a whole new program. Scope new certifications precisely.\n- **Authoritative sources.** Use official mappings where they exist (framework crosswalks published by the bodies) and validate custom mappings with auditors before relying on them.\n- **Evidence architecture.** Centralized evidence repository tagged by control — when the SOC 2 auditor asks, you pull the same tested evidence the ISO auditor saw, with the mapping as the bridge.\n- **Framework versioning.** Frameworks update (ISO 27001:2022, PCI DSS v4.0, NIST CSF 2.0) — track versions in the mapping and run delta analyses on each release.\n- **Control inheritance.** Cloud providers and shared services provide some controls (physical security, hypervisor patching) — document inheritance explicitly rather than re-testing what you cannot test.\n\n- **Control inheritance documentation.** For cloud\u002Fshared-service inherited controls, document exactly what is inherited, from whom, and the evidence source — vague inheritance claims fail audits.\n- **Mapping maintenance ownership.** Assign an owner to the mapping itself with a review cadence; unowned mappings rot silently as frameworks evolve.\n\n## Practical workflow\n\n1. **Inventory obligations:** list every framework, regulation, and customer requirement in scope, with versions and audit cycles. This is the demand side.\n2. **Build the unified set:** draft controls covering the union of requirements, mapped clause-by-clause. Start from the strictest requirements; consolidate duplicates ruthlessly.\n3. **Assign ownership and evidence:** every control gets an owner, a defined evidence artifact, and a testing cadence. Unowned controls are unimplemented controls.\n4. **Run gap analyses:** for each framework, show mapped vs missing. New certifications become scoped projects (the 15% delta), not new programs.\n5. **Test once:** execute the control testing program on its own cadence; tag evidence to controls; auditors across frameworks consume the same tested evidence via the mapping.\n6. **Maintain:** update mappings on framework revisions; review control effectiveness annually; prune controls that no framework or risk requires.\n\n### Quick wins\n\n- Pick your two heaviest frameworks and map their overlap this quarter\n- Centralize audit evidence in one tagged repository before the next audit cycle\n- Run a delta analysis on the most recent framework version update\n\n### Sustaining the practice\n\n- Review framework updates within 90 days of publication; run delta mappings\n- Re-validate custom mappings with auditors annually\n- Audit the evidence repository for completeness before each audit cycle\n- Retire controls that have lost their framework or risk justification\n\n### Metrics that prove it works\n\n- Audit effort hours per framework, trending down with reuse\n- % of controls with current, tested evidence\n- Time to onboard a new framework (should shrink with each addition)\n- Audit finding recurrence across frameworks (same root cause, multiple reports)\n\n## Common pitfalls\n\n- **Mapping without testing.** A beautiful spreadsheet of mappings with untested controls is fiction. The mapping's value comes from tested evidence behind it.\n- **Framework-of-the-month controls.** Bolting on controls per audit creates sprawl. Route every new requirement through the unified set first.\n- **Ignoring version drift.** Auditing against ISO 27001:2013 mappings two years after 2022 published. Track versions explicitly.\n- **Over-mapping.** Mapping every control to every framework \"just in case\" creates maintenance hell. Map where genuine overlap exists; keep the rest framework-specific.\n- **No auditor buy-in.** Custom mappings the auditor rejects waste the effort. Validate mapping approaches with auditors early.\n- **Evidence silos.** Each audit team collecting its own evidence destroys the reuse model. Centralize the repository and enforce tagging.\n- **Confusing mapping with compliance.** The map shows coverage; only implemented, tested controls provide it. Report control effectiveness, not mapping completeness.\n- **Static mapping.** Frameworks, products, and risks change. An unmaintained mapping quietly becomes wrong — schedule its maintenance like any control.\n- **Mapping at the wrong granularity.** One-to-one clause mapping where many-to-many is the reality (or vice versa) produces misleading coverage claims. Map honestly.\n- **Letting consultants own the mapping.** External mappings you cannot maintain internally decay the day the engagement ends. Build internal ownership from the start.\n",{"name":5,"category":24,"description":7},"security","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-compliance-mapper",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill compliance-mapper",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill compliance-mapper",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill compliance-mapper","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-compliance-mapper\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]