getting-started
Skill0 starsChanged 6 months agoLicence not identifiedView on GitHub
Sets up a new Omnipresence member with their own private fork of omnipresence-os/synapse on GitHub and a local clone wired to pull upstream updates. Trigger when the user says any of "run getting started", "set up omnipresence", "install omnipresence", "onboard me to omnipresence", "fork synapse", "I'm a new member", "set me up", "get me started with omni". This is the ONE canonical first-time setup flow for Omnipresence members. Forks omnipresence-os/synapse to the user's GitHub account, clones to a sensible local path, configures upstream remote, installs npm deps, and validates with npm run manifest. Self-installs the gh CLI if missing. Self-authenticates via gh auth login if the user isn't signed in. Idempotent - safe to re-run if interrupted.
- Installs packages
35 other projects use a version of this.
Adopted by
Most recently taken up by
- inferedge-ai/evalkittheir own version, first seen Nov 15, 2026
- vmoranv/jshookmcptheir own version, first seen Nov 15, 2026
- seayniclabs/privacyopstheir own version, first seen Nov 15, 2026
- Jackywine/jackywine-digital-garden-skillstheir own version, first seen Nov 15, 2026
- orgiggly/claude-plugintheir own version, first seen Nov 15, 2026
- aivrar/portable-hermes-agenttheir own version, first seen Nov 14, 2026
Used with
Projects with it also use troubleshooting.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
NVIDIASkilltroubleshooting
Diagnose and resolve common issues including test failures, build errors, performance regressions, and development environment problems. Use this skill whenever the user reports something broken, failing, timing out, hanging, or producing unexpected results. Trigger on test failures (elementIsStable timeouts, flaky tests, screenshot diffs), build errors (Cannot find module, wireit cache issues, stale output), CI/CD failures, Git LFS problems, port conflicts, lighthouse score regressions, SSR errors, or environment setup issues.
Also in 3 projects that use this
Other versions35 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 35
- vmoranv/jshookmcp★ 2.1ksame name
- NVIDIA-NeMo/Curator★ 1.9ksame name
- davekilleen/Dex★ 509same name
- aivrar/portable-hermes-agent★ 247same name
- GoogleCloudPlatform/race-condition★ 232same name
- taskade/mcp★ 170same name
- claude-world/director-mode-lite★ 80same name
- dylantarre/design-system-skills★ 50same name
- crewAIInc/skills★ 45same name
- aks129/HealthClawGuardrails★ 34same name
25 more not listed
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 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
- list-projectsSkill
- list-strategiesSkill
- load-workerSkill
- new-projectSkill
- new-strategySkill
- project-infoSkill
- project-resolverSkill
- push-changesSkill
- reload-workerSkill
- switch-projectSkill
- sync-omnipresenceSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
23 rules. 0 are common, 15 are distinctive, and 8 are very specific to this project.
0
Common
Most of the 34 edited versions we read keep these.
15
Distinctive
This author's own choices. Worth a look.
8
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 measured: kept by at least 6 in 10 of the 34 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.
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.

