pdf-extractor
Design AI extraction configurations for structured and semi-structured insurance and mortgage PDFs. Use when configuring a document AI model to extract data fields from applications, policy documents, EOBs, pay stubs, tax returns, or bank statements.
What this skill does
# PDF Field Extraction Configuration Design Design the extraction configuration for AI-based data extraction from insurance and mortgage PDFs. Covers document type identification, field definition, confidence thresholds, model selection, pre-processing requirements, and structured output schema. --- ## Step 1: Document Type Identification Before extracting fields, the system must identify what type of document is being processed. Route to the correct extraction model based on document type. **Document classification first:** Run a classifier (see `form-classifier` skill) before the extraction model. The classifier returns a document type label that selects the correct field extraction configuration. **Document types and extraction priority:** | Document Type | Extraction Priority | Typical Use | |--------------|---------------------|------------| | ACORD 80 (personal auto application) | High | Insurance new business | | ACORD 125 (commercial applicant) | High | Commercial lines | | Policy declarations page | High | Policy verification | | Loss run | High | Underwriting | | Pay stub | High | Mortgage income verification | | W-2 | High | Mortgage income verification | | 1040 tax return | High | Mortgage income + self-employed | | 1003 Uniform Residential Loan Application | High | Mortgage processing | | Bank statement | High | Mortgage asset verification | | Explanation of Benefits (EOB) | Medium | Claims / medical | | Certificate of insurance | Medium | Proof of coverage | | MVR (Motor Vehicle Record) | Medium | Insurance underwriting | | Inspection report | Medium | Property insurance | --- ## Step 2: Field Definition by Document Type ### Pay Stub | Field Name | Data Type | Required | Validation Rule | Extraction Note | |-----------|-----------|----------|----------------|----------------| | employer_name | string | Required | Non-empty | Top of stub; sometimes in logo area | | employee_name | string | Required | Non-empty | Matches borrower name on 1003 | | employee_ssn_last4 | string | Optional | 4 digits | Often masked; extract if visible | | pay_period_start | date | Required | Valid date | Format: varies (MM/DD/YYYY, etc.) | | pay_period_end | date | Required | Valid date | Must be more recent than prior stub | | pay_date | date | Required | Valid date | Used to determine how current | | pay_frequency | enum | Required | Weekly/Bi-Weekly/Semi-Monthly/Monthly | Calculate annual equivalent | | gross_pay_this_period | currency | Required | Positive number | Current period gross before deductions | | ytd_gross_pay | currency | Required | Positive number | Year-to-date gross | | federal_tax_withheld | currency | Optional | Positive number | Cross-check against W-2 | | net_pay | currency | Optional | Positive number | Informational only | | hourly_rate | currency | Optional | If hourly employee | Used to calculate annual | | hours_worked | number | Optional | Positive number | If hourly employee | **Annual income calculation:** ``` Bi-weekly: ytd_gross / (pay_period_end_week_of_year / 2) × 26 Semi-monthly: ytd_gross / (pay_period_number) × 24 Monthly: gross_pay_this_period × 12 Hourly: hourly_rate × hours_per_week × 52 (use 2-year average if variable) ``` ### W-2 | Field Name | Box | Data Type | Required | Validation | |-----------|-----|-----------|----------|-----------| | employee_name | Employee name box | string | Required | Match to application | | employer_name | Employer name box | string | Required | Match to pay stubs | | employer_ein | b | string | Required | XX-XXXXXXX format | | wages_tips_other | 1 | currency | Required | Primary income figure | | federal_income_tax | 2 | currency | Optional | Cross-check with 1040 | | social_security_wages | 3 | currency | Optional | May differ from Box 1 | | medicare_wages | 5 | currency | Optional | May differ from Box 1 | | state | 15 | string | Optional | State of employment | | state_wages | 16 | currency | Optional | State income | | tax_year | top of form | year | Required | Validate: year should be prior 2 years | ### 1040 Tax Return (Federal) | Field Name | Line | Data Type | Required | Note | |-----------|------|-----------|----------|------| | tax_year | Top of form | year | Required | | | filing_status | Filing status checkbox | enum | Required | Single/MFJ/MFS/HOH/QW | | total_income | 9 | currency | Required | AGI before deductions | | agi | 11 | currency | Required | Adjusted Gross Income | | wages_salaries | 1a | currency | Required for W-2 employees | | | business_income_loss | Schedule C | currency | Required for self-employed | From Schedule C | | schedule_c_gross_revenue | Schedule C line 1 | currency | Self-employed | | | schedule_c_net_profit | Schedule C line 31 | currency | Self-employed | After expenses | | rental_income | Schedule E | currency | If applicable | | | k1_income | Schedule E Part II | currency | Partnership/S-Corp | | | depreciation_added_back | Schedule C + E | currency | Self-employed | Non-cash expense added back | | depletion_added_back | Schedule C + E | currency | Self-employed | Non-cash expense added back | ### Bank Statement | Field Name | Data Type | Required | Validation | |-----------|-----------|----------|-----------| | account_holder_name | string | Required | Match to borrower | | institution_name | string | Required | Non-empty | | account_number_last4 | string | Optional | 4 digits (masked) | | account_type | enum | Required | Checking/Savings/Money Market | | statement_period_start | date | Required | Valid date | | statement_period_end | date | Required | Valid date; should be within 60 days | | beginning_balance | currency | Required | | | ending_balance | currency | Required | Used for asset verification | | total_deposits | currency | Required | Identifies large/unusual deposits | | large_deposits | list | Required | Deposits > $[threshold]; itemized | | nsf_count | integer | Optional | Count of NSF/returned items | ### Policy Declarations Page | Field Name | Data Type | Required | Validation | |-----------|-----------|----------|-----------| | insured_name | string | Required | Match to client record | | policy_number | string | Required | Format varies by carrier | | carrier_name | string | Required | | | lob | enum | Required | Auto/Home/Commercial/GL/etc. | | effective_date | date | Required | Valid date | | expiration_date | date | Required | After effective date | | premium_annual | currency | Required | | | liability_limit | currency | Required for auto/GL | | | deductible | currency | Required | | | property_address | string | Required for property | Match to risk address | | vehicle_info | object | Required for auto | Year/Make/Model/VIN | --- ## Step 3: Extraction Confidence Thresholds | Confidence Level | Threshold | Handling | |-----------------|-----------|---------| | High confidence | ≥ 0.90 | Auto-accept; proceed without human review | | Medium confidence | 0.70 – 0.89 | Flag for human verification; highlight field in review UI | | Low confidence | < 0.70 | Route to human review queue; display extracted value as suggestion, not fact | | Not found | N/A | Mark field as missing; trigger missing-field condition | **Field-specific thresholds:** Critical fields (wrong value has significant downstream impact) should have higher thresholds: - Currency amounts: raise auto-accept to ≥ 0.93 - Dates: raise auto-accept to ≥ 0.93 (off-by-one errors on dates can affect compliance) - SSN / EIN: raise auto-accept to ≥ 0.95; prefer human verification for all **Confidence aggregation:** - Document-level confidence = weighted average of field-level confidence scores (weight by field importance) - If document-level confidence < 0.75: route entire document to human review, not field-by-field --- ## Step 4: Model Selection | Document Type | Recommended Model | Rationale | |-------------|-----------------|-----------| | Machine-printed structured forms (W-2, 1099) | Azure Document Intelligence (Form Recognizer) — preb
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.