EduBase Skills

A collection of Agent Skills that teach AI coding agents how to work with the EduBase e-learning platform.

---

What are Agent Skills?

Agent Skills are an open standard for giving AI agents new capabilities. A skill is a folder containing a SKILL.md file (instructions + metadata) along with optional templates, references, and scripts. When an agent detects a relevant task, it loads the skill automatically — no manual prompting required.

This repository packages EduBase-specific knowledge into skills that any compatible agent can use out of the box.

Available Skills

Skill	Description	Download link
edubase-content-to-question-generator	Generates EduBase quiz questions from educational source materials — textbooks, lecture notes, slides, study guides, or any document containing teachable content.	⬇ .skill
edubase-edu-writer	Writes EduBase questions as EDU files — the single-question text format used for one-by-one upload to EduBase Quizzing.	⬇ .skill
edubase-mcp-setup	Guides setup and first-use of the EduBase MCP server — the integration that connects Claude to the EduBase e-learning platform.	⬇ .skill
edubase-question-creator	Expert EduBase question creator for the EduBase Quizzing platform.	⬇ .skill
edubase-question-extractor	Extracts existing questions from documents into EduBase format — faithfully converting past papers, printed exams, question banks, worksheets, or any document that ALREADY CONTAINS questions into properly structured EduBase questions.	⬇ .skill
edubase-quiz-exam-builder	Builds, assembles, and manages EduBase Quiz sets and Exams end-to-end — from grouping questions into Quiz sets, to creating time-boxed Exams, assigning users, and configuring branding.	⬇ .skill

Getting Started

Prerequisites

You need an AI coding agent that supports the Agent Skills format. Compatible tools include:

• Claude Code / Claude.ai
• Cursor
• GitHub Copilot / VS Code
• Gemini CLI
• JetBrains Junie
• Roo Code
• OpenHands
• ...and many more

Download All Skills at Once

If you'd rather grab everything in one go instead of downloading skills individually:

1. Head to the Releases page.
2. Under Assets, you'll find every .skill file listed individually — plus a .zip archive containing all of them.
3. Download the .zip, extract it, and you'll have every skill ready to install.

Tip: The Releases page is also the easiest place to browse previous versions if you ever need an older release.

How to Use These Skills

Pick the option that matches the tool you're using. You can use as many or as few skills as you like.

With Claude.ai (web or desktop app)

1. Download the .skill file(s) you need — either from the table above or from the Releases page.

2. Open Claude and go to Customize (left sidebar) > Skills.

   See where to find it

   

3. Click the + button, then choose Upload a skill.

   See how it looks

   

4. Drag and drop the .skill file into the upload area — or click to browse and select it from your computer.

5. Done! The skill is now active for all your conversations.

New to this? A .skill file is just a small package that teaches Claude how to do something new. Think of it like installing a plugin — once uploaded, Claude automatically knows when to use it.

With Claude Code (CLI or IDE)

Copy the skill folders you want into one of these locations:

git clone https://github.com/EduBase/skills.git

# Option A: Add to a specific project (great for teams — everyone gets them automatically)
cp -r skills/edubase-question-creator your-project/.claude/skills/

# Option B: Add to your personal skills (available across all your projects)
cp -r skills/edubase-question-creator ~/.claude/skills/

With any other compatible agent

Copy the skill folder into the location your agent expects, or paste the contents of SKILL.md directly into your agent's custom instructions. See the Agent Skills docs for agent-specific guidance.

Verify it works

Once installed, ask your agent something like:

"Set up the EduBase MCP server"

or

"Create a multiple-choice question about photosynthesis for EduBase"

If the skill triggers and the agent follows the instructions, you're all set.

Repository Structure

Each skill folder follows the Agent Skills specification:

• SKILL.md — Required. Contains YAML frontmatter (name, description) and markdown instructions.
• references/ — Optional. Detailed documentation loaded on demand by the agent.
• assets/ — Optional. Templates and static resources.
• *.skill — Auto-generated ZIP archive of the skill folder (built by CI).

Contributing

Contributions are welcome! Whether you're fixing a typo, improving an existing skill, or adding a new one — here's how to get started.

Improving an existing skill

1. Fork the repository and create a feature branch.
2. Edit the SKILL.md or supporting files in the relevant skill folder.
3. Test your changes by loading the skill into a compatible agent and running through realistic prompts.
4. Open a pull request with a clear description of what changed and why.

Adding a new skill

1. Fork the repository and create a feature branch.

2. Create a new folder at the repository root using kebab-case (e.g., edubase-new-skill/).

3. Add a SKILL.md file with the required frontmatter:

   ---
   name: edubase-new-skill
   description: >
     A clear description of what this new skill does and when agents should use it.
     Include specific trigger keywords so agents can discover it reliably.
   ---

4. Write concise, actionable instructions in the markdown body. Remember:

   • Keep SKILL.md under 500 lines — move detailed references to separate files.
   • Use progressive disclosure: put the overview in SKILL.md, details in references/.
   • Write in third person (the description is injected into the agent's system prompt).
   • Be specific in the description field — it determines whether the skill triggers at all.

5. Add optional supporting files under references/ or assets/ as needed.

6. Open a pull request. The CI pipeline will automatically generate the .skill ZIP file on merge.

Style guidelines

• Follow the existing markdown formatting conventions (enforced by markdownlint via pre-commit hooks).
• Use consistent terminology within and across skills.
• Avoid time-sensitive information — prefer evergreen instructions.
• See the Agent Skills best practices for detailed authoring guidance.

CI/CD pipeline

You don't need to build .skill files manually. When changes to skill content are pushed to main:

1. generate-skills.sh packages each skill folder into a deterministic .skill ZIP.
2. update-readme-skills-table.sh regenerates the Available Skills table from SKILL.md frontmatter.
3. commit-changes.sh commits the updated archives and creates a new version tag.
4. GitHub Actions publishes a release with the .skill files attached.

License

This project is licensed under the MIT License.

---

Built for the EduBase e-learning platform