bench-read
Read artifacts from the shared bench — the workspace where desks leave findings, verdicts, and work products for each other and the operator.
Profile →npx skills add github/awesome-copilot --skill bench-read --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Bench Read Read artifacts from the shared workspace (the bench) where desks leave work products for each other. ## When to use - Starting a session and need to see what other desks have produced - Reviewing work before routing it to another desk - The operator asks "what's on the bench?" or "show me what desk X found" - A desk needs context from another desk's output ## What the bench is 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: - **Findings** — scan results, analysis output, data - **Verdicts** — a desk's assessment of another desk's findings - **Drafts** — work-in-progress documents, PRs, proposals - **Reports** — summaries, dashboards, status updates ## Where to look 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 so
- When to use
- What the bench is
- Where to look
- How to read
- Cross-desk context
- Principles
What does the bench-read skill do?
Read artifacts from the shared bench — the workspace where desks leave findings, verdicts, and work products for each other and the operator.
How do I install it?
Run `npx skills add github/awesome-copilot --skill bench-read --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.