real-thesis
Skill8 starsChanged 7 months agoApache-2.0View on GitHub
Use when a historical paper appears to orbit a deeper claim than the one it states directly, and you need to excavate the thesis it repeatedly approaches but does not quite write.
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/collate.mdcCursor rule
- chunqiuSkill
- constellatioSkill
- diff-reviewSkill
- kaozhengSkill
- mp-formatSkill
- ocr-runSkill
- paper-summarySkill
- prep-scanSkill
- prometheusSkill
- proofreadSkill
- setupSkill
- to-docxSkill
- visual-previewSkill
- xray-paperSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
When the surface argument unfolds, pay attention to:
- Distinctive: line 55
Never overwrite the source.
- Distinctive: line 56
Do not upgrade a mood into a thesis without evidence.
- Distinctive: line 57
If the paper is actually direct and nothing deeper is hiding, say so.
≈ “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
real-thesis
The work this skill is for
Many papers are written around a safer surface topic. The explicit claim is the outer layer; the real pressure lives deeper in the structure — what returns, what gets omitted, where the densest citations accumulate, where the conclusion lands with disproportionate force.
This skill excavates that buried centre.
What to look for
When the surface argument unfolds, pay attention to:
- where the author returns repeatedly
- what is
略而不论or passed over in silence - where the conclusion lands and what it cannot let go
- where citations grow abnormally dense
- where footnotes work harder than the body
The aim is not psychoanalysis for its own sake. The aim is to identify the thesis that, if spoken plainly, might reorganize the abstract, the structure, or even the title.
Input
Target: $ARGUMENTS
- workspace directory → read
<ws>/final.md .mdfile → read it directly- empty → ask what to read
Output
- workspace mode →
<workspace>/analysis/{stem}_real-thesis.md - single-file mode →
analysis/{stem}_real-thesis.md
Report layers:
- Surface topic — what the paper openly claims
- Floating concerns — what it repeatedly approaches but does not settle
- Candidate real theses — one to three, each anchored in evidence: returns, elisions, citations, footnotes
- A question the author dare not ask themselves — left open, not answered for them
Guardrails
- Never overwrite the source.
- Do not upgrade a mood into a thesis without evidence.
- If the paper is actually direct and nothing deeper is hiding, say so.
- Precision matters more than theatrical boldness.
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.

