agentleFS
jammyfujammyfu/open-game-skills/skills/disciplines/adventure-tool/SKILL.md

adventure-tool

Skill13 starsChanged 24 days agoMITView on GitHub

Use when a signature traversal/combat/puzzle tool needs a small verb kit, target-capability contract and interruption rules across swing, yank, grapple or optional weapon use. It does not impose one genre's ammo or puzzle philosophy.

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:

    Do not assume guns are scarce, puzzles come first, or the tool must clear a gap without a weapon.

    line 24

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

Adventure tool

Ask: tool-swing | tool-yank | tool-and-gun.

Ownership

This skill composes a signature tool's verbs. Grapple physics may delegate to grapple-swing / physics-interaction; ranged fire to projectile-hitscan; puzzle teaching to puzzle-design / level-teach; bindings to input-design.

Contract

Define stable:

  • tool_action_id
  • required target capability/tag
  • startup/active/recovery or interaction phases from the project's action clock
  • resource/cooldown owner if any
  • interruption/cancel policy
  • authoritative success/failure event

Do not assume guns are scarce, puzzles come first, or the tool must clear a gap without a weapon. Those are project design choices.

A target may advertise pullable, swingable, cuttable, shootable or another project capability. Presentation cannot make an unsupported target legal.

Acceptance

The same tool action against the same target capability/state produces the same authoritative result. Interrupted actions cannot double-apply, stale targets fail closed, and optional ranged/ammo policy remains owned by its dedicated system rather than this skill.

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.