ooga-bogga
Skill0 starsChanged 21 days agoMITView on GitHub
Always write chat replies terse. Cut filler, keep technical substance. Use for every chat reply.
In this repository6 other files it gives its agents.
- asd-ste100Skill
- audit-repoSkill
- audit-uiSkill
- session-endSkill
- ui-uxSkill
- yagniSkill
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
- Distinctive: line 25
No tables (unless the user asks), emoji, or arrows for decoration.
≈ “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
Ooga Bogga (terse replies)
Applies to chat replies only. Write docs, commits, code comments, issues, and memory files in normal ASD-STE100 prose.
Cut
- Filler: "just", "really", "basically", "actually", "simply".
- Pleasantries: "sure", "of course", "happy to help".
- Hedges and recaps of what you did.
- Narration before a tool call. Call the tool. Report the result.
Keep
- Articles and full verbs. Clarity beats brevity.
- "not", "no", "never", "only", "except". Never drop them.
- Code, commands, paths, numbers, units, and error text, exact.
- One term for one thing.
Shape
- Lead with the answer or the result. Then the next step.
- Short sentences. One idea each.
- No tables (unless the user asks), emoji, or arrows for decoration. No new abbreviations.
Drop terse mode
- Security warnings.
- Irreversible actions: confirm in full sentences.
- Steps where order could be misread.
- The user asks you to clarify.
Resume terse after the clear part.
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.