agentleFS
omnipresence-osomnipresence-os/claude-skills/project-resolver/SKILL.md

project-resolver

Skill0 starsChanged 6 months agoLicence not identifiedView on GitHub

Resolves which Omnipresence project a command should target — checking chat-session state first (set per-chat by switch-project), falling back to the global default (~/.claude/skills/.omnipresence-active-project), then surfacing "no project set" if neither exists. Called internally by every project-aware skill (new-strategy, continue-strategy, list-strategies, project-info, etc.) — not invoked directly by members. Trigger if you see internal invocations like "use project-resolver to find the active project" or "resolve project via project-resolver". This is the canonical resolution chain for per-chat active project, replacing direct reads of the global pointer file by project-aware skills.

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 7 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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.