agentleFS
jammyfujammyfu/open-game-skills/skills/disciplines/climb-vault/SKILL.md

climb-vault

Skill13 starsChanged 24 days agoMITView on GitHub

Use when characters need ledge mantle, vault, or sustained climb states with explicit geometry probes, attach/detach transitions, stamina policy, and failure recovery.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Test reachable/unreachable ledges, too-steep surfaces, blocked destination volume, moving geometry if supported, resource exhaustion and …

    line 27

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

Climb and vault

Choose:

ColumnCapability
mantleshort ledge transition
full-climbsustained surface traversal
vaultcross a low authored obstacle
no-climbno climb transition

Rules

  1. Detect candidates with declared geometry evidence: reach volume, surface normal/slope, ledge clearance and destination body clearance. A visual edge alone is not a valid mantle target.
  2. Attach, traverse, crest and detach are logical movement states with explicit interrupt/failure paths. Do not teleport directly from ground to roof because an animation looks correct.
  3. Optional stamina/resource drain is published through stamina-clock or another explicit owner; running out transitions to a legal detach/fall state.
  4. Physical button mapping and whether jump/interact share a control are owned by input-design. This skill requests semantic actions such as jump, interact, climb and does not mandate a physical key layout.
  5. camera-anti-clip still validates the final camera near walls; fall-rules owns consequences after a failed detach.

Accept

Test reachable/unreachable ledges, too-steep surfaces, blocked destination volume, moving geometry if supported, resource exhaustion and interruption. The actor never snaps through a blocker or becomes stuck in an attached state. Debug output shows the candidate surface, destination clearance and state transition reason.

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.