cash-seam
Skill0 starsChanged 11 days agoLicence not identifiedView on GitHub
One record survives from the call to the chase. Binds Booked After Hours, Quote Out, Invoice Out and Debtor Chasing at the handovers: every downstream id read from the job system or the ledger, never minted or matched on a name or a phone number; one job per enquiry with a repeat call attached as duplicate_of; a write with no external id treated as not written; the quote carrying the job id, the invoice the quote or job id, the chase the invoice id off the live ledger; a chat confirmation never a write or a release; every hop woken by a named event; the exception owner on the record. Free to implement, with a conformance checklist. Use when building, reviewing or auditing this workflow. Carries the AIP-BS-CASH-SEAM open standard, free to implement under CC BY 4.0.
In this repository44 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/aipathway-standards.mdcCursor rule
- advice-fileSkill
- booked-after-hoursSkill
- cited-answerSkill
- client-deskSkill
- client-memorySkill
- compliance-calendarSkill
- database-reactivationSkill
- debtor-chasingSkill
- dispatch-boardSkill
- document-filingSkill
- exception-deskSkill
- fault-triageSkill
- fire-service-pack-standardSkill
- follow-upSkill
- inbox-triageSkill
- invoice-checkSkill
- invoice-outSkill
- job-briefSkill
- job-closeSkill
- just-sold-packSkill
- knowledge-baseSkill
- knowledge-graphSkill
- material-orderSkill
- multi-site-conformanceSkill
- next-serviceSkill
- open-home-feedbackSkill
- parts-readySkill
- price-one-pagerSkill
- progress-claim-draftSkill
- quote-outSkill
- recurring-reportSkill
- rejected-packSkill
- remittance-splitSkill
- rent-arrearsSkill
- review-requestSkill
- servicem8-health-checkSkill
- simpro-claude-connectorSkill
- takeaway-ordersSkill
- timesheet-checkSkill
- two-recordsSkill
- virtual-adminSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.