plugins/odoo-token-killer/skills/otk-core/SKILL.md
Core OTK engine: Rust CLI proxy, output filters, token tracking, and analytics. This skill provides the `otk` binary and all 12 filter strategies. AUTO-TRIGGER: Used automatically via PreToolUse hook - no manual invocation needed. Performance: <10ms startup, <5MB binary, <5MB memory. Written in Rust like RTK.
npx skillsauth add letzdoo/claude-marketplace otk-coreInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
A high-performance Rust binary providing:
otk <command> - Token-filtered command executionotk gain - Analytics dashboardotk read <file> - Filtered file reading with tee recovery# After cargo install:
otk git status # Compact status
otk git log # One-line per commit
otk test invoke test module # Failures only
otk logs docker compose logs # Errors/warnings only
otk read models/sale.py # Filtered Python source
otk read views/sale_view.xml # XML structure only
otk gain # Token savings dashboard
otk gain --daily --json # Export analytics
otk proxy <any command> # Passthrough with tracking
When OTK filters output, the full raw version is saved to disk:
[full output: ~/.local/share/otk/tee/1234567890_git_log.log]
Read that file to access the complete unfiltered output.
cd ${CLAUDE_PLUGIN_ROOT}/skills/otk-core && cargo build --release
# Binary: target/release/otk (4.2MB)
cd ${CLAUDE_PLUGIN_ROOT}/skills/otk-core && cargo install --path .
tools
OTK (Odoo Token Killer) - Reduce token consumption by 60-90% on Odoo development operations. Inspired by RTK (Rust Token Killer) by the rtk-ai team. AUTO-USE when running Bash commands during Odoo development. The PreToolUse hook handles transparent rewriting automatically. For manual use, prefix commands with `otk`: otk invoke test my_module → test failures only (90% savings) otk docker compose logs odoo → errors/warnings only (90% savings) otk git status → compact stats (80% savings) otk read models/sale.py → signatures + fields only (60% savings) otk read views/sale_view.xml → structure only (70% savings) otk gain → token savings dashboard Compatible with: odoo-doodba-dev, odoo-development, odoo-query plugins.
data-ai
Connect to Odoo instances via XML-RPC for read-only queries to investigate issues and explore data. Use when user asks to "query odoo", "connect to odoo", "investigate odoo data", "read odoo records", or needs to explore an Odoo instance.
tools
--- name: Odoo Indexer description: Fast indexer for Odoo codebases - 95% more token-efficient than reading files. USE AUTOMATICALLY AND PROACTIVELY before ANY Odoo code work. AUTO-TRIGGER when user mentions models (sale.order, res.partner, account.move, etc.), fields (partner_id, name, state, etc.), views (form, tree, kanban), XML IDs, or when you need to search/validate/explore Odoo code. USE BEFORE writing code to validate references exist, USE BEFORE reading files to locate elements, USE DUR
development
MUST be loaded when ANY Odoo development task is detected. CRITICAL: Claude MUST use this skill for ALL tasks involving: - "odoo", "module", "model", "view", "field", "OWL", "manifest" - ANY mention of Odoo versions (14, 15, 16, 17, 18, 19) - "create odoo module", "generate odoo code", "review odoo module" - "upgrade odoo", "odoo best practices", "odoo security" ALWAYS trigger the odoo-context-gatherer agent BEFORE writing ANY Odoo code.