harness-help
Skill173 starsChanged 17 days agoMITView on GitHub
Orient a non-coder to this project's Agentsmith harness — fires on "what is this harness?", "what are my rules?", "which profile am I on?", "what do I type next?". Part of the Agentsmith harness; reads the canonical instructions and selected agent's safety configuration, then reports the profile, rules, safety mode, and next step in plain language.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- joymin5655/Agenttheir own version, first seen Sep 28, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- joymin5655/Agent★ 2same 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 repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- autonomous-runSkill
- example-skillSkill
- grill-with-docsSkill
- handoffSkill
- harness-doctorSkill
- new-feedbackSkill
- new-researchSkill
- verifySkill
- wayfinderSkill
- writing-rulesSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
Use the agent named by the operator or the explicit AGENTSMITH_AGENT value.
- Distinctive: line 23
Read the canonical managed block in AGENTS.md and report:
≈ “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
Harness help — get oriented
Explain, in plain language with no jargon, what this harness does for the operator and what to do next. This is the non-coder's front door.
When this fires
"what is this harness / what does it do?" / "what are my rules?" / "which profile am I on?" / "what do I type next?" / a general "help me get started here".
Identify the target
Use the agent named by the operator or the explicit AGENTSMITH_AGENT value. Never infer the active
agent from this skill's install path: portable canonical content may be copied into a required
client adapter such as .claude/skills. Without a declared agent, explain the common rules and
label agent-specific safety configuration as unknown.
What to do (no script needed)
Read the canonical managed block in AGENTS.md and report:
- Active profile(s) — the work-type this project is tuned for (from the profile section).
- Your rules, in 3–5 bullets — the load-bearing ones (verify before done, protected main, look before you delete, be honest about what failed). Summarize; don't dump the file.
- Safety mode — when an agent is declared, read its managed native configuration and explain the effective approval and sandbox settings. Otherwise say that client-specific safety was not identified.
- What to type next — take one small task end to end. Say “verify” or “handoff”; mention an invocation prefix only when the declared client documents one.
Point to docs/01-harness-philosophy.md and docs/07-how-to-pick-a-profile.md for the why and the
profile choices. If FIRST-STEPS.md exists, point at it too.
Report
A short, friendly orientation: the selected agent when known, profile, a few rules, safety mode, and the one thing to do next. No file dumps, no jargon.
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.