agentleFS
vikas8520-codervikas8520-coder/nerve/skills/omni-sync-cloud/SKILL.md

omni-sync-cloud

Skill0 starsChanged 3 months agoMITView on GitHub

Synchronise Nerve configuration, provider connections, and settings to/from cloud storage. Manage cloud worker authentication and remote backup targets.

  • Reads credentials
  • Sends data out

3 other projects use a version of this, 3 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 2

    Common

    Most of the 3 edited versions we read keep these.

  • 0

    Distinctive

    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:

    All requests require a valid Bearer token or session cookie.

    line 13
  2. Common:

    Update cloud worker credentials

    line 32
  3. Common:

    Update cloud model alias

    line 65

“Common” is measured: kept by at least 6 in 10 of the 3 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- generated by src/lib/agentSkills/generator.ts; manual edits will be overwritten -->

Overview

Synchronise Nerve configuration, provider connections, and settings to/from cloud storage. Manage cloud worker authentication and remote backup targets.

Authentication

All requests require a valid Bearer token or session cookie. Obtain a token via POST /api/auth/login or configure REQUIRE_API_KEY=false for local development.

Endpoints

POST /api/cloud/auth

Authenticate with cloud worker

Authenticates with the Nerve cloud worker for remote access.

curl -X POST https://localhost:20128/api/cloud/auth \
  -H "Authorization: Bearer $NERVE_TOKEN"
  -H "Content-Type: application/json" \
  -d '{}'

PUT /api/cloud/credentials/update

Update cloud worker credentials

curl -X PUT https://localhost:20128/api/cloud/credentials/update \
  -H "Authorization: Bearer $NERVE_TOKEN"
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/cloud/model/resolve

Resolve model via cloud

Resolves a model request through the cloud worker.

curl -X POST https://localhost:20128/api/cloud/model/resolve \
  -H "Authorization: Bearer $NERVE_TOKEN"
  -H "Content-Type: application/json" \
  -d '{}'

GET /api/cloud/models/alias

Get cloud model aliases

curl https://localhost:20128/api/cloud/models/alias \
  -H "Authorization: Bearer $NERVE_TOKEN"

PUT /api/cloud/models/alias

Update cloud model alias

curl -X PUT https://localhost:20128/api/cloud/models/alias \
  -H "Authorization: Bearer $NERVE_TOKEN"
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/sync/cloud

Sync with cloud

curl -X POST https://localhost:20128/api/sync/cloud \
  -H "Authorization: Bearer $NERVE_TOKEN"
  -H "Content-Type: application/json" \
  -d '{}'

POST /api/sync/initialize

Initialize cloud sync

curl -X POST https://localhost:20128/api/sync/initialize \
  -H "Authorization: Bearer $NERVE_TOKEN"
  -H "Content-Type: application/json" \
  -d '{}'

Payloads

See the full OpenAPI specification at GET /api/openapi/spec or docs/openapi.yaml for detailed request/response schemas.

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.