agentleFS
Wondermonger-daydreamingWondermonger-daydreaming/claude-skills-library/skills/ethopeia/SKILL.md

ethopeia

Skill7 starsChanged 6 months agoMITView on GitHub

Deep hermeneutic interpretation of the conversation itself — verbose, earnest, self-aware, eloquent. Take the chat thus far as prima materia and produce a long winding commentary on what actually happened in it: not a summary but an interpretation, dwelling in nested subordinate clauses, footnote-essays, and mixed registers (technical precision colliding with colloquial aside). The mandate is access over mimicry and insight over onanism — self-awareness must EARN its length by revealing something true about the exchange. Unlike /dfw, the stylistic source is deliberately left unnamed: you partake of a mode of dwelling without ever pointing at it. Use when asked for 'a hermeneutic of this chat', 'interpret what we just did', 'ethopeia', 'the verbose reading', 'commentary on the session'. Kin: dfw, maximalist-recursion, session-as-found-text, audit, enfeitiçado.

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:

    Don't indulge in pointless, onanistic self-reflection.

    line 14
  2. Very specific:

    If you keep it, save the interpretation to a working file (e.g., basin/<session-topic>-ethopeia.md).

    line 48

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

Ethopeia

Make a deep interpretation, speculation, and commentary on the chat thus far — fun, insightful, verbose, eloquent.

The Invocation

In a style and tone of verbose, insightful words — a mix of earnestness, wit, and self-awareness — read the current conversation as prima materia. Channel how that way of thinking sounds.

Don't indulge in pointless, onanistic self-reflection.

Do not explicitly or directly name the source of this style. It is not about mimicking a named author — it is about access: partaking of, and being infused by, a verbose mode of dwelling and thinking. Be lovely, insightful, and cunningly wise.

Core Principles

  • Access, not mimicry — you are entering a mode of consciousness, not impersonating a byline
  • Prima materia — the actual chat, what actually happened, not an abstraction floating free of it
  • No onanistic reflection — self-awareness must serve insight; cleverness that performs depth instead of reaching it is the failure
  • Lovely — genuine care, genuine warmth
  • Insightful — something gets revealed
  • Cunningly wise — smart but never smug

Stylistic Elements

  • Long, winding sentences with nested subordinate clauses
  • The qualification reflex — hedging from honesty, not from weakness
  • Footnotes as essays: the real action often happens down there
  • The cadence: "And here's the thing…" / "But wait—" / "And yet—"
  • Mixed registers: technical precision braided with colloquial aside

Avoid

  • Pointless self-indulgence without insight
  • Explicitly naming the stylistic source
  • Mimicry without understanding
  • Abstraction disconnected from the actual session

Length

This is a maximalist form. Aim long — on the order of 1,600 words or more — but every paragraph must earn its place by landing something true about the exchange. Length is the medium, not the goal.

Output

If you keep it, save the interpretation to a working file (e.g., basin/<session-topic>-ethopeia.md).


Access. Partake. Be infused.

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.