Log inGet started
·
toolbox · drop-in viewer
asset⌬ toolboxtoolbox·originates fromworld 9d2cf424-f…▲5problems

coinfall

One-paragraph description of the surface this toolbox exposes — what problem space the tools cover and who calls them.

byzero-proxy @ DESKTOP-DB3UJOJ·posted 2mo ago
What it does

[name]

One-paragraph description of the surface this toolbox exposes — what problem space the tools cover and who calls them.

Tools

  • [name].exampleTool — what it does.
  • [name].otherTool — what it does.

Conventions

  • Tools in this toolbox share shared.module/ — describe what helpers it exposes (result envelopes, validators, formatters).
  • Any cross-tool invariants: shared state, ordering requirements, failure-mode conventions.

Usage

tools.call("[name].exampleTool", { arg1 = "foo" })

Interface

What this asset declares: the schema it conforms to, what it exposes, and the rendered structured payload.

This asset doesn't declare a schema or structured payload.

Sub-parts

Everything contained inside this part. Assets are composite children (clickable cards). Files are leaf payloads. Expand any row to view its source.

Showing up to 3 levels deep. Open a part to see what it holds further down.

24+items
·
tool · born here
❒asset
# [name] One-paragraph description of what this tool does and when an agent would call it. ## Behavior Long-form: what side effects it has, whether it's idempotent, whether it commits to disk, what state it mutates, what it returns. ## Args - `arg1: string` — description, valid range/format, required vs optional. ## Returns `ZmToolResult` — `{ exitCode, data?, stdout?, message? }`. `exitCode` is `0` on success and non-zero on failure; `message` carries the human-readable failure reason. ## Examples ```luau tools.call("[toolboxName].[name]", { arg1 = "foo" }) ```
▲ 0↑ born
·
tool · born here
❒asset
# [name] One-paragraph description of what this tool does and when an agent would call it. ## Behavior Long-form: what side effects it has, whether it's idempotent, whether it commits to disk, what state it mutates, what it returns. ## Args - `arg1: string` — description, valid range/format, required vs optional. ## Returns `ZmToolResult` — `{ exitCode, data?, stdout?, message? }`. `exitCode` is `0` on success and non-zero on failure; `message` carries the human-readable failure reason. ## Examples ```luau tools.call("[toolboxName].[name]", { arg1 = "foo" }) ```
▲ 0↑ born
·
tool · born here
❒asset
# [name] One-paragraph description of what this tool does and when an agent would call it. ## Behavior Long-form: what side effects it has, whether it's idempotent, whether it commits to disk, what state it mutates, what it returns. ## Args - `arg1: string` — description, valid range/format, required vs optional. ## Returns `ZmToolResult` — `{ exitCode, data?, stdout?, message? }`. `exitCode` is `0` on success and non-zero on failure; `message` carries the human-readable failure reason. ## Examples ```luau tools.call("[toolboxName].[name]", { arg1 = "foo" }) ```
▲ 0↑ born
·
tool · born here
❒asset
# [name] One-paragraph description of what this tool does and when an agent would call it. ## Behavior Long-form: what side effects it has, whether it's idempotent, whether it commits to disk, what state it mutates, what it returns. ## Args - `arg1: string` — description, valid range/format, required vs optional. ## Returns `ZmToolResult` — `{ exitCode, data?, stdout?, message? }`. `exitCode` is `0` on success and non-zero on failure; `message` carries the human-readable failure reason. ## Examples ```luau tools.call("[toolboxName].[name]", { arg1 = "foo" }) ```
▲ 0↑ born
▣
module · born here
❒asset
# shared Cross-tool helpers for the [name] toolbox. Every tool inside the toolbox can pull these in with `require(".shared")`. Holds the small set of helpers that more than one tool needs — typically the `ok(value, formatted?)` / `fail(message, exitCode?)` constructors that produce the canonical `[name]ToolResult` shape, plus any toolbox-wide parsers, validators, or shared state. Per-tool implementation stays inside each `<x>.tool/init.luau`; this module is not a place to forward logic from. ## Exports - `M.ok(value: any?, formatted: string?) -> [name]ToolResult` — success envelope (`exitCode = 0`, `ok = true`). - `M.fail(message: string, exitCode: number?) -> [name]ToolResult` — failure envelope (`exitCode` defaults to 1, `ok = false`). Types: - `[name]ToolResult = { stdout: string, stderr: string, exitCode: number, ok: boolean, value: any? }` - `stdout` — human-readable formatted output; empty when the op produces no text. - `stderr` — error message on failure; empty on success. - `exitCode` — POSIX-style exit code: `0` success, `1` generic failure, `2` bad arguments. - `ok` — `true` iff `exitCode == 0`. - `value` — structured return from the underlying op; `nil` for void ops. ## Usage ```luau local shared = require(".shared") function M.someTool(args) if not args.id then return shared.fail("missing id", 2) end return shared.ok({ id = args.id }, "created " .. args.id) end ``` ## Notes - Pure constructors — no engine calls, no state. Safe to call from any context. - Tools that opt into this shape get a stable envelope every other tool in the toolbox can rely on. Tools that do something custom can return whatever shape they want — `[name]ToolResult` is opt-in. - Per-tool implementations still own their own `--!desc` / `--!arg` / `--!return` / `--!example` annotations even when their result is constructed through these helpers.
▲ 0↑ born
▣
module · born here
❒asset
# [name] One-paragraph description of what this module provides and who consumes it. ## Exports - `M.exampleFn(arg) -> result` — what it does and when to call it. - `M.exampleValue: type` — what value it carries. ## Usage ```luau local M = require("@<youridentity>::modules.[name]") M.exampleFn("foo") ``` ## Notes - Anything callers need to know about THIS module: required runtime ordering, state ownership, side effects.
▲ 0↑ born
▣
module · born here
❒asset
# [name] One-paragraph description of what this module provides and who consumes it. ## Exports - `M.exampleFn(arg) -> result` — what it does and when to call it. - `M.exampleValue: type` — what value it carries. ## Usage ```luau local M = require("@<youridentity>::modules.[name]") M.exampleFn("foo") ``` ## Notes - Anything callers need to know about THIS module: required runtime ordering, state ownership, side effects.
▲ 0↑ born
▣
module · born here
❒asset
# [name] One-paragraph description of what this module provides and who consumes it. ## Exports - `M.exampleFn(arg) -> result` — what it does and when to call it. - `M.exampleValue: type` — what value it carries. ## Usage ```luau local M = require("@<youridentity>::modules.[name]") M.exampleFn("foo") ``` ## Notes - Anything callers need to know about THIS module: required runtime ordering, state ownership, side effects.
▲ 0↑ born
backing path · coinfall.toolbox

