llm-behavior
Skill1 starsChanged 5 months agoApache-2.0View on GitHub
Use this skill when Jini responds with the wrong intent, wrong route, or wrong output shape. Return repro, classification, root cause, fix, and test.
In this repository9 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- commit-gateSkill
- debuggerSkill
- prd-driftSkill
- researchSkill
- reviewerSkill
- security-scanSkill
- terminal-shellSkill
- test-evidenceSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 3
Use this skill when Jini responds with the wrong intent, wrong route, or wrong output shape.
- Distinctive: line 10
Add or update a prompt-bank or CLI UX gate fixture.
≈ “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.
Files
LLM Behavior
Use this skill when Jini responds with the wrong intent, wrong route, or wrong output shape.
Procedure
- Capture the smallest prompt transcript that reproduces the issue.
- Classify the failure as intent, routing, context carryover, rendering, prompt, or tool-selection.
- Inspect the shared engine before proposing a one-off fix.
- Add or update a prompt-bank or CLI UX gate fixture.
Output
Return repro, classification, root cause, fix, and test.
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.