Omni Context Rtk
Configure RTK filters, context engineering rules, and context relay settings. Test compression with real prompt samples and manage context transformation pipelines.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Omni Context Rtk when an AI agent needs a reusable SKILL.md workflow for this job: Configure RTK filters, context engineering rules, and context relay settings. Test compression with real prompt samples and manage context transformation pipelines.
When not to use it
Skip Omni Context Rtk when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/omni-context-rtk # Save SKILL.md to ~/.claude/skills/omni-context-rtk/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/omni-context-rtk/SKILL.md. For a shared project, commit the folder at .claude/skills/omni-context-rtk/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Omni Context Rtk skill for this task: Use Omni Context Rtk when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
71/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
<!-- 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
```bash curl http://localhost:20128/api/context/rtk/config \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### PUT /api/context/rtk/config
Update RTK compression settings
```bash curl -X PUT http://localhost:20128/api/context/rtk/config \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```
### GET /api/context/rtk/filters
List RTK filters and load diagnostics
```bash curl http://localhost:20128/api/context/rtk/filters \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### POST /api/context/rtk/import
Validate or install an RTK TOML schema v1 filter file
```bash curl -X POST http://localhost:20128/api/context/rtk/import \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```
### POST /api/context/rtk/test
Run RTK compression preview for text
```bash curl -X POST http://localhost:20128/api/context/rtk/test \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```
### GET /api/context/rtk/raw-output/{id}
Read retained redacted RTK raw output
```bash curl http://localhost:20128/api/context/rtk/raw-output/{id} \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/context/rtk/discover
GET context › rtk › discover
```bash curl http://localhost:20128/api/context/rtk/discover \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/context/rtk/learn
GET context › rtk › learn
```bash curl http://localhost:20128/api/context/rtk/learn \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
## Payloads
See the full OpenAPI specification at `GET /api/openapi/spec` or `docs/openapi.yaml` for detailed request/response schemas.
Intended uses
- Use Omni Context Rtk when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.