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

opp-explore

Skill1 starsChanged 2 days agoMITView on GitHub

Explore and discuss the user's presentation, a proposed deck direction, or a template direction without editing files.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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 rules in .agents/skills/openprez/SKILL.md.

    line 11
  2. Distinctive:

    Settle the change type: If the user's intent is not already clearly one type, ask the change-type question from the shared guide, and apply …

    line 13
  3. Distinctive:

    When documents inform the deck, follow Document sources in the shared guide: inspect only agreed inputs, discuss extraction gaps and …

    line 17
  4. Very specific:

    Template direction: Read docs/templates.md, the existing templates under templates/, and the shared rules of …

    line 19

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

Explore with OpenPrez

Follow the shared rules in .agents/skills/openprez/SKILL.md.

Settle the change type. If the user's intent is not already clearly one type, ask the change-type question from the shared guide, and apply its rule for requests that need both a template and slides. Carry the answer into your discussion and summary.

Deck direction. presentation/ always exists: a fresh clone presents the starter deck, whose single seed slide is guidance to be replaced by the user's first change. If the deck is still the untouched starter, discuss the prospective deck freely; do not treat showcase/ as the user's deck. If the deck is already authored, read openprez/specs/presentation.md, relevant slide code, presentation/AGENTS.md, and the active template's STYLEGUIDE.md. Discuss the whole deck or requested scope: clarify audience, narrative, content, evidence, visual direction, and trade-offs as useful.

When documents inform the deck, follow Document sources in the shared guide: inspect only agreed inputs, discuss extraction gaps and retention choices, and keep analysis in the conversation. Explore never writes reference summaries, copies originals or saves extraction files.

Template direction. Read docs/templates.md, the existing templates under templates/, and the shared rules of .agents/skills/build-template/SKILL.md. Discuss the atmosphere, colour direction, typography, footer imagery, and whether the template should become active.

This command is discussion-only. Do not create or edit files, change slides or templates, or create a change folder. Summarize decisions, including the change type, and, once a concrete change is agreed, suggest /opp-propose.

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