property-knowledge
Skill0 starsChanged 37 days agoMITView on GitHub
Maintain the private Nowistay AI co-host knowledge base for each property. Use to list, search, add, correct, or copy reusable property questions and answers such as policies, equipment details, access guidance, and local recommendations.
In this repository8 other files it gives its agents.
- calendar-revenueSkill
- daily-briefSkill
- direct-bookingsSkill
- guest-messagingSkill
- guest-recordsSkill
- portfolio-reportingSkill
- team-operationsSkill
- welcome-guideSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Use list_property_knowledge_questions with limit=100.
- Very specific: line 16
Use get_property_knowledge_question only when one exact record needs verification before an update.
- Distinctive: line 21
Check for an existing equivalent question before creating a new one.
- Very specific: line 22
Use create_property_knowledge_question_preview for new Q&A and update_property_knowledge_question_preview for corrections.
- Very specific: line 29
Use copy_property_knowledge_questions_preview with selected question_ids, or omit them to copy all source Q&As.
- Distinctive: line 31
Use one multi-target copy rather than repeating one copy per property.
- Distinctive: line 33
If the user asked only for a proposal, stop at the preview.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Nowistay Property Knowledge
Manage private Q&A knowledge separately from the public welcome guide.
Store reusable property facts, not guest records. Do not add guest names, contact details, booking references, message transcripts, private notes, payment data, government identifiers, medical or biometric data, account credentials, or other guest-specific information to the knowledge base.
Read and find
- Resolve source and target properties once with
list_properties. - Use
list_property_knowledge_questionswithlimit=100; paginate only when needed. Usesearchto avoid loading the full knowledge base for a focused question. - Use
get_property_knowledge_questiononly when one exact record needs verification before an update. - Present questions and answers conversationally. Keep internal IDs out of the response unless needed for disambiguation.
Add or update
- Check for an existing equivalent question before creating a new one.
- Use
create_property_knowledge_question_previewfor new Q&A andupdate_property_knowledge_question_previewfor corrections. - Preserve
need_hostunless the user explicitly changes whether future answers require host intervention. - Summarize the exact question, answer, property, and host-review setting.
Copy between properties
- List the source Q&As first and resolve every target property.
- Use
copy_property_knowledge_questions_previewwith selectedquestion_ids, or omit them to copy all source Q&As. - Explain that copying is a safe merge: matching normalized questions are skipped and target knowledge is never deleted or replaced.
- Use one multi-target copy rather than repeating one copy per property.
If the user asked only for a proposal, stop at the preview. If the user explicitly requested the write, call the matching confirm tool with only the approval token. Do not expose vector-store or database implementation details.
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.

