jaygptpro/amazon-pro-skills

amz-account-health-triage

>- Triage an Amazon Account Health Rating (AHR) screenshot or text dump. Identifies which violations and metrics are pulling the rating down, prioritizes by point weight, and outputs a remediation order. Use when a user asks about Account Health, AHR, account health rating dropping, violations to address, or stabilizing a yellow or red account. Trigger phrases: "account health", "AHR", "violations", "policy strikes", "account at risk". Works with zero tools. the user pastes the AHR snapshot.

First seen May 24, 2026

Installation

$ npx skills add jaygptpro/amazon-pro-skills --skill amz-account-health-triage

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from jaygptpro/amazon-pro-skills · top by installs.

npx skills add jaygptpro/amazon-pro-skills

Browse all from jaygptpro/amazon-pro-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 9
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0
More metadata
author
Jay GPT Pro
library
amazon-pro-skills
version
1.0

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 6,070 B
  • docs SUMMARY.md 526 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 109 installs

SKILL.md

Account Health Triage

Account Health Rating shifts faster than ever under the 2025 expanded visibility. Sellers see numbers move green to yellow to red and do not know which violation matters most. This skill reads the snapshot and tells you what to fix first.

When to use this

  • AHR dropped and the seller does not know why.
  • Multiple violations are open and the seller does not know which to address first.
  • The account is yellow or red and a suspension is plausible.
  • Routine quarterly review.

The framework. The Enforcement Ladder

Not all violations weigh equally. They sit on rungs by how fast they can take the account down, from the top rung that can suspend you on a single complaint down to cosmetic flags. Climb the ladder from the top. fix the highest occupied rung first, then work down.

  1. Rung 1. Suspension-trigger violations. IP complaints, authenticity, restricted,

safety. These can suspend a listing or account on a single bad complaint. Fix immediately, regardless of any point value.

  1. Rung 2. Order-defect rate (ODR). The headline performance metric. negative

feedback, A-to-z claims, chargebacks. A single bad week pushes ODR over the threshold.

  1. Rung 3. Late shipment rate and valid tracking rate. Fulfillment reliability.

Fast to move with operational changes.

  1. Rung 4. Cancellation rate. Seller-caused cancellations from stockouts or

pricing errors.

  1. Rung 5. Policy violations with point values. Each carries weight in the AHR

score. address by point cost.

  1. Rung 6. Listing quality issues. Lowest urgency, but cumulative weight.

Within each rung, sort by recency. fresh violations weigh more than aging ones.

A note on point values. Amazon's Account Health Rating runs on a points system, but Amazon does not publish a fixed per-violation point table, and the displayed AHR score behaves more like a band (green / yellow / red) than a precise tally. Any point numbers in this skill are illustrative estimates for sequencing the work, not official figures. use them to decide what to fix first, never as a promised score change.

Step by step

  1. Collect the snapshot. Current AHR score, list of open violations, current

performance metrics, recent listing flags.

  1. Classify each item onto one of the six rungs above.
  1. Identify the binding rung. Where the score is dropping from. Often one rung

accounts for most of the loss.

  1. Build the remediation order. Rung 1 first, then by point cost within each

rung. Each action has its expected directional impact on the score.

  1. Tie to existing skills. Suspension-trigger items route to

amz-suspension-appeal. Listing-suppression items route to the suppression recovery skill. Compliance items route to amz-product-compliance.

  1. Set the review cadence. Weekly check during recovery, monthly when stable.
  1. Run the quality check, then deliver.

Output format

## Account Health Triage. [account]

Current AHR: [score]   Status: [green/yellow/red]

### Triage list (in order to address)
1. [rung] . [violation] . [point cost or impact] . [route to]
2. ...

### Binding rung
[which rung accounts for most of the drop]

### This week
[top 3 actions, ordered]

### Review cadence
[weekly / monthly]

Worked example

Account AHR at 180, yellow. Open: two IP complaints, an ODR at 1.2 percent, a late shipment rate at 6 percent, three listing-quality flags.

Triage: IP complaints first (rung 1, suspension trigger), route both to suspension appeal workflow with evidence. ODR next (rung 2), respond to the negative feedback and dispute the open A-to-z. Late shipment rate (rung 3), shift to FBA or fix the handling-time process. Listing-quality flags last. Any point figures here are illustrative estimates for sequencing, not Amazon-published values. as a rough illustration, clearing the IP complaints might recover on the order of 50 to 60 points and fixing ODR another 20 to 30, but Amazon does not publish a fixed per- violation point table and the real weights move. use them only to order the work, not as a promised score. The triage shows the path back to green without scattershot action.

Quality check

  • Every violation is classified onto one of the six rungs.
  • Suspension-trigger items (rung 1) are first, regardless of point value.
  • The binding rung is named.
  • Each action has an expected directional score impact, with any point figures

flagged as illustrative estimates, not Amazon-published values.

  • Items requiring other skills are routed to those skills, not duplicated.

Common mistakes

  • Treating all violations equally. A minor listing-quality flag is nowhere near

as dangerous as an IP complaint that can suspend the account outright.

  • Reacting to the score, not the violations. Trying to "raise the number"

without identifying which specific items are pulling it.

  • Ignoring fresh violations. Recent violations weigh more than old ones in the

formula.

  • No review cadence. AHR drifts. a weekly check during recovery catches new

issues before they compound.


Built by Jay GPT Pro

Part of Amazon Pro Skills. Production-grade skills for serious Amazon sellers. Free and open. Built by Jay Margaliot.

I share a new AI play for Amazon sellers every week, free, in my WhatsApp group. Join here: https://chat.whatsapp.com/ILX65p1yWcaIG3c9WGHpTY