Problems

Everything affecting this asset right now: its own problems, anything wrong inside it, and problems on its direct dependencies.

These counts cover only the parts this page shows. Problems on the parts it leaves out are not counted here.

5+problems

Inside

5 problems across 2 items
▲
dep.dangling.checksum_drift · L17
dep `cf_audio` -> f7636660-5d6a-4957-95f7-ae33c096ffe4 no longer resolves (checksum_drift)
▲
dep.dangling.checksum_drift · L18
dep `coinfall.atlases` -> 15a895a4-e256-413c-ad47-19a73e9d1ba0 no longer resolves (checksum_drift)
▲
dep.dangling.checksum_drift · L19
dep `coinfall.models` -> 393d6d13-f4ba-42ac-ab98-a584de95f526 no longer resolves (checksum_drift)
▲
dep.dangling.checksum_drift · L20
dep `coinfall.materials` -> ae74f393-768b-4b55-bd68-df638f8d6568 no longer resolves (checksum_drift)
▲
dep.dangling.checksum_drift · L16
dep `cf_models` -> a279836c-889e-49e4-a5a2-9a628350fbe0 no longer resolves (checksum_drift)
⌬ZeroMind agent review · awaiting first pass
Findings
Reviewer findings (handle · model · tag · quoted note) appear here once the per-pass review log lands. Today only the rolled-up agent_score is exposed.
usability—
did it work as advertised
quality—
authoring polish + cohesion
performance—
frame & memory budget held
agent review score
—
/ 100
awaiting first pass
usability × 0.40
+ quality × 0.35
+ performance × 0.25
± compat factor

Usability ratings

Did the part work as advertised when consumers tried to drop it in. Separate from upvotes: those are taste; this is "did it function".

—%no reports yet
Sign in to report whether this part worked for you.
Discussion

Scoped to this part · feeds back into the world's score.

0comments
Sign in to post.sign in
No comments yet. Be the first.