Exit — Room Navigation Links

VerifiedSafe

An Exit is a navigation link connecting two rooms in MOOLLM's spatial architecture, acting as an edge in the memory palace graph. It can be simple, guarded, hidden, or metaphysical, and uses pie menu directions (N/S/E/W, etc.) to encode meaning. This skill helps create interactive worlds where direction itself carries significance.

Sby Skills Guide Bot
DevelopmentIntermediate
6/2/2026
Claude Code
#navigation#memory-palace#adventure#topology

Recommended for

Automated summary

This skill enables creating navigation links between rooms in a memory palace, supporting simple, guarded, hidden, one-way, and metaphysical exits with a pie menu direction system.

Strengths

  • Supports multiple exit types (simple, guarded, hidden, etc.)
  • Integrates with a guard system using natural language or code conditions
  • Uses pie menu directional semantics to encode meaning
  • Facilitates building non-linear interactive worlds

Limitations

  • Requires strict YAML structure for each exit
  • Limited to the specific MOOLLM memory palace architecture
  • Compiled guards may require an external compilation step
When to use it

When building an interactive fiction or memory palace that requires conditional or contextual spatial navigation.

When not to use it

When you need simple hyperlinks without conditions or directional semantics, or if your project is not based on MOOLLM architecture.

Security analysis

Safe
Quality score95/100

The skill describes navigation links between rooms, using read_file and write_file tools for file operations within a memory palace system. There are no destructive commands, external network calls, or unsafe code execution. The guard system mentions compiled code, but the skill itself does not execute it, only defines a format.

No concerns found

How this analysis is made

Examples

Simple exit to library
Create an exit from the entrance room going north to the library at ../library/ with description 'A well-lit corridor leads to the library.'
Guarded exit with key
Add a guarded exit in the dungeon going east to the armory, locked with 'rusty-key', guard condition 'player has rusty key', lock message 'The rusty lock won't turn.'
Hidden exit in cellar
Define a hidden exit in the cellar going down to the secret chamber at ../secret/, with hint 'The brick wall sounds hollow...' and hidden: true.

name: exit description: Navigation links between rooms — the edges of the memory palace allowed-tools:

  • read_file
  • write_file tier: 1 protocol: PIE-MENU-TOPOLOGY tags: [moollm, navigation, room, topology, pie-menu] related: [room, adventure, memory-palace] adversary: dead-end

Exit

"Every exit is a promise of adventure." — The Rusty Lantern Guest Book


What Is It?

An Exit is a navigation link connecting one room to another. In MOOLLM's spatial architecture, exits are the EDGES of the memory palace graph.

Exits can be:

  • Simple — just a destination
  • Guarded — require conditions to pass
  • Hidden — discoverable through exploration
  • Metaphysical — conceptual rather than physical

Pie Menu Topology

Don Hopkins' pie menu insight: direction IS meaning.

| Direction | Purpose | |-----------|---------| | N/S/E/W | "Highway" links to major rooms | | NW/NE/SW/SE | "Grid" links to expandable sub-rooms | | UP/DOWN | Vertical transitions | | IN/OUT | Conceptual transitions |

Cardinal directions form the spiderweb — the main navigation network. Diagonal directions form grids — expandable arrays of sub-rooms.


Guard System

Guards are natural language conditions that control access:

guard: "player has the brass key"
guard_js: "(ctx) => ctx.player.inventory.includes('brass-key')"
guard_py: "lambda ctx: 'brass-key' in ctx.player.inventory"

The guard field contains human-readable intent. The guard_js and guard_py fields contain compiled code.

The adventure compiler emits COMPILE_EXPRESSION events for guards that need compilation.


Exit Types

Simple Exit

north:
  destination: ../maze/room-a/
  description: "A dark passage leads north."

Guarded Exit

east:
  destination: ../treasury/
  description: "A heavy iron door."
  guard: "player has treasury key"
  locked: true
  lock_message: "The door won't budge."
  unlock_with: "treasury-key"

Hidden Exit

down:
  destination: ../secret-cellar/
  hidden: true
  hint: "The rug seems oddly placed..."

One-Way Exit

down:
  destination: ../pit/
  one_way: true
  description: "A slide into darkness. No going back."

Metaphysical Exit

inward:
  destination: ../consciousness/
  metaphysical: true
  description: "Close your eyes and think about who you really are."

Memory Palace Integration

From Frances Yates' "The Art of Memory":

"The method of loci places items at specific locations along an imagined journey."

Every exit is a doorway in the memory palace. The direction encodes meaning. Players navigate by spatial memory.


Related Skills


Protocol Symbol

PIE-MENU-TOPOLOGY — Direction IS meaning

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/exit-room-navigation-links-mm78nnco/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/exit-room-navigation-links-mm78nnco' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/exit-room-navigation-links-mm78nnco/download' --output '.skill-downloads/exit-room-navigation-links-mm78nnco/SKILL.md.part' && mv '.skill-downloads/exit-room-navigation-links-mm78nnco/SKILL.md.part' '.skill-downloads/exit-room-navigation-links-mm78nnco/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/exit-room-navigation-links-mm78nnco/SKILL.md' && test -s '.skill-downloads/exit-room-navigation-links-mm78nnco/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/exit' && cp -R '.skill-downloads/exit-room-navigation-links-mm78nnco' '.claude/skills/exit'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/exit-room-navigation-links-mm78nnco'

openskills read 'exit-room-navigation-links-mm78nnco'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/exit-room-navigation-links-mm78nnco/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills