agentleFS
vikas8520-codervikas8520-coder/nerve/skills/omni-context-rtk/SKILL.md

omni-context-rtk

Skill0 starsChanged 3 months agoMITView on GitHub

Configure RTK filters, context engineering rules, and context relay settings. Test compression with real prompt samples and manage context transformation pipelines.

  • 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

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

  • 3

    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 RTK compression settings

    line 28
  3. Common:

    Run RTK compression preview for text

    line 59
  4. Common:

    Read retained redacted RTK raw output

    line 70

“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

Configure RTK filters, context engineering rules, and context relay settings. Test compression with real prompt samples and manage context transformation pipelines.

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

GET /api/context/rtk/config

Get RTK compression settings

curl https://localhost:20128/api/context/rtk/config \
  -H "Authorization: Bearer $NERVE_TOKEN"

PUT /api/context/rtk/config

Update RTK compression settings

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

GET /api/context/rtk/filters

List RTK filters and load diagnostics

curl https://localhost:20128/api/context/rtk/filters \
  -H "Authorization: Bearer $NERVE_TOKEN"

POST /api/context/rtk/import

Validate or install an RTK TOML schema v1 filter file

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

POST /api/context/rtk/test

Run RTK compression preview for text

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

GET /api/context/rtk/raw-output/{id}

Read retained redacted RTK raw output

curl https://localhost:20128/api/context/rtk/raw-output/{id} \
  -H "Authorization: Bearer $NERVE_TOKEN"

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.