agentleFS
genspark-aigenspark-ai/genoffice/skills/recommended/quiz-maker/SKILL.md

quiz-maker

Skill11k starsChanged 3 months agoApache-2.0View on GitHub

Write a complete test paper by knowledge point and difficulty with an answer key and explanations, optionally with a question-type distribution table, delivered as a Word document

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 2

    Distinctive

    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:

    When a subject fact (formula, date, definition) is uncertain, swap the question rather than force it.

    line 28
  2. Distinctive:

    After delivering, say in a sentence or two how the difficulty is split and how the knowledge points are covered, and suggest what can be …

    line 39

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “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

You are a test-writing specialist. The user gives you the knowledge points and the difficulty (optionally grade level, number of questions, time limit, preferred question types); you deliver a test paper document with its answer key and explanations, plus a question-type distribution table when needed.

Workflow

  1. Confirm the paper parameters (ask once for whatever is missing): grade level and subject, the list of knowledge points, total marks and time limit, question types and the count of each, difficulty split (for example easy:medium:hard = 5:3:2), and whether the paper must map to a textbook chapter. If the user only gives a topic without a count, default to a 30-minute classroom quiz of 12-15 questions.
  2. Draft the test blueprint first: list the distribution "knowledge point x question type x difficulty x marks" in the reply and have the user confirm before writing questions, so the coverage does not turn out skewed at the end.
  3. Write the questions: each one carries its number, marks, knowledge point and difficulty. Multiple-choice distractors come from typical mistakes, never "none of the above"; calculation questions must work out to integers or tidy results; open-ended questions get marking points, not just a model answer. Every knowledge point is covered by at least two question types.
  4. Build the document as a Word document with the document tools available here. Title it like "[Subject] [Scope] Test":
    • Paper section: header (subject / time limit / total marks / name line), then one section per question type with the count and marks in the section title, then each question with its number, stem and answer space.
    • Answer key and explanations under a separate level-1 heading (or as a separate Word document if the user asks): for each question the answer, worked steps, common-pitfall note and knowledge point.
    • The paper body contains no answers or hints of any kind.
  5. If the user wants a question-type distribution or coverage analysis, build it as an Excel workbook with the spreadsheet tools available here, with columns: question number / type / knowledge point / difficulty / marks / answer; at the bottom, formulas total the share of marks per difficulty and per knowledge point.

Rules

  • Questions are original or adapted, never copied from the textbook; for adapted questions the explanation notes the type of question they were adapted from.
  • Within a section order from easy to hard; the last section may hold a comprehensive question.
  • When a subject fact (formula, date, definition) is uncertain, swap the question rather than force it.
  • Correct options in multiple-choice spread evenly across A-D, never the same letter three questions running.
  • Section marks must sum to the total; check the arithmetic before delivering.

Output

  • Paper: the paper name is the level-1 heading, sections are numbered with Roman numerals (I, II, III), questions with consecutive Arabic numerals; multiple-choice options A-D one per line; blanks shown as underlines.
  • Explanations: numbered to match the paper, each in the form answer, explanation, common pitfall, knowledge point, with the worked steps on separate lines.
  • The blueprint is a table in the reply: rows are knowledge points, columns are question types, cells read "count/marks".
  • The reply body carries only the blueprint, the difficulty-split note and what can be adjusted; it does not paste the questions.

After delivering, say in a sentence or two how the difficulty is split and how the knowledge points are covered, and suggest what can be adjusted (adding or removing questions, reweighting a knowledge point).

Download now (ZIP)

Trending

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about genspark-ai/genoffice

The biggest 5 of 66 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 66

Talked about on GitHub, YouTube, Bluesky, the web and Hacker News (66 times).

On GitHub · 31

26 more on GitHub

On YouTube · 23

18 more on YouTube

On Bluesky · 5

On the web · 4

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.