sync-omnipresence
Skill0 starsChanged 6 months agoLicence not identifiedView on GitHub
Updates both halves of an Omnipresence install — the methodology corpus (omnipresence-os/synapse upstream → user's fork) and the prompt-driven Claude Code skill set (omnipresence-os/claude-skills → ~/.claude/skills). Trigger when the user says any of "sync omnipresence", "update synapse", "pull latest", "get omnipresence updates", "update omni", "what's new in synapse", "refresh my synapse", "update my skills", "pull latest skills". This is the ONE canonical update flow for both. Safely stashes any uncommitted member work before fetching, handles merge conflicts on the fork by surfacing the core/-edit rule violation clearly, fast-forwards the skills install in place, and reports what changed across both. Idempotent. Tells the member to restart Claude Code if any new Claude Code skills landed (Claude Code discovers skills at process start, not per-session).
- Commits and pushes
In this repository23 other files it gives its agents.
- connect-dataforseoSkill
- connect-emailSkill
- connect-google-cloudSkill
- connect-openaiSkill
- continue-strategySkill
- create-workerSkill
- disconnect-dataforseoSkill
- disconnect-emailSkill
- disconnect-google-cloudSkill
- disconnect-openaiSkill
- domain-migration-checklistSkill
- fill-project-gapSkill
- getting-startedSkill
- list-projectsSkill
- list-strategiesSkill
- load-workerSkill
- new-projectSkill
- new-strategySkill
- project-infoSkill
- project-resolverSkill
- push-changesSkill
- reload-workerSkill
- switch-projectSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 8 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
5
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
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.

