vat-submission-failure-alarm-user-lookup

Investigate HMRC VAT submission failure alarms using read-only AWS queries.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/diy-accounting-uk/submit.diyaccounting.co.uk --skill vat-submission-failure-alarm-user-lookup-diy-accounting-uk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vat-submission-failure-alarm-user-lookup
Source: https://github.com/diy-accounting-uk/submit.diyaccounting.co.uk/tree/main/.claude/skills/vat-submission-failure-alarm-user-lookup
Command: npx skills add https://github.com/diy-accounting-uk/submit.diyaccounting.co.uk --skill vat-submission-failure-alarm-user-lookup-diy-accounting-uk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a production VAT submission failure alarm fires, operators need to identify the affected customer, understand what HMRC responded, and decide whether a support reply is needed, all without scanning customer tables or leaking personal data into public alarm issues. ## Core Features & Use Cases - Alarm window pinning: Derives the investigation time window from the alarm datapoint and the Submit/Business VatSubmissionFailure metric. - Customer identification: Queries Athena activity events, DynamoDB HMRC API request records, Cognito users, and bundle tables by hashed_sub to reconstruct who the customer is and what happened. - HMRC response decoding: Interprets masked HMRC responses and fraud-prevention headers, including the 403 not-authorised enrolment case. - Support contact check: Searches support mailboxes to determine whether the customer already wrote in. - Use Case: An operator receives a [ALARM] prod-env-hmrc-submission-failure issue and uses this Skill to find the customer's masked email, the HMRC error message, and whether they need a reply, writing only request ids back to the public issue. ## Quick Start Ask the assistant to look up who was behind the latest prod-env-hmrc-submission-failure alarm and what HMRC answered.

Frequently Asked Questions about vat-submission-failure-alarm-user-lookup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the customer behind a VAT submission failure alarm?▼

Take the datapoint time from the alarm issue, then query the Athena activity_events table for that window to get the hashed_sub, login summary, and request ids. Follow up with DynamoDB queries on prod-env-hmrc-api-requests and a Cognito list-users lookup by sub.

Why must DynamoDB queries avoid Scan on customer tables?▼

A Scan on any customer table triggers the prod-env-dynamodb-customer-table-scan detector alarm. The skill only runs Query operations with a known key such as hashedSub, which keeps the investigation read-only and alarm-free.

What does the HMRC 403 client not authorised error mean?▼

It is HMRC's response on the obligations lookup before any return is sent, meaning the Government Gateway account is not enrolled for MTD VAT for that VRN or has not authorised the application. Nothing in the application code produces it.

Can personal data be posted on the public alarm issue?▼

No. Personal data such as email, name, VRN, IP, and device id goes only to the operator in chat. The public alarm issue should contain only the request ids and the HMRC message.

How do I check if the customer contacted support?▼

Search both support mailboxes with corpus-loom using sources mail-support and mail-antony in lexical mode with the customer's email address as the query. No hit means no enquiry has been received yet.