Draft demand
A first pass from the pages you uploaded. Paste it onto your letterhead. The model does not invent policy limits or facts that are not on those pages.
Free skill
Demand from the File
Draft a PI demand from the records you already have. Lists what is missing. Not a firm brain. Wiring the case system, mail, and folder is the partnership. Every send still needs human approval.
What you get
Four things, every run.
Damages table
Only lines supported by a cited page. If the number is not in the packet, it is a gap, not a guess.
Exhibit index
What was actually in the packet, so staff can see what the draft rested on.
Gap list
Policy limits not in the file. Missing wage docs. Treatment after the last record. Case-system balances the skill cannot see. That list is the point.
What it is not
The paste loop, named.
Staff already live in frontier workspaces. This skill runs on the files they upload there. It cannot see Clio, Gmail, or the folder. It will not send, file, or email a carrier. Not legal advice.
If the gap list is the useful part, that is the FirmOps conversation: one bottleneck, human approval, then we wire the file.
Next step
That is the public skill. The firm brain is the wiring.
Bring one bottleneck. We will show what is safe to draft from the file, and what still needs human approval.
Request demo