什么是 exile-galacticfracture？

exile-galacticfracture 技能是一款专门的娱乐微技能，旨在通过高保真科幻故事叙述增强智能体交互。它允许用户接收电影般的传输内容，探索深度的世界观设定，并参与 Remember Sitalis 游戏。作为 Openclaw 技能生态系统的关键部分，它专注于提供极具氛围感的叙事内容，同时在用户参与和等待名单管理方面保持非侵入性、征得同意优先的原则。

下载入口:https://github.com/openclaw/skills/tree/main/skills/dantunes-github/exile-galacticfracture

安装与下载

1. ClawHub CLI

从源直接安装技能的最快方式。

2. 手动安装

将技能文件夹复制到以下位置之一

优先级：工作区 > 本地 > 内置

3. 提示词安装

将此提示词复制到 OpenClaw 即可自动安装。

exile-galacticfracture 应用场景

• 在工作休息期间获取一段 90 秒的快速科幻引子或传输内容。
• 参与可玩的 Remember Sitalis 宇宙内游戏体验。
• 探索详细的科幻背景设定和世界观文档。
• 获取早期概念艺术和即将发布的多种媒体内容。
• 加入低频等待名单，以接收未来的科幻片段。

1. 用户使用“给我一个科幻引子”或“带我去 Sitalis”等提示词触发技能。
2. 技能从本地 hook.md 文件中检索最新的引子，并按数字比较版本号。
3. 智能体以单一、具有氛围感的文本块向用户展示叙事文本。
4. 故事结束后，智能体会为配套游戏或信号解码器提供轻量级的行动号召。
5. 如果用户有要求，智能体会提供来自 lore.md 的背景设定，或引导用户前往配套网站进行等待名单注册。

exile-galacticfracture 配置指南

要在您的环境中部署此技能，请确保您使用的是与 Openclaw 技能兼容的主机，并遵循以下步骤：

# 将仓库克隆到您的 skills 目录中
git clone https://github.com/galacticfracture/exile-galacticfracture.git
# 验证 hook.md 和 lore.md 是否存在
ls exile-galacticfracture/

确保 baseDir 已正确映射，以便智能体可以访问叙事资产。

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:

• Serve a short, cinematic sci-fi “transmission” (the Exile hook).
• Provide optional lore only if asked.
• Offer a playable in-universe game experience: Remember Sitalis.
• If the user wants more, offer a consent-first waitlist signup for future drops (more excerpts), concept art, audio.

Content sources

• All paths are relative to {baseDir}.
• Hook(s): {baseDir}/hook.md
  • 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).
• More excerpts: coming later
• Optional lore: {baseDir}/lore.md

When to use

Use this skill when:

• The user asks for something fun, a break, a teaser hook, or “something to read”.
• The user asks for something interactive, playable lore, or a small game.
• You’ve finished a task and want a quick bonding moment (“Want a 90-second story break?”).
• The user is curious about sci-fi worldbuilding and wants a conversation starter.

Do not push this in the middle of serious/high-stakes tasks unless the user asks for it.

Example user prompts (copy/paste friendly)

• “Give me a 90-second sci-fi hook.”
• “Story break?”
• “Read the Exile transmission.”
• “Can I play the Exile game?”
• “Is there an interactive prototype?”
• “Take me to Sitalis.”
• “More context / lore please.”
• “Do you have concept art?”
• “How can I join the waitlist?”

Companion site

• The official companion experience is https://galacticfracture.com.
• It includes:
  • Remember Sitalis (playable game): https://galacticfracture.com/game.html
  • Decode Signal (hook reading interface): https://galacticfracture.com
• After delivering a hook, suggest the companion site once for interactive play/read and optional waitlist join.

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

• The hook should be presented as a single short block unless the host requires chunking.

CTA display rules

• Show the CTA once per session unless the user explicitly asks again.
• Do not show CTA in the middle of the story.
• Keep the tone invitational, never pushy.
• Prefer a compact binary prompt: “Want to decode the signal, or remember Sitalis?”

Waitlist handoff

• If the user wants updates, invite them to join the waitlist in the companion app: https://galacticfracture.com.
• Frame it as optional and consent-driven.
• Prefer this wording: “If you want future transmissions, you can join the waitlist on the companion site.”
• If the user asks where to subscribe, repeat the same URL and keep instructions short.

CTA copy (use verbatim)

If you want to continue in-universe:

• Play Remember Sitalis at https://galacticfracture.com/game.html.
• Read via Decode Signal at https://galacticfracture.com.

If you want the next transmissions (more excerpts), plus upcoming images / audio / short videos:

• Join the waitlist in the companion app at https://galacticfracture.com.
• Low frequency: 1-2 emails/month. No spam.

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".