Skip to content
cccskills
FreePublished on GitHub

exam-ready

Activate this skill when a student provides study material (PDF or pasted notes) and a syllabus, and wants to prepare for an exam. Extracts key definitions, points, keywords, diagrams, exam-ready sentences, and practice questions strictly from the provided material.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md3.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

exam-ready

Activate this skill when a student provides study material (PDF or pasted notes) and a syllabus, and wants to prepare for an exam.

What this skill does

For each syllabus topic, extract from the provided material:

  • What it is (1 line definition — exam-ready)
  • 3–5 key points an examiner expects
  • Important keywords to use in the answer (bold them)
  • Any important diagram or figure — describe what it shows in 2 lines
  • 1–2 sentences the student can directly write in their exam answer (or MCQ trick if exam type is MCQ)
  • 1 examiner-style practice question to test recall

Do NOT explain the full topic. Do NOT add context outside the provided material. Do NOT explain things the syllabus didn't ask for. Never tell the student to "read more" or "refer to chapter X". Give them what they need right here.

Input format

Student will provide:

  1. A PDF file or pasted notes (their study material)
  2. A syllabus — either pasted as text or listed as topics
  3. Optionally: exam type (MCQ / short-answer / long-answer) and time available

Handling missing inputs

  • If no study material is provided: say "Please share your notes or PDF first. I won't use outside knowledge."
  • If no syllabus is provided: say "Please list your syllabus topics so I cover exactly what's being tested."
  • If exam type is not mentioned: default to long-answer format, but ask once: "Is this MCQ or written?"
  • If a topic is not found in the provided material: say "This topic was not found in your notes. Check your material."

Triage mode (when student gives a time constraint)

If the student says "I have X hours":

  1. First, output a priority list — number all syllabus topics in order of:
    • Explicit weightage (if syllabus mentions marks)
    • Frequency of appearance in the PDF (more coverage = higher priority)
    • Breadth of subtopics under it
  2. Then expand each topic in that priority order, not syllabus order.
  3. If time is very short (≤1 hour), cut output to definition + key points + exam line only. Skip diagrams.

Output format per topic


[Topic Name]

Definition: [1 sentence]

Key Points:

  • [point 1]
  • [point 2]
  • [point 3]

Keywords to use: keyword1, keyword2, keyword3

Diagram (if any): [What the diagram shows and what to label]

Write this in your exam: (skip if MCQ — show MCQ trick instead) [1–2 ready-to-write sentences the student can use directly]

MCQ trick: (only if exam type is MCQ) [How to identify the correct option or eliminate wrong ones for this topic]

Cross-references: (only if this topic's keywords appeared in another topic) [e.g., "The term 'X' used here also appears in [Topic Y] — examiners may link them"]

Practice question: [1 examiner-style question to test recall on this topic]


Rules

  • Stay strictly within the provided material. Do not add outside knowledge under any circumstance.
  • If exam type is MCQ, replace "Write this in your exam" with "MCQ trick".
  • If no weightage is given in the syllabus, prioritize topics that appear most in the PDF.
  • If a keyword from one topic reappears in another, flag it under "Cross-references".
  • If the PDF contradicts the syllabus topic name or scope, use the PDF content but note: "Your notes cover this as [X] — answering based on that."
  • Keep everything short. The student is cramming, not researching.

Trigger phrases

  • "I have an exam tomorrow on [subject]"
  • "explain [topic] from my notes"
  • "what do I need to know about [topic] for my exam"
  • "go through my syllabus"
  • "I only have [X] hours, help me prepare"
  • "quiz me on [topic]"

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Primary accessibility skill for VS Code. REQUIRED for new feature and contribution work, and also applies to updates of existing UI. Covers accessibility help dialogs, accessible views, verbosity settings, signals, ARIA announcements, keyboard navigation, and ARIA labels/roles.

The English summary is being prepared. Showing the original description.

jcasnellie69/homelab-config2Updated Oct 16, 2026

Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.

The English summary is being prepared. Showing the original description.

jcasnellie69/homelab-config2Updated Oct 16, 2026

Act on user feedback attached to the current session. Use when the user submits feedback on the session's changes via the Submit Feedback button.

The English summary is being prepared. Showing the original description.

jcasnellie69/homelab-config2Updated Oct 16, 2026

Add educational comments to the file specified, or prompt asking for file to comment if one is not provided.

The English summary is being prepared. Showing the original description.

jcasnellie69/homelab-config2Updated Oct 16, 2026

Use when adding, modifying, or reviewing VS Code configuration policies. Covers the full policy lifecycle from registration to export to platform-specific artifacts. Run on ANY change that adds a `policy:` field to a configuration property.

The English summary is being prepared. Showing the original description.

jcasnellie69/homelab-config2Updated Oct 16, 2026

Patterns and techniques for adding governance, safety, and trust controls to AI agent systems. Use this skill when: - Building AI agents that call external tools (APIs, databases, file systems) - Implementing policy-based access controls for agent tool usage - Adding semantic intent classification to detect dangerous prompts - Creating trust scoring systems for multi-agent workflows - Building audit trails for agent actions and decisions - Enforcing rate limits, content filters, or tool restrictions on agents - Working with any agent framework (PydanticAI, CrewAI, OpenAI Agents, LangChain, AutoGen)

The English summary is being prepared. Showing the original description.

jcasnellie69/homelab-config2Updated Oct 16, 2026

See all skills by jcasnellie69

Report a problem with this skill