agentleFS
Sign inStart free
Runtime-3rr0rRuntime-3rr0r/canvas-scanner/skills/homework-checklist/SKILL.md

homework-checklist

Skill2 starsChanged 57 days agoMITView on GitHub

Use when pre-checking homework against the rubric.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never rewrite or ghostwrite answers — flags only.

    line 22
  2. Distinctive:

    If the rubric bucket is ambiguous, say so and move on (don't fabricate a rule).

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Homework Pre-Submit Checklist

Pre-submission diagnostic: score the student's written work against the assignment's rubric buckets. A diagnosis, never a grade, and never a ghostwriter.

When to Use

  • "Check my homework before I submit", "will I lose points for X", "did I miss anything"

Procedure

  1. Rubric: extract from the assignment sheet via vision_analyze, or read Submission Norms from the course COURSE-BRAIN (format, naming, units/sig-figs expectations, late policy). If the rubric is unknown, mark buckets as unknown rather than guessing.
  2. Read the work (photos/PDF/AI-guide-adjacent files).
  3. Per-problem checklist against buckets: correct answer ✅ / work shown ✅ / units 🟡 / sig figs 🟡 / format+naming ❌ — one row per problem.
  4. Aggregate patterns: "strong on correctness and work-shown; units missed on 3 of 7; sig-fig rounding slips on numbers < 1."
  5. File <HW-name>-PreSubmit-Checklist.md beside the work (auditable — the instructor can see what was flagged).
  6. Repeated patterns → auto-add a drill block to the Roadmap before the next assignment in that course.

Pitfalls

  • Never rewrite or ghostwrite answers — flags only.
  • A clean checklist is not a guarantee; state that scoring is the instructor's call.
  • If the rubric bucket is ambiguous, say so and move on (don't fabricate a rule).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free