[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F8NNY3GXVTPBW0HAYEXAP0":3,"skill-same:01M7F8NNY3GXVTPBW0HAYEXAP0":63},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":14,"repositoryHtmlUrl":46,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M7F8NNY3GXVTPBW0HAYEXAP0","managing-insurance-fraud-detection",null,"Structures insurance fraud detection with red flag identification, investigation protocols, and SIU referral documentation. Use when detecting insurance fraud, investigating suspicious claims, or documenting fraud indicators.","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Ffinance\u002Fmanaging-insurance-fraud-detection\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: managing-insurance-fraud-detection\nlanguage: en\ndescription: Structures insurance fraud detection with red flag identification, investigation protocols, and SIU referral documentation. Use when detecting insurance fraud, investigating suspicious claims, or documenting fraud indicators.\ntags:\n  - management\n  - insurance\nmetadata:\n  author: casemark\n  practice_areas:\n    - Insurance\n    - Actuarial Science\n    - Reinsurance\n  document_types:\n    - Management Report\n  skill_modes:\n    - Management\n    - Coordination\nsource: \"https:\u002F\u002Fgithub.com\u002FCaseMark\u002Fskills\"\nsource_repository: \"CaseMark\u002Fskills\"\nsource_path: \"skills\u002Ffinance\u002Fmanaging-insurance-fraud-detection\u002FSKILL.md\"\nlicense: \"Apache-2.0\"\nimported_at: \"2026-09-20\"\n---\n# Managing Insurance Fraud Detection\n\nStructures insurance fraud detection programs covering red flag identification, investigation protocols, SIU referral documentation, and cross-functional coordination across claims, underwriting, and compliance teams.\n\n## When To Use\n\n- Standing up or auditing a fraud detection program for a carrier or MGA\n- Triaging suspicious claims against known fraud indicator patterns\n- Building or refining SIU referral criteria and escalation workflows\n- Documenting fraud investigation findings for regulatory reporting or litigation support\n- Evaluating analytics\u002Fmodel outputs that flag anomalous claim or policy activity\n- Coordinating between claims adjusters, SIU investigators, legal counsel, and law enforcement\n\n## Inputs To Gather\n\n- **Line of business**: Auto, property, health\u002Fmedical, workers' comp, life, disability, or commercial liability\n- **Claim file or policy data**: Claim number, policy details, loss description, claimant\u002Finsured information, payment history\n- **Red flag triggers**: What prompted suspicion (adjuster referral, analytics alert, tip, pattern match)\n- **Prior investigation history**: Past SIU referrals, prior claims by same claimant\u002Fprovider, related party flags\n- **Jurisdictional context**: State fraud reporting statutes, mandatory referral thresholds, immunity protections [VERIFY]\n- **Internal thresholds**: Company-specific scoring models, referral criteria, authority limits for SIU action\n- **Regulatory obligations**: State fraud bureau reporting deadlines, NICB membership requirements, federal program fraud considerations (e.g., crop insurance, flood insurance) [VERIFY]\n\n## Workflow\n\n1. **Classify the fraud type**\n   - Distinguish hard fraud (staged accidents, arson, fabricated claims) from soft fraud (inflated damages, misrepresented facts, premium evasion)\n   - Identify the scheme pattern: provider fraud, policyholder fraud, agent\u002Fbroker fraud, organized ring activity\n   - Map to the relevant line of business — red flags differ materially between auto PIP fraud, property water-loss fraud, and workers' comp malingering\n\n2. **Catalog red flags**\n   - Document each indicator with specificity: financial pressure signals, timeline inconsistencies, claimant behavior anomalies, medical treatment patterns, policy inception-to-loss timing\n   - Cross-reference against established indicator libraries (NICB, ISO ClaimSearch, Coalition Against Insurance Fraud resources)\n   - Score or weight indicators — a single flag rarely warrants SIU referral; accumulation of 3+ correlated indicators typically triggers escalation\n\n3. **Assess investigation viability**\n   - Determine whether the claim reserve and potential recovery justify investigation costs\n   - Identify available evidence sources: surveillance feasibility, social media intelligence, EUO\u002Fstatement under oath opportunities, medical record audits, financial record subpoenas\n   - Evaluate statute of limitations and reporting deadlines for the jurisdiction [VERIFY]\n\n4. **Structure the SIU referral package**\n   - Prepare a referral memo with: claim synopsis, enumerated red flags with supporting evidence, recommended investigation actions, preliminary fraud type classification\n   - Attach supporting documentation: indexed claim file excerpts, analytics output, prior claim history, public records search results\n   - Assign priority tier (routine, elevated, urgent\u002Fring activity) based on dollar exposure and scheme complexity\n\n5. **Define investigation protocol**\n   - Outline specific investigative steps: recorded statements, surveillance windows, scene inspections, canvass interviews, financial analysis, expert retention\n   - Set milestone checkpoints (30\u002F60\u002F90-day reviews) with go\u002Fno-go decision criteria\n   - Establish chain-of-custody procedures for physical and digital evidence\n   - Coordinate with claims on reservation of rights letters and EUO scheduling\n\n6. **Manage regulatory and law enforcement coordination**\n   - Prepare state fraud bureau referral forms per jurisdictional requirements [VERIFY]\n   - Determine whether to file a Suspicious Activity Report (SAR) if federally regulated program is involved [VERIFY]\n   - Coordinate with NICB for organized fraud or multi-carrier schemes\n   - Document all law enforcement contacts and information-sharing with appropriate privilege protections\n\n7. **Produce the management report**\n   - Summarize open investigations by status, priority, and estimated exposure\n   - Track key metrics: referral-to-resolution time, denial\u002Frecovery rates, investigation ROI\n   - Highlight emerging scheme trends and recommend adjustments to detection models or adjuster training\n   - Flag cases approaching regulatory reporting deadlines or litigation hold triggers\n\n## Output\n\nThe deliverable is a **Fraud Detection Management Report** containing:\n\n- **Executive summary**: Total referrals, open investigations, recoveries, and denial savings for the reporting period\n- **Red flag analysis**: Cataloged indicators by scheme type with frequency and correlation data\n- **Active investigation tracker**: Case-by-case status with priority tier, assigned investigator, next action, and target dates\n- **SIU referral packages**: Completed referral memos with supporting documentation indices\n- **Regulatory compliance log**: Filed reports, upcoming deadlines, and outstanding obligations by jurisdiction\n- **Trend analysis and recommendations**: Emerging patterns, model tuning suggestions, training needs, and resource allocation proposals\n\n## Quality Checks\n\n- Every red flag cited is tied to a specific, documented data point — no conclusory assertions without evidentiary support\n- Fraud type classification aligns with NICB\u002FISO standard taxonomy\n- SIU referral memos distinguish between confirmed facts, adjuster observations, and analytical inferences\n- Jurisdictional reporting requirements are verified against current statutes — mark with [VERIFY] if not independently confirmed\n- Investigation protocols include chain-of-custody requirements and privilege preservation steps\n- Management metrics use consistent definitions (e.g., \"recovery\" includes subrogation, denial savings, and restitution separately)\n- No accusatory language in documentation — use \"indicators consistent with\" rather than \"fraud\" until adjudicated\n- All timelines account for applicable statutes of limitation and regulatory filing windows [VERIFY]\n","# Managing Insurance Fraud Detection\n\nStructures insurance fraud detection programs covering red flag identification, investigation protocols, SIU referral documentation, and cross-functional coordination across claims, underwriting, and compliance teams.\n\n## When To Use\n\n- Standing up or auditing a fraud detection program for a carrier or MGA\n- Triaging suspicious claims against known fraud indicator patterns\n- Building or refining SIU referral criteria and escalation workflows\n- Documenting fraud investigation findings for regulatory reporting or litigation support\n- Evaluating analytics\u002Fmodel outputs that flag anomalous claim or policy activity\n- Coordinating between claims adjusters, SIU investigators, legal counsel, and law enforcement\n\n## Inputs To Gather\n\n- **Line of business**: Auto, property, health\u002Fmedical, workers' comp, life, disability, or commercial liability\n- **Claim file or policy data**: Claim number, policy details, loss description, claimant\u002Finsured information, payment history\n- **Red flag triggers**: What prompted suspicion (adjuster referral, analytics alert, tip, pattern match)\n- **Prior investigation history**: Past SIU referrals, prior claims by same claimant\u002Fprovider, related party flags\n- **Jurisdictional context**: State fraud reporting statutes, mandatory referral thresholds, immunity protections [VERIFY]\n- **Internal thresholds**: Company-specific scoring models, referral criteria, authority limits for SIU action\n- **Regulatory obligations**: State fraud bureau reporting deadlines, NICB membership requirements, federal program fraud considerations (e.g., crop insurance, flood insurance) [VERIFY]\n\n## Workflow\n\n1. **Classify the fraud type**\n   - Distinguish hard fraud (staged accidents, arson, fabricated claims) from soft fraud (inflated damages, misrepresented facts, premium evasion)\n   - Identify the scheme pattern: provider fraud, policyholder fraud, agent\u002Fbroker fraud, organized ring activity\n   - Map to the relevant line of business — red flags differ materially between auto PIP fraud, property water-loss fraud, and workers' comp malingering\n\n2. **Catalog red flags**\n   - Document each indicator with specificity: financial pressure signals, timeline inconsistencies, claimant behavior anomalies, medical treatment patterns, policy inception-to-loss timing\n   - Cross-reference against established indicator libraries (NICB, ISO ClaimSearch, Coalition Against Insurance Fraud resources)\n   - Score or weight indicators — a single flag rarely warrants SIU referral; accumulation of 3+ correlated indicators typically triggers escalation\n\n3. **Assess investigation viability**\n   - Determine whether the claim reserve and potential recovery justify investigation costs\n   - Identify available evidence sources: surveillance feasibility, social media intelligence, EUO\u002Fstatement under oath opportunities, medical record audits, financial record subpoenas\n   - Evaluate statute of limitations and reporting deadlines for the jurisdiction [VERIFY]\n\n4. **Structure the SIU referral package**\n   - Prepare a referral memo with: claim synopsis, enumerated red flags with supporting evidence, recommended investigation actions, preliminary fraud type classification\n   - Attach supporting documentation: indexed claim file excerpts, analytics output, prior claim history, public records search results\n   - Assign priority tier (routine, elevated, urgent\u002Fring activity) based on dollar exposure and scheme complexity\n\n5. **Define investigation protocol**\n   - Outline specific investigative steps: recorded statements, surveillance windows, scene inspections, canvass interviews, financial analysis, expert retention\n   - Set milestone checkpoints (30\u002F60\u002F90-day reviews) with go\u002Fno-go decision criteria\n   - Establish chain-of-custody procedures for physical and digital evidence\n   - Coordinate with claims on reservation of rights letters and EUO scheduling\n\n6. **Manage regulatory and law enforcement coordination**\n   - Prepare state fraud bureau referral forms per jurisdictional requirements [VERIFY]\n   - Determine whether to file a Suspicious Activity Report (SAR) if federally regulated program is involved [VERIFY]\n   - Coordinate with NICB for organized fraud or multi-carrier schemes\n   - Document all law enforcement contacts and information-sharing with appropriate privilege protections\n\n7. **Produce the management report**\n   - Summarize open investigations by status, priority, and estimated exposure\n   - Track key metrics: referral-to-resolution time, denial\u002Frecovery rates, investigation ROI\n   - Highlight emerging scheme trends and recommend adjustments to detection models or adjuster training\n   - Flag cases approaching regulatory reporting deadlines or litigation hold triggers\n\n## Output\n\nThe deliverable is a **Fraud Detection Management Report** containing:\n\n- **Executive summary**: Total referrals, open investigations, recoveries, and denial savings for the reporting period\n- **Red flag analysis**: Cataloged indicators by scheme type with frequency and correlation data\n- **Active investigation tracker**: Case-by-case status with priority tier, assigned investigator, next action, and target dates\n- **SIU referral packages**: Completed referral memos with supporting documentation indices\n- **Regulatory compliance log**: Filed reports, upcoming deadlines, and outstanding obligations by jurisdiction\n- **Trend analysis and recommendations**: Emerging patterns, model tuning suggestions, training needs, and resource allocation proposals\n\n## Quality Checks\n\n- Every red flag cited is tied to a specific, documented data point — no conclusory assertions without evidentiary support\n- Fraud type classification aligns with NICB\u002FISO standard taxonomy\n- SIU referral memos distinguish between confirmed facts, adjuster observations, and analytical inferences\n- Jurisdictional reporting requirements are verified against current statutes — mark with [VERIFY] if not independently confirmed\n- Investigation protocols include chain-of-custody requirements and privilege preservation steps\n- Management metrics use consistent definitions (e.g., \"recovery\" includes subrogation, denial savings, and restitution separately)\n- No accusatory language in documentation — use \"indicators consistent with\" rather than \"fraud\" until adjudicated\n- All timelines account for applicable statutes of limitation and regulatory filing windows [VERIFY]\n",{"name":5,"tags":24,"source":27,"license":15,"language":28,"metadata":29,"description":7,"imported_at":40,"source_path":41,"source_repository":42},[25,26],"management","insurance","https:\u002F\u002Fgithub.com\u002FCaseMark\u002Fskills","en",{"author":30,"skill_modes":31,"document_types":34,"practice_areas":36},"casemark",[32,33],"Management","Coordination",[35],"Management Report",[37,38,39],"Insurance","Actuarial Science","Reinsurance","2026-09-20","skills\u002Ffinance\u002Fmanaging-insurance-fraud-detection\u002FSKILL.md","CaseMark\u002Fskills","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Ffinance\u002Fmanaging-insurance-fraud-detection","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill managing-insurance-fraud-detection",{"tool":55,"command":56},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill managing-insurance-fraud-detection",{"tool":58,"command":59},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill managing-insurance-fraud-detection","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Ffinance\u002Fmanaging-insurance-fraud-detection\u002FSKILL.md",true,[],[64,72,79,86,93,100],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]