[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77J5A04ZXV668ZJCMTYM80R":3,"skill-same:01M77J5A04ZXV668ZJCMTYM80R":43},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":42},"01M77J5A04ZXV668ZJCMTYM80R","save-as-standalone-html",null,"Single self-contained file that works offline","raaOS\u002Fsystem_prompts_leaks","raaOS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F214067397?v=4","01M77HV6K4ZTA4BZAGX00GTW6J","01M77HV6KX55HVRY679V25JXF8",0,"CC0-1.0","https:\u002F\u002Fgithub.com\u002FraaOS\u002Fsystem_prompts_leaks\u002Fblob\u002Fmain\u002FAnthropic\u002Fclaude-design\u002Fskills\u002Fsave-as-standalone-html\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: save-as-standalone-html\ndescription: \"Single self-contained file that works offline\"\nuser-invocable: true\n---\n\n# Save as standalone HTML\n\nExport the current design as a single self-contained HTML file that works completely offline — no external dependencies.\n\n### How it works\n\nThere is a deterministic bundler (super_inline_html tool) that can inline resources referenced directly in HTML attributes — img src\u002Fsrcset, source src\u002Fsrcset, video\u002Faudio\u002Ftrack src, video poster, SVG `\u003Cimage href>`\u002F`\u003Cuse href>`, link href (stylesheets, favicons), script src, CSS url() and @import, inline style attributes. However, it CANNOT discover resources that are only referenced as strings in JavaScript or JSX code — for example:\n- An image src set in React: `\u003Cimg src={\".\u002Fhero.png\"} \u002F>`\n- A background URL in a styled-component: `background: url('.\u002Fpattern.svg')`\n- A dynamically imported script\n\nYour job is to prepare the HTML file so the bundler can capture everything, then run it.\n\n### Step 1: Make a copy of the HTML file and update code-referenced resources\n\nCopy the current HTML file. Read it. Copy its dependencies. Look through ALL the code (inline scripts, imported JSX files, styled-components, etc) for any resource URL that is referenced as a string in code rather than as an HTML attribute. This includes:\n- Image URLs in React\u002FJSX (`\u003Cimg src={...} \u002F>`, `style={{ backgroundImage: ... }}`)\n- URLs in CSS-in-JS (styled-components, inline styles set via JS)\n- Script tags that import other scripts which themselves reference resources\n- Any fetch() or XMLHttpRequest calls that load assets\n- Audio\u002Fvideo sources set programmatically\n\nNote: if you use the Anthropic API in the project, it will not work standalone. If this is core to the project, STOP and tell the user!\n\n### Step 2: Add ext-resource-dependency meta tags\n\nFor EACH resource found in step 1, add a `\u003Cmeta>` tag in the `\u003Chead>`:\n\n```html\n\u003Cmeta name=\"ext-resource-dependency\" content=\"\u003Curl>\" data-resource-id=\"\u003Cid>\" \u002F>\n```\n\nWhere:\n- `content` is the URL of the resource (relative to the HTML file, or absolute)\n- `data-resource-id` is a short, unique identifier (e.g. \"heroImage\", \"patternSvg\")\n\nThen update the code to reference `window.__resources[id]` instead of the hardcoded URL. At runtime in the bundled file, `window.__resources[id]` will contain a blob URL pointing to the inlined resource data.\n\nExample:\n```html\n\u003C!-- In \u003Chead>: -->\n\u003Cmeta name=\"ext-resource-dependency\" content=\".\u002Fhero.png\" data-resource-id=\"heroImg\" \u002F>\n\u003Cmeta name=\"ext-resource-dependency\" content=\".\u002Fpattern.svg\" data-resource-id=\"patternBg\" \u002F>\n\n\u003C!-- In code, replace: -->\n\u003C!-- \u003Cimg src={\".\u002Fhero.png\"} \u002F> -->\n\u003C!-- with: -->\n\u003C!-- \u003Cimg src={window.__resources.heroImg} \u002F> -->\n```\n\nIMPORTANT:\n- The relative paths in `content` are relative to the HTML page itself\n- You must also do this for any external script tags that are imported and themselves reference resources — those scripts will be inlined by the bundler, but their resource references need to be lifted too\n- Be thorough! Missing even one resource means a broken image or missing asset in the final file\n\n### Step 3: Create a thumbnail (REQUIRED — the bundler will reject the file without it)\n\nCreate a lightweight SVG thumbnail that acts as a splash screen while the bundled file unpacks. This SVG should be a simplified, representative preview of the design — e.g. the key shapes, layout silhouette, or a branded loading visual. It doesn't need to be pixel-perfect, just visually representative so the user sees something meaningful instantly. It will be displayed TINY so a simple glyph on a vibrant color BG is enough.\n\nAdd it as a `\u003Ctemplate>` tag in the source HTML:\n\n```html\n\u003Ctemplate id=\"__bundler_thumbnail\" data-bg-color=\"#0a5e3e\">\n  \u003Csvg viewBox=\"0 0 1200 800\" xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\">\n    \u003C!-- Simplified icon -->\n  \u003C\u002Fsvg>\n\u003C\u002Ftemplate>\n```\n\n- Set `data-bg-color` to match the page's background color\n- The SVG should use `viewBox` for proper aspect-fit scaling\n- Keep it simple — this is just a loading placeholder, not a full reproduction\n- Use the design's actual colors so the transition feels seamless\n\nThe bundler will extract this and display it fullscreen (aspect-fit with the background color) while unpacking assets, then replace it with the real page. It also remains visible as the permanent fallback when JavaScript is disabled.\n\n### Step 4: Run the bundler\n\nIf you made changes in steps 1-3, save the modified HTML file first. Then (or if no changes were needed) call:\n\n```\nsuper_inline_html({ input_path: \"\u003Cpath-to-html>\", output_path: \"My Deck.html\" })\n```\n\nGive the output file a friendly human name.\n\n### Step 5: Verify (internal check only)\n\n**Read the tool result first** — if any asset couldn't be resolved, super_inline_html lists it directly in its output (\"N asset(s) could not be bundled: - asset not found: .\u002Ffoo.png\"). That's the authoritative miss list; fix those references and re-run before opening anything.\n\nThen open the bundled output with show_html TO CHECK IT WORKS — this is a private verification step for YOU, not the delivery mechanism. Check get_webview_logs for runtime errors (JS exceptions, failed decodes). If there are issues, fix the source file and re-run.\n\n### Step 6: Present for download — MANDATORY\n\nYou MUST deliver the final file using **present_fs_item_for_download** pointing directly at the inlined HTML output. This is the ONLY correct way to hand off a standalone export.\n\n- Do NOT use show_html \u002F show_to_user as the delivery step — those are preview tools, not download tools. The user cannot save the file from them.\n- Do NOT ask whether they want to download it — just call present_fs_item_for_download.\n- If you skip this step, the user has no way to get the file. This step is non-negotiable.\n","# Save as standalone HTML\n\nExport the current design as a single self-contained HTML file that works completely offline — no external dependencies.\n\n### How it works\n\nThere is a deterministic bundler (super_inline_html tool) that can inline resources referenced directly in HTML attributes — img src\u002Fsrcset, source src\u002Fsrcset, video\u002Faudio\u002Ftrack src, video poster, SVG `\u003Cimage href>`\u002F`\u003Cuse href>`, link href (stylesheets, favicons), script src, CSS url() and @import, inline style attributes. However, it CANNOT discover resources that are only referenced as strings in JavaScript or JSX code — for example:\n- An image src set in React: `\u003Cimg src={\".\u002Fhero.png\"} \u002F>`\n- A background URL in a styled-component: `background: url('.\u002Fpattern.svg')`\n- A dynamically imported script\n\nYour job is to prepare the HTML file so the bundler can capture everything, then run it.\n\n### Step 1: Make a copy of the HTML file and update code-referenced resources\n\nCopy the current HTML file. Read it. Copy its dependencies. Look through ALL the code (inline scripts, imported JSX files, styled-components, etc) for any resource URL that is referenced as a string in code rather than as an HTML attribute. This includes:\n- Image URLs in React\u002FJSX (`\u003Cimg src={...} \u002F>`, `style={{ backgroundImage: ... }}`)\n- URLs in CSS-in-JS (styled-components, inline styles set via JS)\n- Script tags that import other scripts which themselves reference resources\n- Any fetch() or XMLHttpRequest calls that load assets\n- Audio\u002Fvideo sources set programmatically\n\nNote: if you use the Anthropic API in the project, it will not work standalone. If this is core to the project, STOP and tell the user!\n\n### Step 2: Add ext-resource-dependency meta tags\n\nFor EACH resource found in step 1, add a `\u003Cmeta>` tag in the `\u003Chead>`:\n\n```html\n\u003Cmeta name=\"ext-resource-dependency\" content=\"\u003Curl>\" data-resource-id=\"\u003Cid>\" \u002F>\n```\n\nWhere:\n- `content` is the URL of the resource (relative to the HTML file, or absolute)\n- `data-resource-id` is a short, unique identifier (e.g. \"heroImage\", \"patternSvg\")\n\nThen update the code to reference `window.__resources[id]` instead of the hardcoded URL. At runtime in the bundled file, `window.__resources[id]` will contain a blob URL pointing to the inlined resource data.\n\nExample:\n```html\n\u003C!-- In \u003Chead>: -->\n\u003Cmeta name=\"ext-resource-dependency\" content=\".\u002Fhero.png\" data-resource-id=\"heroImg\" \u002F>\n\u003Cmeta name=\"ext-resource-dependency\" content=\".\u002Fpattern.svg\" data-resource-id=\"patternBg\" \u002F>\n\n\u003C!-- In code, replace: -->\n\u003C!-- \u003Cimg src={\".\u002Fhero.png\"} \u002F> -->\n\u003C!-- with: -->\n\u003C!-- \u003Cimg src={window.__resources.heroImg} \u002F> -->\n```\n\nIMPORTANT:\n- The relative paths in `content` are relative to the HTML page itself\n- You must also do this for any external script tags that are imported and themselves reference resources — those scripts will be inlined by the bundler, but their resource references need to be lifted too\n- Be thorough! Missing even one resource means a broken image or missing asset in the final file\n\n### Step 3: Create a thumbnail (REQUIRED — the bundler will reject the file without it)\n\nCreate a lightweight SVG thumbnail that acts as a splash screen while the bundled file unpacks. This SVG should be a simplified, representative preview of the design — e.g. the key shapes, layout silhouette, or a branded loading visual. It doesn't need to be pixel-perfect, just visually representative so the user sees something meaningful instantly. It will be displayed TINY so a simple glyph on a vibrant color BG is enough.\n\nAdd it as a `\u003Ctemplate>` tag in the source HTML:\n\n```html\n\u003Ctemplate id=\"__bundler_thumbnail\" data-bg-color=\"#0a5e3e\">\n  \u003Csvg viewBox=\"0 0 1200 800\" xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\">\n    \u003C!-- Simplified icon -->\n  \u003C\u002Fsvg>\n\u003C\u002Ftemplate>\n```\n\n- Set `data-bg-color` to match the page's background color\n- The SVG should use `viewBox` for proper aspect-fit scaling\n- Keep it simple — this is just a loading placeholder, not a full reproduction\n- Use the design's actual colors so the transition feels seamless\n\nThe bundler will extract this and display it fullscreen (aspect-fit with the background color) while unpacking assets, then replace it with the real page. It also remains visible as the permanent fallback when JavaScript is disabled.\n\n### Step 4: Run the bundler\n\nIf you made changes in steps 1-3, save the modified HTML file first. Then (or if no changes were needed) call:\n\n```\nsuper_inline_html({ input_path: \"\u003Cpath-to-html>\", output_path: \"My Deck.html\" })\n```\n\nGive the output file a friendly human name.\n\n### Step 5: Verify (internal check only)\n\n**Read the tool result first** — if any asset couldn't be resolved, super_inline_html lists it directly in its output (\"N asset(s) could not be bundled: - asset not found: .\u002Ffoo.png\"). That's the authoritative miss list; fix those references and re-run before opening anything.\n\nThen open the bundled output with show_html TO CHECK IT WORKS — this is a private verification step for YOU, not the delivery mechanism. Check get_webview_logs for runtime errors (JS exceptions, failed decodes). If there are issues, fix the source file and re-run.\n\n### Step 6: Present for download — MANDATORY\n\nYou MUST deliver the final file using **present_fs_item_for_download** pointing directly at the inlined HTML output. This is the ONLY correct way to hand off a standalone export.\n\n- Do NOT use show_html \u002F show_to_user as the delivery step — those are preview tools, not download tools. The user cannot save the file from them.\n- Do NOT ask whether they want to download it — just call present_fs_item_for_download.\n- If you skip this step, the user has no way to get the file. This step is non-negotiable.\n",{"name":5,"description":7,"user-invocable":23},true,"main","2975a5ac469614541ae22929d43b6da2635e1ee9","Anthropic\u002Fclaude-design\u002Fskills\u002Fsave-as-standalone-html","https:\u002F\u002Fgithub.com\u002FraaOS\u002Fsystem_prompts_leaks","https:\u002F\u002Fgithub.com\u002FraaOS","2026-11-14 21:19:17",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":23},[32,35,38],{"tool":33,"command":34},"npx","npx skills add raaOS\u002Fsystem_prompts_leaks --skill save-as-standalone-html",{"tool":36,"command":37},"bunx","bunx skills add raaOS\u002Fsystem_prompts_leaks --skill save-as-standalone-html",{"tool":39,"command":40},"pnpm","pnpm dlx skills add raaOS\u002Fsystem_prompts_leaks --skill save-as-standalone-html","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FraaOS\u002Fsystem_prompts_leaks\u002Fblob\u002Fmain\u002FAnthropic\u002Fclaude-design\u002Fskills\u002Fsave-as-standalone-html\u002FSKILL.md",[],[44,50,57,64,71,78],{"skillNo":45,"name":46,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":47,"categories":48,"keywords":49,"publishedAt":18},"01M77JV1M0ZZTZZREM9Q96TKZZ","model-council","https:\u002F\u002Fgithub.com\u002FraaOS\u002Fsystem_prompts_leaks\u002Fblob\u002Fmain\u002FPerplexity\u002Fskills\u002Fmodel-council\u002FSKILL.md",[],[],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":18},"01M77JTYND3ETS9EGCX3B9CW6E","writing-style","Draft or edit writing in the user's voice for the person who will read it and where it will appear. Use for messages, emails, documents or slides written on their behalf, not for your own replies.","https:\u002F\u002Fgithub.com\u002FraaOS\u002Fsystem_prompts_leaks\u002Fblob\u002Fmain\u002FOpenAI\u002Fdots\u002Fskills\u002Fwriting-style\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M77JTVWEHY80JC2H1JG1JMQB","write-page","Create or edit requested Page\u002FSpace content, or use for prose you have already decided to save as a standalone Markdown file, only if the user did not explicitly request a Markdown file. Honor established formats, destinations, and repository documentation. A selected Page alone does not authorize a write.","https:\u002F\u002Fgithub.com\u002FraaOS\u002Fsystem_prompts_leaks\u002Fblob\u002Fmain\u002FOpenAI\u002Fdots\u002Fskills\u002Fwrite-page\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M77JTQ5ND23QPF6RJYJPXHSZ","software-engineering","For use only in threads for this proactive personal assistant. Investigate software issues; inspect, write, review, or test code; work on a repository or local engineering file; or create, fix, or monitor a pull request or CI run. Use for actual engineering or product QA work, not a general programming explanation.","https:\u002F\u002Fgithub.com\u002FraaOS\u002Fsystem_prompts_leaks\u002Fblob\u002Fmain\u002FOpenAI\u002Fdots\u002Fskills\u002Fsoftware-engineering\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M77JTM3ZDPCYE8C1FW7G7S2B","slides-artifact","Use when the user asks to create, edit, or review slides or a presentation (PowerPoint or Google Slides), including when the task clearly calls for an audience-ready slide deck. Also use to answer questions that require inspecting an existing deck; not for general presentation advice or a chat-only outline.","https:\u002F\u002Fgithub.com\u002FraaOS\u002Fsystem_prompts_leaks\u002Fblob\u002Fmain\u002FOpenAI\u002Fdots\u002Fskills\u002Fslides-artifact\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M77JTHTWZN2J27KD2H66XDBZ","slack","Use when reading Slack conversations, deciding when to respond, or sending messages, files, and reactions in Slack.","https:\u002F\u002Fgithub.com\u002FraaOS\u002Fsystem_prompts_leaks\u002Fblob\u002Fmain\u002FOpenAI\u002Fdots\u002Fskills\u002Fslack\u002FSKILL.md",[],[]]