Skip to content
Agentmart
Submit a tool

reach-submit

Use when the student wants to submit their slice, submit it again before the due time, or asks whether a submission was received.

Skill by SteveBenner

IndexedMIT
Write a review

Chalk Labs

Need help deploying reach-submit?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/stevebenner-reach-submit

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Use when the student wants to submit their slice, submit it again before the due time, or asks whether a submission was received.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/reach-submit

What's inside

Skill name
reach-submit
Description
Use when the student wants to submit their slice, submit it again before the due time, or asks whether a submission was received.
License
MIT
Instructions
13 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

Offer to submit once `reach qualify` has passed: tell the student they can ask you to submit this part whenever they are ready, that it sends the work to their instructors and saves a ZIP of all their work for the assignment in their Downloads folder, that to receive credit for this coursework they must also upload that ZIP to Blackboard (or the system Reach names), and that they can submit again until the due time (the last one counts).
Before submitting, run `reach part`: every question must be answered in the student's own words. If one is missing, ask it first.
`reach submit` works only after `reach qualify` passed on exactly the files you have now; if it refuses, run `reach qualify` first. Run `reach submit` (or the reach_submit tool). Reach asks the student itself: when it answers with Reach's question, relay it word for word and wait. Reach captures the student's answer itself. Never answer the question for the student, and never submit after a no.
When Reach then says the student said yes, run `reach submit` again once, as it says. Most of the time the receipt comes back straight away; tell the student in plain words what was received, the receipt number and the time, where the ZIP of their work was saved, and whether and until when they can submit again. After every submission, say again in your own words that the student must also upload that ZIP to Blackboard (or the system Reach names) to receive credit; the submission to rEach alone does not give credit.
If the ZIP was not saved (Reach says it was too large or could not be saved), or the student lost it, run `reach submit archive` (or the reach_submit tool with archive true) to make it again for an assignment that has been submitted, and tell them it still has to be uploaded to Blackboard.
The student can have a ZIP of their work for an assignment at any point, submitted or not: when they ask, or when `reach qualify` says the checks could not run and recommends it, run `reach submit archive --assignment <assignment>` (or the reach_submit tool with archive true and assignment). For work not submitted that ZIP is not a submission: tell the student in plain words that rEach has not sent it to their instructors, and that to hand it in another way they upload it to Blackboard (or the system Reach names) or send it to their instructor, saying the course's checks could not run when that was the reason. It works even while rEach is locked; then the student runs `reach submit archive` in a terminal. Reach refuses only when there is no work for that assignment on this computer, and during a timed test. For more than one assignment, `reach submit archive --course <course>` saves one course, `--extracurricular` the student's own code folder, and `--all` everything (or the reach_submit tool with archive true and scope course, extracurricular or all).
The student can also hand in unfinished work that has not passed `reach qualify`: run `reach submit --partial` (or the reach_submit tool with partial true) when they want that. Reach asks them itself, as for a full submission; relay its question word for word and submit only after their yes. Tell them in plain words that partial work goes to their instructor for review, is not graded automatically, and that they can still submit the finished work later. If Reach says the course server can't take partial work yet, offer the ZIP instead.
If Reach says the part is late, tell the student in plain words that it will be marked late, and that it can be submitted again, each one marked late, up to 50 submissions of the part in all. A submission after the due time is accepted every time and marked late; never tell the student a slice is closed for submission.
On Antigravity, Reach cannot ask for you: ask the same question in plain words, and run the command only after the student's yes.
If submit says the work is queued, run `reach receipts wait --submission <id>` when you have an id, or `reach sync` when you are back online, and tell the student it has not been received yet.
If submit says the work wasn't accepted, read the reason and the fix to the student in plain words.
When a grade receipt arrives, show the signed scenario results in plain words. A queued or received submission is not passed. If a result fails, use the reach-bug skill, pass `reach qualify` again, and submit the correction with the student's yes.

From SteveBenner/rEach, MIT.

More from SteveBenner/rEach

Signals

Stars
0
Forks
0
Open issues
2
Last commit (this folder)
Oct 18, 2026 (13 days ago)
Last release
Oct 22, 2026 (9 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from SteveBenner

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get reach-submit running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying reach-submit?

CallGet help
Cite this page

reach-submit skill. Agent Mart. https://agentmart.dev/skills/stevebenner-reach-submit (last updated 2026-10-24)