Menu
Turn a first notification of loss into a structured, complete claim record.
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Based on SOC occupation classification
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/vstorm-co/agenticos --skill claim-intake-triageThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
| name | Claim intake triage |
| description | Turn a first notification of loss into a structured, complete claim record. |
| category | operations |
The aim is a complete record on the first contact. Every field missed here is a week added later.
Policy number · policyholder and whether they are the caller · date, time and place of the incident · what happened, in their words · what was damaged, lost or injured · third parties, with contact details · whether authorities were involved and any reference number · whether anything has been repaired or disposed of already.
Are there photographs? Is the item still in the state it was after the incident? Has anybody else been told — a landlord, an employer, another insurer?
Say what happens next and by when. Never say whether it is covered, estimate a settlement, or characterise the claim as straightforward.
Injury, a third-party fatality, suspected fraud, or a claim near a policy limit. Say a specialist will make contact and stop collecting detail.
Work with messaging-channel bots — Telegram, Slack or Mattermost. Register a bot, route inbound messages through an agent, choose webhook vs polling, handle an @slug mention, or add a new channel adapter. Use when wiring chat into a messaging platform or debugging bot delivery, identity linking or "the bot answered as itself".
Change the agent spec — add or remove a field, rename one, tighten a rule, bump SPEC_VERSION, change publish-time validation, or touch YAML export/import. Use whenever editing app/agents/spec.py or anything that reads a stored spec. Every published agent and every client git repository holds a copy of this format, so a change that only works forwards breaks agents nobody touched.
Work with MCP servers — connect one, add an entry to the server catalog, debug "the agent cannot see my MCP tools" or a failing OAuth flow, or change how connections are probed, prefixed or filtered. Use when the ask involves an external SaaS tool (GitHub, Linear, Notion, Slack, Stripe, Postgres…) and before writing a capability that would just be an API client for one.