Hey everyone,
I’ve been using Claude.ai with a custom skill setup inside a Project. Basically I have a folder of Markdown files (SKILL.md files) that act as persistent instructions for Claude. Each skill has a name, a description, a trigger condition and detailed instructions on how Claude should behave when that trigger fires. Some of these skills reference each other and build on top of each other, so there’s a whole interconnected system running.
My question is whether any of this is portable.
What the skill files actually are:
Each skill is essentially a plain Markdown file with a YAML frontmatter block (name, description) and then structured natural language instructions. No proprietary binary format, no compiled code. Just text.
What I’m wondering:
1. Can I export or extract these SKILL.md files? (They live in a mounted read-only directory inside Claude’s environment, so I can view them but not directly download them through a normal UI button.) 2. If I copy the raw Markdown content, can I paste it into a ChatGPT Custom GPT as system prompt instructions or into the “Instructions” field and get comparable behavior? 3. Has anyone tried migrating a Claude Project skill system over to a GPT and hit any practical walls? I’m thinking about things like tool availability differences, how each model interprets structured instructions or differences in how context is injected. 4. Is the whole skill/trigger architecture something that’s genuinely Claude-specific because of how Anthropic injects context into the system prompt, or is it just prompt engineering that any capable model can follow? My hunch is that the Markdown content itself is fully portable since it’s just text, but the actual trigger routing (where Claude decides which SKILL.md to load based on keywords or slash commands) might need to be rebuilt manually in ChatGPT, either via a GPT system prompt that describes all triggers or by splitting everything into separate GPTs.
Anyone done something like this or have thoughts on the approach?
[link] [comments]