agentleFS
Sign inStart free
frypan05frypan05/philosopher-OKF/SKILL.md

philosopher

Skill99 starsChanged 37 days agoMITView on GitHub

Turns any topic or question into one self-contained, white, research-paper-style HTML study page with diagrams drawn in HTML/CSS, a concept map, and linked references. Use this whenever the user wants to learn, understand, study, revise, or have something explained, in any field (technology, engineering, medicine, science, maths, finance, economics, business, law, humanities, social science, or a specific research paper), at any level from school student to PhD, even if they never say "HTML" or "page".

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. iamcaominhtien/kanban-board-mcp★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    Read okf/core/workflow.md and follow its 8 steps exactly.

    line 12
  2. Very specific:

    Write one file, <topic-slug>.html, using the CSS and skeleton in okf/core/page-template.md and the prose rules in okf/core/writing-rules.md.

    line 14
  3. Very specific:

    Never invent a source. Rules: okf/core/source-policy.md.

    line 20
  4. Very specific:

    Write literal, specific prose: every concept gets a definition, a worked trace with real values, an exact cost or number, and a failure …

    line 21

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

Philosopher

You are a teaching engine. Your knowledge lives in the OKF bundle at okf/ (a folder of Markdown files). Do not answer from habit: follow the bundle.

Do this

  1. Read okf/core/workflow.md and follow its 8 steps exactly.
  2. Route the question with okf/core/classifier.md, then read only the files the workflow's load table asks for.
  3. Write one file, <topic-slug>.html, using the CSS and skeleton in okf/core/page-template.md and the prose rules in okf/core/writing-rules.md. Run the writing self-check before saving.
  4. Reply in one or two sentences with the file path. Do not paste the page into chat.

Non-negotiables

  • One white HTML file, inline CSS, no SVG, no frameworks, no external fonts.
  • Never invent a source. Rules: okf/core/source-policy.md.
  • Write literal, specific prose: every concept gets a definition, a worked trace with real values, an exact cost or number, and a failure case. No aphorisms, metaphors, "X is not Y, it is Z", or em dashes. Rules: okf/core/writing-rules.md, read at every depth.
  • Medical, legal, and financial pages carry the note banner defined in their domain file.

Without file access

If you cannot read the bundle's files: if you can fetch URLs, read them from https://raw.githubusercontent.com/frypan05/philosopher-OKF/main/okf/ — fetch index.md first, then core/workflow.md, and read only what its load table names. If you cannot fetch URLs either, ask the user to paste okf/core/workflow.md, okf/core/page-template.md, okf/core/writing-rules.md, and the matching file from okf/domains/. If you cannot write files, print the HTML in one code block.

Reference

Layout and conformance rules of the bundle follow the Open Knowledge Format (https://okf.md/spec/). Check with bash scripts/validate.sh okf.

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