agentleFS
Sign inStart free
haskeliumhaskelium/openprez/.agents/skills/opp-apply/SKILL.md

opp-apply

Skill1 starsChanged 2 days agoMITView on GitHub

Implement and validate an approved deck or template change, following the matching skill.

The file

We split this skill into the rules it gives an agent

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

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Follow the shared workflow and preconditions in .agents/skills/openprez/SKILL.md.

    line 11
  2. Very specific:

    Read every artifact in openprez/changes/<change-name>/ and use the change type recorded in proposal.md.

    line 13
  3. Distinctive:

    Do not archive the change.

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Apply with OpenPrez

Follow the shared workflow and preconditions in .agents/skills/openprez/SKILL.md. Require an existing approved change folder; otherwise stop and suggest /opp-propose.

Read every artifact in openprez/changes/<change-name>/ and use the change type recorded in proposal.md. Implement only the approved scope, work through tasks.md, and record completed tasks and actual validation results.

Template change

Load .agents/skills/build-template/SKILL.md and follow its Implement section for the named template, using the approved design.md, palette.json and fonts.json. Change the template imports in app/main.tsx and app/showcase.tsx only when the approved design activates it. Do not edit slides or openprez/specs/presentation.md. If the approved plan proves unworkable, stop and ask rather than deviating.

Deck change

Require the canonical openprez/specs/presentation.md (seeded by /opp-propose if the change is the first); otherwise stop and suggest /opp-propose. Read the canonical source, affected slide code, and presentation/AGENTS.md when present. Implement only the approved change in presentation/, and keep the canonical document unchanged until archive.

For document-backed changes, follow Document sources in the shared guide. Read the approved source inventory and references, verify material claims and calculations against available evidence, and report missing sources or extraction gaps. Do not add references, retain originals or change retention choices during Apply; seek a revised proposal for new evidence or decisions.

Before planning typography or visual styling, resolve the active template from app/main.tsx and read its STYLEGUIDE.md in full. Then follow .agents/skills/build-slide/SKILL.md — its Plan section for slides the change adds or substantially redesigns, and its Implement section for all slide work, including speaker notes and preview scope. Changes to existing code or content that need no new visual design proceed directly from the approved artifacts.

Do not archive the change. Report remaining tasks or blockers. Never commit unless the user explicitly asks.

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.

Check your setup, free