@1aboveio/skills 0.20.2 → 0.20.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (85) hide show
  1. package/README.md +14 -6
  2. package/package.json +1 -1
  3. package/runtime/skills/distribution/generated/recipes.json +220 -25
  4. package/runtime/skills/distribution/scripts/bundles.mjs +167 -48
  5. package/runtime/skills/engineering/engineering-runtime/scripts/workflow-coherence.mjs +4 -0
  6. package/runtime/skills/engineering/engineering-runtime/scripts/workflow-policy.mjs +1 -1
  7. package/skills/compliance/compliance-audit/LICENSE +3 -0
  8. package/skills/compliance/compliance-audit/SKILL.md +466 -0
  9. package/skills/compliance/compliance-audit/references/findings-schema.md +290 -0
  10. package/skills/compliance/compliance-audit/references/vars-checklist.md +1068 -0
  11. package/skills/compliance/compliance-audit/references/vars-findings-schema.md +395 -0
  12. package/skills/compliance/compliance-audit/scripts/reconcile_tracker.py +454 -0
  13. package/skills/compliance/compliance-audit/scripts/test_validate_tracker.py +90 -0
  14. package/skills/compliance/compliance-audit/scripts/validate_tracker.py +752 -0
  15. package/skills/compliance/doc-authenticity/LICENSE +3 -0
  16. package/skills/compliance/doc-authenticity/SKILL.md +158 -0
  17. package/skills/compliance/doc-authenticity/references/agreement.md +66 -0
  18. package/skills/compliance/doc-authenticity/references/bank-statement.md +150 -0
  19. package/skills/compliance/doc-authenticity/references/forensic-signals.md +157 -0
  20. package/skills/compliance/doc-authenticity/references/image-signals.md +114 -0
  21. package/skills/compliance/doc-authenticity/references/invoice.md +66 -0
  22. package/skills/compliance/doc-authenticity/references/issuer-profiles.md +86 -0
  23. package/skills/compliance/doc-authenticity/references/verdict-and-report.md +95 -0
  24. package/skills/compliance/doc-authenticity/references/verdict.schema.json +81 -0
  25. package/skills/compliance/doc-authenticity/scripts/image_forensics.py +294 -0
  26. package/skills/compliance/doc-authenticity/scripts/pdf_forensics.py +401 -0
  27. package/skills/compliance/doc-authenticity/scripts/validate_codes.py +224 -0
  28. package/skills/compliance/doc-authenticity/scripts/validate_verdict.py +308 -0
  29. package/skills/compliance/report-writing/LICENSE +3 -0
  30. package/skills/compliance/report-writing/SKILL.md +206 -0
  31. package/skills/compliance/report-writing/references/audit-report-template.md +121 -0
  32. package/skills/compliance/report-writing/references/external-assessment-template.md +167 -0
  33. package/skills/compliance/report-writing/references/management-report-template.md +145 -0
  34. package/skills/compliance/report-writing/references/vars-report-template.md +224 -0
  35. package/skills/document-utils/doc-to-md/LICENSE +3 -0
  36. package/skills/document-utils/doc-to-md/SKILL.md +77 -0
  37. package/skills/document-utils/doc-to-md/scripts/convert.py +157 -0
  38. package/skills/document-utils/reg-parser/LICENSE +3 -0
  39. package/skills/document-utils/reg-parser/SKILL.md +201 -0
  40. package/skills/document-utils/reg-parser/references/checklist-schema.md +223 -0
  41. package/skills/document-utils/reg-parser/references/checklists/hk-amlo-checklist.json +1306 -0
  42. package/skills/document-utils/reg-parser/references/checklists/hk-amlo-checklist.md +469 -0
  43. package/skills/document-utils/reg-parser/references/checklists/hk-fi-corporate-onboarding-cdd-checklist.json +634 -0
  44. package/skills/document-utils/reg-parser/references/checklists/hk-fi-corporate-onboarding-cdd-checklist.md +233 -0
  45. package/skills/document-utils/reg-parser/references/checklists/hk-mso-guideline-checklist.json +2194 -0
  46. package/skills/document-utils/reg-parser/references/checklists/hk-mso-guideline-checklist.md +771 -0
  47. package/skills/document-utils/reg-parser/references/checklists/kyc-aml-checklist.md +258 -0
  48. package/skills/document-utils/reg-parser/references/checklists/visa-vars-checklist.md +1058 -0
  49. package/skills/document-utils/reg-parser/references/mandates/hk-amlo-cap615.md +389 -0
  50. package/skills/document-utils/reg-parser/references/mandates/visa-vars.md +205 -0
  51. package/skills/document-utils/reg-parser/scripts/compare_checklist.py +228 -0
  52. package/skills/document-utils/reg-parser/scripts/dump_checklist.py +348 -0
  53. package/skills/document-utils/reg-parser/scripts/preprocess-mandate.sh +171 -0
  54. package/skills/document-utils/reg-parser/scripts/test_quarantine.sh +102 -0
  55. package/skills/document-utils/reg-parser/scripts/validate_checklist.py +532 -0
  56. package/skills/document-utils/reg-parser/scripts/validate_mandate.py +242 -0
  57. package/skills/engineering/engineering-runtime/coherence/workflow.json +16 -16
  58. package/skills/engineering/engineering-runtime/scripts/workflow-coherence.mjs +4 -0
  59. package/skills/engineering/engineering-runtime/scripts/workflow-policy.mjs +1 -1
  60. package/skills/payment/similar-domain/LICENSE +3 -0
  61. package/skills/payment/similar-domain/SKILL.md +178 -0
  62. package/skills/payment/similar-domain/references/entities.md +58 -0
  63. package/skills/payment/similar-domain/references/fingerprints.md +82 -0
  64. package/skills/payment/similar-domain/references/pivots.md +66 -0
  65. package/skills/payment/similar-domain/references/report-template.md +76 -0
  66. package/skills/payment/similar-domain/references/scoring.md +61 -0
  67. package/skills/payment/similar-domain/references/terminology.md +37 -0
  68. package/skills/payment/similar-domain/references/workflow.md +79 -0
  69. package/skills/payment/tld-detection/SKILL.md +76 -21
  70. package/skills/payment/tld-detection/references/clean.md +1 -1
  71. package/skills/payment/tld-detection/references/clustering.md +21 -6
  72. package/skills/payment/tld-detection/references/decision.md +7 -2
  73. package/skills/payment/tld-detection/references/fx-conversion.md +229 -0
  74. package/skills/payment/tld-detection/references/report-template.md +63 -27
  75. package/skills/payment/tld-detection/references/streams.md +90 -0
  76. package/skills/payment/tld-detection/references/terminology.md +15 -7
  77. package/skills/payment/tld-detection/references/workflow.md +1 -1
  78. package/skills/payment/tld-detection/scripts/detect_streams.py +542 -0
  79. package/skills/engineering/ensure-coverage/evals/evals.json +0 -125
  80. package/skills/engineering/rush-issues/evals/evals.json +0 -65
  81. package/skills/engineering/rush-release/evals/evals.json +0 -58
  82. package/skills/fullstack/shadcn/evals/evals.json +0 -90
  83. package/skills/payment/fraud-analysis/evals/evals.json +0 -40
  84. package/skills/payment/tld-detection/evals/evals.json +0 -107
  85. package/skills/payment/tld-detection/tests/test_detect_ladders.py +0 -132
