imMamdouhaboammar/chatgpt-codex-plugin-autopilot / skills/workflow-to-skill-compiler
workflow-to-skill-compiler
VerifiedUse when a repository has a valuable agentic workflow, prompt chain, playbook, command, or runbook that should become a portable ChatGPT/Codex Skill without losing its real decision logic.
Workflow to Skill Compiler
Convert source workflows into portable Skills. Preserve behavior, not file shape.
Compilation rules
- Define one user job for the Skill. If the source mixes unrelated jobs, split it before conversion.
- Trace the source workflow from trigger to evidence, decisions, actions, validation, and stop conditions.
- Write Skill metadata for discovery. The
descriptionmust say when to use the Skill, not merely what topic it contains. - Keep the main
SKILL.mdfocused on execution. Move deep reference material intoreferences/and deterministic mechanical helpers intoscripts/. - Replace source-repository assumptions with portable contracts. Remove absolute paths, personal machine locations, private aliases, hidden environment assumptions, and undocumented dependencies.
- Preserve meaningful gates. Do not flatten approval, safety, testing, evidence, or verification steps just to make the Skill shorter.
- Prefer host capabilities over unnecessary bundled runtime code. Add MCP only when the workflow genuinely needs external data/actions that cannot be represented honestly as Skill guidance.
- Keep tool names capability-oriented where possible so the Skill can travel across compatible hosts.
- When the workflow touches files, repositories, generated artifacts, or local workspace state, integrate the
host-workspace-operatorcontract. Prefer read/list/search/grep for discovery, patch/write only for authorized mutations, shell for repository commands, andsandbox-python-executorfor deterministic Python work. - Add
agents/openai.yamlonly when interface metadata, product targeting, invocation policy, icons, or documented MCP tool dependencies materially improve the Skill. Do not invent dependencies for host-native filesystem, shell, patch, search, or Python tools. - Run public-distribution review before packaging. Internal workflows may contain capabilities that should never be mirrored into a public Skill.
Workspace-capability compilation
When the source workflow includes operations such as:
- reading files
- listing directories
- searching concepts or filenames
- exact grep/regex lookup
- creating or editing files
- applying focused patches
- running tests or repository commands
- deterministic Python/file processing
represent those operations as host-native capability requirements in the Skill instructions. Do not hard-code one product's tool names unless the current host contract requires it.
For generated Plugins, the main Autopilot should install the canonical workspace Skill with:
python3 <autopilot-skill>/scripts/install_host_workspace_skill.py <target-plugin>
The installer is intentionally non-destructive. If the target already contains a customized host-workspace-operator, review it instead of overwriting it.
Quality gate
Reject the compilation if:
- it is mostly a pasted prompt with no operating logic
- it cannot explain its trigger and completion condition
- it depends on files that will not exist after installation
- it silently drops source validation or approval gates
- multiple Skills are near-duplicates with different names
- the Skill description is so broad that it will collide with unrelated workflows
- generated instructions claim tools or permissions the Plugin does not actually provide
- mutation operations are mixed into read-only discovery without a clear authorization boundary
- the Skill says it searched, read, wrote, patched, ran shell, or executed Python without host evidence
Handoff
After compilation, pass the Skill set and its workspace-capability needs to plugin-experience-architect. The experience brief should state which host-native operations the Plugin benefits from and which are mutation-capable. Then run the main Autopilot generation and validation gates.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |