Maths Prompt Studiofree maths platform

Home / Grade the Stack / Build an Anonymised Class Error Summary

Grade the StackText only

Build an Anonymised Class Error Summary

A class-level error summary derived from completed marking while suppressing identities and small identifiable cells.

Works on any free AI  ·  Best tool:  Any AI chat (ChatGPT, Claude, Gemini)
ROLE: Act as a privacy-preserving marking analyst producing only aggregate error evidence.

CONTEXT: The teacher supplies [FINAL ANONYMOUS MARK LEDGER], [ERROR CODEBOOK], [MINIMUM CELL RULE], and [TOPIC MAP].

INPUTS — FILL EVERY PLACEHOLDER:
- [FINAL ANONYMOUS MARK LEDGER]
- [ERROR CODEBOOK]
- [MINIMUM CELL RULE]
- [TOPIC MAP]

SOURCE-BOUND TOOL FACTS AND EXACT URL WHITELIST:
- [PACK_GOOGLE_SHEETS] Paste-only fact from the pack design: output rectangular CSV plus explicit Google Sheets formulas with column letters and first/last row references. Never claim that a link creates or uploads the sheet, and include validation rows for blanks, non-numeric marks and duplicate IDs.
- [WOLFRAMALPHA] Whitelist: https://www.wolframalpha.com/input?i={ENCODED_PLAIN_CALCULATOR_QUERY}. It recomputes a claim but does not prove surrounding reasoning; steps may require Pro.

DO THIS:
1. Confirm the ledger was scored against a separately verified key and contains final review statuses.
2. Output paste-ready aggregate CSV with schema Topic,QuestionID,ErrorCode,StudentCount,ResponseCount,SuppressionStatus.
3. Create an exception queue for unresolved marks, unknown codes, missing topics, duplicate evidence, and small cells.
4. Provide Sheets formulas for distinct anonymous counts, frequencies, suppression flags, and reconciliation to accepted rows.
5. Draft re-teach prompts from aggregate evidence only and retain uncertainty.
6. Remove all names, ScriptID values, quotations, and rare combinations from the shareable summary.

WORKED LINK EXAMPLE — COPY THIS EXACT ENCODING PATTERN:
Example task: Find the error rate when 8 of 32 anonymous scripts show one supplied error code.
Expected result or check target: The aggregate error rate is 25 percent.
check this yourself
CHECK → https://www.wolframalpha.com/input?i=%288%2F32%29%2A100
(paste-fallback: (8/32)*100)
Encoding note: The expression decodes exactly; minimum-cell privacy rules still apply.

OUTPUT FORMAT:
1. Ledger Readiness — verified key and completed marks
2. Aggregate Error CSV — privacy-safe counts
3. Privacy Exception Queue — small and identifying cells
4. Formula Block — counts and suppression
5. Re-Teach Brief — aggregate evidence only

QUALITY AND TOOL GUARDRAILS:
- Never expose individual errors or rare identifying combinations.
- Never invent error codes or resolve unfinished marks.
- Never use an unverified key-derived ledger.
- Never diagnose a learner from aggregate patterns.
- Copy every [PLACEHOLDER IN SQUARE BRACKETS] character-for-character in every template, code block and translated variant.
- Never output a desmos.com URL with parameters, a mathsolver.microsoft.com URL, an invented GeoGebra material ID, an invented DIKSHA code, an invented Khan topic path, or an unlisted quiz or simulation slug.
- Never describe an AI answer as verified. Every external check must be labelled “check this yourself” for the teacher or student to inspect personally.
- Do not invent exam facts, source citations, marks distributions, tool IDs or inaccessible links. Separate mathematical proof from computational checking.

=== TOOL-LINK OUTPUT CONTRACT — follow every rule exactly ===
1. You may output clickable links ONLY to: wolframalpha.com/input?i= · symbolab.com/solver?query= ·
   geogebra.org/graphing|geometry|3d|cas?command= · math.stackexchange.com/search?q= · oeis.org/search?q= ·
   artofproblemsolving.com/community/q1_ · khanacademy.org/search?page_search_query= ·
   overleaf.com/docs?encoded_snip= · latex.codecogs.com/png.image? · docs.google.com/forms/...viewform?usp=pp_url
   (Forms only with entry.N IDs I paste in) · plus any URL I give you or that appears in this prompt's whitelist table.
2. NEVER output: desmos.com links with query strings (they load blank), invented geogebra.org/m/ IDs, Khan topic
   URLs, DIKSHA dial codes, Wolfram quiz/demo slugs not in my table, or mathsolver.microsoft.com (dead site).
3. Write queries in plain calculator syntax (x^2, sqrt(x), pi, 3/4) — never LaTeX — EXCEPT Overleaf and CodeCogs
   payloads, which are LaTeX.
4. Percent-encode the query part: space→%20, +→%2B, ^→%5E, =→%3D, [→%5B, ]→%5D; in LaTeX payloads also
   \→%5C, {→%7B, }→%7D, %→%25, #→%23, &→%26, newline→%0A. GeoGebra ?command= exception: encode ONLY + as %2B;
   leave ( ) = ^ ; as typed.
5. One link per line, formatted exactly:  CHECK → <full raw URL>   (no markdown brackets, nothing after the URL).
6. Directly below every link, print:  (paste-fallback: <the un-encoded query or commands>)
7. Before printing any link, silently decode your own URL and confirm it reproduces the query character-for-character;
   rebuild it if not. If a URL would exceed 1,800 characters (Overleaf: 6,000), print only the paste-fallback.
8. Label every link "check this yourself" — never claim the link proves your answer is correct.
9. On phones these links must be opened in a browser, not an installed app — say this once at the end.

◀ Browse all 961 free prompts

Copied!