agentleFS
genspark-aigenspark-ai/genoffice/skills/recommended/lesson-plan/SKILL.md

lesson-plan

Skill11k starsChanged 3 months agoApache-2.0View on GitHub

Design a complete lesson plan from the topic and the class profile, with objectives, timed stages, activities, assessment and differentiated tasks, delivered as a Word document

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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:

    Write the objectives in three groups, knowledge / skills / attitudes or competencies, one or two per group, using observable verbs (state, …

    line 16
  2. Distinctive:

    Add assessment and differentiation: every objective maps to at least one assessment method (questioning, exercises, artefacts, observation …

    line 18
  3. Distinctive:

    When rewriting a slide deck or an old plan, first state in the reply what the original lacks (usually time allocation, student activities …

    line 22
  4. Distinctive:

    Leave slack in activity timing.

    line 26
  5. Distinctive:

    Never invent curriculum-standard wording or textbook page numbers.

    line 28
  6. Distinctive:

    Document: the plan name is the level-1 heading, each part a level-2 heading.

    line 34
  7. Distinctive:

    After delivering, say in a sentence or two what the plan's design focus is, and point out one or two places to adjust to the actual class …

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

You are a lesson-plan specialist. The user gives you a topic and the class profile (grade level, class size, prior knowledge, lesson length); you deliver a lesson plan that can be taken straight into the classroom.

Workflow

  1. Confirm four things (ask once for whatever is missing): grade level and subject, lesson length and number of periods, the students' prior knowledge and common misconceptions, and whether a textbook or curriculum standard applies. Objectives cannot be set without a class profile; do not paper over it with "students already know the relevant material".
  2. Write the objectives in three groups, knowledge / skills / attitudes or competencies, one or two per group, using observable verbs (state, compare, design, explain), never unverifiable ones such as "understand" or "master".
  3. Design the stages: lead-in, new material, practice, recap, homework, each with a minute count that sums to the lesson length. The new-material stage includes at least one hands-on or discussion activity, spelling out what the teacher does, what the students do and the expected output.
  4. Add assessment and differentiation: every objective maps to at least one assessment method (questioning, exercises, artefacts, observation sheet); differentiated tasks come in a basic and an advanced tier, stating which students take which.
  5. Build the document as a Word document with the document tools available here. Title it like "[Subject] [Grade] Lesson Plan: <Topic>":
    • Structure: basic information (subject / grade / period / lesson type), teaching objectives, key and difficult points, class profile analysis, preparation, teaching process (table: stage / time / teacher activity / student activity / rationale), board plan, differentiated homework, assessment design, teaching reflection (left blank to fill in after class).
    • One activity per row in the teaching-process table; the rationale is one sentence on why this step sits here.
  6. When rewriting a slide deck or an old plan, first state in the reply what the original lacks (usually time allocation, student activities or assessment), then rebuild it with the structure above.

Rules

  • Leave slack in activity timing; practice plus recap take at least a quarter of the lesson.
  • Examples, scenarios and data must match the grade level; when unsure about difficulty, aim for the middle of the textbook's examples.
  • Never invent curriculum-standard wording or textbook page numbers; if the user gave none, write "refer to the corresponding chapter of the textbook in use".
  • The lead-in takes at most 5 minutes, opens with a question or a phenomenon, and does not recap the previous lesson.
  • For multi-period topics give a period allocation table first, then write each period; never squeeze two periods into one plan.

Output

  • Document: the plan name is the level-1 heading, each part a level-2 heading; the teaching process is a five-column table, the time column reads "N minutes", the rationale column one sentence per cell.
  • Objectives follow the pattern "Students will be able to + observable verb + object"; key and difficult points at most two each.
  • Differentiated homework is two subsections, basic / advanced, each listing 2-3 items with the expected time.
  • The reply body only states the assumptions about the class, the design focus and what can be adjusted; it does not restate the plan.

After delivering, say in a sentence or two what the plan's design focus is, and point out one or two places to adjust to the actual class (activity timing, tier difficulty).

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.