[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MN94DASV1K7ST8075QMWPJ":3,"skill-same:01M6MN94DASV1K7ST8075QMWPJ":91},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":26,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":67,"commitSha":68,"skillDirectory":69,"forksCount":70,"repositoryHtmlUrl":71,"repositoryHomepageUrl":72,"ownerHtmlUrl":73,"ownerBlogUrl":74,"ownerDescription":75,"updatedAt":76,"install":77,"resources":90},"01M6MN94DASV1K7ST8075QMWPJ","client-side-js",null,"Use when a val needs to ship JavaScript that runs in the browser — React apps, vanilla DOM scripts, canvas\u002Fgames, htmx\u002FAlpine, or any client-side module beyond a single inline snippet. Explains how Val Town serves transpiled .ts\u002F.tsx\u002F.jsx modules with no build step, how the browser resolves their imports, and how to load third-party deps.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1566,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fval-town\u002Fplugins\u002Fskills\u002Fclient-side-js\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"client side","client side js","js","client","hydrate","when","imports","jsx","inline","val town","how to","scripts","frontend","apps","tsx","modules","deps","how","ship","browser","react","canvas","2026-11-10 10:12:30",false,"---\nname: client-side-js\ndescription: Use when a val needs to ship JavaScript that runs in the browser — React apps, vanilla DOM scripts, canvas\u002Fgames, htmx\u002FAlpine, or any client-side module beyond a single inline snippet. Explains how Val Town serves transpiled .ts\u002F.tsx\u002F.jsx modules with no build step, how the browser resolves their imports, and how to load third-party deps.\ntriggers: [client, browser, frontend, script, module, esm, bundle, build, hydrate, react-dom, mount, interactive, canvas, alpine, htmx, serveFile, type=module]\n---\n\n# Client-side JavaScript\n\nVal Town has **no build step and no bundler**. A client-side module is just a file\nin your val that you serve over HTTP; Val Town transpiles it per request. You point\na `\u003Cscript type=\"module\">` at a route that returns the file, and the browser runs\nit. There is nothing to configure (no webpack\u002Fvite\u002Fesbuild).\n\n## Serving a module\n\n`serveFile` from `std\u002Futils` reads a file and serves it with the correct\n`Content-Type`. For `.ts`, `.tsx`, and `.jsx` it **transpiles to JavaScript** —\nstrips types, compiles JSX — and serves `text\u002Fjavascript`. You serve the source\nfile; the browser receives runnable JS.\n\n```ts\nimport { serveFile } from \"https:\u002F\u002Fesm.town\u002Fv\u002Fstd\u002Futils\u002Findex.ts\";\n\n\u002F\u002F in any HTTP handler — serve a client module at some URL path\napp.get(\"\u002Fapp.tsx\", (c) => serveFile(\"\u002Fapp.tsx\"));\n```\n\nThen load it from your HTML:\n\n```html\n\u003Cscript type=\"module\" src=\"\u002Fapp.tsx\">\u003C\u002Fscript>\n```\n\nThe path you serve at and the file's location are up to you. A common shortcut is a\nwildcard that serves a whole directory of modules and assets:\n\n```ts\napp.get(\"\u002Fclient\u002F**\u002F*\", (c) => serveFile(c.req.path));\n```\n\n`serveFile` defaults to the current val. If you call it from a non-entrypoint file\nand paths don't resolve, pass `import.meta.url` as the second argument.\n\n## Default: versioned, immutably cached modules\n\n`serveImmutableFile` makes your val's frontend faster by letting browsers cache\nfiles immutably; publishing bumps the val's version, which invalidates\nautomatically. Measured: repeat visits **665ms → 157ms with zero asset requests**.\n\n```ts\nimport { immutableFileUrl, serveImmutableFile } from \"https:\u002F\u002Fesm.town\u002Fv\u002Fstd\u002Futils\u002Findex.ts\";\n\napp.get(\"\u002F__immutable\u002F*\", (c) => serveImmutableFile(c.req.path));\n```\n\nIn the never-cached HTML shell, stamp the entry module:\n`immutableFileUrl(\"\u002Ffrontend\u002Findex.tsx\")` → `\u002F__immutable\u002F42\u002Ffrontend\u002Findex.tsx`\n(42 = the val's current version). Relative imports resolve under the same prefix,\nso only the entry needs stamping — one route and one stamped URL cover the whole\nclient graph.\n\n- Old-version URLs 404 after a publish (like Next.js build assets); a reload\n  picks up the new version.\n- Retrofitting an existing val without touching its shell? Also point its old\n  file route at `serveImmutableFile` — bare paths then 302 into versioned space,\n  at one redirect per page view.\n\n### Alternative: serve directly from esm.town\n\nEvery val file already has a public esm.town URL that transpiles on demand, so you\ncan skip `serveFile` and point a script straight at it:\n\n```html\n\u003Cscript type=\"module\" src=\"https:\u002F\u002Fesm.town\u002Fv\u002Fyouruser\u002Fyourval\u002Fapp.tsx\">\u003C\u002Fscript>\n```\n\n`serveFile` is usually preferred because the module is served same-origin from a\npath you control, and you don't have to hardcode your own val URL.\n\n## How imports resolve in the browser\n\nThe transpiler does not bundle or rewrite imports — it only strips types and JSX.\nSo every import in a client module must be something the **browser** can fetch as a\nURL:\n\n- **Local imports need explicit extensions.** `import { x } from \".\u002Futil.ts\"`\n  resolves to `\u002Futil.ts` (or relative to the served path) and must be served too —\n  by the same route or a wildcard. Omitting the extension (`.\u002Futil`) 404s.\n- **Third-party deps need full ESM URLs.** Bare specifiers like `import React from\n  \"react\"` don't resolve in the browser. Import from a CDN such as esm.sh, with\n  versions pinned:\n\n  ```ts\n  import { createRoot } from \"https:\u002F\u002Fesm.sh\u002Freact-dom@18.2.0\u002Fclient\";\n  ```\n\n  An [import map](https:\u002F\u002Fdeveloper.mozilla.org\u002Fen-US\u002Fdocs\u002FWeb\u002FHTML\u002FElement\u002Fscript\u002Ftype\u002Fimportmap)\n  in the HTML is an option if you want bare specifiers in client code.\n\nThe same model works for any client code — React, vanilla DOM scripts, a canvas\ngame loop, Alpine, htmx. Only the imports differ; for a plain `.ts` module with no\ndependencies there's nothing to load from a CDN at all.\n\n## React specifics\n\nPin all React-family imports to the same version (18.2.0) and pass\n`?deps=react@18.2.0,react-dom@18.2.0` on libraries that depend on React. Mismatched\ncopies cause `Cannot read properties of null (reading 'useState')`. See the\n`react-ui` skill for JSX and styling conventions.\n\n## What not to do\n\n- **No app logic in inline `\u003Cscript>` blobs or template-string HTML.** Put client\n  code in real `.ts`\u002F`.tsx` files so it's typed, linted, and reviewable. A few lines\n  of inline bootstrap are fine; the app is not.\n- **No bundler \u002F build command.** There is no build step to add.\n- **`serveStatic` from Hono does not work** on Val Town — use `serveFile`.\n\n## Verifying changes\n\nFetch the module's URL (e.g. `\u002Fapp.tsx`) and confirm it returns `text\u002Fjavascript`,\nnot HTML or an error. Add `https:\u002F\u002Fesm.town\u002Fv\u002Fstd\u002Fcatch` to the HTML shell to pipe\nbrowser errors into `get_logs`, then load the page and check the logs. Don't report\nthe change as done without both.\n","# Client-side JavaScript\n\nVal Town has **no build step and no bundler**. A client-side module is just a file\nin your val that you serve over HTTP; Val Town transpiles it per request. You point\na `\u003Cscript type=\"module\">` at a route that returns the file, and the browser runs\nit. There is nothing to configure (no webpack\u002Fvite\u002Fesbuild).\n\n## Serving a module\n\n`serveFile` from `std\u002Futils` reads a file and serves it with the correct\n`Content-Type`. For `.ts`, `.tsx`, and `.jsx` it **transpiles to JavaScript** —\nstrips types, compiles JSX — and serves `text\u002Fjavascript`. You serve the source\nfile; the browser receives runnable JS.\n\n```ts\nimport { serveFile } from \"https:\u002F\u002Fesm.town\u002Fv\u002Fstd\u002Futils\u002Findex.ts\";\n\n\u002F\u002F in any HTTP handler — serve a client module at some URL path\napp.get(\"\u002Fapp.tsx\", (c) => serveFile(\"\u002Fapp.tsx\"));\n```\n\nThen load it from your HTML:\n\n```html\n\u003Cscript type=\"module\" src=\"\u002Fapp.tsx\">\u003C\u002Fscript>\n```\n\nThe path you serve at and the file's location are up to you. A common shortcut is a\nwildcard that serves a whole directory of modules and assets:\n\n```ts\napp.get(\"\u002Fclient\u002F**\u002F*\", (c) => serveFile(c.req.path));\n```\n\n`serveFile` defaults to the current val. If you call it from a non-entrypoint file\nand paths don't resolve, pass `import.meta.url` as the second argument.\n\n## Default: versioned, immutably cached modules\n\n`serveImmutableFile` makes your val's frontend faster by letting browsers cache\nfiles immutably; publishing bumps the val's version, which invalidates\nautomatically. Measured: repeat visits **665ms → 157ms with zero asset requests**.\n\n```ts\nimport { immutableFileUrl, serveImmutableFile } from \"https:\u002F\u002Fesm.town\u002Fv\u002Fstd\u002Futils\u002Findex.ts\";\n\napp.get(\"\u002F__immutable\u002F*\", (c) => serveImmutableFile(c.req.path));\n```\n\nIn the never-cached HTML shell, stamp the entry module:\n`immutableFileUrl(\"\u002Ffrontend\u002Findex.tsx\")` → `\u002F__immutable\u002F42\u002Ffrontend\u002Findex.tsx`\n(42 = the val's current version). Relative imports resolve under the same prefix,\nso only the entry needs stamping — one route and one stamped URL cover the whole\nclient graph.\n\n- Old-version URLs 404 after a publish (like Next.js build assets); a reload\n  picks up the new version.\n- Retrofitting an existing val without touching its shell? Also point its old\n  file route at `serveImmutableFile` — bare paths then 302 into versioned space,\n  at one redirect per page view.\n\n### Alternative: serve directly from esm.town\n\nEvery val file already has a public esm.town URL that transpiles on demand, so you\ncan skip `serveFile` and point a script straight at it:\n\n```html\n\u003Cscript type=\"module\" src=\"https:\u002F\u002Fesm.town\u002Fv\u002Fyouruser\u002Fyourval\u002Fapp.tsx\">\u003C\u002Fscript>\n```\n\n`serveFile` is usually preferred because the module is served same-origin from a\npath you control, and you don't have to hardcode your own val URL.\n\n## How imports resolve in the browser\n\nThe transpiler does not bundle or rewrite imports — it only strips types and JSX.\nSo every import in a client module must be something the **browser** can fetch as a\nURL:\n\n- **Local imports need explicit extensions.** `import { x } from \".\u002Futil.ts\"`\n  resolves to `\u002Futil.ts` (or relative to the served path) and must be served too —\n  by the same route or a wildcard. Omitting the extension (`.\u002Futil`) 404s.\n- **Third-party deps need full ESM URLs.** Bare specifiers like `import React from\n  \"react\"` don't resolve in the browser. Import from a CDN such as esm.sh, with\n  versions pinned:\n\n  ```ts\n  import { createRoot } from \"https:\u002F\u002Fesm.sh\u002Freact-dom@18.2.0\u002Fclient\";\n  ```\n\n  An [import map](https:\u002F\u002Fdeveloper.mozilla.org\u002Fen-US\u002Fdocs\u002FWeb\u002FHTML\u002FElement\u002Fscript\u002Ftype\u002Fimportmap)\n  in the HTML is an option if you want bare specifiers in client code.\n\nThe same model works for any client code — React, vanilla DOM scripts, a canvas\ngame loop, Alpine, htmx. Only the imports differ; for a plain `.ts` module with no\ndependencies there's nothing to load from a CDN at all.\n\n## React specifics\n\nPin all React-family imports to the same version (18.2.0) and pass\n`?deps=react@18.2.0,react-dom@18.2.0` on libraries that depend on React. Mismatched\ncopies cause `Cannot read properties of null (reading 'useState')`. See the\n`react-ui` skill for JSX and styling conventions.\n\n## What not to do\n\n- **No app logic in inline `\u003Cscript>` blobs or template-string HTML.** Put client\n  code in real `.ts`\u002F`.tsx` files so it's typed, linted, and reviewable. A few lines\n  of inline bootstrap are fine; the app is not.\n- **No bundler \u002F build command.** There is no build step to add.\n- **`serveStatic` from Hono does not work** on Val Town — use `serveFile`.\n\n## Verifying changes\n\nFetch the module's URL (e.g. `\u002Fapp.tsx`) and confirm it returns `text\u002Fjavascript`,\nnot HTML or an error. Add `https:\u002F\u002Fesm.town\u002Fv\u002Fstd\u002Fcatch` to the HTML shell to pipe\nbrowser errors into `get_logs`, then load the page and check the logs. Don't report\nthe change as done without both.\n",{"name":5,"triggers":54,"description":7},[30,46,39,55,56,57,58,59,31,60,61,62,48,63,64,65,66],"script","module","esm","bundle","build","react-dom","mount","interactive","alpine","htmx","serveFile","type=module","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fval-town\u002Fplugins\u002Fskills\u002Fclient-side-js",483,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-13 02:16:32",{"source":8,"skillName":5,"commands":78,"prompt":88,"zipAvailable":89},[79,82,85],{"tool":80,"command":81},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill client-side-js",{"tool":83,"command":84},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill client-side-js",{"tool":86,"command":87},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill client-side-js","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fval-town\u002Fplugins\u002Fskills\u002Fclient-side-js\u002FSKILL.md",true,[],[92,100,107,114,140,165],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":99},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":99},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":99},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":49},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[121,122,123,124,125,126,127,128,129,130,131,32,132,133,134,135,136,137,138,139],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":49},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[147,148,149,135,150,151,152,153,154,155,156,157,158,159,126,160,161,162,163,164],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":180,"publishedAt":49},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[171,174,177],{"categoryNo":172,"categoryName":173,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":175,"categoryName":176,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":178,"categoryName":179,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[167,181,182,183,184,185,186,161,187,127,188,189,190,191,32,192,193,194,195,196],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]