tool-authoring
Skill1 starsChanged 6 months agoMITView on GitHub
Use when creating, modifying, reviewing, or debugging Theseus Tool primitives or concrete tools in packages/theseus-core/src/tool and packages/theseus-tools.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- RomeCore/LLMDesktopAssistanttheir own version, first seen Oct 11, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- RomeCore/LLMDesktopAssistant★ 1same 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 repository28 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-self-checkSkill
- biome-grit-rulesSkill
- biome-toolingSkill
- bun-testSkill
- bun-workspaceSkill
- cleanup-auditSkill
- code-reviewSkill
- dispatch-satelliteSkill
- docs-managementSkill
- docs-readingSkill
- effect-concurrency-lifecycleSkill
- effect-errors-schemaSkill
- effect-observability-timeSkill
- effect-services-layersSkill
- effect-testing-runtimeSkill
- effect-v4Skill
- jsx-md-authoringSkill
- monorepo-maintenanceSkill
- refactoring-disciplineSkill
- roadmap-managementSkill
- runtime-engineSkill
- server-runtimeSkill
- testing-patternsSkill
- theseus-designSkill
- typescript-strictSkill
- ui-layout-disciplineSkill
- theseus-designSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 4 are distinctive, and 7 are 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.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use this skill for Tool primitive work and concrete tools.
- Very specific: line 24
Run tool.execute, applying tool.retry if present.
- Very specific: line 34
Use Tool.defineTool; do not create ad hoc tool objects unless testing a boundary directly.
- Very specific: line 35
Use Effect Schema for input, output, and failure.
- Very specific: line 36
Use Tool.Defaults.NoFailure only when the tool has no declared domain failure.
- Distinctive: line 37
Keep tool names stable and LLM-callable.
- Distinctive: line 38
Keep descriptions operational: what the tool does, not implementation trivia.
- Distinctive: line 40
If a tool touches the filesystem, shell, network, or process state, model that risk in policy and failure shape.
- Distinctive: line 41
Prefer small concrete tools over a generic "do anything" tool.
- Very specific: line 45
Run the package-local test when changing packages/theseus-tools: bun test src/ from that package or root bun run test when impact crosses …
- Very specific: line 46
Run root bun run typecheck when signatures, schemas, exports, or Effect environments change.
≈ “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
Tool Authoring
Use this skill for Tool primitive work and concrete tools.
Read First
packages/theseus-core/src/Tool.tspackages/theseus-core/src/tool/index.tspackages/theseus-core/src/tool/run.ts- For concrete tools: the relevant file in
packages/theseus-tools/src/
Contract
A tool is typed world access for the model. It declares input, output, known failure, execution, presentation, and interaction policy.
Preserve this pipeline:
- Decode raw model args with
tool.input. - Run
tool.execute, applyingtool.retryif present. - Validate success output with
tool.output. - Validate known failure with
tool.failure. - Present success or known failure as
Presentation. - Convert defects into
ToolDefect.
Known failures are tool-result content for the model, not runtime exceptions. Runtime errors are decode, output-shape, failure-shape, and defect errors.
Authoring Rules
- Use
Tool.defineTool; do not create ad hoc tool objects unless testing a boundary directly. - Use Effect Schema for
input,output, andfailure. - Use
Tool.Defaults.NoFailureonly when the tool has no declared domain failure. - Keep tool names stable and LLM-callable.
- Keep descriptions operational: what the tool does, not implementation trivia.
- Set
policy.interactionintentionally. Do not default write-like behavior to observe/read semantics. - If a tool touches the filesystem, shell, network, or process state, model that risk in policy and failure shape.
- Prefer small concrete tools over a generic "do anything" tool.
Verification
- Run the package-local test when changing
packages/theseus-tools:bun test src/from that package or rootbun run testwhen impact crosses packages. - Run root
bun run typecheckwhen signatures, schemas, exports, or Effect environments change.
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.