@1aboveio/core-skills 0.1.5 → 0.1.7
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.
- package/package.json +2 -2
- package/skills/distill-writing/SKILL.md +22 -4
- package/skills/distill-writing/references/extraction.md +19 -3
- package/skills/doc-to-md/SKILL.md +1 -1
- package/skills/editorial-review/SKILL.md +1 -1
- package/skills/house-style/SKILL.md +2 -1
- package/skills/house-style/references/persistence.md +93 -0
- package/skills/house-style/references/rules.md +22 -6
- package/skills/house-style/templates/gap-analysis.md +1 -1
- package/skills/plain-language/SKILL.md +40 -4
- package/skills/polish-cn/SKILL.md +1 -1
- package/skills/reg-parser/SKILL.md +2 -2
- package/skills/reg-parser/scripts/dump_checklist.py +1 -1
- package/skills/terminology/SKILL.md +1 -1
- package/skills/write-doc/SKILL.md +31 -12
- package/skills/write-doc/references/bilingual.md +10 -1
- package/skills/write-doc/references/compliance-reports.md +163 -0
- package/skills/write-doc/references/reports/audit-report-template.md +121 -0
- package/skills/write-doc/references/reports/external-assessment-template.md +183 -0
- package/skills/write-doc/references/reports/management-report-template.md +150 -0
- package/skills/write-doc/references/reports/vars-report-template.md +227 -0
|
@@ -0,0 +1,227 @@
|
|
|
1
|
+
# VARS Review Report Template
|
|
2
|
+
|
|
3
|
+
Read [compliance reports](../compliance-reports.md) before using this layout.
|
|
4
|
+
|
|
5
|
+
Authoritative template for **Visa Acceptance Risk Standards (VARS)** review reports
|
|
6
|
+
distributed by Visa to acquirers. Mirrors Visa's official 2025 *Visa Acceptance Risk
|
|
7
|
+
Standards Report Template* (Confidential, Final).
|
|
8
|
+
|
|
9
|
+
Use this template **verbatim** for VARS engagements — section numbering, headings,
|
|
10
|
+
ordering, and the nine VARS sub-domains are fixed by Visa. Do not rename, reorder, or
|
|
11
|
+
omit sections without explicit instruction.
|
|
12
|
+
|
|
13
|
+
## Source of truth: the full assessment tracker
|
|
14
|
+
|
|
15
|
+
A VARS Review Report is **always** a roll-up of a complete control-by-control
|
|
16
|
+
assessment against the VARS checklist. The expected input is the `tracker.md` produced
|
|
17
|
+
by the `compliance-audit` skill (or a directly-equivalent worksheet) covering **all
|
|
18
|
+
nine sub-domains**. The report itself is the executive layer; per-control evidence,
|
|
19
|
+
testing notes, and remediation owners live in the companion *VARS Control Testing and
|
|
20
|
+
Remediation Tracking* spreadsheet, which is the same tracker in Visa's Excel format.
|
|
21
|
+
|
|
22
|
+
Before drafting:
|
|
23
|
+
1. Confirm the tracker exists and covers all nine sub-domains. If any are missing or
|
|
24
|
+
marked "Not Assessed", stop and raise it — do not paper over gaps in the report.
|
|
25
|
+
2. Confirm every control row has a Control Effectiveness Rating and the mandatory
|
|
26
|
+
fields required by the tracker schema. Sections 3.d and 4 use these ratings;
|
|
27
|
+
VARS has no generic severity-priority field. Do not invent one.
|
|
28
|
+
3. Note the tracker's filename and version — it will be referenced from Section 5 and
|
|
29
|
+
should accompany the report when distributed.
|
|
30
|
+
|
|
31
|
+
---
|
|
32
|
+
|
|
33
|
+
## Cover page
|
|
34
|
+
|
|
35
|
+
```
|
|
36
|
+
Visa Acceptance Risk Standards (VARS)
|
|
37
|
+
Review Report
|
|
38
|
+
|
|
39
|
+
Author: {{assessor name}}
|
|
40
|
+
Date: {{YYYY-MM-DD}}
|
|
41
|
+
Document Status: Final
|
|
42
|
+
Type of Review: Visa Acceptance Risk Standards (VARS)
|
|
43
|
+
Version: {{n}}
|
|
44
|
+
Document Classification: Confidential
|
|
45
|
+
```
|
|
46
|
+
|
|
47
|
+
## Table of Contents
|
|
48
|
+
|
|
49
|
+
Auto-generate from the section headings below.
|
|
50
|
+
|
|
51
|
+
---
|
|
52
|
+
|
|
53
|
+
## Section 1: Document History
|
|
54
|
+
|
|
55
|
+
| Version | Date | Updated By | Description |
|
|
56
|
+
|---------|---------|------------|-------------------|
|
|
57
|
+
| 1.0 | | | Document Creation |
|
|
58
|
+
| 2.0 | MM/YEAR | | Updated Report |
|
|
59
|
+
| 3.0 | MM/YEAR | | Final Report |
|
|
60
|
+
|
|
61
|
+
## Section 2: Document Distribution List — Acquirer Bank and Visa
|
|
62
|
+
|
|
63
|
+
| Position | Name | Date |
|
|
64
|
+
|----------|------|------|
|
|
65
|
+
| | | |
|
|
66
|
+
|
|
67
|
+
(Repeat rows for each distribution recipient.)
|
|
68
|
+
|
|
69
|
+
---
|
|
70
|
+
|
|
71
|
+
## Section 3: Executive Summary
|
|
72
|
+
|
|
73
|
+
### a. Purpose
|
|
74
|
+
|
|
75
|
+
> The purpose of this VARS Control Assessment is to perform an evaluation of the risk
|
|
76
|
+
> profile and controls used by the Acquirer to manage its acquiring program and
|
|
77
|
+
> maintain compliance with the Visa Acceptance Risk Standards (VARS). This review is
|
|
78
|
+
> based on the VARS Guide, Visa Core Rules and Visa Product and Service Rules
|
|
79
|
+
> requirements.
|
|
80
|
+
|
|
81
|
+
(Use the paragraph above verbatim. Do not paraphrase.)
|
|
82
|
+
|
|
83
|
+
### b. Background
|
|
84
|
+
|
|
85
|
+
Describe the Acquirer: legal entity, license/registration, acquiring footprint,
|
|
86
|
+
portfolio scale, and the policies, procedures, and controls in place for VARS
|
|
87
|
+
compliance. Close with the assessment objective:
|
|
88
|
+
|
|
89
|
+
> The objective of this Visa Control Assessment is to evaluate the effectiveness and
|
|
90
|
+
> adequacy of the Acquirer's controls for managing its portfolio, Third Parties,
|
|
91
|
+
> identifying any gaps or weaknesses that may pose a risk to the Visa payment system,
|
|
92
|
+
> and providing recommendations for improvement.
|
|
93
|
+
|
|
94
|
+
### c. VARS Control Assessment
|
|
95
|
+
|
|
96
|
+
State the onsite review interview date. Confirm adherence to VARS Guide, Visa Core
|
|
97
|
+
Rules, and Visa Product and Service Rules. List scope:
|
|
98
|
+
|
|
99
|
+
- Self-Assessment Questionnaire (SAQ) and evidence review, conducted by Visa.
|
|
100
|
+
- Control Assessment interview with key Acquirer staff; further evidence and samples
|
|
101
|
+
shared during the assessment. Focus VARS sub-domains:
|
|
102
|
+
- Chargebacks/Disputes
|
|
103
|
+
- Data Integrity/Quality
|
|
104
|
+
- Data Security
|
|
105
|
+
- Monitoring
|
|
106
|
+
- Network and Scheme Compliance
|
|
107
|
+
- Onboarding
|
|
108
|
+
- Regulatory Risk
|
|
109
|
+
- Risk Appetite and Policy Framework
|
|
110
|
+
- Written Agreement
|
|
111
|
+
- Visa shared observations during the session.
|
|
112
|
+
- Visa prepares and distributes the VARS Review Report.
|
|
113
|
+
|
|
114
|
+
Close with the reliance statement:
|
|
115
|
+
|
|
116
|
+
> Visa relies on the information, evidence and comments shared by the Acquirer, and
|
|
117
|
+
> to the best of our knowledge these findings are accurate.
|
|
118
|
+
|
|
119
|
+
### d. Summary of Findings
|
|
120
|
+
|
|
121
|
+
**Audience: executive.** Open with a one- or two-sentence overall-posture headline —
|
|
122
|
+
how many areas are Satisfactory, where the single material gap (if any) sits, and
|
|
123
|
+
whether any issue poses critical exposure to the Visa payment system. Then give **one
|
|
124
|
+
bullet per sub-domain with a 2–3 sentence, business-oriented summary**: the posture and
|
|
125
|
+
its risk/business implication, in plain language. Keep it **non-operational** — no
|
|
126
|
+
control IDs, document names, or clause-level detail (that belongs in Section 4 / the
|
|
127
|
+
tracker). **Always list all nine sub-domains in this order** (add a **Third Party Agent**
|
|
128
|
+
bullet when the ATPA archetype is in scope — see Section 4):
|
|
129
|
+
|
|
130
|
+
- **Risk Appetite and Policy Framework:** {{2–3 sentence business posture}}
|
|
131
|
+
- **Written Agreement:** {{…}}
|
|
132
|
+
- **Onboarding:** {{…}}
|
|
133
|
+
- **Monitoring:** {{…}}
|
|
134
|
+
- **Chargebacks/Disputes:** {{…}}
|
|
135
|
+
- **Data Integrity/Quality:** {{…}}
|
|
136
|
+
- **Data Security:** {{…}}
|
|
137
|
+
- **Network and Scheme Compliance:** {{…}}
|
|
138
|
+
- **Regulatory Risk:** {{…}}
|
|
139
|
+
|
|
140
|
+
Example — `**Onboarding — Satisfactory:** Prospective merchants are risk-assessed,
|
|
141
|
+
identity-verified, sanctions-screened and fraud-checked before they can transact. This
|
|
142
|
+
keeps higher-risk and illegitimate merchants out of the portfolio at the point of entry.`
|
|
143
|
+
|
|
144
|
+
### e. Recommendation Summary
|
|
145
|
+
|
|
146
|
+
Use this sentence **verbatim** — do not expand it or add per-domain detail:
|
|
147
|
+
|
|
148
|
+
> The Acquirer must address the identified control gaps and submit a remediation plan within 30 days. Visa will review the plan and schedule follow-up assessments as needed.
|
|
149
|
+
|
|
150
|
+
---
|
|
151
|
+
|
|
152
|
+
## Section 4: Observations Overview
|
|
153
|
+
|
|
154
|
+
**Audience: department managers / control owners.** Visa's standard Section 4 columns are retained; the **values** are drawn from the tracker (Priority is dropped — VARS has no severity-priority). This section is more detailed than Section 3.d — it gives the responsible owner a substantive picture of what is in place and what (if anything) to fix.
|
|
155
|
+
|
|
156
|
+
| # | Section Title | Compliance Status | Findings and Comments | Revision after Remediation Completion |
|
|
157
|
+
|---|------------------------------------|-------------------|-----------------------|---------------------------------------|
|
|
158
|
+
| 1 | Risk Appetite and Policy Framework | | | |
|
|
159
|
+
| 2 | Written Agreement | | | |
|
|
160
|
+
| 3 | Onboarding | | | |
|
|
161
|
+
| 4 | Monitoring | | | |
|
|
162
|
+
| 5 | Chargebacks/Disputes | | | |
|
|
163
|
+
| 6 | Data Integrity/Quality | | | |
|
|
164
|
+
| 7 | Data Security | | | |
|
|
165
|
+
| 8 | Network and Scheme Compliance | | | |
|
|
166
|
+
| 9 | Regulatory Risk | | | |
|
|
167
|
+
|
|
168
|
+
**Note on numbering:** the official 2025 template skips row 9 and labels Regulatory
|
|
169
|
+
Risk as #10. That is a known artifact in the source document. Use sequential 1–9 here
|
|
170
|
+
unless the Visa engagement lead requires the legacy numbering.
|
|
171
|
+
|
|
172
|
+
**Third Party Agent row.** When the ATPA (Acquirer Third Party Agent) archetype is in
|
|
173
|
+
scope, rows 1–9 cover the Acquirer's own (AACQ) controls and **all ATPA controls are
|
|
174
|
+
consolidated into an additional row 10, "Third Party Agent"** — rather than scattering
|
|
175
|
+
TPA controls across the AACQ sub-domains (so e.g. a TPA-agreement gap does not pull the
|
|
176
|
+
"Written Agreement" or "Onboarding" rows down). Omit row 10 when ATPA is out of scope.
|
|
177
|
+
|
|
178
|
+
**Compliance Status values:** Satisfactory / Improvement Recommended / Unsatisfactory / N/A — the tracker's Control Effectiveness Rating. A sub-domain takes the **worst** rating among its controls (any Unsatisfactory ⇒ Unsatisfactory; else any Improvement Recommended ⇒ Improvement Recommended; else Satisfactory; N/A only if every control is N/A).
|
|
179
|
+
**Findings and Comments:** written as an **inline auditor narrative** — flowing prose (no bold sub-headings) that conveys, in order, what was **observed** (the controls and practices in place), the **finding** (the rating and any mandatory gaps), and **comments** (recommendations and scoping notes such as N/A controls). Describe the controls in the report's **own words**; do **not** cite the underlying evidence documents, clauses, attestation numbers, or specific samples — that detail lives in the tracker (Section 5), and repeating it here duplicates the tracker. Lightweight control-ID cross-references (e.g. `AACQ.C8.1`) may be included as pointers. The **Actions Required** and **Recommendations** items must be reproduced **verbatim — word for word — from the tracker's Issue Description** (only the observations narrative is in the report's own words); put each item on its own line so they stay visible. For a fully **Satisfactory** row, close with `No remediation required.` When rendering to DOCX/PDF, each `<br>`-separated line in this cell must appear on its own line — see [export checks](../compliance-reports.md#export-checks) (a plain pandoc table conversion collapses them).
|
|
180
|
+
|
|
181
|
+
---
|
|
182
|
+
|
|
183
|
+
## Section 5: Detailed Information
|
|
184
|
+
|
|
185
|
+
> Refer to the accompanying *VARS Control Testing and Remediation Tracking* spreadsheet
|
|
186
|
+
> (including HIR template) for detailed information on all controls tested during this
|
|
187
|
+
> VARS review.
|
|
188
|
+
|
|
189
|
+
If the audit produced a Markdown tracker (e.g., from the `compliance-audit` skill),
|
|
190
|
+
note its filename here and confirm it has been converted to / synchronized with the
|
|
191
|
+
official Visa Excel tracker.
|
|
192
|
+
|
|
193
|
+
---
|
|
194
|
+
|
|
195
|
+
## Section 6: Next Steps
|
|
196
|
+
|
|
197
|
+
Describe required remediation timeline, due dates, next review schedule, and any
|
|
198
|
+
follow-up commitments. Close with:
|
|
199
|
+
|
|
200
|
+
> For any questions or additional information regarding this report, please send an
|
|
201
|
+
> email to **VIRPregistration@visa.com**.
|
|
202
|
+
|
|
203
|
+
*— End of Report —*
|
|
204
|
+
|
|
205
|
+
---
|
|
206
|
+
|
|
207
|
+
## Mapping audit findings → VARS report
|
|
208
|
+
|
|
209
|
+
When converting `compliance-audit` tracker output into this report:
|
|
210
|
+
|
|
211
|
+
| Tracker field | Report destination |
|
|
212
|
+
|------------------------------|---------------------------------------------------------------------------|
|
|
213
|
+
| Sub-domain / Category (AACQ) | Section 4 rows 1–9 + Section 3.d bullet; ATPA controls → the Third Party Agent row (Section 4 row 10) + its 3.d bullet |
|
|
214
|
+
| Control Effectiveness Rating | Section 4 "Compliance Status" (worst rating across the row's controls) + the row's Section 3.d posture |
|
|
215
|
+
| Observations | Section 4 "Findings and Comments" — re-narrated in the report's **own words** (no source-document/clause/sample citations) |
|
|
216
|
+
| Issue Description (Actions Required / Recommendations) | Section 4 "Findings and Comments" — reproduced **verbatim, word for word** (not paraphrased) |
|
|
217
|
+
| Evidence / per-control detail / document citations | Excel tracker (referenced from Section 5) — not repeated in the report |
|
|
218
|
+
| Remediation owner/ETA | Section 6 |
|
|
219
|
+
|
|
220
|
+
For **Section 3.d** (executive), aggregate each sub-domain into a 2–3 sentence
|
|
221
|
+
business-oriented posture under an overall headline. For **Section 4** (department
|
|
222
|
+
managers), keep one row per sub-domain (plus the Third Party Agent row when ATPA is in
|
|
223
|
+
scope): the Findings and Comments cell is an inline observed → finding → comments
|
|
224
|
+
narrative in the report's own words, the Actions Required / Recommendations are verbatim
|
|
225
|
+
from the tracker, and the Compliance Status is the worst rating across the row's
|
|
226
|
+
controls. Per-control evidence and citations belong in the companion Excel tracker, not
|
|
227
|
+
the report.
|