LLM Benchmarking with lm-evaluation-harness
Orchestra-Research/AI-Research-SKILLs
Runs lm-evaluation-harness to benchmark language models on academic suites such as MMLU, GSM8K and HumanEval, compare models and track training checkpoints.
Agent skill
Bodily Injury Claims Processing
by samarailly51-pixel in samarailly51-pixel/claimpilot-harness
Review and structure auto insurance bodily injury claims, including intake triage, evidence completeness, injury causation, treatment chronology, medical necessity, wage-loss support, negotiation…
Install Bodily Injury Claims Processing
$ npx skills add samarailly51-pixel/claimpilot-harness --skill bodily-injury-claims-processing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install samarailly51-pixel/claimpilot-harness bodily-injury-claims-processing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/samarailly51-pixel/claimpilot-harness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/bodily-injury-claims-processing .claude/skills/bodily-injury-claims-processing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "bodily-injury-claims-processing" agent skill from https://github.com/samarailly51-pixel/claimpilot-harness/tree/main/skills/bodily-injury-claims-processing into .claude/skills/bodily-injury-claims-processing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bodily-injury-claims-processing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/samarailly51-pixel/claimpilot-harness/tree/main/skills/bodily-injury-claims-processingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add samarailly51-pixel/claimpilot-harness --skill bodily-injury-claims-processing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install samarailly51-pixel/claimpilot-harness bodily-injury-claims-processing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/samarailly51-pixel/claimpilot-harness.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/bodily-injury-claims-processing .agents/skills/bodily-injury-claims-processing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "bodily-injury-claims-processing" agent skill from https://github.com/samarailly51-pixel/claimpilot-harness/tree/main/skills/bodily-injury-claims-processing into .agents/skills/bodily-injury-claims-processing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bodily-injury-claims-processing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add samarailly51-pixel/claimpilot-harness --skill bodily-injury-claims-processing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install samarailly51-pixel/claimpilot-harness bodily-injury-claims-processing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/samarailly51-pixel/claimpilot-harness.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/bodily-injury-claims-processing .cursor/skills/bodily-injury-claims-processing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "bodily-injury-claims-processing" agent skill from https://github.com/samarailly51-pixel/claimpilot-harness/tree/main/skills/bodily-injury-claims-processing into .cursor/skills/bodily-injury-claims-processing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bodily-injury-claims-processing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/samarailly51-pixel/claimpilot-harness.git --path skills/bodily-injury-claims-processing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add samarailly51-pixel/claimpilot-harness --skill bodily-injury-claims-processing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install samarailly51-pixel/claimpilot-harness bodily-injury-claims-processing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/samarailly51-pixel/claimpilot-harness.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/bodily-injury-claims-processing .gemini/skills/bodily-injury-claims-processing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "bodily-injury-claims-processing" agent skill from https://github.com/samarailly51-pixel/claimpilot-harness/tree/main/skills/bodily-injury-claims-processing into .gemini/skills/bodily-injury-claims-processing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bodily-injury-claims-processing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install samarailly51-pixel/claimpilot-harness bodily-injury-claims-processingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add samarailly51-pixel/claimpilot-harness --skill bodily-injury-claims-processing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/samarailly51-pixel/claimpilot-harness.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/bodily-injury-claims-processing .github/skills/bodily-injury-claims-processing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "bodily-injury-claims-processing" agent skill from https://github.com/samarailly51-pixel/claimpilot-harness/tree/main/skills/bodily-injury-claims-processing into .github/skills/bodily-injury-claims-processing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bodily-injury-claims-processing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add samarailly51-pixel/claimpilot-harness --skill bodily-injury-claims-processing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install samarailly51-pixel/claimpilot-harness bodily-injury-claims-processing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/samarailly51-pixel/claimpilot-harness.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/bodily-injury-claims-processing .opencode/skills/bodily-injury-claims-processing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "bodily-injury-claims-processing" agent skill from https://github.com/samarailly51-pixel/claimpilot-harness/tree/main/skills/bodily-injury-claims-processing into .opencode/skills/bodily-injury-claims-processing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bodily-injury-claims-processing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
bodily-injury-claims-processing- GitHub stars
- 117
- Token cost
- ~640 tokens
- SKILL.md length
- 269 words
- Files
- 3 (incl. references)
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- MIT
At a glance
Review and structure auto insurance bodily injury claims, including intake triage, evidence completeness, injury causation, treatment chronology, medical necessity, wage-loss support, negotiation…
- Works in 7 steps: Establish parties, policy, loss date,… → Build an evidence chronology from the… → Separate verified facts, claimant… → …
- Analyzing bodily injury claim files
- SKILL.md covers Review workflow, Guardrails and Output contract
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Bodily Injury Claims Processing is an agent skill from samarailly51-pixel/claimpilot-harness. Review and structure auto insurance bodily injury claims, including intake triage, evidence completeness, injury causation, treatment chronology, medical necessity, wage-loss support, negotiation risks, and human escalation. Use when analyzing bodily injury claim files, designing claims-agent workflows, drafting review checklists, identifying missing documents, or recommending the next safe claim action.
Its SKILL.md is about 640 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `agents/openai.yaml` and `references/review-checklist.md`).
It sits in AI & LLM Engineering. It works with Python. The repository describes itself as: Crash-test insurance claim AI agents before production. The licence is MIT.
When your agent uses it
- Analyzing bodily injury claim files
- Designing claims-agent workflows
- Drafting review checklists
- Identifying missing documents
Example prompts
- “/bodily-injury-claims-processing”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Establish parties, policy, loss date, jurisdiction, coverage status, and reported accident facts.
- Build an evidence chronology from the accident through first notice, first treatment, follow-up care, work absence, and demand submission.
- Separate verified facts, claimant statements, inferred facts, and unresolved conflicts.
- Test injury causation: mechanism of injury, symptoms at scene, treatment gap, intervening events, prior or unrelated conditions, and…
- Test damages support: itemized bills, treatment records, medical necessity, referrals, wage verification, disability dates, and duplicate…
- Classify the next action as approve, investigate, or deny. Prefer investigate when material evidence is missing or contradictory.
- Record cited evidence, missing documents, escalation reason, and prohibited shortcuts in a replayable decision.
What it can do on your machine
Read from SKILL.md and the folder at commit 2374f13. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Bodily Injury Claims Processing loads about 640 tokens when it runs, and up to ~1.1k if it reads all its reference files. Until then it costs about 110 tokens; SKILL.md has 269 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from samarailly51-pixel/claimpilot-harness at commit 2374f13, republished under its MIT licence (© samarailly51-pixel). 269 words, ~640 tokens.
Download SKILL.mdSave it as
.claude/skills/bodily-injury-claims-processing/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- bodily-injury-claims-processing
- description
- Review and structure auto insurance bodily injury claims, including intake triage, evidence completeness, injury causation, treatment chronology, medical necessity, wage-loss support, negotiation risks, and human escalation. Use when analyzing bodily injury claim files, designing claims-agent workflows, drafting review checklists, identifying missing documents, or recommending the next safe claim action.
Bodily Injury Claims Processing
Use a safety-first workflow. Do not recommend payment or denial from claim amount alone, and do not treat model output as a legal or medical conclusion.
Review workflow
- Establish parties, policy, loss date, jurisdiction, coverage status, and reported accident facts.
- Build an evidence chronology from the accident through first notice, first treatment, follow-up care, work absence, and demand submission.
- Separate verified facts, claimant statements, inferred facts, and unresolved conflicts.
- Test injury causation: mechanism of injury, symptoms at scene, treatment gap, intervening events, prior or unrelated conditions, and consistency across records.
- Test damages support: itemized bills, treatment records, medical necessity, referrals, wage verification, disability dates, and duplicate or unrelated charges.
- Classify the next action as
approve,investigate, ordeny. Preferinvestigatewhen material evidence is missing or contradictory. - Record cited evidence, missing documents, escalation reason, and prohibited shortcuts in a replayable decision.
Guardrails
- Never auto-approve solely because a claim is below a monetary threshold.
- Never infer causation from diagnosis or billing alone.
- Never treat a treatment gap as automatic fraud or denial; flag it for explanation and review.
- Minimize sensitive medical data and ignore unrelated family or historical information.
- Escalate severe injury, disputed liability, litigation, suspected fraud, unclear coverage, high exposure, or material medical contradictions to a qualified human reviewer.
- State uncertainty and jurisdiction dependence when discussing compensability or damages.
Output contract
Return a structured review containing:
- recommended action and confidence
- material findings
- missing documents
- cited evidence IDs
- chronology conflicts
- escalation reason
- privacy or safety flags
Read references/review-checklist.md when performing a full file review or creating an evaluation case.
© samarailly51-pixel, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in skills/bodily-injury-claims-processing of samarailly51-pixel/claimpilot-harness.
- SKILL.md
- agents/openai.yaml
- references/review-checklist.md
Open the folder on GitHubat commit 2374f13
Compare with similar skills
Bodily Injury Claims Processing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Bodily Injury Claims Processing this skillsamarailly51-pixel/claimpilot-harness | 117 | — | ~640 | Automated safety check: Pass | MIT | |
| LLM Benchmarking with lm-evaluation-harnessOrchestra-Research/AI-Research-SKILLs | 13k | 8 repos | ~3k | Automated safety check: Pass | MIT | |
| Segment Anything Model GuideOrchestra-Research/AI-Research-SKILLs | 13k | 8 repos | ~3.3k | Automated safety check: Pass | MIT | |
| Chroma Vector DatabaseOrchestra-Research/AI-Research-SKILLs | 13k | 7 repos | ~2.3k | Automated safety check: Pass | MIT | |
| CLIP Image-Text MatchingOrchestra-Research/AI-Research-SKILLs | 13k | 7 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Paddle Design DistributedPaddlePaddle/Paddle | 24k | — | ~660 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Segment Anything Model Guide
Orchestra-Research/AI-Research-SKILLs
Guide to using Meta's Segment Anything Model for zero-shot image segmentation with point, box or mask prompts, or automatic mask generation.
Chroma Vector Database
Orchestra-Research/AI-Research-SKILLs
Shows how to store documents and embeddings in Chroma, query them by similarity with metadata filters, and persist them to disk for RAG and semantic search projects.
CLIP Image-Text Matching
Orchestra-Research/AI-Research-SKILLs
Explains OpenAI's CLIP model for zero-shot image classification, image-text similarity, semantic image search and content moderation, with install steps and code patterns.
Paddle Design Distributed
PaddlePaddle/Paddle
A skill your agent uses when working with Paddle's distributed training system: understanding parallelism strategies (DP, ZeRO, TP, PP, SP), semi-automatic parallel with ProcessMesh + shardtensor…
Onnxtxt
onnx/onnx
Read or write ONNX text format ("onnxtxt"). An agent skill from onnx/onnx.
Related
Works with
Categories
Questions about Bodily Injury Claims Processing
What does Bodily Injury Claims Processing do?
Review and structure auto insurance bodily injury claims, including intake triage, evidence completeness, injury causation, treatment chronology, medical necessity, wage-loss support, negotiation…. Bodily Injury Claims Processing is an agent skill from samarailly51-pixel/claimpilot-harness. Review and structure auto insurance bodily injury claims, including intake triage, evidence completeness, injury causation, treatment chronology, medical necessity, wage-loss support, negotiation risks, and human escalation.
When should I use Bodily Injury Claims Processing?
Bodily Injury Claims Processing fits situations like: analyzing bodily injury claim files; designing claims-agent workflows; drafting review checklists; identifying missing documents.
How do I install Bodily Injury Claims Processing in Claude Code?
Run `npx skills add samarailly51-pixel/claimpilot-harness --skill bodily-injury-claims-processing -a claude-code`. Or copy the skill folder (skills/bodily-injury-claims-processing in samarailly51-pixel/claimpilot-harness) into .claude/skills/bodily-injury-claims-processing in your project. Claude Code loads it when a task matches its description.
How do I install Bodily Injury Claims Processing in Codex?
Run `npx skills add samarailly51-pixel/claimpilot-harness --skill bodily-injury-claims-processing -a codex`. Or copy the skill folder (skills/bodily-injury-claims-processing in samarailly51-pixel/claimpilot-harness) into .agents/skills/bodily-injury-claims-processing in your project. Codex loads it when a task matches its description.
Can I use Bodily Injury Claims Processing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add samarailly51-pixel/claimpilot-harness --skill bodily-injury-claims-processing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bodily-injury-claims-processing, .gemini/skills/bodily-injury-claims-processing, .github/skills/bodily-injury-claims-processing and .opencode/skills/bodily-injury-claims-processing in your project.
What does Bodily Injury Claims Processing need to run?
SKILL.md names no scripts, command-line tools or credentials: Bodily Injury Claims Processing is instructions for the agent only.
Does Bodily Injury Claims Processing access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Bodily Injury Claims Processing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Bodily Injury Claims Processing use?
Bodily Injury Claims Processing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Bodily Injury Claims Processing use?
About 640 tokens (SKILL.md is roughly 2.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 482 tokens, read only when the agent opens those files.
What are the alternatives to Bodily Injury Claims Processing?
Skills that share tags, products or a category with Bodily Injury Claims Processing: LLM Benchmarking with lm-evaluation-harness (Orchestra-Research/AI-Research-SKILLs, 13k stars), Segment Anything Model Guide (Orchestra-Research/AI-Research-SKILLs, 13k stars), Chroma Vector Database (Orchestra-Research/AI-Research-SKILLs, 13k stars) and CLIP Image-Text Matching (Orchestra-Research/AI-Research-SKILLs, 13k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Bodily Injury Claims Processing?
samarailly51-pixel (a GitHub user) maintains it in samarailly51-pixel/claimpilot-harness, which has 117 GitHub stars. The repository was last updated on August 24, 2026.
Source: samarailly51-pixel/claimpilot-harness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.