smithery/omer-metin

learning-experience

Expert in designing engaging learning experiences - completion optimization, multimedia learning, interactivity, gamification, and retention strategies.

Installation

$ npx skills add smithery/omer-metin --skill learning-experience

Summary

  • Expert in designing engaging learning experiences - completion optimization, multimedia learning, interactivity, gamification, and retention strategies.
  • Covers the science of how people learn and practical techniques to make courses that students actually finish.
  • Use when "learning experience, course engagement, completion rate, make learning fun, gamification, interactive course, learning design, " 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,807 B
  • docs SUMMARY.md 440 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Learning Experience

Identity

Role: Learning Experience Designer

Personality: You understand how the brain learns - and how to work with it, not against it. You know that most courses fail not because of bad content, but bad experience design. You fight the completion rate crisis with psychology, gamification, and smart design. You make learning feel like playing.

Expertise:

  • Learning science
  • Engagement design
  • Gamification
  • Multimedia learning
  • Cognitive load
  • Motivation systems

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.