okhp3-gpt-skill-conversion-plan

Plan conversion of Custom GPT configurations into portable Agent Skill architectures.

1|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/OKHP3/refoldec --skill okhp3-gpt-skill-conversion-plan-okhp3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: okhp3-gpt-skill-conversion-plan
Source: https://github.com/OKHP3/refoldec/tree/main/.agents/skills/okhp3-gpt-skill-conversion-plan
Command: npx skills add https://github.com/OKHP3/refoldec --skill okhp3-gpt-skill-conversion-plan-okhp3

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Converting an existing Custom GPT into a portable Agent Skill is risky: instructions, knowledge files, actions, and hidden platform behavior do not map one-to-one, and naive copying causes silent semantic loss. This Skill produces a structured conversion plan with capability mapping, semantic-loss tracking, and a migration backlog before any authoring begins. ## Core Features & Use Cases - Capability Mapping: Inventories GPT instructions, knowledge files, actions, starters, and prompt chains, then maps each behavior to a skill construct (trigger, procedure, reference, script, adapter, or drop). - Semantic-Loss Analysis: Identifies platform-bound capabilities like connectors, OAuth actions, conversation memory, and hidden Builder behavior, pairing each loss with a mitigation or acceptance test. - Foundry Handoff: Emits a machine-readable conversion dossier and exactly three eval cases so okhp3-skill-foundry can author, benchmark, and iterate on the final SKILL.md. - Use Case: You have a GPT that reviews architecture decision records using a rubric, a glossary PDF, and a six-stage prompt chain. Use this Skill to produce a conversion verdict, capability map, and migration backlog before rebuilding it as a portable skill. ## Quick Start Plan the conversion of my Custom GPT into an Agent Skill based on its instructions, knowledge files, and actions.

Frequently Asked Questions about okhp3-gpt-skill-conversion-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a Custom GPT into an Agent Skill?▼

Inventory the GPT's instructions, knowledge files, actions, and prompt chains, then map each behavior to a skill construct such as a trigger, procedure, reference, or script. This Skill produces the conversion plan, capability map, and migration backlog; okhp3-skill-foundry authors the final SKILL.md.

What GPT features cannot transfer to a portable skill?▼

Platform-bound capabilities like private connectors, OAuth actions, conversation memory, hidden Builder instructions, and retrieval ranking do not transfer cleanly. The plan isolates these as adapters or explicit exclusions and records each loss with impact, mitigation, and an acceptance test.

Can I convert a GPT if I only have a screenshot of it?▼

No, a name and screenshot are insufficient source material. The Skill issues a needs_source_artifacts disposition, requests the smallest high-value artifacts needed, and provides only a provisional architecture without inventing instructions or behavior.

How is semantic loss detected during GPT migration?▼

Each source capability is classified by evidence and checked against portability: reasoning patterns and schemas transfer, while tool auth, connector permissions, and undocumented model behavior are flagged. Every loss gets an impact statement plus a mitigation or eval case.

What does the conversion plan hand off to Skill Foundry?▼

The handoff is a machine-readable dossier following references/conversion-dossier-schema.md, containing the verdict, capability map, semantic-loss register, skill architecture, migration backlog, and exactly three eval cases with four expectations each.