agentleFS
Sign inStart free
nathanadaynathanaday/atlas-obsidian/skills/repo-unlink/SKILL.md

repo-unlink

Skill1 starsChanged 25 days agoMITView on GitHub

Unlink a repository from the vault: mark its document unlinked, and decide what happens to the topics under its tag. The document stays, so every link to it holds. The repository on disk is never touched. Use for unlink, remove this repository, forget this repo, the repository moved away. Linking is repo-link.

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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
  1. Very specific:

    Call context with repository: its own tag (defines).

    line 18
  2. Distinctive:

    Ask one question with the count and the recommended answer: keep the topics (recommended.

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

repo-unlink

A repository can leave the vault while its code stays on disk. The repository document stays too, marked unlinked, so the topics and sessions that cite it keep a live link. Agents no longer work in the old folder. The topics under the repository's tag must go somewhere, so this skill asks once, with a recommendation, and then makes the change.

Tools: context, search, change. References: changes.md.

Procedure

  1. Call context with repository: its own tag (defines).
  2. Count the topics under its own tag: search with tags: [<its tag>] and types: [topic].
  3. Ask one question with the count and the recommended answer: keep the topics (recommended; they still describe the system, and the tag and the repository document remain), or remove the ones the user names.
  4. Build the change: a modify of the repository document with fields: {unlinked: true}. Code empties path, drops the git facts, and turns the lead callout into [!repository-missing]. Add a remove for each topic the user chose to remove, with redirect to a document that covers its subject when one exists. A remove moves the topic to tool/trash/. Give every write a why. Never remove the repository document.

Gate

Propose the change. Show the preview. Wait for the yes, then apply the change. Apply runs sync, which takes the path out of .claude/settings.local.json. Nothing touches the folder on disk.

Hand off

None.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free