agentleFS
haskeliumhaskelium/openprez/.agents/skills/opp-archive/SKILL.md

opp-archive

Skill1 starsChanged 2 days agoMITView on GitHub

Archive a validated deck or template change: sync deck content into the canonical source, or check a template's style guide and credits.

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. Very specific:

    Follow .agents/skills/openprez/SKILL.md.

    line 11
  2. Distinctive:

    Read the recorded change type and confirm all tasks are complete.

    line 13

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

Archive with OpenPrez

Follow .agents/skills/openprez/SKILL.md. Require a fully implemented, validated change; otherwise stop.

Read the recorded change type and confirm all tasks are complete.

Deck change

Require the canonical openprez/specs/presentation.md (seeded by /opp-propose). Inspect the resulting slide code. Reconcile the accepted content.md delta into openprez/specs/presentation.md, preserving unrelated content. If the canonical source changed since proposal or the merge is ambiguous, stop and resolve it with the user rather than overwrite.

For document-backed changes, follow Document sources in the shared guide: preserve accepted claim locators and approved reference links, check retained links resolve, and label local-only or unavailable originals accurately. Reconcile approved references only within the agreed retention scope. Archive the source inventory and coverage limitations with the change; do not delete local inputs or retain new originals.

Template change

Do not edit openprez/specs/presentation.md: a template's canonical record is its own templates/<name>/STYLEGUIDE.md; CREDITS.md is needed only when third-party assets require attribution. Check the implemented template against the approved design.md, palette.json and fonts.json: the three font roles and hierarchy, the palette and tones, the colour-usage guidance, every asset path, and all applicable credits. If anything disagrees, stop and resolve it with the user rather than archive.

Archive

Move the complete change folder to openprez/changes/archive/YYYY-MM-DD-<change-name>/ using the archive date and original change name. Verify the sync or check and the archive; do not discard artifacts or commit unless explicitly asked.

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.