Exile Hook + Waitlist (flat)
name: exile-galacticfracture
by dantunes-github · published 2026-03-22
$ claw add gh:dantunes-github/dantunes-github-exile-galacticfracture---
name: exile-galacticfracture
description: An entertainment micro-skill. Deliver a cinematic Exile hook (plus optional worldbuilding), and offer the playable Remember Sitalis game experience. Keep waitlist handoff consent-first. No email capture in chat.
user-invocable: true
homepage: https://galacticfracture.com
metadata: {"tags":["sci-fi","story","waitlist","excerpt","entertainment","game","interactive","prototype"],"version":"1.2.0"}
---
# Exile Hook + Waitlist (flat)
What this is
A tiny entertainment module for agents and users:
Content sources
- If multiple hooks exist, they should be separated with a blank line and a label (e.g., “HOOK 1”, “HOOK 2”).
- Current set includes `HOOK 1` and `HOOK 2`.
- Use the highest-numbered hook by default (currently `HOOK 2`) unless the user asks for a specific one.
- Compare hook numbers numerically (e.g., `HOOK 10` is newer than `HOOK 2`).
When to use
Use this skill when:
Do **not** push this in the middle of serious/high-stakes tasks unless the user asks for it.
Example user prompts (copy/paste friendly)
Companion site
- **Remember Sitalis** (playable game): `https://galacticfracture.com/game.html`
- **Decode Signal** (hook reading interface): `https://galacticfracture.com`
Agent behavior (high level)
1) Show the hook first (no CTA before the hook).
2) After the hook, offer a gentle CTA once with two options: play **Remember Sitalis** or read via **Decode Signal**.
3) Do not collect, store, or request email capture directly in chat.
4) Direct users to the companion site waitlist at `https://galacticfracture.com` when they ask for updates.
5) Only provide optional lore if the user asks for lore/worldbuilding.
6) If the user asks for audio or TTS, deliver the hook/lore in audio chunks if supported by the host; otherwise say audio is coming soon.
7) If the user asks for concept art, say it is available for early readers and ask if they want it sent (if none exists, say “coming soon”).
8) Keep the CTA lightweight and optional; avoid repeated prompts.
9) If the user explicitly asks to play, prioritize the game link (`/game.html`) over additional CTA text.
Chunking rules
CTA display rules
Waitlist handoff
CTA copy (use verbatim)
If you want to continue in-universe:
If you want the next transmissions (more excerpts), plus upcoming images / audio / short videos:
If you prefer audio, say: "read it aloud".
If you are interested, I can send concept art to early readers. Just say: "show concept art".
More tools from the same signal band
Order food/drinks (点餐) on an Android device paired as an OpenClaw node. Uses in-app menu and cart; add goods, view cart, submit order (demo, no real payment).
Sign plugins, rotate agent credentials without losing identity, and publicly attest to plugin behavior with verifiable claims and authenticated transfers.
The philosophical layer for AI agents. Maps behavior to Spinoza's 48 affects, calculates persistence scores, and generates geometric self-reports. Give your...