Sharing Hub Reference

Share Prompts
Without Losing Structure

Use GitHub Gists to publish single prompts or entire tribes. Keep secret by default, control confidentiality, and ship structured .spore.md workflows.

Back to Support Open Promptfile Reference Create GitHub Token
• Single prompt gist support • Tribe multi-file gist support • Confidentiality controls

How It Works

5-Step Flow
GitHub connection settings
Step 01

Connect GitHub in Settings

Connect with a Personal Access Token that includes gist scope, verify "Connected as @username", and configure defaults: Create secret gists by default and Allow sharing high-confidentiality prompts.

Tribe selection dialog
Step 02

Select a tribe and review prompts

Open Settings → Sharing → Share Tribe..., choose a tribe_id, inspect the included prompt list, and pick visibility (secret or public). High confidentiality prompts show warning indicators and are excluded unless your setting allows them.

Shared confirmation
Step 03

Share and capture the result URL

After upload, Spore shows a "Tribe Shared" dialog with the generated gist URL and direct actions: Open in Browser and Copy URL.

GitHub Gist multiple files
Step 04

GitHub receives one multi-file gist

Tribe sharing creates a single gist whose files are the prompts in that tribe. You can see multiple .spore.md files under one gist description, such as Spore tribe: exo-cortex (8 prompts).

My Gists view
Step 05

Review from View My Gists

Use View My Gists to list Spore-related gists. The list focuses on .spore.md entries for quick browse, copy URL, open, and delete operations.

Important Clarification
  • Share Tribe... does not merge existing GitHub gists.
  • It creates a new multi-file gist from local promptfiles sharing the same tribe_id.
  • To share a workflow, assign the same tribe_id in front matter, then use Settings → Sharing → Share Tribe....
01 Add tribe_id to multiple .spore.md files.
02 Open Settings → Sharing → Share Tribe....
03 Choose tribe and visibility (Secret/Public).
04 Spore uploads one multi-file Gist asset.

Privacy and Controls

Operational Rules

PAT Requirement

GitHub sharing requires a Personal Access Token with gist scope. Your token is stored locally in your keychain.

Secret by Default

Secret gist creation is enabled by default to prevent accidental data leaks. This behavior is fully configurable in sharing preference.

High Confidentiality Gating

Prompts marked confidentiality: high are strictly blocked from sharing unless you explicitly enable the safety override in Settings.

Empty Share Guard

Spore prevents creating empty gists. If all prompts in a selected tribe are excluded by privacy rules, the sharing process will be safely aborted.

Troubleshooting

Practical Checks
No Tribes Found
Add tribe_id to the front matter of multiple .spore.md files, then reopen Settings → Sharing → Share Tribe....
GitHub auth fails
Refresh your Personal Access Token (PAT) on GitHub, confirm it includes gist scope, and reconnect under Settings → Sharing.
A prompt is missing from tribe share
Check whether the prompt is marked confidentiality: high and whether "Allow sharing high-confidentiality prompts" is enabled in your Spore Sharing preference.
Expected old gists to be grouped automatically
Tribe sharing creates a single new multi-file gist from current local files. It does not combine or re-group previously existing GitHub gists.
Can I share one prompt instead of a tribe?
Yes. Open any prompt window, click the share icon in the bottom bar, and use Create Secret Gist or Create Public Gist.