welcome-guide
Skill0 starsChanged 37 days agoMITView on GitHub
Create and edit structured Nowistay welcome guides while preserving headings, lists, images, videos, tables, separators, translations, and EditorJS formatting. Use for page creation, page updates, translations, reordering, image uploads, and guide-wide locale or intro changes.
In this repository8 other files it gives its agents.
- calendar-revenueSkill
- daily-briefSkill
- direct-bookingsSkill
- guest-messagingSkill
- guest-recordsSkill
- portfolio-reportingSkill
- property-knowledgeSkill
- team-operationsSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 4 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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
- Distinctive: line 8
Treat every page as structured content unless the full page proves it is paragraph-only.
- Very specific: line 15
Call list_welcome_book_pages once to get the page index, IDs, order, icons, and short previews.
- Distinctive: line 16
Never edit from the list result.
- Very specific: line 17
Before every page update, call get_welcome_book_page for the target page and use its full contents and editingGuidance.
- Distinctive: line 24
Never flatten a structured page into plain text.
- Very specific: line 29
Use the pageCreationGuidance.contentStructure.blockConstructionTemplates returned by list_welcome_book_pages.
- Very specific: line 36
Call upload_welcome_book_image with the required property ID and either a direct public HTTPS image_url or exact-file image_base64.
- Distinctive: line 37
Prefer the URL when both are available.
≈ “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 Welcome Guide
Treat every page as structured content unless the full page proves it is paragraph-only.
Welcome guides contain reusable property information. Do not add guest-specific personal data, booking references, private messages, payment data, government identifiers, medical or biometric data, or account credentials.
Find the page
- Resolve the property once with
list_properties. - Call
list_welcome_book_pagesonce to get the page index, IDs, order, icons, and short previews. - Never edit from the list result. Its text is intentionally shortened and is not editable source.
- Before every page update, call
get_welcome_book_pagefor the target page and use its fullcontentsandeditingGuidance.
Update a page safely
- Copy the complete existing EditorJS document for every affected locale.
- Change only the requested visible text or explicitly requested blocks.
- Preserve block order, types, IDs,
data,tunes, nested list item objects, inline HTML, media, tables, embeds, separators, and unknown fields. - Never flatten a structured page into plain text. Never stringify list item objects. Never paste escaped object representations into visible text.
- Stage the full preserved structure with
update_welcome_book_page_preview.
Create a page
- Use the
pageCreationGuidance.contentStructure.blockConstructionTemplatesreturned bylist_welcome_book_pages. - Build exact EditorJS content with
time,version, and orderedblocksfor each locale. - Choose
position=start,position=end, orposition=after_pagewith the correct reference page from the index. - Stage with
create_welcome_book_page_preview.
Add images
- Call
upload_welcome_book_imagewith the required property ID and either a direct public HTTPSimage_urlor exact-fileimage_base64. - Prefer the URL when both are available. Never invent, shorten, or repair base64.
- Insert the returned
editorJsImageBlockexactly intocontent.blocks. Never insert the URL or base64 directly as page text.
Apply changes
Summarize the exact page, locales, placement, and changed blocks. If the user asked only for a preview, stop. If the user explicitly requested the change, call the matching confirm tool with only the approval token. Do not reconstruct page content during confirmation.
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.

