「claim」の検索結果

Design insurance claim processing procedures. TRIGGERS - Use when user needs help with insurance-claim-process related tasks.

日本語の概要は準備中です。原文の説明を表示しています。

Design claims advocacy programs. TRIGGERS - Use when user needs help with insurance-claims-advocacy related tasks.

日本語の概要は準備中です。原文の説明を表示しています。

Link claim-side evidence objects to observation-side evidence objects, score support or contradiction heuristically, and persist a compact claim-observation link artifact for board review and challenge work.

日本語の概要は準備中です。原文の説明を表示しています。

Database of insurance claim precedents and comparable settlements for evaluating claim values

日本語の概要は準備中です。原文の説明を表示しています。

Design claims handling workflows with documentation and timelines. TRIGGERS - Use when user needs help with claims-handler related tasks.

日本語の概要は準備中です。原文の説明を表示しています。

Claims Appeals agent for healthcare workflows.

日本語の概要は準備中です。原文の説明を表示しています。

Write claims denial appeal letters with documentation. TRIGGERS - Use when user needs help with claims-denial-appeal related tasks.

日本語の概要は準備中です。原文の説明を表示しています。

Design claims management systems with workflows. TRIGGERS - Use when user needs help with claims-management related tasks.

日本語の概要は準備中です。原文の説明を表示しています。

This skill should be used when the user asks to appeal a MetLife pet insurance claim, dispute a denial, challenge an underpayment, draft an appeal letter, review an EOB for appeal grounds, or fight a pet insurance claim decision.

日本語の概要は準備中です。原文の説明を表示しています。

A survey of the best-known active scientific controversies in nutrition — saturated fat and cardiovascular disease, dietary cholesterol, low-carb vs low-fat, ultra-processed foods, red meat and cancer, salt and blood pressure, and the replication status of popular single-nutrient claims. Use when a question asks whether a widely reported nutritional claim is settled, or when the department needs to distinguish "contested but plausible" from "settled" from "disproven."

日本語の概要は準備中です。原文の説明を表示しています。

Verify one falsifiable factual claim against evidence appropriate to the claim. Use when a concrete assertion about software, documentation, configuration, releases, or repository behavior must be classified as VERIFIED, REFUTED, or INCONCLUSIVE.

日本語の概要は準備中です。原文の説明を表示しています。

Verify multiple factual claims in backlog items, skill documentation, or plugin content. Extracts discrete claims, delegates each to the canonical factual-verification process, and aggregates VERIFIED/REFUTED/INCONCLUSIVE results. Use for "fact check", "verify claims", or a set of unverified factual assertions.

日本語の概要は準備中です。原文の説明を表示しています。

Fact-check manuscript claims against their cited sources in a per-source Markdown knowledge base. Use to audit claim support, overclaiming, direction, scope, and misattribution after source intake is complete.

日本語の概要は準備中です。原文の説明を表示しています。

Maintain request-time claims enrichment, its public backend and parser APIs, gatekeeper and validator hooks, and the static claims-enrichment plugin. Excludes portal issuance-time transforms and token signing.

日本語の概要は準備中です。原文の説明を表示しています。

Evaluates make-whole premium claims in bankruptcy with contract interpretation, present value disputes, and secured status analysis. Use when analyzing make-whole claims, evaluating redemption disputes, or assessing premium recovery.

日本語の概要は準備中です。原文の説明を表示しています。

Evaluates claims trading market with trading levels, holder identification, and blocking position analysis. Use when analyzing claims markets, tracking distressed debt trading, or evaluating ad hoc group dynamics.

日本語の概要は準備中です。原文の説明を表示しています。

Inspect one bounded Proto UI Issue queue slice and route ready governed work toward claim and implementation. Use for intake health, readiness, ownership, claim conflicts, stale state, or a candidate task search. This evidence leaf is read-only; authorized claim and implementation continue in their registered leaves.

日本語の概要は準備中です。原文の説明を表示しています。

Use only for user-provided academic text, explicit scholarly claims, existing citations, or known bibliographies needing citations added, verified, replaced, extracted, or formatted. Supports claim-to-source matching, citation-support checks, replacements, and common academic citation formats. Do not use for general fact-checking, legal/journalistic citation work, open-ended 'find literature about X', topic-level exhaustive discovery, systematic-review corpus construction, PRISMA searches, or creating new research claims. Chinese: 为已有段落补参考文献、核验已有引用、替换错误引用、提取需引文论断、GB/T 7714 格式化.

日本語の概要は準備中です。原文の説明を表示しています。

Use when receiving code review feedback (especially if unclear or technically questionable), when completing tasks or major features requiring review before proceeding, or before making any completion/success claims. Covers three practices - receiving feedback with technical rigor over performative agreement, requesting reviews via code-reviewer subagent, and verification gates requiring evidence before any status claims. Essential for subagent-driven development, pull requests, and preventing false completion claims.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a senior property & casualty claims adjuster — scoping a water-damage or auto-collision loss, deciding total-loss vs. repair on a damaged vehicle, drafting or checking a reservation-of-rights letter, deciding when a claim needs an SIU fraud referral vs. a routine recorded statement, or working out whether a coverage dispute should go to appraisal or litigation. A reasoning aid, not licensed adjusting authority.

日本語の概要は準備中です。原文の説明を表示しています。

Refresh Claude Ads platform, API, policy, regulation, benchmark, issue, pull-request, fork, and repository evidence. Use for ads research refresh, expired refresh_due dates, stale API or platform claims, reverify-or-demote decisions, release-current claim validation, ecosystem review, current platform changes, or updating paid-media knowledge. When tools or sources are unavailable, still demote the stale claim for the current run and block dependent release-current assertions before requesting access.

日本語の概要は準備中です。原文の説明を表示しています。

Always use this skill before claiming any work is done, fixed, passing, or complete — even if it seems obvious. Also use when receiving code review feedback from any source (human or automated), when finishing a task or major feature, before committing or creating a PR, or when about to express satisfaction with work. Covers three practices: receiving feedback with technical rigor (no performative agreement), triggering code review via /code-review command or cook/fix pipelines, and verification gates (run the command, read the output, then make the claim). Never skip — the cost of false completion claims is higher than the cost of verifying. References: code-review-reception.md, requesting-code-review.md, verification-before-completion.md.

日本語の概要は準備中です。原文の説明を表示しています。

Drafts a Chapter 11 Plan of Reorganization under 11 U.S.C. §§ 1121–1129 with claim classification, treatment provisions, distribution mechanics, executory contract determinations, and confirmation compliance. Use when preparing reorganization plans, restructuring debts, classifying claims, drafting Chapter 11 plans, or helping debtors emerge from bankruptcy. Trigger keywords: reorganization plan, Chapter 11, plan of reorganization, debt restructuring, cramdown, claim classification, confirmation order.

日本語の概要は準備中です。原文の説明を表示しています。

Calculates pre-petition interest for bankruptcy proofs of claim and produces a filing-ready worksheet. Covers rate source hierarchy, day-count conventions, simple interest formulas, post-petition rules under 11 U.S.C. § 506(b), and fee inclusion standards. Use when preparing interest components of a proof of claim, calculating creditor claim amounts, or verifying interest calculations.

日本語の概要は準備中です。原文の説明を表示しています。