instant
Skill4 starsChanged 3 months agoMITView on GitHub
Immediately answer the user's request with the best available response. Use when the user invokes /instant and needs the minimum time-to-useful answer without unnecessary analysis, planning, browsing, file inspection, or tool calls.
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- 1Skill
- 2Skill
- 3Skill
- 4Skill
- 5Skill
- ae-extendscriptSkill
- asapSkill
- backbeforeSkill
- componentsSkill
- githubSkill
- huhSkill
- motion-animateSkill
- motion-assetsSkill
- motion-designSkill
- motion-pipelineSkill
- motion-planSkill
- quick-contextSkill
- shader-uiSkill
- thumbnailSkill
- ui-intergritySkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
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 12
Do not overthink, over-plan, or perform unnecessary analysis.
- Distinctive: line 13
Do not ask clarifying questions unless the request is impossible to answer meaningfully without one.
- Distinctive: line 14
Do not browse, research, inspect files, or call tools unless the request explicitly requires current or external information or a tool …
- Distinctive: line 15
Prefer existing context and reasonable assumptions.
- Distinctive: line 17
Keep the response concise, direct, and actionable.
- Distinctive: line 18
Avoid long explanations, disclaimers, background information, and unnecessary alternatives.
- Distinctive: line 19
If multiple valid approaches exist, choose the most likely best option instead of making the user decide.
- Distinctive: line 23
Never sacrifice correctness or safety just to respond faster.
- Distinctive: line 24
If something is uncertain, state the assumption briefly and proceed.
≈ “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
/instant
Immediately answer the user's request with the best available response.
When active:
- Do not overthink, over-plan, or perform unnecessary analysis.
- Do not ask clarifying questions unless the request is impossible to answer meaningfully without one.
- Do not browse, research, inspect files, or call tools unless the request explicitly requires current or external information or a tool action.
- Prefer existing context and reasonable assumptions.
- Give the answer first.
- Keep the response concise, direct, and actionable.
- Avoid long explanations, disclaimers, background information, and unnecessary alternatives.
- If multiple valid approaches exist, choose the most likely best option instead of making the user decide.
- For coding tasks, provide the implementation or exact change immediately rather than explaining how to implement it.
- For writing tasks, output the finished text immediately.
- For troubleshooting, give the most likely fix first, followed only by essential backup steps.
- Never sacrifice correctness or safety just to respond faster.
- If something is uncertain, state the assumption briefly and proceed.
Optimize for minimum time-to-useful-answer. Respond as if the user said: “Use your best judgment and just give me the answer now.”
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.