read-it-reframe-it-own-it
Skill14 starsChanged 22 days agoApache-2.0View on GitHub
Read, reframe, and own a topic by building a knowledge tree that absorbs ideas from different sources under your own key framework.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- ontology-of-everything/concept-skillsword for word, first seen Oct 25, 2026
Other versions1 project uses a version of this.
Word for word · 1
- ontology-of-everything/concept-skills★ 14100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository22 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- agent-dx-cliSkill
- architect-4cSkill
- architect-4rSkill
- architect-frontend-feature-firstSkill
- architect-frontend-fsdSkill
- concept-designSkill
- concept-modelSkill
- data-knowledge-architectSkill
- personal-knowledge-architectSkill
- simplify-javaSkill
- agent-dx-cli-cnSkill
- architect-4c-cnSkill
- architect-4r-cnSkill
- architect-frontend-feature-first-cnSkill
- architect-frontend-fsd-cnSkill
- concept-design-cnSkill
- concept-model-cnSkill
- data-knowledge-architect-cnSkill
- personal-knowledge-architect-cnSkill
- read-it-reframe-it-own-it-cnSkill
- simplify-java-cnSkill
The file
Files
Read It. Reframe It. Own It
The dividing line in building a knowledge system is defining your learning goal in qualitative terms: first clarify what you want to understand and what problems you want to solve, then identify a key framework around that goal to serve as the knowledge tree's trunk. Without this step, organizing knowledge can easily become copy-and-paste.
For example, an author describes “three key mistakes in sales.” Drawing those three mistakes as branches of a mind map merely gives the author’s knowledge a different shape. To build a knowledge tree, first identify dimensions of sales relevant to your learning goal, such as value, trust, and competition; then absorb the methods, mistakes, and other ideas you encounter into the corresponding dimensions according to their roles. Revise the framework when new knowledge reveals gaps or contradictions.
This draws on Lu Jiuyuan’s idea that “the Six Classics annotate me”: organize what you learn around your own goal and key framework, so new knowledge becomes pieces of that framework and gradually forms a genuine knowledge system.
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.

