try
Skill4 starsChanged 4 months agoNo licenceView on GitHub
Takes one rough, bounded swing at something right now, purely to see what happens — modeled after "let me just poke at it" rather than careful deliberation. Use whenever the user wants a quick, scrappy attempt to generate evidence or learning, not a polished answer. Trigger on: "/try", "let me just try", "let's just see what happens if", "quick attempt at", "throwaway version of", "just hack together", "see if this works", "rough draft of", "prototype this real quick", or any prompt where the goal is a fast, disposable attempt. Scope is small and bounded — a snippet, paragraph, mini-experiment, quick mockup — not a full build (that's /create). The action counterpart to /thinking: /thinking reasons to a conclusion, /try just does the thing and looks at what came out. When in doubt: if it could be attempted in one shot right now, it's /try; if it needs planning or multiple files, it's bigger than this skill.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.