@@ -0,0 +1,233 @@
1
+ ```yaml
2
+ name: "HK FI Corporate Onboarding — CDD Checklist"
3
+ regulation: "Anti-Money Laundering and Counter-Terrorist Financing Ordinance (Cap. 615), Hong Kong — Schedule 2 (CDD)"
4
+ version: "1.0"
5
+ scope: "Customer due diligence obligations under Schedule 2 of Cap. 615 applicable to a financial institution at the point of onboarding a corporate (legal-person) client. Derived from hk-amlo-checklist.md; trimmed to onboarding-time CDD only — ongoing monitoring, wire/remittance/virtual-asset transfer operations, correspondent banking, insurance beneficiary, group-wide application, and record-retention periods beyond initial record creation are out of scope."
6
+ date: "2026-05-15"
7
+ summary:
8
+ categories: 6
9
+ total_items: 15
10
+ critical: 10
11
+ major: 5
12
+ minor: 0
13
+ ```
14
+
15
+ ## CAT-01: Customer Identification and Verification
16
+
17
+ ### CAT-01-001: Apply CDD before establishing the business relationship
18
+
19
+ - **Requirement:** Before establishing a business relationship with a corporate customer, the financial institution must carry out CDD measures; verification may be completed during or after establishment only where it is necessary not to interrupt the normal conduct of business and the ML/TF risk of deferral is effectively managed, with verification completed as soon as reasonably practicable.
20
+ - **Source:** Schedule 2, §3(1)(a), §3(2), §3(3), Cap. 615
21
+ - **Severity:** critical
22
+ - **Verification:**
23
+ - [ ] Onboarding workflow blocks relationship setup until CDD is complete (subject to §3(2) deferral)
24
+ - [ ] Where deferral is used, conditions of §3(2) are documented per case
25
+ - [ ] Verification is completed as soon as reasonably practicable, tracked against a defined SLA
26
+ - **Evidence:**
27
+ - Onboarding control documentation
28
+ - Deferred-verification case files
29
+ - Verification SLA tracker
30
+
31
+ ### CAT-01-002: Identify and verify the corporate customer
32
+
33
+ - **Requirement:** The financial institution must identify the corporate customer and verify the customer's identity using documents, data, or information from a governmental body, the relevant authority/regulator, an equivalent foreign authority, a recognized digital identification system, or another reliable and independent source recognized by the relevant authority.
34
+ - **Source:** Schedule 2, §2(1)(a), Cap. 615
35
+ - **Severity:** critical
36
+ - **Verification:**
37
+ - [ ] Certificate of incorporation (or equivalent registration/re-domiciliation document) obtained
38
+ - [ ] Company-registry extract or constitutional document obtained, current at time of verification
39
+ - [ ] Source of each identifying document falls within an approved source class
40
+ - [ ] Verification date, method, and source recorded in the customer file
41
+ - **Evidence:**
42
+ - Certificate of incorporation / registration
43
+ - Company-registry extract
44
+ - Constitutional documents (articles, bylaws)
45
+ - Onboarding form with verification source and date
46
+
47
+ ### CAT-01-003: Refusal and termination when CDD cannot be completed
48
+
49
+ - **Requirement:** If unable to comply with §3(1) or the deferred-verification completion duty under §3(3), the financial institution must not establish the business relationship or carry out the occasional transaction; if a relationship has already been established under deferral, it must be terminated as soon as reasonably practicable.
50
+ - **Source:** Schedule 2, §3(4), Cap. 615
51
+ - **Severity:** critical
52
+ - **Verification:**
53
+ - [ ] Documented refusal/termination procedure for CDD-failure cases
54
+ - [ ] Refused applicants and terminated relationships logged
55
+ - [ ] STR-assessment performed and recorded on termination
56
+ - **Evidence:**
57
+ - Refusal/termination procedure
58
+ - Refused-applicant log
59
+ - Termination case files
60
+
61
+ ## CAT-02: Beneficial Ownership and Control Structure
62
+
63
+ ### CAT-02-001: Identify and verify beneficial owners
64
+
65
+ - **Requirement:** The financial institution must identify each beneficial owner of the corporate customer (individuals who, directly or indirectly, own or control more than 25% of issued share capital, are entitled to exercise or control more than 25% of voting rights, or exercise ultimate control over management; or, where the corporation acts on behalf of another person, that other person), and take reasonable measures to verify each beneficial owner's identity.
66
+ - **Source:** Schedule 2, §1(1), §2(1)(b), Cap. 615
67
+ - **Severity:** critical
68
+ - **Verification:**
69
+ - [ ] Beneficial ownership declaration obtained from the customer
70
+ - [ ] Beneficial owners identified using the >25% ownership/voting threshold and "ultimate control" test
71
+ - [ ] Reasonable measures applied to verify each beneficial owner's identity
72
+ - [ ] Verification records retained per beneficial owner
73
+ - **Evidence:**
74
+ - Signed beneficial-ownership declaration
75
+ - Identification and verification records for each beneficial owner
76
+
77
+ ### CAT-02-002: Understand the ownership and control structure
78
+
79
+ - **Requirement:** Where the corporate customer is a legal person (or has a beneficial owner that is a trust within the ownership chain), the financial institution must take measures to understand the ownership and control structure of the customer.
80
+ - **Source:** Schedule 2, §2(1)(b), Cap. 615
81
+ - **Severity:** critical
82
+ - **Verification:**
83
+ - [ ] Group/ownership structure chart obtained, current at time of onboarding
84
+ - [ ] Intermediate holding entities mapped through to ultimate beneficial owners
85
+ - [ ] Trust arrangements in the chain identified (settlor, trustee, protector/enforcer, beneficiary class, ultimate controller per §1(1))
86
+ - **Evidence:**
87
+ - Ownership structure chart
88
+ - Trust documentation for any trust in the chain
89
+
90
+ ## CAT-03: Authorised Representatives
91
+
92
+ ### CAT-03-001: Verify persons purporting to act on behalf of the customer
93
+
94
+ - **Requirement:** Where a person purports to act on behalf of the corporate customer (directors, authorised signatories, account operators), the financial institution must identify that person, take reasonable measures to verify the person's identity using documents/data/information from the approved source classes, and verify the person's authority to act on behalf of the customer.
95
+ - **Source:** Schedule 2, §2(1)(d), Cap. 615
96
+ - **Severity:** critical
97
+ - **Verification:**
98
+ - [ ] Identity of each authorised representative captured and verified per §2(1)(d)(i)
99
+ - [ ] Documentary evidence of authority obtained (board resolution, power of attorney, authorisation letter, signatory mandate)
100
+ - [ ] Authorised-signatory register updated and approved
101
+ - **Evidence:**
102
+ - Representative identification records
103
+ - Authorisation documents (board resolution, POA, letter)
104
+ - Authorised-signatory mandate
105
+
106
+ ## CAT-04: Purpose, Nature and Customer Risk Profile
107
+
108
+ ### CAT-04-001: Obtain purpose and intended nature of the business relationship
109
+
110
+ - **Requirement:** The financial institution must obtain information on the purpose and intended nature of the business relationship at onboarding, unless the purpose and intended nature are obvious.
111
+ - **Source:** Schedule 2, §2(1)(c), Cap. 615
112
+ - **Severity:** major
113
+ - **Verification:**
114
+ - [ ] Onboarding questionnaire captures purpose and expected nature
115
+ - [ ] Expected transaction types, volumes, and counterparties documented
116
+ - [ ] Source of funds and (where relevant) source of wealth captured
117
+ - [ ] Where the purpose is deemed "obvious" and the measure omitted, the determination is recorded
118
+ - **Evidence:**
119
+ - Completed onboarding questionnaire
120
+ - Account-opening memo with expected activity profile
121
+
122
+ ## CAT-05: Enhanced and Simplified Due Diligence at Onboarding
123
+
124
+ ### CAT-05-001: Apply SDD only where the corporate customer or product qualifies
125
+
126
+ - **Requirement:** A financial institution applying Simplified CDD (limited to measures §2(1)(a), (c) and (d)) to a corporate customer must do so only where it has reasonable grounds to believe the customer falls within §4(3) (e.g. another financial institution, a corporation listed on any stock exchange, a supervised investment vehicle, the Government or a public body in Hong Kong, or the government/qualifying body of an equivalent jurisdiction) or the product falls within §4(5).
127
+ - **Source:** Schedule 2, §4(1), §4(3), §4(4), §4(5), Cap. 615
128
+ - **Severity:** major
129
+ - **Verification:**
130
+ - [ ] SDD eligibility test applied and documented before applying simplified measures
131
+ - [ ] Documentary basis for the qualifying customer/product category recorded (e.g. listing confirmation, regulator licence, public-body status)
132
+ - [ ] SDD discontinuation triggers documented (e.g. ML/TF suspicion, doubt about prior information)
133
+ - **Evidence:**
134
+ - SDD eligibility memo
135
+ - Listing/regulator confirmation
136
+ - Product specification with §4(5) basis
137
+
138
+ ### CAT-05-002: Enhanced due diligence when the customer or beneficial owner is a PEP
139
+
140
+ - **Requirement:** Where, at onboarding, the corporate customer or any beneficial owner is known to be a politically exposed person, the financial institution must, before establishing the business relationship, obtain approval from senior management and take reasonable measures to establish the customer's or beneficial owner's source of wealth and source of funds. The former-PEP carve-out applies only after a documented risk assessment finds no high ML/TF risk.
141
+ - **Source:** Schedule 2, §10(1), §10(3), Cap. 615
142
+ - **Severity:** critical
143
+ - **Verification:**
144
+ - [ ] PEP screening run on the corporate customer and all beneficial owners at onboarding
145
+ - [ ] Senior-management approval recorded before relationship setup
146
+ - [ ] Source-of-wealth and source-of-funds inquiries documented
147
+ - [ ] Former-PEP carve-out, if invoked, backed by a risk-assessment memo
148
+ - **Evidence:**
149
+ - PEP screening hit reports
150
+ - Senior-management approval record
151
+ - SoW/SoF documentation
152
+
153
+ ### CAT-05-003: EDD for high-risk corporate onboarding cases
154
+
155
+ - **Requirement:** In a situation specified in writing by the relevant authority, or in any other situation that by its nature presents a high ML/TF risk (e.g. complex/opaque ownership structures, jurisdictions of higher risk, anonymising delivery channels), the financial institution must obtain senior-management approval to establish the business relationship and either take reasonable measures to establish source of wealth/source of funds or take additional measures to mitigate the ML/TF risk.
156
+ - **Source:** Schedule 2, §15, Cap. 615
157
+ - **Severity:** critical
158
+ - **Verification:**
159
+ - [ ] High-risk identification procedure in place, covering regulator notices and intrinsic high-risk indicators (e.g. shell-vehicle features, nominee structures, bearer shares, high-risk geography)
160
+ - [ ] Senior-management approval recorded for high-risk onboarding cases
161
+ - [ ] SoW/SoF measures or alternative mitigation documented
162
+ - **Evidence:**
163
+ - High-risk customer policy with regulator-notice register
164
+ - Senior-management approval records
165
+ - Mitigation-measure case files
166
+
167
+ ### CAT-05-004: Non-face-to-face onboarding additional measures
168
+
169
+ - **Requirement:** Where the corporate customer has not been physically present for identification purposes (e.g. remote onboarding of the entity, or where its authorised representatives complete onboarding through a non-face-to-face channel), the financial institution must carry out at least one of the §9(1) measures: further verification using documents/data not previously used; supplementary measures to verify obtained information; or routing the first payment through an account in the customer's name with an authorised institution or qualifying foreign institution. The requirement does not apply where identification was performed using a recognized digital identification system.
170
+ - **Source:** Schedule 2, §9(1), §9(2), Cap. 615
171
+ - **Severity:** critical
172
+ - **Verification:**
173
+ - [ ] Non-face-to-face onboarding workflow applies at least one §9(1) measure
174
+ - [ ] Selected measure(s) recorded per customer
175
+ - [ ] Digital-ID-system exemption applied only where the system is recognised by the relevant authority
176
+ - **Evidence:**
177
+ - Non-face-to-face onboarding procedure
178
+ - Per-customer record of §9(1) measure applied
179
+ - Digital ID system approval reference
180
+
181
+ ## CAT-06: Prohibitions, Intermediaries, Procedures and Records
182
+
183
+ ### CAT-06-001: Prohibition on anonymous or fictitious-name accounts
184
+
185
+ - **Requirement:** The financial institution must not open or maintain any anonymous account or account in a fictitious name for any customer.
186
+ - **Source:** Schedule 2, §16, Cap. 615
187
+ - **Severity:** critical
188
+ - **Verification:**
189
+ - [ ] System controls prevent account opening without an identified customer
190
+ - [ ] Numbered or codename accounts (if any) are subject to full CDD
191
+ - **Evidence:**
192
+ - Account-opening control documentation
193
+ - Numbered-account control procedure
194
+
195
+ ### CAT-06-002: Use of intermediaries for CDD at onboarding
196
+
197
+ - **Requirement:** Where CDD on the corporate customer is carried out by an intermediary specified in §18(3), the intermediary must consent in writing to act; must be a permitted category (Hong Kong accounting/estate-agent/legal professional, TCSP licensee, qualifying domestic financial institution, qualifying equivalent-jurisdiction professional/institution, or qualifying related foreign financial institution under §18(3)(d) and (3A)); and the financial institution must immediately obtain the data/information collected and ensure the intermediary will supply copies of underlying documents on request within the §20 retention period. The financial institution remains liable for any CDD failure by the intermediary.
198
+ - **Source:** Schedule 2, §18(1), §18(2), §18(3), §18(3A), §18(4), Cap. 615
199
+ - **Severity:** major
200
+ - **Verification:**
201
+ - [ ] Written intermediary consent on file
202
+ - [ ] Eligible-category and qualifying-basis documented per intermediary
203
+ - [ ] Information-on-demand workflow operational, with retention-period commitment
204
+ - **Evidence:**
205
+ - Intermediary register
206
+ - Signed intermediary consents
207
+ - Document-request workflow
208
+
209
+ ### CAT-06-003: Procedures for PEP detection at onboarding
210
+
211
+ - **Requirement:** The financial institution must establish and maintain effective procedures for determining whether a customer or a beneficial owner of a customer is a politically exposed person; the procedures must be operative at the point of onboarding and capable of producing a determination before the business relationship is established.
212
+ - **Source:** Schedule 2, §19(1), Cap. 615
213
+ - **Severity:** major
214
+ - **Verification:**
215
+ - [ ] Documented PEP-detection procedure (lists used, screening cadence, escalation)
216
+ - [ ] PEP determination produced for the customer and each beneficial owner before relationship setup
217
+ - **Evidence:**
218
+ - PEP-detection procedure document
219
+ - Screening logs covering customer and beneficial owners
220
+
221
+ ### CAT-06-004: Records of onboarding identification and verification
222
+
223
+ - **Requirement:** For each corporate customer, the financial institution must keep the original or a copy of the documents and a record of the data and information obtained in the course of identifying and verifying the customer and any beneficial owner, together with the original or a copy of the files relating to the customer's account and business correspondence with the customer and any beneficial owner.
224
+ - **Source:** Schedule 2, §20(1)(b), Cap. 615
225
+ - **Severity:** major
226
+ - **Verification:**
227
+ - [ ] Customer file holds identification and verification records for the customer and each beneficial owner
228
+ - [ ] Account-opening records and onboarding correspondence retained
229
+ - [ ] Records are retrievable within authority-response timelines
230
+ - **Evidence:**
231
+ - Customer file inventory
232
+ - Sample onboarding file
233
+ - Retrieval-time test record