open-home-feedback
Skill0 starsChanged 10 days agoLicence not identifiedView on GitHub
Open specification for following up open-home attendees and reporting to the vendor: the sign-in register read as written, no follow-up without consent recorded at sign-in, one attendee across opens, a draft with one question that a person approves before it sends, an opt-out honoured across every listing, every reply classified as hot buyer, price feedback, not interested or appraisal lead, an offer or a complaint handed to the agent unanswered, a vendor report of counts and verbatim price comments with no invented sentiment that the agent approves before it goes, and a record of who said what that answers a vendor dispute. Free to implement, with a conformance checklist, a runnable stub and a copyable Google Sheet. Use when building, reviewing or auditing this workflow. Carries the AIP-BS-OPEN-HOME-FEEDBACK 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
- cash-seamSkill
- 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
- 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.