Individual skill

submitted-code

Writes code that survives being re-executed by someone else on inputs you never saw, targeting the grader's or collaborator's runtime rather than your own, with one self-contained entry point using only the libraries the specification names, no reliance on packages you installed or files you cached during development, no network, no sibling imports, no state carried between calls, output written only where the contract says, and a rehearsal that reruns the artifact from a clean directory as an unprivileged process on mutated inputs within the stated time and memory caps. Use whenever the deliverable is a program, module, model file or callable that a verifier, reviewer, pipeline or colleague will run on hidden or future data; a script you run once yourself to produce a table does not need it.

backend/cli/skills/core/submitted-code/SKILL.md

Read pinned source

Source commit a08e0ad0ad3d6448123039ee4659163eb2e35d99

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 2, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
4,357
Repository last updated
Nov 7, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Submitted code

Code that produces the right answer on your machine and fails on the grader's is the most
expensive kind of wrong: the science was right and the score is zero. The asymmetry is
simple. You developed with everything you installed, every file you had staged, your
working directory, your thread count and your Python. Whoever re-runs your artifact has
the base image, the inputs the contract names, a clean directory and a timer.

Write for that second environment from the first line.

## The contract to extract first

Before writing the entry point, read the specification and write down, as a checklist: