agentleFS
jammyfujammyfu/open-game-skills/skills/disciplines/durability-economy/SKILL.md

durability-economy

Skill13 starsChanged 25 days agoMITView on GitHub

Use when tools or equipment can wear, dull, break, repair, consume charges, or recover condition and the wear transaction, warning policy, replacement flow, or economy pressure is unclear.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every wear/repair event has a stable cause/transaction identity when duplicate callbacks are possible.

    line 23
  2. Very specific:

    Test condition at one-before/at/after thresholds, duplicate wear events, interrupted repair, save/load, break or minimum-condition state, …

    line 31

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

Durability Economy

This skill owns condition state and wear/repair transactions. It does not author hitstop, cancel windows, inventory capacity, or item progression identity.

Modes

ModeCondition model
consumeinstance can reach an authored terminal/broken state
sharpnesseffectiveness changes across condition bands
repaircondition is restored by an authored repair transaction
unbreakableno durability state

Wear contract

Publish what events spend condition: hit contact, shot fired, block received, elapsed use, environment interaction, charges, or another project rule. Misses, soft targets and hard-target multipliers are project-specific; do not assume one mass/contact formula fits every tool.

Every wear/repair event has a stable cause/transaction identity when duplicate callbacks are possible. Applying the same logical event twice must not double-spend or double-repair condition.

Warnings are authored presentation tied to condition thresholds or predicted remaining uses. The number of warning hits, swap time, break animation and replacement availability are project data.

Economy balance may target replacement abundance, scarcity, field maintenance or permanent gear. A fight does not universally need to refund at least the wear it consumed; validate the selected economy using inventory-economy, loot-roll and play evidence.

Acceptance

Test condition at one-before/at/after thresholds, duplicate wear events, interrupted repair, save/load, break or minimum-condition state, and the selected replacement/recovery path. The condition ledger and transaction IDs explain every change. Do not claim balance from the durability formula alone.

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.