agentleFS
jammyfujammyfu/open-game-skills/skills/disciplines/cover-shooter/SKILL.md

cover-shooter

Skill13 starsChanged 25 days agoMITView on GitHub

Use when an actor enters, occupies, peeks, fires from, and exits authored cover and needs one cover-session state machine with explicit interruption and ownership handoff.

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:

    If the anchor becomes stale, blocked, destroyed, or the actor is interrupted, the session exits or re-resolves without leaving two movement …

    line 30

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

Cover shooter

Ask: stick-cover | tap-cover | soft-cover.

Ownership

cover-shooter owns the actor's cover-session state. cover-space owns valid anchors/capabilities; projectile-hitscan owns shots; aim-assist / fps-feel own aim/handling; input-design owns bindings.

Contract

Publish:

  • stable cover_session_id
  • actor ID and cover_anchor_id + revision
  • state: enter / attached / peek / fire / exit / aborted
  • movement-control owner
  • authored transition/cancel conditions
  • optional stance/fire-side selected from anchor capabilities

Exactly one system owns the actor's cover locomotion at a time. Duplicate enter/exit requests for one session are idempotent. Cover state does not imply invulnerability unless another gameplay rule explicitly grants it.

Blind/peek fire produces a normal shot request with declared origin/direction/handling state; it does not maintain a second shooting truth.

Acceptance

If the anchor becomes stale, blocked, destroyed, or the actor is interrupted, the session exits or re-resolves without leaving two movement owners. Firing from cover produces one authoritative shot path through projectile-hitscan, and exiting cover cannot replay a stale fire input.

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.