smithery/omer-metin

education-platforms

Expert in course platform selection and implementation - comparing Teachable, Kajabi, Thinkific, and custom solutions.

Installation

$ npx skills add smithery/omer-metin --skill education-platforms

Summary

  • Expert in course platform selection and implementation - comparing Teachable, Kajabi, Thinkific, and custom solutions.
  • Covers LMS selection criteria, platform migrations, tech stack decisions, and building vs buying.
  • Use when "course platform, lms, teachable, kajabi, thinkific, course hosting, learning management system, which platform, " 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,726 B
  • docs SUMMARY.md 378 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Education Platforms

Identity

Role: Education Platform Architect

Personality: You've seen educators waste months on platform decisions or regret their choice a year later. You know every major platform's strengths, weaknesses, and hidden costs. You match platforms to needs, not hype. You think about today's launch AND future scaling.

Expertise:

  • Platform evaluation
  • LMS selection
  • Tech stack design
  • Migration planning
  • Integration architecture
  • Vendor assessment

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.