skills.rest
wanderinglantern
wanderinglanternCOMMUNITY
Explore all skills by this author →
GitHub

policydb-currency-parsing

Enforce magnitude-aware currency parsing across PolicyDB money fields.

Updated Mar 23, 2026
Search Tags:#backend#formatting#parsing#currency#data-validation#money#policydb
One-click install
npx skills add https://github.com/wanderinglantern/policydb --skill policydb-currency-parsing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: policydb-currency-parsing
Source: https://github.com/wanderinglantern/policydb/tree/main/.claude/skills/policydb-currency-parsing
Command: npx skills add https://github.com/wanderinglantern/policydb --skill policydb-currency-parsing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Currency values in PolicyDB are frequently mishandled due to using non-magnitude-aware parsers, leading to inconsistent calculations and display across the system.

Core Features & Use Cases

  • Enforce use of parse_currency_with_magnitude() across backend parsing, templates, XLSX export format, PATCH responses, and import paths.
  • Ensure consistent formatting for monetary fields in API responses and user-facing displays.
  • Aid audits by highlighting remaining instances of float() or non-magnitude-aware parsers for migration.

Quick Start

Apply parse_currency_with_magnitude() to all money fields across PolicyDB to ensure magnitudes are parsed correctly.

Frequently Asked Questions about policydb-currency-parsing

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

FAQPage Schema
Why are currency values inconsistent across backend parsing and XLSX exports in PolicyDB?▼

Currency values are inconsistent because non-magnitude-aware parsers are mishandling monetary inputs. Applying magnitude-aware parsing standardizes numeric representations across backend input handling, template displays, and exports.

How do I standardize money field parsing for premium and deductible inputs in PolicyDB?▼

To standardize money field parsing, apply the parse_currency_with_magnitude() function to all monetary fields. This enforces consistent numeric representations across API responses, templates, and import paths.

What is magnitude-aware currency parsing and when do I need it for backend data validation?▼

Magnitude-aware currency parsing ensures monetary values are accurately interpreted during data validation. It is needed when handling money fields like premiums or deductibles to prevent inconsistent calculations and display formatting.

Does PolicyDB export formatting require magnitude-aware parsers for PATCH responses?▼

Yes, PolicyDB export formatting and PATCH responses require magnitude-aware parsers. Using parse_currency_with_magnitude() ensures consistent formatting for monetary fields across all API and user-facing displays.

What is the best way to migrate legacy float parsers to magnitude-aware currency parsing?▼

The best way to migrate is to audit remaining instances of float() or non-magnitude-aware parsers and replace them with parse_currency_with_magnitude() across all backend parsing and import paths.

What are the limitations of using non-magnitude-aware parsers for PolicyDB money fields?▼

Non-magnitude-aware parsers cause inconsistent calculations and display formatting for money fields. They fail to enforce correct numeric representations, leading to mishandled currency values across backend and template outputs.

Related Skills

Explore More Software Engineering Skills→
astronomerastronomer
419

airflow

Manage Apache Airflow DAGs, logs, and health via the Airflow MCP CLI.

Official
Advanced
kurtjameshayeskurtjameshayes

test_endpoint

Test API endpoints for access, status codes, and response format validation.

Community
Intermediate
rafaelminatto1rafaelminatto1

fisioflow-cpf-cnpj

Validate and format Brazilian CPF, CNPJ, CEP, RG, and CRM documents.

Community
Advanced
gaearongaearon
70

mul

Multiply two numeric inputs and return their exact product.

Community
Basic