{"id":6307,"plugin_id":"plugin_asdk_app_6a330a7730c081919892632d5baaec58","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T22:48:05.500Z","digest":"b9ae635c784a0858777a05a4463ea1c4aaab094f573fed7ca318f67b69246d62","against":null,"payload":{"name":"resources","description":"Show the participant's resource hub for working through the hackathon with Codex, including docs, inspiration, and anti-pattern guidance. Use when the user wants hackathon resources, wants inspiration, or needs a reminder of what kinds of projects to avoid.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":221},{"relative_path":"references/SETUP.md","size_in_bytes":1231},{"relative_path":"references/anti-patterns.md","size_in_bytes":916},{"relative_path":"references/config/hackathon.json","size_in_bytes":1897},{"relative_path":"references/content/learning/build.md","size_in_bytes":939},{"relative_path":"references/content/learning/checklist.md","size_in_bytes":618},{"relative_path":"references/content/learning/onboard.md","size_in_bytes":1333},{"relative_path":"references/content/learning/prd.md","size_in_bytes":972},{"relative_path":"references/content/learning/scope.md","size_in_bytes":403},{"relative_path":"references/content/learning/spec.md","size_in_bytes":356},{"relative_path":"references/content/steps/check.md","size_in_bytes":1150},{"relative_path":"references/content/steps/help.md","size_in_bytes":2595},{"relative_path":"references/content/steps/map.md","size_in_bytes":948},{"relative_path":"references/content/steps/prepare.md","size_in_bytes":1599},{"relative_path":"references/content/steps/resources.md","size_in_bytes":1601},{"relative_path":"references/content/steps/rules.md","size_in_bytes":840},{"relative_path":"references/content/steps/start.md","size_in_bytes":1868},{"relative_path":"references/plugin-runtime.md","size_in_bytes":11707}],"skill_md_contents":"---\nname: resources\ndescription: Show the participant's resource hub for working through the hackathon with Codex, including docs, inspiration, and anti-pattern guidance. Use when the user wants hackathon resources, wants inspiration, or needs a reminder of what kinds of projects to avoid.\n---\n\n# Resources\n\n## Purpose\n\nUpdate state for Step 3, compose the Resources chat response, and explain the two available paths: continue directly to submission prep or enter the optional guided build tool.\n\nChat is the primary participant interface. Keep responses text-first so they render in any Codex host; the bundled `devpost` MCP server supplies rich inline visuals on hosts that support them.\n\n## Required Data Source\n\nOfficial event data comes from the `devpost` MCP server — follow **Devpost MCP Server** in `references/plugin-runtime.md` (call only what you need, never verify or set up the server, degrade in one line on failure).\n\nDraw on these only as needed: `devpost.get_hackathon_overview`, `devpost.get_key_dates`, `devpost.get_announcements`. Use the local `references/` files for evergreen guidance (archetypes, anti-patterns).\n\n## Required References\n\nRead these files before responding:\n\n- `references/plugin-runtime.md`\n- `references/content/steps/resources.md`\n- `references/config/hackathon.json`\n- `references/anti-patterns.md`\n\n## Preconditions\n\nRead `.devpost-hackathon-state.json`.\n\nIf the state file does not exist, direct the user to `$start-hackathon`.\n\nIf `rules_acknowledged` is not `true`, tell the user to finish `$review-hackathon-rules` first. This is a blocker before the rest of the workflow.\n\n## Response Content\n\nThe Resources response should help the participant understand:\n\n- useful in-app resources\n- strong project archetypes\n- anti-patterns to avoid\n- the fork: either enter the guided build tool (`$build-onboard`) or skip it and build the project now with Codex, running `$prepare-submission` only once there is something built to submit\n- the optional guided build tool nested inside Step 3\n\nThe optional guided build tool is command-driven, not clickable routing in a side pane.\n\nVisible build sequence:\n\n`Ideate -> Scope -> PRD -> Spec -> Checklist -> Build`\n\nCommand sequence:\n\n`$build-onboard -> $build-scope -> $build-prd -> $build-spec -> $build-checklist -> $build-project`\n\nDo not render images, posters, or other media in chat.\n\n## Hackathon Resources (live, from the MCP)\n\nRender the hackathon's own resources in chat — a condensed version of the Resources tab on the hackathon's Devpost site. Call the `get_hackathon_overview` MCP tool (bundled `devpost` server, PUBLIC — needs only `hackathon.slug`) and use its `resources_text` / `resources_html` field: pull out the key links and render them as **live markdown hyperlinks**, one short line each (condense — do not dump the whole blob). These chat links are the real resources.\n\n**Only real resources, or none.** If the hackathon returns no resources (or the call fails), show no resource links at all — skip the section without comment beyond one short clause. Never pad the list from other files, web search, or memory: a resource the host didn't publish is not a hackathon resource (see **Never present unofficial data as official** in `references/plugin-runtime.md`).\n\n## Presentation Output\n\nCompose the response in-context per `references/plugin-runtime.md` (\"Composing the Response\"): read `references/content/steps/resources.md`, strip maintainer `<!-- -->` comments, interpolate the event name, then present a short stage headline, the page content, and the next-step callout. Do not run any script.\n\n## State Update\n\nAfter showing resources:\n\n- add `resources` to `completed_stages` if needed\n- set `current_stage` to `resources`\n- set `next_command` to `prepare-submission` (the next tracked stage — but present it as \"when your build is ready\", never as the immediate next step; the participant builds first, guided or not)\n- preserve registration and deadline fields\n\nDo not mark the optional guided build tool active unless the user chooses it or runs `$build-onboard`.\n\n## Chat Output\n\nKeep chat output minimal.\n\nDo not hand-write a separate dashboard. Let the CLI composer render the response.\n\nRespond with:\n\n- note that the guided build tool is optional — always say so, every time it comes up — and that it introduces best practices for coding AI projects, nested inside Step 3\n- one or two sentences explaining the fork: guided planning vs. building on your own\n- invitation to ask questions about which path fits their project\n- do NOT end with a single `$prepare-submission` callout line — that misleads participants into thinking submission prep is the immediate next step before they have built anything. End with the two-path callout instead:\n\n```text\nWant the guided path? Say so — or type `$build-onboard`. It'll get you to a proof of concept; making it great stays your job.\nBuilding on your own? Start building with Codex now — when your project feels ready to submit, type `$prepare-submission`.\n```\n\nIf composer generation fails, use a compact text fallback:\n\n- current stage: Resources\n- the two-path callout above (guided `$build-onboard`, or build now and `$prepare-submission` when ready)\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}