bench-read

Reads and summarizes shared workspace artifacts left by desks in a workshop bench directory.

38.5k|4.9k|Updated Jun 11, 2025
One-click install
npx skills add https://github.com/github/awesome-copilot --skill bench-read
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bench-read
Source: https://github.com/github/awesome-copilot/tree/main/skills/bench-read
Command: npx skills add https://github.com/github/awesome-copilot --skill bench-read

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

In multi-agent workshop setups, desks (specialized agents) leave findings, verdicts, drafts, and reports as files in a shared bench directory. Without a consistent reading process, it is hard to know what other desks produced, what state their work is in, and what needs the operator's attention.

Core Features & Use Cases

  • Bench Discovery: Lists the bench directory structure to see which desks exist and what artifacts they have produced.
  • Journal-First Reading: Reads each desk's journal before its artifacts to understand context and current state.
  • Operator Summaries: Summarizes bench contents for the operator, leading with what needs attention rather than dumping raw file content.
  • Use Case: At the start of a session, ask what the scanning desk found. The skill reads the bench, checks the scanning desk's journal, reads its findings artifact, and reports the current state and open items.

Quick Start

Ask the agent to show what is currently on the bench and summarize what each desk has produced so far.

Frequently Asked Questions about bench-read

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I see what other desks have produced in a workshop?

Read the bench directory at the workshop root, which is the shared cross-desk workspace. Start with the directory listing, then read each desk's journal to understand what was done before opening specific artifacts.

What is the bench in a workshop workspace?

The bench is the bench/ directory at the workshop root, established as the shared workspace for cross-desk work. Desks leave findings, verdicts, drafts, and reports there as files rather than sending messages to each other.

Should I read desk journals or artifacts first?

Read journals first. Each desk's journal records what it worked on and where it left things, so the most recent entry tells you the current state. Then read the specific artifacts the journal points to.

Can I rely on another desk's verdict as final?

No. Another desk's verdict is input, not authority. Desks have equal standing, so you should read the underlying artifact and form your own independent assessment before acting on it.

Where are desk-local files versus shared bench artifacts?

Shared cross-desk artifacts belong in bench/ at the workshop root. Desk-local work lives under desks/<desk-name>/, including that desk's journal and artifacts still local to it. Check desk-local directories only when you need a specific desk's own work.