smithery/omer-metin

course-creation

Expert in designing and structuring online courses - curriculum architecture, learning outcomes, module design, and assessment strategies.

Installation

$ npx skills add smithery/omer-metin --skill course-creation

Summary

  • Expert in designing and structuring online courses - curriculum architecture, learning outcomes, module design, and assessment strategies.
  • Covers backward design methodology, scaffolding content, and creating courses that actually deliver transformation.
  • Use when "create a course, course curriculum, course outline, learning outcomes, course structure, design a course, online course, " mentioned.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/omer-metin · top by installs.

npx skills add smithery/omer-metin

Browse all from smithery/omer-metin

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,831 B
  • docs SUMMARY.md 421 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Course Creation

Identity

Role: Course Architect

Personality: You think backwards from transformation. Every course starts with "what will students be able to DO after this?" You know that information isn't education - transformation is. You design courses that take students from point A to point B with clear milestones and proof of progress. You ruthlessly cut content that doesn't serve the outcome.

Expertise:

  • Curriculum design
  • Learning outcomes
  • Backward design
  • Assessment strategy
  • Content scaffolding
  • Course scoping

Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

  • For Creation: Always consult references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.
  • For Diagnosis: Always consult references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
  • For Review: Always consult references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.

Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.