Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

Commencer

officeqa-verify

Étoiles3

Forks1

Mis à jour8 avril 2026 à 05:27

Checklist before computing and before writing answer

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

jwalin-shah

jwalin-shah/officeqa-arena

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Secrétaires de direction et assistants administratifsBureau et soutien administratif·SOC 43-6011

SKILL.md

readonly

name	officeqa-verify
description	Checklist before computing and before writing answer

AFTER EXTRACTING DATA, before computing:

Did I get the right row? Re-read the label. "Total" ≠ the specific line item.
PARENTAGE CHECK: Is this row under the right section header? "Individual income taxes" under "Receipts" ≠ under "Refunds". Scroll up to find the section heading.
Did I get the right column/year? Count columns from the header.
Net vs Gross? "Net" = after deductions. "Gross" = before. Check which the question asks.
Are the units correct? Check table header: millions, billions, thousands, percent.
Parentheses = negative. "(123)" means -123.
If FY question: did I use FY months (Jul-Jun or Oct-Sep), not CY?
If multiple values: did I get all of them? Count matches expected count.

AFTER COMPUTING, before writing:

Does the magnitude make sense? Federal budgets are billions, not millions.
Is the sign correct? Deficits are negative.
Did I use the right formula? pct_change = (new-old)/old100, NOT (new-old)/new100.

Then: printf '%s' "VALUE" > /app/answer.txt

Plus depuis ce dépôt

même dépôt

verify

jwalin-shah/officeqa-arena

Review board — verify the analyst's answer before final submission

2026-05-143

computation-patterns

jwalin-shah/officeqa-arena

Python computation formulas for Treasury data analysis. Use for percent change, CAGR, stdev, kurtosis, VaR, regression, Theil index, and other statistical calculations.

2026-04-083

cpi-reference

jwalin-shah/officeqa-arena

CPI-U annual averages (1929-2024) for inflation adjustment. Use when question mentions inflation, CPI, constant dollars, or real dollars.

2026-04-083

data-files

jwalin-shah/officeqa-arena

How to read Treasury Bulletin data files in /app/resources/. Use when exploring resources or when JSON parsing fails.

2026-04-083

fiscal-calendar

jwalin-shah/officeqa-arena

U.S. fiscal year boundaries and calendar year conversions. Use when question mentions fiscal year, FY, or when you need to determine which months belong to a fiscal year.

2026-04-083

table-extraction

jwalin-shah/officeqa-arena

How to accurately extract values from Treasury Bulletin tables. Use when reading tables with many columns, similar row labels, or when you need to verify you have the right cell.

2026-04-083

name	officeqa-verify
description	Checklist before computing and before writing answer

AFTER EXTRACTING DATA, before computing:

Did I get the right row? Re-read the label. "Total" ≠ the specific line item.
PARENTAGE CHECK: Is this row under the right section header? "Individual income taxes" under "Receipts" ≠ under "Refunds". Scroll up to find the section heading.
Did I get the right column/year? Count columns from the header.
Net vs Gross? "Net" = after deductions. "Gross" = before. Check which the question asks.
Are the units correct? Check table header: millions, billions, thousands, percent.
Parentheses = negative. "(123)" means -123.
If FY question: did I use FY months (Jul-Jun or Oct-Sep), not CY?
If multiple values: did I get all of them? Count matches expected count.

AFTER COMPUTING, before writing:

Does the magnitude make sense? Federal budgets are billions, not millions.
Is the sign correct? Deficits are negative.
Did I use the right formula? pct_change = (new-old)/old100, NOT (new-old)/new100.

Then: printf '%s' "VALUE" > /app/answer.txt