{"id":"699f46ca-6e27-4583-a484-dda94d556124","entityType":"agent","slug":"clawhub-harrylabsj-legal-regulatory-compliance-mapper","name":"Legal Regulatory Compliance Mapper","canonicalUrl":"https://www.xpersona.co/agent/clawhub-harrylabsj-legal-regulatory-compliance-mapper","canonicalPath":"/agent/clawhub-harrylabsj-legal-regulatory-compliance-mapper","generatedAt":"2026-10-11T21:00:38.038Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-11T17:08:32.616Z","emptyReason":null},"description":"Provides structured frameworks and checklists to map regulatory obligations, controls, evidence, and review plans for compliance program development. Skill: Legal Regulatory Compliance Mapper Owner: harrylabsj Summary: Provides structured frameworks and checklists to map regulatory obligations, controls, evidence, and review plans for compliance program development. Tags: compliance:1.1.1, latest:1.1.1, legal:1.1.1, operations:1.1.1, regulatory:1.1.1 Version history: v1.1.1 | 2026-06-25T13:24:17.804Z | user Add required compliance matrix columns, verification gaps","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1K downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s17a8m9q4jybb46cv60h4fxard83hmsn:legal-regulatory-compliance-mapper","sourceUrl":"https://clawhub.ai/harrylabsj/legal-regulatory-compliance-mapper","homepage":"https://clawhub.ai/harrylabsj/skills/legal-regulatory-compliance-mapper","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/harrylabsj/legal-regulatory-compliance-mapper","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/harrylabsj/skills/legal-regulatory-compliance-mapper","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":60,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Provides structured frameworks and checklists to map regulatory obligations, controls, evidence, and review plans for compliance program development. Skill: Leg"},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T17:08:32.616Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T17:08:32.616Z","emptyReason":null},"stars":null,"forks":null,"downloads":1021,"likes":null,"task":null,"library":null,"packageName":null,"latestVersion":"1.1.1","tractionLabel":"1K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T17:08:32.604Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T17:08:32.616Z","lastCrawledAt":"2026-10-11T17:08:32.604Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T17:08:32.604Z","lastVerifiedAt":null,"highlights":[{"version":"1.1.1","createdAt":"2026-06-25T13:24:17.804Z","changelog":"Add required compliance matrix columns, verification gaps, and stronger no-invented-citation boundaries.","fileCount":6,"zipByteSize":6816},{"version":"1.0.1","createdAt":"2026-06-21T23:16:44.131Z","changelog":"**Legal Regulatory Compliance Mapper v1.1.0** - Added `tags` field to metadata for better categorization and discovery. - Introduced detailed \"Usage Scenarios\" table with realistic multi-jurisdictional compliance mapping examples. - Included a localized step-by-step scenario for opening a restaurant company in Shanghai. - No changes to workflow or core module structure; package remains descriptive only. - Added `_meta.json` for improved metadata structure.","fileCount":6,"zipByteSize":6303},{"version":"1.0.0","createdAt":"2026-04-26T14:17:00.418Z","changelog":"Initial release: document-only legal workflow skill.","fileCount":5,"zipByteSize":3823}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17a8m9q4jybb46cv60h4fxard83hmsn:legal-regulatory-compliance-mapper","setupComplexity":"low","setupSteps":["Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-harrylabsj-legal-regulatory-compliance-mapper/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-harrylabsj-legal-regulatory-compliance-mapper/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-harrylabsj-legal-regulatory-compliance-mapper/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-harrylabsj-legal-regulatory-compliance-mapper/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-harrylabsj-legal-regulatory-compliance-mapper/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-harrylabsj-legal-regulatory-compliance-mapper/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-11T21:00:38.037Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-harrylabsj-legal-regulatory-compliance-mapper/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-harrylabsj-legal-regulatory-compliance-mapper/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-harrylabsj-legal-regulatory-compliance-mapper/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-harrylabsj-legal-regulatory-compliance-mapper/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-11T17:08:32.616Z","emptyReason":null},"readme":"Skill: Legal Regulatory Compliance Mapper\n\nOwner: harrylabsj\n\nSummary: Provides structured frameworks and checklists to map regulatory obligations, controls, evidence, and review plans for compliance program development.\n\nTags: compliance:1.1.1, latest:1.1.1, legal:1.1.1, operations:1.1.1, regulatory:1.1.1\n\nVersion history:\n\nv1.1.1 | 2026-06-25T13:24:17.804Z | user\n\nAdd required compliance matrix columns, verification gaps, and stronger no-invented-citation boundaries.\n\nv1.0.1 | 2026-06-21T23:16:44.131Z | auto\n\n**Legal Regulatory Compliance Mapper v1.1.0**\n\n- Added `tags` field to metadata for better categorization and discovery.\n- Introduced detailed \"Usage Scenarios\" table with realistic multi-jurisdictional compliance mapping examples.\n- Included a localized step-by-step scenario for opening a restaurant company in Shanghai.\n- No changes to workflow or core module structure; package remains descriptive only.\n- Added `_meta.json` for improved metadata structure.\n\nv1.0.0 | 2026-04-26T14:17:00.418Z | user\n\nInitial release: document-only legal workflow skill.\n\nArchive index:\n\nArchive v1.1.1: 6 files, 6816 bytes\n\nFiles: _meta.json (153b), ACCEPTANCE.md (796b), README.md (1252b), skill-card.md (2140b), skill.json (860b), SKILL.md (7146b)\n\nFile v1.1.1:SKILL.md\n\n---\nslug: legal-regulatory-compliance-mapper\nversion: 1.1.1\ntype: descriptive\nlanguage: en\ntags: compliance, regulatory-mapping, legal-operations, multi-jurisdiction\n---\n\n# Legal Regulatory Compliance Mapper\n\n## Overview\n\nHelps map regulatory obligations, controls, owners, evidence, and review cadence for a product, business unit, or jurisdiction. This is a descriptive OpenClaw skill for legal-industry workflow support. It provides structured frameworks, checklists, templates, and issue-spotting prompts. It does not execute code, call external APIs, access legal databases, retrieve court records, automate filings, or perform legal services.\n\n## When to Use\n\n- Building a compliance program\n- Entering a regulated market\n- Preparing an internal audit\n\n\n## Target Users\n\n- Compliance counsel\n- In-house legal teams\n- Risk managers\n- Startup operators\n\n\n## Inputs to Collect\n\n- Matter or project context, including jurisdiction if known\n- Relevant facts, documents, parties, dates, and constraints\n- Desired output format, audience, and level of detail\n- Known deadlines, risk concerns, or review priorities\n\n## Core Modules\n\n1. **Regulatory obligation inventory** — provides structured prompts, checklists, and review fields for this area.\n2. **Control-owner mapping** — provides structured prompts, checklists, and review fields for this area.\n3. **Evidence and documentation tracker** — provides structured prompts, checklists, and review fields for this area.\n4. **Review cadence planner** — provides structured prompts, checklists, and review fields for this area.\n5. **Issue escalation matrix** — provides structured prompts, checklists, and review fields for this area.\n\n## Workflow\n\n1. Confirm the user's legal workflow goal and the relevant practice context.\n2. Ask for missing facts, documents, dates, parties, jurisdiction, and audience where needed.\n3. Apply the modules below as a structured thinking framework.\n4. Produce checklists, templates, matrices, memos, or planning aids tailored to the user's context.\n5. Flag uncertainty, verification needs, deadlines, ethics concerns, confidentiality issues, and attorney-review points.\n6. Label every obligation row with jurisdiction, source basis, verification status, owner, evidence, review cadence, and attorney-review trigger.\n\n## Expected Outputs\n\n- Compliance obligation map\n- Controls tracker\n- Evidence checklist\n- Review calendar\n- Verification gap list\n\n## Required Output Columns\n\nWhen producing a matrix, include these columns unless the user asks for a shorter\nformat:\n\n| Column | Purpose |\n|---|---|\n| Jurisdiction | Country/state/region or \"unknown\" |\n| Obligation / Issue | The compliance topic to verify |\n| Source basis | User-provided source, known framework, or \"needs authoritative source\" |\n| Verification status | confirmed by user / likely / unknown / needs counsel |\n| Owner | Business, legal, compliance, product, security, or other owner |\n| Evidence | Document, control, filing, policy, log, or artifact to retain |\n| Review cadence | One-time, launch gate, monthly, quarterly, annual, event-driven |\n| Attorney-review trigger | Why qualified counsel should review |\n\n## Example Prompts\n\n- \"Map compliance obligations for a fintech product launch.\"\n- \"Create a regulatory controls tracker for a healthcare startup.\"\n\n## Safety and Legal Limitations\n\n- This skill provides informational workflow support only and is not legal advice.\n- It does not create an attorney-client relationship and does not replace review by a qualified attorney.\n- Laws, court rules, deadlines, ethics duties, privilege, confidentiality, and professional responsibility rules vary by jurisdiction and matter.\n- Users must verify all legal authorities, filing requirements, deadlines, facts, citations, and strategic decisions with qualified counsel.\n- The skill must not be used to fabricate evidence, coach false testimony, evade regulation, access data unlawfully, or bypass confidentiality obligations.\n- Specific limitation for this skill: Does not determine full legal compliance; users must confirm obligations with qualified jurisdiction-specific professionals.\n- Do not invent citations, filing deadlines, regulator names, thresholds, or license requirements. If the user has not provided an authoritative source, mark the item as a verification gap.\n\n## Acceptance Criteria\n\n- Package is descriptive only: no handler.py, scripts, external APIs, network calls, or command execution.\n- SKILL.md and README.md are English-first and include an explicit legal-information disclaimer.\n- Outputs are frameworks, checklists, templates, or planning aids rather than legal conclusions.\n- Includes target users, when-to-use guidance, inputs, workflow, outputs, examples, and safety limitations.\n- skill.json contains unique slug, tags, trigger keywords, requires_api=false, and readiness=stable.\n- Matrices include jurisdiction, source basis, verification status, evidence, cadence, and attorney-review trigger.\n\n\n## Usage Scenarios\n\n| # | User Input | Expected Output |\n|---|---|---|\n| 1 | \"Map the regulatory requirements for a fintech offering BNPL services in the US, UK, and Australia.\" | Jurisdiction comparison matrix: US (state-level lender licenses, CFPB oversight, TILA disclosure), UK (FCA authorization, Consumer Duty, CONC rules), Australia (ASIC credit license, NCCP Act, DDO). Color-coded: harmonized (AML/KYC), divergent (rate-cap rules), missing (Australian BNPR code pending). |\n| 2 | \"We are compliant in the EU. What additional requirements apply if we add Singapore?\" | Delta analysis: additional requirements (MAS licensing for payment services, PDPA data-protection obligations, Singapore-specific consumer-protection guidelines). Implementation roadmap with 90-day timeline. |\n| 3 | \"Generate a compliance calendar with all filing deadlines, renewal dates, and audit requirements across our 5 operating countries.\" | Annual calendar: Q1 (US annual report, EU DPO review), Q2 (UK FCA renewal, AU ASIC levy), Q3 (SG MAS quarterly return), Q4 (US state license renewals, EU SCC review). Deadline-alert settings and document-prep checklists per event. |\n\n\n### Scenario 2: 开公司要办什么证\n**User input:** \"我想在上海注册一家餐饮公司，但搞不清楚要办哪些许可证、怎么办、找谁办。能帮我梳理一下流程吗？\"\n**Expected output:** 上海餐饮公司开办证照流程——第一步：营业执照（去上海市市场监督管理局网站/一网通办线上申请，经营范围写\"餐饮服务\"\"食品销售\"，约3-5个工作日）；第二步：食品经营许可证（拿到营业执照后申请，需要场地平面图+食品安全管理制度+健康证，15个工作日）；第三步：消防安全检查合格证（消防部门实地检查后才发，50-200平方米的餐饮店必须通过）；第四步：环境影响登记表（环保局备案，网上填表即可）；第五步：税务登记（拿到营业执照后30天内办好，在一网通办上就能一起办）。总流程约45-60天。关键工具：上海一网通办（zwdt.sh.gov.cn）+各区行政服务中心现场咨询。\n\nFile v1.1.1:README.md\n\n# Legal Regulatory Compliance Mapper\n\nHelps map regulatory obligations, controls, owners, evidence, and review cadence for a product, business unit, or jurisdiction.\n\n## What This Skill Does\n\nThis document-only legal workflow skill helps users structure their thinking and deliverables using checklists, templates, matrices, and planning prompts. It is designed for lawyers, legal operations teams, paralegals, and adjacent professionals who need repeatable workflows without code execution.\n\n## Core Modules\n\n- Regulatory obligation inventory\n- Control-owner mapping\n- Evidence and documentation tracker\n- Review cadence planner\n- Issue escalation matrix\n\n## Trigger Keywords\n\nregulatory compliance, obligation map, controls tracker, compliance program, legal-regulatory-compliance-mapper, legal regulatory compliance mapper\n\n## Example Prompts\n\n- \"Map compliance obligations for a fintech product launch.\"\n- \"Create a regulatory controls tracker for a healthcare startup.\"\n\n## Outputs\n\n- Compliance obligation map\n- Controls tracker\n- Evidence checklist\n- Review calendar\n\n\n## Safety\n\nInformational support only. Not legal advice. Does not replace qualified attorney review, jurisdiction-specific research, ethics analysis, or professional judgment.\n\nFile v1.1.1:_meta.json\n\n{\n  \"ownerId\": \"kn77zzg9p845zanvy6vrf76k7d81mcnm\",\n  \"slug\": \"legal-regulatory-compliance-mapper\",\n  \"version\": \"1.1.1\",\n  \"publishedAt\": 1782393857804\n}\n\nFile v1.1.1:ACCEPTANCE.md\n\n# Acceptance Criteria\n\n1. Package is descriptive only: no handler.py, scripts, external APIs, network calls, or command execution.\n2. SKILL.md and README.md are English-first and include an explicit legal-information disclaimer.\n3. Outputs are frameworks, checklists, templates, or planning aids rather than legal conclusions.\n4. Includes target users, when-to-use guidance, inputs, workflow, outputs, examples, and safety limitations.\n5. skill.json contains unique slug, tags, trigger keywords, requires_api=false, and readiness=stable.\n\n## Package Rules\n\n- Allowed files: SKILL.md, README.md, skill.json, ACCEPTANCE.md.\n- Forbidden files: handler.py, scripts, tests, binaries, credentials, generated caches, or workspace artifacts.\n- The package must remain descriptive-only and English-first.\n\nFile v1.1.1:skill-card.md\n\n## Description:\n\nHelps map regulatory obligations, controls, owners, evidence, review cadence, verification gaps, and attorney-review triggers for a product, business unit, or jurisdiction.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[harrylabsj](https://clawhub.ai/user/harrylabsj)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nCompliance counsel, in-house legal teams, risk managers, legal operations teams, paralegals, and startup operators use this skill to structure compliance obligation maps, controls trackers, evidence checklists, review calendars, and verification gap lists.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Users may over-rely on sample jurisdiction-specific legal outputs, obligations, regulator names, or deadlines.\n\nMitigation: Require authoritative sources and qualified counsel for every jurisdiction-specific obligation, filing deadline, license, regulator, and timeline.\n\nRisk: Unverified legal requirements could be treated as confirmed compliance guidance.\n\nMitigation: Mark unsupported items as verification gaps and include attorney-review triggers before using outputs for decisions.\n\n## Reference(s):\n\n- [Skill documentation](artifact/SKILL.md)\n- [README](artifact/README.md)\n- [Acceptance criteria](artifact/ACCEPTANCE.md)\n- [ClawHub skill page](https://clawhub.ai/harrylabsj/skills/legal-regulatory-compliance-mapper)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, guidance]\n\n**Output Format:** [Markdown checklists, matrices, trackers, calendars, templates, and planning aids]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Document-only legal workflow support; no API calls, external database retrieval, filings, or legal services.]\n\n## Skill Version(s):\n\n1.1.1 (source: SKILL.md frontmatter, skill.json, server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nFile v1.1.1:skill.json\n\n{\n  \"name\": \"Legal Regulatory Compliance Mapper\",\n  \"slug\": \"legal-regulatory-compliance-mapper\",\n  \"version\": \"1.1.1\",\n  \"description\": \"Helps map regulatory obligations, controls, owners, evidence, review cadence, verification gaps, and attorney-review triggers for a product, business unit, or jurisdiction.\",\n  \"author\": \"Pearl Team (OpenClaw)\",\n  \"tags\": [\n    \"legal\",\n    \"compliance\",\n    \"regulatory\",\n    \"risk\",\n    \"descriptive\"\n  ],\n  \"trigger_keywords\": [\n    \"regulatory compliance\",\n    \"obligation map\",\n    \"controls tracker\",\n    \"compliance program\",\n    \"legal-regulatory-compliance-mapper\",\n    \"legal regulatory compliance mapper\"\n  ],\n  \"language\": \"en\",\n  \"outputs\": \"markdown\",\n  \"requires_api\": false,\n  \"readiness\": \"stable\",\n  \"type\": \"descriptive\",\n  \"legal_disclaimer\": \"Informational workflow support only; not legal advice.\"\n}\n\nArchive v1.0.1: 6 files, 6303 bytes\n\nFiles: _meta.json (153b), ACCEPTANCE.md (796b), README.md (1252b), skill-card.md (2145b), skill.json (815b), SKILL.md (5938b)\n\nFile v1.0.1:SKILL.md\n\n---\nslug: legal-regulatory-compliance-mapper\nversion: 1.1.0\ntype: descriptive\nlanguage: en\ntags: compliance, regulatory-mapping, legal-operations, multi-jurisdiction\n---\n\n# Legal Regulatory Compliance Mapper\n\n## Overview\n\nHelps map regulatory obligations, controls, owners, evidence, and review cadence for a product, business unit, or jurisdiction. This is a descriptive OpenClaw skill for legal-industry workflow support. It provides structured frameworks, checklists, templates, and issue-spotting prompts. It does not execute code, call external APIs, access legal databases, retrieve court records, automate filings, or perform legal services.\n\n## When to Use\n\n- Building a compliance program\n- Entering a regulated market\n- Preparing an internal audit\n\n\n## Target Users\n\n- Compliance counsel\n- In-house legal teams\n- Risk managers\n- Startup operators\n\n\n## Inputs to Collect\n\n- Matter or project context, including jurisdiction if known\n- Relevant facts, documents, parties, dates, and constraints\n- Desired output format, audience, and level of detail\n- Known deadlines, risk concerns, or review priorities\n\n## Core Modules\n\n1. **Regulatory obligation inventory** — provides structured prompts, checklists, and review fields for this area.\n2. **Control-owner mapping** — provides structured prompts, checklists, and review fields for this area.\n3. **Evidence and documentation tracker** — provides structured prompts, checklists, and review fields for this area.\n4. **Review cadence planner** — provides structured prompts, checklists, and review fields for this area.\n5. **Issue escalation matrix** — provides structured prompts, checklists, and review fields for this area.\n\n## Workflow\n\n1. Confirm the user's legal workflow goal and the relevant practice context.\n2. Ask for missing facts, documents, dates, parties, jurisdiction, and audience where needed.\n3. Apply the modules below as a structured thinking framework.\n4. Produce checklists, templates, matrices, memos, or planning aids tailored to the user's context.\n5. Flag uncertainty, verification needs, deadlines, ethics concerns, confidentiality issues, and attorney-review points.\n\n## Expected Outputs\n\n- Compliance obligation map\n- Controls tracker\n- Evidence checklist\n- Review calendar\n\n## Example Prompts\n\n- \"Map compliance obligations for a fintech product launch.\"\n- \"Create a regulatory controls tracker for a healthcare startup.\"\n\n## Safety and Legal Limitations\n\n- This skill provides informational workflow support only and is not legal advice.\n- It does not create an attorney-client relationship and does not replace review by a qualified attorney.\n- Laws, court rules, deadlines, ethics duties, privilege, confidentiality, and professional responsibility rules vary by jurisdiction and matter.\n- Users must verify all legal authorities, filing requirements, deadlines, facts, citations, and strategic decisions with qualified counsel.\n- The skill must not be used to fabricate evidence, coach false testimony, evade regulation, access data unlawfully, or bypass confidentiality obligations.\n- Specific limitation for this skill: Does not determine full legal compliance; users must confirm obligations with qualified jurisdiction-specific professionals.\n\n## Acceptance Criteria\n\n- Package is descriptive only: no handler.py, scripts, external APIs, network calls, or command execution.\n- SKILL.md and README.md are English-first and include an explicit legal-information disclaimer.\n- Outputs are frameworks, checklists, templates, or planning aids rather than legal conclusions.\n- Includes target users, when-to-use guidance, inputs, workflow, outputs, examples, and safety limitations.\n- skill.json contains unique slug, tags, trigger keywords, requires_api=false, and readiness=stable.\n\n\n## Usage Scenarios\n\n| # | User Input | Expected Output |\n|---|---|---|\n| 1 | \"Map the regulatory requirements for a fintech offering BNPL services in the US, UK, and Australia.\" | Jurisdiction comparison matrix: US (state-level lender licenses, CFPB oversight, TILA disclosure), UK (FCA authorization, Consumer Duty, CONC rules), Australia (ASIC credit license, NCCP Act, DDO). Color-coded: harmonized (AML/KYC), divergent (rate-cap rules), missing (Australian BNPR code pending). |\n| 2 | \"We are compliant in the EU. What additional requirements apply if we add Singapore?\" | Delta analysis: additional requirements (MAS licensing for payment services, PDPA data-protection obligations, Singapore-specific consumer-protection guidelines). Implementation roadmap with 90-day timeline. |\n| 3 | \"Generate a compliance calendar with all filing deadlines, renewal dates, and audit requirements across our 5 operating countries.\" | Annual calendar: Q1 (US annual report, EU DPO review), Q2 (UK FCA renewal, AU ASIC levy), Q3 (SG MAS quarterly return), Q4 (US state license renewals, EU SCC review). Deadline-alert settings and document-prep checklists per event. |\n\n\n### Scenario 2: 开公司要办什么证\n**User input:** \"我想在上海注册一家餐饮公司，但搞不清楚要办哪些许可证、怎么办、找谁办。能帮我梳理一下流程吗？\"\n**Expected output:** 上海餐饮公司开办证照流程——第一步：营业执照（去上海市市场监督管理局网站/一网通办线上申请，经营范围写\"餐饮服务\"\"食品销售\"，约3-5个工作日）；第二步：食品经营许可证（拿到营业执照后申请，需要场地平面图+食品安全管理制度+健康证，15个工作日）；第三步：消防安全检查合格证（消防部门实地检查后才发，50-200平方米的餐饮店必须通过）；第四步：环境影响登记表（环保局备案，网上填表即可）；第五步：税务登记（拿到营业执照后30天内办好，在一网通办上就能一起办）。总流程约45-60天。关键工具：上海一网通办（zwdt.sh.gov.cn）+各区行政服务中心现场咨询。\n\nFile v1.0.1:README.md\n\n# Legal Regulatory Compliance Mapper\n\nHelps map regulatory obligations, controls, owners, evidence, and review cadence for a product, business unit, or jurisdiction.\n\n## What This Skill Does\n\nThis document-only legal workflow skill helps users structure their thinking and deliverables using checklists, templates, matrices, and planning prompts. It is designed for lawyers, legal operations teams, paralegals, and adjacent professionals who need repeatable workflows without code execution.\n\n## Core Modules\n\n- Regulatory obligation inventory\n- Control-owner mapping\n- Evidence and documentation tracker\n- Review cadence planner\n- Issue escalation matrix\n\n## Trigger Keywords\n\nregulatory compliance, obligation map, controls tracker, compliance program, legal-regulatory-compliance-mapper, legal regulatory compliance mapper\n\n## Example Prompts\n\n- \"Map compliance obligations for a fintech product launch.\"\n- \"Create a regulatory controls tracker for a healthcare startup.\"\n\n## Outputs\n\n- Compliance obligation map\n- Controls tracker\n- Evidence checklist\n- Review calendar\n\n\n## Safety\n\nInformational support only. Not legal advice. Does not replace qualified attorney review, jurisdiction-specific research, ethics analysis, or professional judgment.\n\nFile v1.0.1:_meta.json\n\n{\n  \"ownerId\": \"kn77zzg9p845zanvy6vrf76k7d81mcnm\",\n  \"slug\": \"legal-regulatory-compliance-mapper\",\n  \"version\": \"1.0.1\",\n  \"publishedAt\": 1782083804131\n}\n\nFile v1.0.1:ACCEPTANCE.md\n\n# Acceptance Criteria\n\n1. Package is descriptive only: no handler.py, scripts, external APIs, network calls, or command execution.\n2. SKILL.md and README.md are English-first and include an explicit legal-information disclaimer.\n3. Outputs are frameworks, checklists, templates, or planning aids rather than legal conclusions.\n4. Includes target users, when-to-use guidance, inputs, workflow, outputs, examples, and safety limitations.\n5. skill.json contains unique slug, tags, trigger keywords, requires_api=false, and readiness=stable.\n\n## Package Rules\n\n- Allowed files: SKILL.md, README.md, skill.json, ACCEPTANCE.md.\n- Forbidden files: handler.py, scripts, tests, binaries, credentials, generated caches, or workspace artifacts.\n- The package must remain descriptive-only and English-first.\n\nFile v1.0.1:skill-card.md\n\n## Description: <br>\nProvides structured frameworks and checklists to map regulatory obligations, controls, evidence, and review plans for compliance program development. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[harrylabsj](https://clawhub.ai/user/harrylabsj) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nCompliance counsel, in-house legal teams, risk managers, and operators use this skill to structure compliance obligation maps, control trackers, evidence checklists, and review calendars for products, business units, or jurisdictions. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Users may treat generated compliance maps, license lists, or deadlines as legal advice or current jurisdiction-specific requirements. <br>\nMitigation: Verify all jurisdiction-specific requirements, deadlines, permits, licenses, and filing obligations with qualified local counsel or official sources before relying on them. <br>\nRisk: Incomplete facts or missing jurisdictional context can produce misleading planning aids. <br>\nMitigation: Collect matter context, relevant facts, documents, dates, constraints, and the intended audience before using outputs for compliance planning. <br>\n\n\n## Reference(s): <br>\n- [ClawHub skill page](https://clawhub.ai/harrylabsj/legal-regulatory-compliance-mapper) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, guidance] <br>\n**Output Format:** [Markdown checklists, matrices, calendars, templates, and planning aids] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Descriptive only; no code execution, external API calls, legal database access, court record retrieval, or filing automation.] <br>\n\n## Skill Version(s): <br>\n1.0.1 (source: ClawHub release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nFile v1.0.1:skill.json\n\n{\n  \"name\": \"Legal Regulatory Compliance Mapper\",\n  \"slug\": \"legal-regulatory-compliance-mapper\",\n  \"version\": \"1.0.0\",\n  \"description\": \"Helps map regulatory obligations, controls, owners, evidence, and review cadence for a product, business unit, or jurisdiction.\",\n  \"author\": \"Pearl Team (OpenClaw)\",\n  \"tags\": [\n    \"legal\",\n    \"compliance\",\n    \"regulatory\",\n    \"risk\",\n    \"descriptive\"\n  ],\n  \"trigger_keywords\": [\n    \"regulatory compliance\",\n    \"obligation map\",\n    \"controls tracker\",\n    \"compliance program\",\n    \"legal-regulatory-compliance-mapper\",\n    \"legal regulatory compliance mapper\"\n  ],\n  \"language\": \"en\",\n  \"outputs\": \"markdown\",\n  \"requires_api\": false,\n  \"readiness\": \"stable\",\n  \"type\": \"descriptive\",\n  \"legal_disclaimer\": \"Informational workflow support only; not legal advice.\"\n}\n\nArchive v1.0.0: 5 files, 3823 bytes\n\nFiles: ACCEPTANCE.md (796b), README.md (1252b), skill.json (815b), SKILL.md (3709b), _meta.json (153b)\n\nFile v1.0.0:SKILL.md\n\n---\nslug: legal-regulatory-compliance-mapper\nversion: \"1.0.0\"\ntype: descriptive\nlanguage: en\n---\n\n# Legal Regulatory Compliance Mapper\n\n## Overview\n\nHelps map regulatory obligations, controls, owners, evidence, and review cadence for a product, business unit, or jurisdiction. This is a descriptive OpenClaw skill for legal-industry workflow support. It provides structured frameworks, checklists, templates, and issue-spotting prompts. It does not execute code, call external APIs, access legal databases, retrieve court records, automate filings, or perform legal services.\n\n## When to Use\n\n- Building a compliance program\n- Entering a regulated market\n- Preparing an internal audit\n\n\n## Target Users\n\n- Compliance counsel\n- In-house legal teams\n- Risk managers\n- Startup operators\n\n\n## Inputs to Collect\n\n- Matter or project context, including jurisdiction if known\n- Relevant facts, documents, parties, dates, and constraints\n- Desired output format, audience, and level of detail\n- Known deadlines, risk concerns, or review priorities\n\n## Core Modules\n\n1. **Regulatory obligation inventory** — provides structured prompts, checklists, and review fields for this area.\n2. **Control-owner mapping** — provides structured prompts, checklists, and review fields for this area.\n3. **Evidence and documentation tracker** — provides structured prompts, checklists, and review fields for this area.\n4. **Review cadence planner** — provides structured prompts, checklists, and review fields for this area.\n5. **Issue escalation matrix** — provides structured prompts, checklists, and review fields for this area.\n\n## Workflow\n\n1. Confirm the user's legal workflow goal and the relevant practice context.\n2. Ask for missing facts, documents, dates, parties, jurisdiction, and audience where needed.\n3. Apply the modules below as a structured thinking framework.\n4. Produce checklists, templates, matrices, memos, or planning aids tailored to the user's context.\n5. Flag uncertainty, verification needs, deadlines, ethics concerns, confidentiality issues, and attorney-review points.\n\n## Expected Outputs\n\n- Compliance obligation map\n- Controls tracker\n- Evidence checklist\n- Review calendar\n\n## Example Prompts\n\n- \"Map compliance obligations for a fintech product launch.\"\n- \"Create a regulatory controls tracker for a healthcare startup.\"\n\n## Safety and Legal Limitations\n\n- This skill provides informational workflow support only and is not legal advice.\n- It does not create an attorney-client relationship and does not replace review by a qualified attorney.\n- Laws, court rules, deadlines, ethics duties, privilege, confidentiality, and professional responsibility rules vary by jurisdiction and matter.\n- Users must verify all legal authorities, filing requirements, deadlines, facts, citations, and strategic decisions with qualified counsel.\n- The skill must not be used to fabricate evidence, coach false testimony, evade regulation, access data unlawfully, or bypass confidentiality obligations.\n- Specific limitation for this skill: Does not determine full legal compliance; users must confirm obligations with qualified jurisdiction-specific professionals.\n\n## Acceptance Criteria\n\n- Package is descriptive only: no handler.py, scripts, external APIs, network calls, or command execution.\n- SKILL.md and README.md are English-first and include an explicit legal-information disclaimer.\n- Outputs are frameworks, checklists, templates, or planning aids rather than legal conclusions.\n- Includes target users, when-to-use guidance, inputs, workflow, outputs, examples, and safety limitations.\n- skill.json contains unique slug, tags, trigger keywords, requires_api=false, and readiness=stable.\n\nFile v1.0.0:README.md\n\n# Legal Regulatory Compliance Mapper\n\nHelps map regulatory obligations, controls, owners, evidence, and review cadence for a product, business unit, or jurisdiction.\n\n## What This Skill Does\n\nThis document-only legal workflow skill helps users structure their thinking and deliverables using checklists, templates, matrices, and planning prompts. It is designed for lawyers, legal operations teams, paralegals, and adjacent professionals who need repeatable workflows without code execution.\n\n## Core Modules\n\n- Regulatory obligation inventory\n- Control-owner mapping\n- Evidence and documentation tracker\n- Review cadence planner\n- Issue escalation matrix\n\n## Trigger Keywords\n\nregulatory compliance, obligation map, controls tracker, compliance program, legal-regulatory-compliance-mapper, legal regulatory compliance mapper\n\n## Example Prompts\n\n- \"Map compliance obligations for a fintech product launch.\"\n- \"Create a regulatory controls tracker for a healthcare startup.\"\n\n## Outputs\n\n- Compliance obligation map\n- Controls tracker\n- Evidence checklist\n- Review calendar\n\n\n## Safety\n\nInformational support only. Not legal advice. Does not replace qualified attorney review, jurisdiction-specific research, ethics analysis, or professional judgment.\n\nFile v1.0.0:_meta.json\n\n{\n  \"ownerId\": \"kn77zzg9p845zanvy6vrf76k7d81mcnm\",\n  \"slug\": \"legal-regulatory-compliance-mapper\",\n  \"version\": \"1.0.0\",\n  \"publishedAt\": 1777213020418\n}\n\nFile v1.0.0:ACCEPTANCE.md\n\n# Acceptance Criteria\n\n1. Package is descriptive only: no handler.py, scripts, external APIs, network calls, or command execution.\n2. SKILL.md and README.md are English-first and include an explicit legal-information disclaimer.\n3. Outputs are frameworks, checklists, templates, or planning aids rather than legal conclusions.\n4. Includes target users, when-to-use guidance, inputs, workflow, outputs, examples, and safety limitations.\n5. skill.json contains unique slug, tags, trigger keywords, requires_api=false, and readiness=stable.\n\n## Package Rules\n\n- Allowed files: SKILL.md, README.md, skill.json, ACCEPTANCE.md.\n- Forbidden files: handler.py, scripts, tests, binaries, credentials, generated caches, or workspace artifacts.\n- The package must remain descriptive-only and English-first.\n\nFile v1.0.0:skill.json\n\n{\n  \"name\": \"Legal Regulatory Compliance Mapper\",\n  \"slug\": \"legal-regulatory-compliance-mapper\",\n  \"version\": \"1.0.0\",\n  \"description\": \"Helps map regulatory obligations, controls, owners, evidence, and review cadence for a product, business unit, or jurisdiction.\",\n  \"author\": \"Pearl Team (OpenClaw)\",\n  \"tags\": [\n    \"legal\",\n    \"compliance\",\n    \"regulatory\",\n    \"risk\",\n    \"descriptive\"\n  ],\n  \"trigger_keywords\": [\n    \"regulatory compliance\",\n    \"obligation map\",\n    \"controls tracker\",\n    \"compliance program\",\n    \"legal-regulatory-compliance-mapper\",\n    \"legal regulatory compliance mapper\"\n  ],\n  \"language\": \"en\",\n  \"outputs\": \"markdown\",\n  \"requires_api\": false,\n  \"readiness\": \"stable\",\n  \"type\": \"descriptive\",\n  \"legal_disclaimer\": \"Informational workflow support only; not legal advice.\"\n}","readmeExcerpt":"Skill: Legal Regulatory Compliance Mapper Owner: harrylabsj Summary: Provides structured frameworks and checklists to map regulatory obligations, controls, evidence, and review plans for compliance program development. Tags: compliance:1.1.1, latest:1.1.1, legal:1.1.1, operations:1.1.1, regulatory:1.1.1 Version history: v1.1.1 | 2026-06-25T13:24:17.804Z | user Add required compliance matrix columns, verification gaps","codeSnippets":[],"executableExamples":[],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nslug: legal-regulatory-compliance-mapper\nversion: 1.1.1\ntype: descriptive\nlanguage: en\ntags: compliance, regulatory-mapping, legal-operations, multi-jurisdiction\n---\n\n# Legal Regulatory Compliance Mapper\n\n## Overview\n\nHelps map regulatory obligations, controls, owners, evidence, and review cadence for a product, business unit, or jurisdiction. This is a descriptive OpenClaw skill for legal-industry workflow support. It provides structured frameworks, checklists, templates, and issue-spotting prompts. It does not execute code, call external APIs, access legal databases, retrieve court records, automate filings, or perform legal services.\n\n## When to Use\n\n- Building a compliance program\n- Entering a regulated market\n- Preparing an internal audit\n\n\n## Target Users\n\n- Compliance counsel\n- In-house legal teams\n- Risk managers\n- Startup operators\n\n\n## Inputs to Collect\n\n- Matter or project context, including jurisdiction if known\n- Relevant facts, documents, parties, dates, and constraints\n- Desired output format, audience, and level of detail\n- Known deadlines, risk concerns, or review priorities\n\n## Core Modules\n\n1. **Regulatory obligation inventory** — provides structured prompts, checklists, and review fields for this area.\n2. **Control-owner mapping** — provides structured prompts, checklists, and review fields for this area.\n3. **Evidence and documentation tracker** — provides structured prompts, checklists, and review fields for this area.\n4. **Review cadence planner** — provides structured prompts, checklists, and review fields for this area.\n5. **Issue escalation matrix** — provides structured prompts, checklists, and review fields for this area.\n\n## Workflow\n\n1. Confirm the user's legal workflow goal and the relevant practice context.\n2. Ask for missing facts, documents, dates, parties, jurisdiction, and audience where needed.\n3. Apply the modules below as a structured thinking framework.\n4. Produce checklists, templates, matrices, memos, or planning aids tailored to the user's context.\n5. Flag uncertainty, verification needs, deadlines, ethics concerns, confidentiality issues, and attorney-review points.\n6. Label every obligation row with jurisdiction, source basis, verification status, owner, evidence, review cadence, and attorney-review trigger.\n\n## Expected Outputs\n\n- Compliance obligation map\n- Controls tracker\n- Evidence checklist\n- Review calendar\n- Verification gap list\n\n## Required Output Columns\n\nWhen producing a matrix, include these columns unless the user asks for a shorter\nformat:\n\n| Column | Purpose |\n|---|---|\n| Jurisdiction | Country/state/region or \"unknown\" |\n| Obligation / Issue | The compliance topic to verify |\n| Source basis | User-provided source, known framework, or \"needs authoritative source\" |\n| Verification status | confirmed by user / likely / unknown / needs counsel |\n| Owner | Business, legal, compliance, product, security, or other owner |\n| Evidence | Document, control, filing, policy, log, or artifact to"},{"path":"README.md","content":"# Legal Regulatory Compliance Mapper\n\nHelps map regulatory obligations, controls, owners, evidence, and review cadence for a product, business unit, or jurisdiction.\n\n## What This Skill Does\n\nThis document-only legal workflow skill helps users structure their thinking and deliverables using checklists, templates, matrices, and planning prompts. It is designed for lawyers, legal operations teams, paralegals, and adjacent professionals who need repeatable workflows without code execution.\n\n## Core Modules\n\n- Regulatory obligation inventory\n- Control-owner mapping\n- Evidence and documentation tracker\n- Review cadence planner\n- Issue escalation matrix\n\n## Trigger Keywords\n\nregulatory compliance, obligation map, controls tracker, compliance program, legal-regulatory-compliance-mapper, legal regulatory compliance mapper\n\n## Example Prompts\n\n- \"Map compliance obligations for a fintech product launch.\"\n- \"Create a regulatory controls tracker for a healthcare startup.\"\n\n## Outputs\n\n- Compliance obligation map\n- Controls tracker\n- Evidence checklist\n- Review calendar\n\n\n## Safety\n\nInformational support only. Not legal advice. Does not replace qualified attorney review, jurisdiction-specific research, ethics analysis, or professional judgment."},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn77zzg9p845zanvy6vrf76k7d81mcnm\",\n  \"slug\": \"legal-regulatory-compliance-mapper\",\n  \"version\": \"1.1.1\",\n  \"publishedAt\": 1782393857804\n}"},{"path":"ACCEPTANCE.md","content":"# Acceptance Criteria\n\n1. Package is descriptive only: no handler.py, scripts, external APIs, network calls, or command execution.\n2. SKILL.md and README.md are English-first and include an explicit legal-information disclaimer.\n3. Outputs are frameworks, checklists, templates, or planning aids rather than legal conclusions.\n4. Includes target users, when-to-use guidance, inputs, workflow, outputs, examples, and safety limitations.\n5. skill.json contains unique slug, tags, trigger keywords, requires_api=false, and readiness=stable.\n\n## Package Rules\n\n- Allowed files: SKILL.md, README.md, skill.json, ACCEPTANCE.md.\n- Forbidden files: handler.py, scripts, tests, binaries, credentials, generated caches, or workspace artifacts.\n- The package must remain descriptive-only and English-first."},{"path":"skill-card.md","content":"## Description:\n\nHelps map regulatory obligations, controls, owners, evidence, review cadence, verification gaps, and attorney-review triggers for a product, business unit, or jurisdiction.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[harrylabsj](https://clawhub.ai/user/harrylabsj)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nCompliance counsel, in-house legal teams, risk managers, legal operations teams, paralegals, and startup operators use this skill to structure compliance obligation maps, controls trackers, evidence checklists, review calendars, and verification gap lists.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Users may over-rely on sample jurisdiction-specific legal outputs, obligations, regulator names, or deadlines.\n\nMitigation: Require authoritative sources and qualified counsel for every jurisdiction-specific obligation, filing deadline, license, regulator, and timeline.\n\nRisk: Unverified legal requirements could be treated as confirmed compliance guidance.\n\nMitigation: Mark unsupported items as verification gaps and include attorney-review triggers before using outputs for decisions.\n\n## Reference(s):\n\n- [Skill documentation](artifact/SKILL.md)\n- [README](artifact/README.md)\n- [Acceptance criteria](artifact/ACCEPTANCE.md)\n- [ClawHub skill page](https://clawhub.ai/harrylabsj/skills/legal-regulatory-compliance-mapper)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, guidance]\n\n**Output Format:** [Markdown checklists, matrices, trackers, calendars, templates, and planning aids]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Document-only legal workflow support; no API calls, external database retrieval, filings, or legal services.]\n\n## Skill Version(s):\n\n1.1.1 (source: SKILL.md frontmatter, skill.json, server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Provides structured frameworks and checklists to map regulatory obligations, controls, evidence, and review plans for compliance program development. Skill: Legal Regulatory Compliance Mapper Owner: harrylabsj Summary: Provides structured frameworks and checklists to map regulatory obligations, controls, evidence, and review plans for compliance program development. Tags: compliance:1.1.1, latest:1.1.1, legal:1.1.1, operations:1.1.1, regulatory:1.1.1 Version history: v1.1.1 | 2026-06-25T13:24:17.804Z | user Add required compliance matrix columns, verification gaps","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1336,"uniquenessScore":46,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T17:08:32.616Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-11T17:08:32.616Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-11T21:00:38.038Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}