Update to gstack Workflows

{
  "description": "Convert a proven repeatable workflow into a reusable Skill with clear triggers and checks.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 277
    }
  ],
  "name": "skillify",
  "skill_md_contents": "---\nname: skillify\ndescription: Convert a proven repeatable workflow into a reusable Skill with clear triggers and checks.\n---\n\n# Skillify\n\nPortable ChatGPT/Codex adaptation of the `skillify` workflow from `garrytan/gstack`. Preserve the original job and safety intent while mapping execution to capabilities the current host actually exposes.\n\n## When to use\n\nUse this Skill when the user explicitly names `skillify` or asks for the same job described above.\n\n## Host contract\n\n- Inspect repository or file evidence before making claims about the current state.\n- Use host-native read, list, search, grep, patch, write, shell, browser, computer, and Python capabilities only when they actually exist.\n- Never claim commands, tests, browser actions, device actions, file writes, Git operations, or external mutations that were not executed.\n- Prefer read-only discovery before mutation.\n- Respect repository instructions and preserve unrelated work.\n- When the original native gstack runtime is available in Codex, it may be used as an implementation detail after inspecting the installed upstream Skill. Do not hard-code Claude-only paths as a requirement.\n\n## Workflow\n\n1. Start from a workflow that has been observed or clearly specified.\n2. Define a narrow trigger, user job, inputs, outputs, stop conditions, and mutation boundary.\n3. Map operations to host capabilities rather than hard-coded proprietary tool names.\n4. Add verification and negative routing cases.\n5. Package the result using the current Agent Skills contract and validate the files.\n\n## Completion\n\nReturn the decision, findings, changed artifacts if any, executed verification, skipped checks, and remaining blockers.\n"
}