agentleFS
zedarvateszedarvates/botte-secrete/skills/nlp_deterministic/SKILL.md

nlp_deterministic

Skill2 starsChanged 3 months agoMITView on GitHub

Classify and extract from text WITHOUT an LLM — intent classification (lexical overlap + local embedding), entity extraction (regex/gazetteers for urls/emails/ips/paths/env vars/flags/numbers), and stopword-filtered keyword frequency. Deterministic, instant, 0 cloud tokens. Use instead of asking a model to classify text or extract entities, and as the routing/intent layer that keeps cheap language decisions off the LLM.

The file

Files
SKILL.md

nlp_deterministic — classify & extract without a model

Many "ask the model to classify / extract" calls don't need a model: a rule + gazetteer + local-embedding pass is deterministic, instant, 0 cloud tokens. This is the NLP half of the determinism program (alongside the combinatorial solvers): replace LLM reasoning for structured language decisions with exact, repeatable computation.

python -m skills.nlp_deterministic.cli classify "speed up my SQL" perf=fast,optimize,slow auth=login,token
python -m skills.nlp_deterministic.cli entities "GET https://x.io from 10.0.0.1 with $TOKEN --json"
python -m skills.nlp_deterministic.cli keywords "cache the cache so queries stay fast"
  • classify(text, intents) — intents = {label: [keywords]}. Score = keyword recall blended with a local hash-embedding cosine ([[ingest]] embedding + [[vector_protocol]] cosine, offline). Returns the best label + per-label scores.
  • extract_entities(text) — regexes for urls, emails, IPs, file paths, env vars ($VAR/%VAR%), CLI flags (--flag), and numbers.
  • keywords(text) — stopword-filtered (EN+FR) frequency keyphrases.

Exposed via [[llm_mcp]] as nlp_classify and nlp_extract. Pairs with [[auto_router]] (effort/intent before routing) and [[skill_finder]]. Deterministic classification is the cheapest possible routing/triage layer — 0 tokens, always the same answer.

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.