Skip to main content
SkillCreator supports exporting skills to multiple AI coding agent runtimes. Each runtime has its own convention for loading instructions.

Supported runtimes

RuntimeSkill locationFormat
Claude Code.claude/skills/ or CLAUDE.mdMarkdown
Cursor.cursor/skills/Markdown
GitHub Copilot.github/copilot-instructions.mdMarkdown
Codex CLIAGENTS.mdMarkdown
Gemini CLIGEMINI.mdMarkdown
Amp.amp/skills/Markdown
Goose.goose/skills/Markdown
OpenCode.opencode/skills/Markdown

How export works

When you export a skill from SkillCreator, the app:
  1. Reads the skill’s frontmatter to determine the target runtime(s)
  2. Converts the skill format to the runtime’s expected structure
  3. Shows a diff preview of what will change
  4. Writes the file(s) to your project directory
Exports are transactional. If something goes wrong, SkillCreator rolls back the changes.

Claude Code

Claude Code reads skills from two locations:
  • CLAUDE.md: the project instruction file that Claude Code reads
  • .claude/skills/: individual skill files loaded on demand
SkillCreator can write to either location. For most skills, .claude/skills/ is preferred because it keeps instructions modular.

Cursor

Cursor loads custom rules from .cursor/rules/ in your project root. Each file becomes a separate rule that Cursor applies during code generation.

GitHub Copilot

Copilot reads repository-level instructions from .github/copilot-instructions.md. SkillCreator installs skills to .github/skills/ as separate files.

MCP integration

Beyond file-based exports, SkillCreator also runs an MCP server that agents can query directly. This allows agents to:
  • List available skills
  • Read skill content on demand
  • Check skill health and eval scores
  • Search skills by tag or keyword
See MCP setup for configuration details.
Last modified on March 19, 2026