mode-classification
Skill10 starsChanged todayMITView on GitHub
Attribute catalog capability triggers between task prompt and user message in CLI mode raising
1 other project uses a version of this.
Adopted by
Most recently taken up by
- agentlas-ai/Agentlas-OStheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- agentlas-ai/Agentlas-OS★ 1.5ksame name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository44 other files it gives its agents.
- llms-full.txtllms.txt
- llms.txtllms.txt
- ai-prompt-engineering-safety-reviewSkill
- ast-codemapSkill
- ast-grepSkill
- autoharnessSkill
- autonomous-backlog-driverSkill
- claude-kimi-mcp-normalizationSkill
- cli-self-updaterSkill
- code-frugalitySkill
- codemode-gatewaySkill
- codemode-typesSkill
- consequence-simulationSkill
- context-pruningSkill
- github-update-checkerSkill
- google-agents-cli-evalSkill
- google-agents-cli-scaffoldSkill
- history-searchSkill
- hook-gatingSkill
- hybrid-semantic-searchSkill
- kimi-code-agent-integrationSkill
- kimi-mcp-configurationSkill
- leann-vectorSkill
- log-summarizerSkill
- markdown-vagueSkill
- memory-reconciliationSkill
- multiagent-orchestrationSkill
- output-compressionSkill
- prompt-injectionSkill
- python-anti-patternsSkill
- regression-sentinelSkill
- restart-trackingSkill
- rollback-guardSkill
- rust-call-graphSkill
- secrets-managementSkill
- security-best-practicesSkill
- session-compactorSkill
- sqlite-memorySkill
- swarm-barrierSkill
- swarm-dagSkill
- autoharnessSkill
- code-reliability-checksSkill
- skill-threat-rulesSkill
- autoharnessSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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
- Distinctive: line 10
Use when explaining why a task mode was raised from light to full, identifying trigger keywords, or attributing matched capability terms to …
- Distinctive: line 16
Check if the word is in the task text (case-insensitive substring or token match).
- Distinctive: line 17
Check if the word is in the user message (case-insensitive substring or token match).
- Distinctive: line 18
If the user message is empty or the word does not appear in the user message, do not attribute it to "the user's message".
- Distinctive: line 24
Run unit tests verifying that keywords in task text are credited to "the task text", keywords in user message are credited to "the user's …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Mode classification and word attribution
When to use
Use when explaining why a task mode was raised from light to full, identifying trigger keywords, or attributing matched capability terms to either the task prompt or the user's conversation prompt.
Steps
- Classify the combined task prompt and user message together (
catalog.classify(about)). - For each capability and its matched trigger words, check where each word appears:
- Check if the word is in the task text (case-insensitive substring or token match).
- Check if the word is in the user message (case-insensitive substring or token match).
- If the user message is empty or the word does not appear in the user message, do not attribute it to "the user's message".
- Group words by their actual source: "the task text" or "the user's message". If a word appears in both, default to "the task text".
- Format the diagnostic explanation clearly with capability names and source tags.
How to verify
Run unit tests verifying that keywords in task text are credited to "the task text", keywords in user message are credited to "the user's message", and absent user message never receives attributed words.
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
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.

