[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MCE8DXS1W7FHNT4T88R3VM":3,"skill-same:01M6MCE8DXS1W7FHNT4T88R3VM":96},{"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":23,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":63,"repositoryHtmlUrl":64,"repositoryHomepageUrl":65,"ownerHtmlUrl":66,"ownerBlogUrl":67,"ownerDescription":68,"updatedAt":69,"install":70,"resources":83},"01M6MCE8DXS1W7FHNT4T88R3VM","htmx-realtime",null,"Build and review realtime and near-realtime htmx features. Use when implementing polling, load polling, job status updates, WebSockets, Server-Sent Events, htmx ws or sse extensions, streaming server-rendered fragments, multi-client updates, reconnect behavior, or deciding between polling, SSE, and WebSockets.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1571,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fhtmx-realtime\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"htmx realtime","realtime","htmx","build","when","features","implementing","load","updates","extensions","near","multi","events","websockets","frontend","status updates","use","behavior","sse","server","streaming","code","status","codex","review","2026-11-10 10:12:30",false,"---\nname: htmx-realtime\ndescription: Build and review realtime and near-realtime htmx features. Use when implementing polling, load polling, job status updates, WebSockets, Server-Sent Events, htmx ws or sse extensions, streaming server-rendered fragments, multi-client updates, reconnect behavior, or deciding between polling, SSE, and WebSockets.\nlicense: MIT\ncompatibility: Codex, Claude Code, and other Agent Skills-compatible clients.\nmetadata:\n  version: \"0.1.0\"\n  displayName: htmx Realtime\n  category: Frontend\n  tags: htmx,realtime,websockets,sse,polling\n---\n\n# htmx Realtime\n\nUse this skill when a page needs updates after initial render without full refresh. Choose the simplest transport that matches update frequency, direction, and operational cost.\n\n## Transport Decision\n\n| Need | Use |\n| --- | --- |\n| Occasional status refresh for one user | Polling |\n| Load until a job completes | Load polling or bounded polling |\n| Server-to-client event stream | Server-Sent Events |\n| Two-way low-latency messages | WebSockets |\n| Multi-user collaborative state | Usually WebSockets, with explicit state reconciliation |\n\nDo not start with WebSockets just because updates feel realtime. Polling is easier to operate and test when updates are infrequent.\n\n## Polling\n\nUse polling for job status, notifications, progress panels, and dashboards where a short delay is acceptable.\n\n- Keep the response small.\n- Choose an interval based on business need, not impatience.\n- Stop polling when the work is complete.\n- Return a final fragment that removes or disables the polling trigger.\n- Use server-side throttling or caching when many users poll the same state.\n- Avoid polling hidden tabs or offscreen widgets unless the value justifies it.\n\n## Load Polling\n\nUse load polling when each response decides whether another request should happen. It works well for background jobs because the server can stop the loop by returning the final state without the next trigger.\n\nKeep the next trigger near the fragment that owns the state so a final replacement removes the loop.\n\n## Server-Sent Events\n\nUse SSE when the server pushes one-way updates to the browser:\n\n- notifications;\n- progress messages;\n- append-only activity feeds;\n- operational status streams.\n\nTypical htmx SSE extension shape:\n\n```html\n\u003Csection hx-ext=\"sse\" sse-connect=\"\u002Fevents\" sse-swap=\"message\">\n  \u003Cdiv id=\"events\">\u003C\u002Fdiv>\n\u003C\u002Fsection>\n```\n\nServer responsibilities:\n\n- authenticate the stream;\n- send heartbeat comments or events when infrastructure requires it;\n- close streams cleanly;\n- format event payloads as trusted HTML fragments when htmx will swap them;\n- document reconnect behavior.\n\n## WebSockets\n\nUse WebSockets when the browser and server both send messages over a long-lived connection:\n\n- chat;\n- multiplayer or collaborative UI;\n- live dashboards with user actions;\n- bidirectional device or workflow control.\n\nTypical htmx WebSocket extension shape:\n\n```html\n\u003Cdiv hx-ext=\"ws\" ws-connect=\"\u002Fsocket\">\n  \u003Cform ws-send>\n    \u003Cinput name=\"message\">\n    \u003Cbutton type=\"submit\">Send\u003C\u002Fbutton>\n  \u003C\u002Fform>\n  \u003Cdiv id=\"messages\">\u003C\u002Fdiv>\n\u003C\u002Fdiv>\n```\n\nServer messages should usually be HTML fragments with stable targets or out-of-band swaps. Keep message formats narrow and versionable.\n\n## State And Reconciliation\n\n- The server should remain the source of truth for durable state.\n- Messages should be idempotent or safely replaceable.\n- Include resource identifiers in fragments or targets so late messages do not corrupt the wrong component.\n- Decide how to handle disconnects: missed messages, reload, replay, or fetch current state.\n- For optimistic UI over WebSockets, design rollback and server confirmation explicitly.\n\n## Operational Checks\n\n- Does the deployment platform support long-lived connections?\n- Are proxies configured for buffering, timeout, and upgrade behavior?\n- Is authentication refreshed or rejected cleanly when sessions expire?\n- Are connection counts bounded?\n- Is backpressure handled when clients are slow?\n- Are heartbeats and reconnects tested?\n\n## Security\n\n- Authenticate streams and sockets just like normal endpoints.\n- Enforce authorization per message, not only at connection time.\n- Escape or sanitize user content before sending HTML fragments.\n- Avoid putting secrets in client-visible stream messages.\n- Review CSP and extension loading with `htmx-security`.\n\n## Testing Checklist\n\n- Test initial connection and expected fragment updates.\n- Test disconnect\u002Freconnect behavior.\n- Test expired or unauthorized sessions.\n- Test malformed client messages for WebSockets.\n- Test that final polling states stop further requests.\n- Test multiple simultaneous clients when state is shared.\n\n## Avoid\n\n- Do not use WebSockets for simple \"check every few seconds\" status.\n- Do not leave infinite polling without a stop condition.\n- Do not stream unescaped user content into HTML swaps.\n- Do not assume all hosting providers treat SSE and WebSockets the same.\n- Do not couple realtime messages to page structure that may change without tests.\n","# htmx Realtime\n\nUse this skill when a page needs updates after initial render without full refresh. Choose the simplest transport that matches update frequency, direction, and operational cost.\n\n## Transport Decision\n\n| Need | Use |\n| --- | --- |\n| Occasional status refresh for one user | Polling |\n| Load until a job completes | Load polling or bounded polling |\n| Server-to-client event stream | Server-Sent Events |\n| Two-way low-latency messages | WebSockets |\n| Multi-user collaborative state | Usually WebSockets, with explicit state reconciliation |\n\nDo not start with WebSockets just because updates feel realtime. Polling is easier to operate and test when updates are infrequent.\n\n## Polling\n\nUse polling for job status, notifications, progress panels, and dashboards where a short delay is acceptable.\n\n- Keep the response small.\n- Choose an interval based on business need, not impatience.\n- Stop polling when the work is complete.\n- Return a final fragment that removes or disables the polling trigger.\n- Use server-side throttling or caching when many users poll the same state.\n- Avoid polling hidden tabs or offscreen widgets unless the value justifies it.\n\n## Load Polling\n\nUse load polling when each response decides whether another request should happen. It works well for background jobs because the server can stop the loop by returning the final state without the next trigger.\n\nKeep the next trigger near the fragment that owns the state so a final replacement removes the loop.\n\n## Server-Sent Events\n\nUse SSE when the server pushes one-way updates to the browser:\n\n- notifications;\n- progress messages;\n- append-only activity feeds;\n- operational status streams.\n\nTypical htmx SSE extension shape:\n\n```html\n\u003Csection hx-ext=\"sse\" sse-connect=\"\u002Fevents\" sse-swap=\"message\">\n  \u003Cdiv id=\"events\">\u003C\u002Fdiv>\n\u003C\u002Fsection>\n```\n\nServer responsibilities:\n\n- authenticate the stream;\n- send heartbeat comments or events when infrastructure requires it;\n- close streams cleanly;\n- format event payloads as trusted HTML fragments when htmx will swap them;\n- document reconnect behavior.\n\n## WebSockets\n\nUse WebSockets when the browser and server both send messages over a long-lived connection:\n\n- chat;\n- multiplayer or collaborative UI;\n- live dashboards with user actions;\n- bidirectional device or workflow control.\n\nTypical htmx WebSocket extension shape:\n\n```html\n\u003Cdiv hx-ext=\"ws\" ws-connect=\"\u002Fsocket\">\n  \u003Cform ws-send>\n    \u003Cinput name=\"message\">\n    \u003Cbutton type=\"submit\">Send\u003C\u002Fbutton>\n  \u003C\u002Fform>\n  \u003Cdiv id=\"messages\">\u003C\u002Fdiv>\n\u003C\u002Fdiv>\n```\n\nServer messages should usually be HTML fragments with stable targets or out-of-band swaps. Keep message formats narrow and versionable.\n\n## State And Reconciliation\n\n- The server should remain the source of truth for durable state.\n- Messages should be idempotent or safely replaceable.\n- Include resource identifiers in fragments or targets so late messages do not corrupt the wrong component.\n- Decide how to handle disconnects: missed messages, reload, replay, or fetch current state.\n- For optimistic UI over WebSockets, design rollback and server confirmation explicitly.\n\n## Operational Checks\n\n- Does the deployment platform support long-lived connections?\n- Are proxies configured for buffering, timeout, and upgrade behavior?\n- Is authentication refreshed or rejected cleanly when sessions expire?\n- Are connection counts bounded?\n- Is backpressure handled when clients are slow?\n- Are heartbeats and reconnects tested?\n\n## Security\n\n- Authenticate streams and sockets just like normal endpoints.\n- Enforce authorization per message, not only at connection time.\n- Escape or sanitize user content before sending HTML fragments.\n- Avoid putting secrets in client-visible stream messages.\n- Review CSP and extension loading with `htmx-security`.\n\n## Testing Checklist\n\n- Test initial connection and expected fragment updates.\n- Test disconnect\u002Freconnect behavior.\n- Test expired or unauthorized sessions.\n- Test malformed client messages for WebSockets.\n- Test that final polling states stop further requests.\n- Test multiple simultaneous clients when state is shared.\n\n## Avoid\n\n- Do not use WebSockets for simple \"check every few seconds\" status.\n- Do not leave infinite polling without a stop condition.\n- Do not stream unescaped user content into HTML swaps.\n- Do not assume all hosting providers treat SSE and WebSockets the same.\n- Do not couple realtime messages to page structure that may change without tests.\n",{"name":5,"license":15,"metadata":54,"description":7,"compatibility":59},{"tags":55,"version":56,"category":57,"displayName":58},"htmx,realtime,websockets,sse,polling","0.1.0","Frontend","htmx Realtime","Codex, Claude Code, and other Agent Skills-compatible clients.","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fhtmx-realtime",490,"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-14 02:12:02",{"source":8,"skillName":5,"commands":71,"prompt":81,"zipAvailable":82},[72,75,78],{"tool":73,"command":74},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill htmx-realtime",{"tool":76,"command":77},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill htmx-realtime",{"tool":79,"command":80},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill htmx-realtime","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fhtmx-realtime\u002FSKILL.md",true,[84,90],{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"agents\u002Fopenai.yaml","REFERENCE","参考文档",315,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fhtmx-realtime\u002Fagents\u002Fopenai.yaml",{"path":91,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":94,"sourceHtmlUrl":95},"assets\u002Ficons8-code.svg","ASSET","资产文件",460,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fhtmx-realtime\u002Fassets\u002Ficons8-code.svg",[97,106,113,120,146,170],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":101,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":105},"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.","Apache-2.0","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":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":101,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":105},"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":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":101,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":105},"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":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":101,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"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",[],[127,128,129,130,131,132,133,134,135,136,137,28,138,139,140,141,142,143,144,145],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":101,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"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",[],[153,154,48,141,155,156,157,158,159,160,161,162,163,164,132,165,166,167,168,169],"deja reflect","reflect","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":101,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":185,"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",[176,179,182],{"categoryNo":177,"categoryName":178,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":180,"categoryName":181,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":183,"categoryName":184,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[172,186,187,188,189,190,191,166,192,133,193,194,195,196,28,197,198,199,200,201],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]