Update to gstack Workflows

{
  "description": "Extract structured data from a web page using the safest available browser or web capability.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 276
    }
  ],
  "name": "scrape",
  "skill_md_contents": "---\nname: scrape\ndescription: Extract structured data from a web page using the safest available browser or web capability.\n---\n\n# Scrape\n\nPortable ChatGPT/Codex adaptation of the `scrape` 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 `scrape` 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. Prefer a host browser or web capability when one is available.\n2. Establish the exact page, fields, and output schema before extraction.\n3. Minimize navigation and avoid actions that change external state unless explicitly requested.\n4. Validate extracted data for completeness and obvious parsing errors.\n5. If browser capability is absent, explain the limitation instead of simulating browser output.\n\n## Completion\n\nReturn the decision, findings, changed artifacts if any, executed verification, skipped checks, and remaining blockers.\n"
}