The work moment
A national team sends its REDD+ technical annex close to review week. The report FCCC/PA/CMA/2026/10 covers this.
"In some cases, technical annexes were submitted shortly before the corresponding review weeks, leaving limited time for the secretariat and LULUCF experts to prepare for the technical analysis."
FCCC/PA/CMA/2026/10 · Technical expert review of biennial transparency reports, p. 24
The same report says more of these annexes are likely.
"The number of technical annexes submitted is likely to increase in the second cycle of BTRs"
FCCC/PA/CMA/2026/10 · Technical expert review of biennial transparency reports, p. 23
What the test showed
I gave Claude a made-up annex with a missing Table X, a results section that said TBD and a methods section that pointed to an unnamed report. I asked the same question twice, with the same tools.
Without the skill, Claude said the annex was not ready and listed fixes. It did not open the UN document. It said:
"Reviewers will flag an empty results section straight away."
"Add the forest area table with its source, years and units, or change the reference to the table that's actually there."
With the skill, Claude also said the annex was not ready. It opened the source and quoted it with its page:
"Source opened: yes. I read FCCC/PA/CMA/2026/10 from the PDF."
"You plan to send soon, and review week follows shortly after."
"UN document, page 24 (Annex I, para. 13)."
It also said what it could not check:
"Not checked: you gave no BTR text, so I could not compare values."
"The source does not list what an annex must contain, so required sections are
NOT IN SOURCE."
"The source sets no deadline."
The steps of the skill
- Open the UN document. Copy the line on annexes submitted shortly before review weeks, with its page.
- Copy the line on more annexes in the second cycle of BTRs, with its page.
- Read the whole annex before writing anything.
- List every section heading. If there is a table of contents, check that each listed section is there.
- Find every placeholder: TBD, to be added, XX, empty tables, highlighted notes and comments left in the text.
- Find every cross-reference. Check that each table, figure, annex or section it points to exists.
- Flag any passage that sends the reader to another document without naming it.
- If BTR text is given, compare each shared value and term. List each mismatch with both locations.
- If a send plan is given and it puts the annex close to review week, flag the timing risk and quote the line. Do not state a deadline.
- Sort the flags. Blockers first, then fixes, then notes.
If the UN document does not open, the answer says so and marks the timing line SOURCE NOT OPENED. It never fills the quote from memory.
Copy-paste prompt
Check my draft REDD+ technical annex before we send it with our Biennial Transparency Report. Use only my annex, the BTR text I give you and the UNFCCC document at https://documents.un.org/api/symbol/access?s=FCCC/PA/CMA/2026/10&l=en&t=pdf. List every placeholder, every cross-reference that points to something missing, every passage that sends the reader to an unnamed document and every value that differs from my BTR text. Quote my text for each problem and say where it is. Sort the list into blockers, fixes and notes. If my send plan puts the annex close to review week, quote the UN document's line about annexes that arrived shortly before review weeks, with its page. If you cannot open the UN document, say so and do not quote it from memory. Do not invent deadlines or required sections.