writing-science
Skill2 starsChanged 7 months agoMITView on GitHub
Writes new science files following academic prose standards: third-person voice, present tense for laws, in-universe terminology, consistent equation formatting, citation format. Use when creating new physics, chemistry, biology, or science files, expanding existing science content, or when user says "write", "create", "draft", "formalize", or "derive" in a science context. Does NOT write civilization or narrative content — use /writing-worldbuilding for that.
In this repository19 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- auditing-canonSkill
- auditing-human-assumptionsSkill
- auditing-physicsSkill
- canon-rulesSkill
- compiling-entitiesSkill
- cross-checkingSkill
- deep-readingSkill
- deriving-social-systemsSkill
- designing-loreSkill
- designing-worldsSkill
- extracting-entitiesSkill
- integrating-researchSkill
- interrogating-designSkill
- planning-worldbuildingSkill
- researching-papersSkill
- verifying-completionSkill
- writing-styleSkill
- writing-worldbuildingSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 13 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈13
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
- Distinctive: line 16
Write new science files following canon standards.
- Distinctive: line 20
Read CLAUDE.md for conventions
- Very specific: line 21
Read references/writing-standards.md for detailed prose rules
- Distinctive: line 22
Read all files this content depends on (upstream science)
- Distinctive: line 23
Search for relevant research if grounding is needed (/researching-papers)
- Distinctive: line 27
Write in dependency order — define terms before using them
- Distinctive: line 28
Every mechanism derives from established upstream science
- Distinctive: line 29
Use in-universe terminology in science files
- Distinctive: line 30
Add YAML frontmatter: title, tags, status: draft
- Distinctive: line 31
Add ## References with citations and one-sentence annotations
- Distinctive: line 32
Add ## Cross-References with relative paths to related files
- Distinctive: line 37
Does NOT write civilization or narrative content (use /writing-worldbuilding).
- Distinctive: line 38
Does NOT audit existing content (use /auditing-physics or /auditing-canon).
- Distinctive: line 39
Does NOT search for research papers (use /researching-papers).
≈ “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.
Files
Writing Science
Write new science files following canon standards.
Prerequisites
- Read CLAUDE.md for conventions
- Read
references/writing-standards.mdfor detailed prose rules - Read all files this content depends on (upstream science)
- Search for relevant research if grounding is needed (/researching-papers)
Process
- Write in dependency order — define terms before using them
- Every mechanism derives from established upstream science
- Use in-universe terminology in science files
- Add YAML frontmatter: title, tags, status: draft
- Add ## References with citations and one-sentence annotations
- Add ## Cross-References with relative paths to related files
- Status: draft — author promotes after review
Out of Scope
Does NOT write civilization or narrative content (use /writing-worldbuilding). Does NOT audit existing content (use /auditing-physics or /auditing-canon). Does NOT search for research papers (use /researching-papers).
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
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.

