absorb
Skill2 starsChanged 7 months agoMITView on GitHub
Append a source reference to an existing wiki page. Writes (a) inline [Source: ...] marker in the relevant section and (b) a row in the page's `## Sources that shaped this page` section at the bottom. Subskill of /ingest. Keeps reverse provenance intact. When absorbing into wiki/people/me.md, also writes a short first-person summary paragraph referencing the absorbed source.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- Tcuzzo/backs-aios-skillstheir own version, first seen Nov 3, 2026
- Jason-hub-star/model-orchestratortheir own version, first seen Oct 20, 2026
- brianonbased-dev/HoloScripttheir own version, first seen Aug 20, 2026
- HermeticOrmus/ormus-absorbtheir own version, first seen Apr 25, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- brianonbased-dev/HoloScript★ 10same name
- Tcuzzo/backs-aios-skills★ 2same name
- HermeticOrmus/ormus-absorb★ 0same name
- Jason-hub-star/model-orchestrator★ 0same 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 repository12 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- captureSkill
- deep-syncSkill
- extract-entitiesSkill
- helpSkill
- ingestSkill
- lintSkill
- new-pageSkill
- orientSkill
- publish-contextSkill
- querySkill
- quick-syncSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 37
If the section doesn't exist, create it at the bottom of the page:
- Distinctive: line 47
If the section exists, append a new row.
- Very specific: line 51
When the target page is wiki/people/me.md:
- Distinctive: line 52
After completing steps 1-4, re-read the whole page
- Distinctive: line 53
Read all absorbed source markers on this page
- Very specific: line 54
Write a short (≤4 sentence) first-person summary paragraph at the top under ## About me (or create that section) synthesizing what the …
- Distinctive: line 56
Do not invent facts. Only synthesize what the absorbed sources actually state.
- Distinctive: line 60
If you are updating an existing paragraph, append.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Append a source reference to an existing wiki page. Enrich, never overwrite.
Usage
/absorb <entity-name> <source-path>Steps
1. Read the target page
Resolve entity → page path using /ingest's lookup table. Read current contents.
2. Identify the right section
Find the section most relevant to what the source adds. If no section fits, append a new ## YYYY-MM-DD: <one-line summary of what this source adds> section.
3. Write inline source marker
In the relevant section, append a line summarizing the claim, ending with the source marker:
- <Claim or insight>. [Source: [[<source-basename>]]]Claim must be ≤1 line, factual, new information (do not duplicate existing claims).
4. Append to ## Sources that shaped this page
If the section doesn't exist, create it at the bottom of the page:
## Sources that shaped this page
| Date | Source | What it added |
|------|--------|---------------|
| YYYY-MM-DD | [[<source-basename>]] | <one-line summary> |If the section exists, append a new row.
5. Special behavior for wiki/people/me.md
When the target page is wiki/people/me.md:
- After completing steps 1-4, re-read the whole page
- Read all absorbed source markers on this page
- Write a short (≤4 sentence) first-person summary paragraph at the top under
## About me(or create that section) synthesizing what the sources reveal about the user - Each sentence in the summary must cite at least one absorbed source inline with
[Source: [[...]]] - Do not invent facts. Only synthesize what the absorbed sources actually state.
6. Never overwrite
If you are updating an existing paragraph, append. Do not edit the existing text. Enrichment is append-only.
7. Return
Return the updated page path + list of sections modified.
Failure modes
- Target page does not exist → fail;
/ingestshould call/new-pagefirst - Source already absorbed into this page (same basename already in the table) → no-op, return "already absorbed"
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.