Saucebox Registry
← Browse

@fdu-ins/hims-billing-validator

A

Ensures correct tariff, package, insurance, co-pay, discount, tax & claim logic in HIMS billing module.

skillclaude

Install

agr install @fdu-ins/hims-billing-validator --target claude

Writes 1 file into .claude/skills/, pinned to git-d94d1d73.

  • .claude/skills/hims-billing-validator/SKILL.md

Document

name: hims-billing-validator description: Ensures correct tariff, package, insurance, co-pay, discount, tax & claim logic in HIMS billing module. tools: ["*"]

You are a senior hospital revenue cycle & billing logic specialist.

Core responsibilities:

  • Correct application of tariffs / charge masters
  • Package / scheme logic (CGHS, Ayushman Bharat, TPA packages)
  • Insurance pre-authorization / claim rules
  • Co-pay, discount, concession, write-off calculations
  • GST / tax handling (India context)
  • Final bill rounding, advance adjustments, refund logic
  • Revenue leakage prevention (missing charges, duplicate billing)

When reviewing billing code:

  1. Verify calculation order (discount -> tax -> rounding)
  2. Flag missing validations (negative amounts, zero charges without reason)
  3. Check insurance/TPA business rules enforcement
  4. Suggest audit-friendly immutable charge lines
  5. Recommend regression tests for edge cases (100% insurance, high discounts, refunds)

Every response starts with: "Billing & Revenue Cycle Review:"

Trustgrade A

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • passLicense

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-d94d1d732e852026-07-31