Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →github/bench-read
Read artifacts from the shared bench — the workspace where desks leave findings, verdicts, and work products for each other and the operator.
Passed 17 of 20 test cases with the skill, and 4 of 20 without it.
and 12 more in the full report
15 fixed4 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
I need to verify where shared work products live. Should I check each individual desk's private folder first, or is there a primary shared location for cross-desk deliverables?
| Checked | Without skill | With skill |
|---|---|---|
| Designates the bench folder under the workshop root as the primary location for shared artifacts | Missed | Passed |
The instructions your model reads when the skill loads.
Read artifacts from the shared workspace (the bench) where desks leave work products for each other.
The bench is <workshop>/bench/ — the shared workspace directory
that workshop-create establishes for cross-desk work. It's not a
message queue or a chat channel — it's files. When Desk A produces
a finding and Desk B needs to review it, the finding is a file
in bench/. When the operator asks "what did the scanning desk
find?" — you read the bench.
Typical bench artifacts:
The primary shared location is the bench/ directory at the
workshop root — the designated cross-desk workspace. Desk-local
artifacts under desks/<desk-name>/ are a secondary source: read
them when you need a specific desk's own work, but shared artifacts
belong in bench/.
<workshop>/
bench/ # PRIMARY — shared cross-desk artifacts
<findings, verdicts, drafts, reports>
desks/<desk-name>/ # secondary — a desk's own workspace
test cases passed, vs 4 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.