agentleFS
NowistayNowistay/claude/skills/welcome-guide/SKILL.md

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.

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
  1. Distinctive:

    Treat every page as structured content unless the full page proves it is paragraph-only.

    line 8
  2. Very specific:

    Call list_welcome_book_pages once to get the page index, IDs, order, icons, and short previews.

    line 15
  3. Distinctive:

    Never edit from the list result.

    line 16
  4. Very specific:

    Before every page update, call get_welcome_book_page for the target page and use its full contents and editingGuidance.

    line 17
  5. Distinctive:

    Never flatten a structured page into plain text.

    line 24
  6. Very specific:

    Use the pageCreationGuidance.contentStructure.blockConstructionTemplates returned by list_welcome_book_pages.

    line 29
  7. Very specific:

    Call upload_welcome_book_image with the required property ID and either a direct public HTTPS image_url or exact-file image_base64.

    line 36
  8. Distinctive:

    Prefer the URL when both are available.

    line 37

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Resolve the property once with list_properties.
  2. Call list_welcome_book_pages once to get the page index, IDs, order, icons, and short previews.
  3. Never edit from the list result. Its text is intentionally shortened and is not editable source.
  4. Before every page update, call get_welcome_book_page for the target page and use its full contents and editingGuidance.

Update a page safely

  1. Copy the complete existing EditorJS document for every affected locale.
  2. Change only the requested visible text or explicitly requested blocks.
  3. Preserve block order, types, IDs, data, tunes, nested list item objects, inline HTML, media, tables, embeds, separators, and unknown fields.
  4. Never flatten a structured page into plain text. Never stringify list item objects. Never paste escaped object representations into visible text.
  5. Stage the full preserved structure with update_welcome_book_page_preview.

Create a page

  1. Use the pageCreationGuidance.contentStructure.blockConstructionTemplates returned by list_welcome_book_pages.
  2. Build exact EditorJS content with time, version, and ordered blocks for each locale.
  3. Choose position=start, position=end, or position=after_page with the correct reference page from the index.
  4. Stage with create_welcome_book_page_preview.

Add images

  1. Call upload_welcome_book_image with the required property ID and either a direct public HTTPS image_url or exact-file image_base64.
  2. Prefer the URL when both are available. Never invent, shorten, or repair base64.
  3. Insert the returned editorJsImageBlock exactly into content.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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.