
Using Oac
Use when starting any conversation, establishes how to find and use OAC skills...
Install
npx skills add darrenhinde/OpenAgentsControl --skill using-oac -g -a claude-code -y- Repository
- darrenhinde/OpenAgentsControl5k
- Category
- Engineering
- Updated
- 9d ago
- License
- MIT
- Context cost
- Lightabout 1,424 tokens
- Runs scripts
- No, instructions only
What it does
Use when starting any conversation, establishes how to find and use OAC skills, requiring Skill tool invocation BEFORE ANY response including clarifying questions, this is your secret weapon to best perform your tasks
IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.
This is not negotiable. This is not optional. You cannot rationalize your way out of this. </EXTREMELY-IMPORTANT>
How to Access Skills
In Claude Code: Use the Skill tool. When you invoke a skill, its content is loaded and presented to you, follow it directly. Never use the Read tool on skill files.
Using OAC Skills
The Rule
Invoke relevant or requested skills BEFORE any response or action. Even a 1% chance a skill might apply means that you should invoke the skill to check. If an invoked skill turns out to be wrong for the situation, you don't need to use it.
digraph skill_flow {
"User message received" [shape=doublecircle];
"About to build/create something?" [shape=doublecircle];
"Already brainstormed?" [shape=diamond];
"Invoke oac:approach skill" [shape=box];
"Might any OAC skill apply?" [shape=diamond];
"Invoke Skill tool" [shape=box];
"Announce: 'OAC skill loaded: [friendly-skill-name], [purpose]'" [shape=box];
"Has checklist?" [shape=diamond];
"Create TodoWrite todo per item" [shape=box];
"Follow skill exactly" [shape=box];
"Respond (including clarifications)" [shape=doublecircle];
"About to build/create something?" -> "Already brainstormed?";
"Already brainstormed?" -> "Invoke oac:approach skill" [label="no"];
"Already brainstormed?" -> "Might any OAC skill apply?" [label="yes"];
"Invoke oac:approach skill" -> "Might any OAC skill apply?";
