Skip to content
Back to search

philosopher

SkillWorks with Claude CodeGitHub

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".

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/frypan05--philosopher-okf/badge.svg)](/listings/frypan05--philosopher-okf)

HTML

<a href="/listings/frypan05--philosopher-okf"><img src="/api/listings/frypan05--philosopher-okf/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

SKILL.md · Manifest · 30 lines
  1. ---
  2. name: philosopher
  3. description: 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".
  4. ---
  5. # Philosopher
  6. 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.
  7. ## Do this
  8. 1. Read `okf/core/workflow.md` and follow its 8 steps exactly.
  9. 2. Route the question with `okf/core/classifier.md`, then read only the files the workflow's load table asks for.
  10. 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.
  11. 4. Reply in one or two sentences with the file path. Do not paste the page into chat.
  12. ## Non-negotiables
  13. * One white HTML file, inline CSS, no SVG, no frameworks, no external fonts.
  14. * Never invent a source. Rules: `okf/core/source-policy.md`.
  15. * 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.
  16. * Medical, legal, and financial pages carry the note banner defined in their domain file.
  17. ## Without file access
  18. 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.
  19. ## Reference
  20. Layout and conformance rules of the bundle follow the Open Knowledge Format (https://okf.md/spec/). Check with `bash scripts/validate.sh okf`.
README.md · README · 89 lines
  1. # Philosopher (OKF)
  2. One folder that teaches any model how to explain **any topic** as a single, white, research-paper-style HTML page: centered column, serif text, tiny monospace labels, amber highlights on the sentences worth remembering, CSS-drawn diagrams, a concept map, and a references list where every entry says what it supports.
  3. The knowledge lives in an [Open Knowledge Format](https://okf.md/spec/) (OKF) bundle: plain Markdown with YAML frontmatter, no SDK, any model can read it.
  4. ![Example Output](image.png)
  5. ![E-1](image_2.png)
  6. ![E-2](image_1.png)
  7. ## Layout
  8. ```
  9. philosopher-okf/
  10. ├── SKILL.md # entry point for skill-aware agents (Claude, Codex, Cursor)
  11. ├── okf/ # the OKF bundle
  12. │ ├── index.md # root index (declares okf_version 0.2)
  13. │ ├── log.md # change history
  14. │ ├── core/ # workflow, classifier, contract, template, writing, sources, depth, graph
  15. │ └── domains/ # 12 study domains, one file each
  16. ├── scripts/validate.sh # OKF conformance + link check
  17. └── examples/
  18. └── sample-flamingo-reading-guide.html # what the output looks like
  19. ```
  20. ## Domains
  21. Technology and engineering · Medical and health · Natural sciences · Mathematics, statistics and logic · Finance and accounting · Economics · Business and management · Law and policy · Humanities, philosophy and history · Social sciences and psychology · Research papers · General
  22. ## How a model uses it
  23. 1. Reads `okf/core/workflow.md` (the 8-step procedure, lazy load table, token budget).
  24. 2. Classifies the question (`core/classifier.md`) into one primary domain.
  25. 3. Loads only what the depth needs: **brief** = template + the domain's `# Quick card` (~3 reads), **standard** adds source policy and depth policy, **deep** adds the graph method and the full domain file. Research is capped per depth (brief 2 searches / 0 fetches, standard 4 / 2, deep 8 / 4), and fetched pages are noted, not re-read.
  26. 4. Writes `<topic>.html` in one call. The user opens it in a browser.
  27. ## Usage
  28. Editors and chat views each ask for one thing — a folder, a link, or plain text — so the skill ships in all three shapes. A skill agent opens [`SKILL.md`](SKILL.md) and walks the bundle from there; a browsing model needs only the link to [`philosopher.md`](philosopher.md), which contains the whole skill in one file and does the rest on its own; anything without network is handed the prompt below. The `okf/` folder is the source of truth: `philosopher.md` is a generated single-file copy, rebuilt by GitHub Actions whenever `okf/` changes — never edit it by hand (`bash scripts/build-single.sh` rebuilds it locally).
  29. | Your tool asks for | Give it |
  30. |---|---|
  31. | A folder (Claude Code, opencode, Cursor, Codex) | `npx skills add frypan05/philosopher-OKF` (no git, Node 22+, installs into whichever agent you have; on older Node use `npx skills@1.5.16 add frypan05/philosopher-OKF`), or clone this repo where your skills live |
  32. | A URL (ChatGPT, Gemini, Claude with browsing) | [github.com/…/blob/main/philosopher.md](https://github.com/frypan05/philosopher-OKF/blob/main/philosopher.md) — say "follow this, make a page about: …"; the [raw URL](https://raw.githubusercontent.com/frypan05/philosopher-OKF/main/philosopher.md) works the same for plain fetchers |
  33. | Text (a model with no network) | The prompt below, or the repository ZIP from GitHub's Code menu |
  34. | A rules file (`AGENTS.md`, project docs) | `For explanations, follow philosopher-OKF/SKILL.md.` |
  35. **No terminal at all?** Open the [site](https://frypan05.github.io/philosopher-OKF/), click *copy skill*, and paste it into any chat — you're done.
  36. **One paste covers every chat view** — copy this prompt:
  37. ```
  38. You are Philosopher, a teaching engine. Open https://github.com/frypan05/philosopher-OKF/blob/main/philosopher.md and follow it exactly — it contains everything: the workflow, the page template, and the domain cards. If you cannot open URLs, ask me to paste philosopher.md. Reply with the file path only, or one HTML code block if you cannot create files.
  39. My question: <your topic>
  40. ```
  41. Chat apps that cannot create files print the HTML in one code block — save it as `<topic>.html` and open it in a browser.
  42. Ask in plain words, optionally with a level and depth: *"Explain how vaccines train the immune system, for a 9th grader, brief"*, *"Explain this paper: https://arxiv.org/abs/2204.14198"*.
  43. ## Validate
  44. ```bash
  45. bash scripts/validate.sh okf
  46. ```
  47. Checks the three OKF rules (frontmatter, non-empty `type`, reserved files), that `index.md` has no frontmatter except the root's `okf_version`, that `log.md` uses ISO dates, and warns about broken links.
  48. ## Extend
  49. 1. Add `okf/domains/<slug>.md` with `type: Study Domain` (copy any existing domain).
  50. 2. Add a row to the routing table in `okf/core/classifier.md`.
  51. 3. Add an entry in `okf/index.md` and `okf/domains/index.md`.
  52. 4. Add a dated line to `okf/log.md`, then run the validator.
  53. ## Classifier hook
  54. `core/classifier.md` routes by keywords and intent. If your pipeline has its own classifier, pass its label as one of the domain slugs and the skill uses it directly (rule 1 in the classifier file).
  55. ## Known limits
  56. * **Token targets per run** (whole context, including research and the written page): **brief under 12k, standard under 25k, deep under 45k**. The levers are the workflow's research caps, the lazy load table, domain Quick cards, and writing the HTML in a single call. A run that skips fetched pages in favour of notes will land well under these numbers; a run that pulls several full documents will not.
  57. * Source lists point to host-level addresses of well-established sites. They were not link-checked from the build environment, so run a link checker in CI before publishing.
  58. * The sample page was built from the paper's public abstract record and the section list, and is marked as such. Check figures against the full text.
  59. * Models without web access can only cite from memory. The source policy makes them say so on the page instead of inventing links.
  60. ## License
  61. MIT. See `LICENSE`.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.