project-consolidation SKILL.md skillA
project-consolidation from linxule/memex-plugin is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add linxule/memex-plugin/project-consolidation@git:20261028.8eb19a8Pins git:20261028.8eb19a8 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- linxule/memex-plugin
- Path
skills/project-consolidation/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261028.8eb19a8, committed Oct 28, 2026
- First version recorded
- Jun 22, 2026
- Size
- 14,199 bytes
- Repository stars
- 7
- License
- MIT
Safely consolidate drifted/duplicate project folders in the memex vault — cwd-fragment folders (e.g. `Apps-arena`, `GitHub-loom`), duplicate/split projects (one project's content scattered across two folders), and name-mismatch folders. Trigger on "consolidate project folders", "merge duplicate projects", "fix project detection drift", "deduplicate Apps-* folders", "clean up fragment folders", or after `memex check --folders` reports drift. Use `memex project move <from> <to>` (dry run first)…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Project-Folder Consolidation Drifted project folders happen when session→project detection produced a non-canonical name: a cwd-path fragment (`Apps-arena` instead of `arena`), a project split across folders (content under both `personal-website` and `linxule_com`), a folder minted by a fleet seat's temp directory, or claude.ai relay sessions filed under a catch-all cwd. Detection fixes (v0.15.5/v0.15.6, and v0.22.0's temp-root, remembered-remote and channel routing) close the known forms and `memex check --folders` reports the rest, but new forms keep turning up — this skill cleans up existing debt. ## The cardinal rule **Never run `memex project move --apply` or `memex obs reassign --apply` on a folder until you have confirmed it is the same project as the canonical target (a duplicate, a strict subset, or the same work under a drifted name).** A wrong merge collapses two distinct projects. And **never** consolidate via `git mv` + `memex index rebuild` — the incremental rebuild detects the old paths as deleted and **cascade-deletes the observations and their embeddings**. `memex project move` is the safe primitive; `obs reassign` underneath it (it …
Read the whole file at its exact version.
How to install
mdr add linxule/memex-plugin/project-consolidation@sha256:651c181134b6ab21The line at the top of this page pins the label git:20261028.8eb19a8, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_wcasswjbuvwaug3f)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Jun 22, 2026 and Oct 28, 2026, about one every 64 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261028.8eb19a8 latest | 2026-10-28 | 8eb19a8 | 14,199 B | A | view · diff |
| git:20260923.9411521 | 2026-09-23 | 9411521 | 8,111 B | A | view · diff |
| git:20260622.89581ed | 2026-06-22 | 89581ed | 6,061 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (14199 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
linxule/memex-plugin · 7 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_wcasswjbuvwaug3f GET https://markdownregistry.com/api/v1/resolve?ref=linxule/memex-plugin/project-consolidation GET https://markdownregistry.com/api/v1/blob/651c181134b6ab21058a3c36fe93a43858815bdfbd1a3de23dd1f80cf1952053
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from linxule/memex-plugin
Every file in linxule/memex-plugin