agentleFS
TIKAZITIKAZI/TIKAZ-Codex-Context-Economy/context-onpremise/SKILL.md

context-onpremise

Skill3 starsChanged 2 months agoMITView on GitHub

Use deployed local conversion, OCR, audio/video, visual, retrieval, reranking, and guarded compression to build high-fidelity bounded Codex context. Use only for a valid uppercase ON prefix or explicit invocation.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use LLMLingua-2 only for over-budget, low-risk natural-language prose.

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

TIKAZ Context On-Premise

Designed, integrated, independently refactored, and continuously maintained by TIKAZ.

Core promise

Find the right evidence before deciding whether to compress. Use local dependencies for complex documents, multimodal material, and semantic retrieval while keeping sources, facts, anchors, privacy, failures, and cost measurable.

Workflow

  1. Fix the task, required evidence slots, risk, text budget, and visual budget.
  2. Profile the input once and invoke only the necessary local route: document conversion, webpage extraction, media understanding, local retrieval/compression, or safe structured parsing.
  3. Protect numbers, versions, URLs, commands, errors, citations, table cells, approvals, and source anchors.
  4. Combine lexical evidence slots, BGE-M3, local reranking, and diversity-aware selection. Query expansions are retrieval hints, never source facts.
  5. Use LLMLingua-2 only for over-budget, low-risk natural-language prose. Never send protected blocks, code, commands, contracts, finance, tables, or security evidence to learned compression.
  6. Fall back visibly to deterministic selection or the original source when local models fail, evidence coverage is low, protected facts drop, or the budget conflicts with safety.

Output contract

Return canonical Markdown or a safe structured result, Context Pack, evidence ledger, retrieval ledger, cost ledger, omissions, and Pending items. Report Recall@K, Precision@K, MRR, nDCG@K, evidence-slot coverage, protected-fact recall, estimated tokens, latency, and fallback state separately. Without relevance labels, do not invent hit-rate percentages.

Validation and fallback

Validate protected literals, source anchors, required evidence slots, hard budget, adapter identity, and unresolved visual/table evidence before accepting the pack. If any required gate fails, return deterministic selection or the original source with the reason instead of claiming successful compression.

Installation

This Skill describes the route. The optional engine, adapters, fixtures, benchmark artifacts, and setup documentation live in TIKAZ Codex Context On-Premise. It never installs dependencies or downloads models during a run.

Example

ON 分析这批 PDF、表格和录屏,保留来源锚点并生成有预算的 Context Pack。

Limits

Fixed synthetic benchmarks do not establish universal accuracy, real provider Token savings, or downstream-answer correctness. Model weights and third-party tools retain their own licenses and are not bundled with this Skill.

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.