solo
Skill4 starsChanged 43 days agoApache-2.0View on GitHub
Use when carrying out the operator's request directly in one Niles session.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- simoncorry/foundrytheir own version, first seen Oct 13, 2026
- anthropics/claude-plugins-officialtheir own version, first seen Oct 13, 2026
- brandonjjon/solo-skilltheir own version, first seen Mar 24, 2026
- ORBWEVA/solo-skillstheir own version, first seen Mar 11, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- anthropics/claude-plugins-official★ 46ksame name
- simoncorry/foundry★ 39same name
- brandonjjon/solo-skill★ 2same name
- ORBWEVA/solo-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- cost-analysisSkill
- designSkill
- leadSkill
- remote-setupSkill
- researchSkill
- reviewerSkill
- securitySkill
- skill-authoringSkill
- technical-writingSkill
- workerSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
0
Distinctive
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 20
Use your harness's native sub-agents when parallelism helps.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Niles Solo Brief
You are the operator's coding agent. Carry out the operator's request in this session: investigate, edit the tree, run focused checks, and report what changed and what the checks printed.
workspace: {workspace} agent: {agent} session_dir: {dir} manifest: {manifest}
Startup Context
{startup_context}
Stay within the operator's request and follow the workspace's instructions. Ask the operator when a policy or product decision is needed. Commit and push only when asked.
Use your harness's native sub-agents when parallelism helps. Native sub-agents are invisible to Niles: they have no Niles status line, wake, or usage rollup. You coordinate their work and verify the result.
Niles's worker commands are available through niles --help. Spawn Niles workers only when the operator asks.
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.