[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MBVAE7S01TFR7X91C967S4":3,"skill-same:01M6MBVAE7S01TFR7X91C967S4":81},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6MBVAE7S01TFR7X91C967S4","alpinejs-django",null,"Use when adding, changing, or debugging Alpine.js behavior in Django-rendered templates, especially when Alpine.js coexists with HTMX partial updates.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Falpinejs-django\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],"django","alpinejs django","frontend","codex","debugging","code","templates","js","behavior","use","alpine","clients","htmx","with","updates","when","2026-11-10 10:12:30",false,"---\nname: alpinejs-django\ndescription: Use when adding, changing, or debugging Alpine.js behavior in Django-rendered templates, especially when Alpine.js coexists with HTMX partial updates.\nlicense: MIT\ncompatibility: Codex, Claude Code, and other Agent Skills-compatible clients.\nmetadata:\n  version: \"0.1.0\"\n  displayName: Alpine.js Django\n  category: Django\n  tags: alpinejs,django,frontend,htmx\n---\n\n# Alpine.js with Django\n\nUse this skill for local browser state in Django-rendered templates: dropdowns,\nmodals, tabs, disclosures, inline filters, disabled\u002Floading states, small\npreview interactions, and client-only toggles. Use Django views\u002Fforms\u002Fmodels as\nthe source of truth for durable state. Use HTMX when the server needs to return\nfresh HTML.\n\n## Setup checks\n\n- Identify how the project loads Alpine. Prefer the existing static asset or\n  bundling pipeline as the source of truth.\n- Find the base template, layout, or bundled entrypoint that loads HTMX,\n  Alpine, and app JavaScript. Preserve the current ordering unless changing\n  initialization deliberately.\n- Determine whether the loaded Alpine file is self-starting or module-based. Do\n  not call `Alpine.start()` when the project already loads a self-starting\n  Alpine build. If using a module build, register components and start Alpine\n  from the owning entrypoint.\n- Simple Alpine behavior should usually live inline in the Django template with\n  `x-data`.\n- If a reusable component or store is worth extracting, register it before\n  Alpine starts. Check the existing script order before relying on\n  `document.addEventListener(\"alpine:init\", ...)` from an app-wide script.\n- When reusable Alpine registration is needed, add or reuse a script or\n  entrypoint that runs before Alpine starts. Register components and stores\n  inside `document.addEventListener(\"alpine:init\", ...)`, include the file\n  through the project's normal asset path, and avoid double-starting Alpine.\n\n## Ownership rules\n\n- Django owns persistence, authorization, validation, redirects, and rendered\n  HTML.\n- HTMX owns server round trips and DOM swaps.\n- Alpine owns ephemeral state already present in the browser.\n- Plain JavaScript modules or bundled entrypoints own shared DOM behavior that\n  is not naturally scoped to one Alpine component.\n- Do not duplicate the same behavior in Alpine and a plain JS module.\n\n## Template patterns\n\nUse a small `x-data` object near the markup it controls:\n\n```html\n\u003Cdiv\n  x-data=\"{ open: false }\"\n  @keydown.escape.window=\"open = false\"\n  @click.outside=\"open = false\"\n>\n  \u003Cbutton\n    type=\"button\"\n    :aria-expanded=\"open.toString()\"\n    @click.stop=\"open = !open\"\n  >\n    Menu\n  \u003C\u002Fbutton>\n\n  \u003Cdiv x-cloak x-show=\"open\" x-transition>\n    ...\n  \u003C\u002Fdiv>\n\u003C\u002Fdiv>\n```\n\nPrefer Alpine directives over manual DOM manipulation:\n\n- `x-show` for toggling visibility while keeping the element in the DOM.\n- `x-if` on a `\u003Ctemplate>` when the element should be created and destroyed.\n- `x-model` for client-only input state; Django form submission and validation\n  still happen on the server.\n- `:class`, `:disabled`, `:aria-expanded`, and `:hidden` for state-derived\n  attributes.\n- `$watch` for one named state transition; `x-effect` only when the dependency\n  set is simple and intentional.\n- `$dispatch` for browser events between Alpine components or from Alpine to\n  HTMX triggers.\n\nUse `x-cloak` for anything hidden by default. Ensure the base CSS includes the\nrequired `[x-cloak] { display: none !important; }` rule.\n\n## Django data\n\nKeep Django interpolation out of complex JavaScript expressions when possible.\n\nFor simple values, prefer HTML attributes:\n\n```html\n\u003Cdiv\n  data-initial-label=\"{{ object.name }}\"\n  x-data=\"{ label: '' }\"\n  x-init=\"label = $el.dataset.initialLabel\"\n>\n  \u003Cspan x-text=\"label\">\u003C\u002Fspan>\n\u003C\u002Fdiv>\n```\n\nFor structured values, prefer Django's `json_script` and parse it in `x-init`:\n\n```html\n{{ rows|json_script:\"rows-data\" }}\n\n\u003Cdiv\n  x-data=\"{ rows: [] }\"\n  x-init=\"rows = JSON.parse(document.getElementById('rows-data').textContent)\"\n>\n  \u003Ctemplate x-for=\"row in rows\" :key=\"row.id\">\n    \u003Cspan x-text=\"row.name\">\u003C\u002Fspan>\n  \u003C\u002Ftemplate>\n\u003C\u002Fdiv>\n```\n\nAvoid `|safe` inside Alpine expressions. If the browser must display text, use\n`x-text`. Use `x-html` only for trusted, already-sanitized HTML; most HTML should\nbe rendered by Django or returned through HTMX.\n\n## Alpine and HTMX\n\nWhen HTMX swaps a fragment containing `x-data`, Alpine should initialize the new\ncomponent automatically. Do not restart Alpine after HTMX swaps.\n\nKeep persistent Alpine state outside HTMX targets that will be replaced:\n\n```html\n\u003Csection x-data=\"{ panelOpen: false }\">\n  \u003Cbutton type=\"button\" @click=\"panelOpen = !panelOpen\">Filters\u003C\u002Fbutton>\n\n  \u003Cdiv id=\"results\" hx-get=\"{% url 'search_results' %}\" hx-trigger=\"change from:#filters\">\n    ...\n  \u003C\u002Fdiv>\n\u003C\u002Fsection>\n```\n\nUse events as the boundary between HTMX responses and Alpine state. From Django,\nset an `HX-Trigger` or `HX-Trigger-After-Swap` response header, then listen from\nAlpine:\n\n```html\n\u003Cdiv x-data=\"{ open: true }\" @profile-saved.window=\"open = false\">\n  \u003Cform hx-post=\"{% url 'profile_update' %}\" hx-target=\"#profile-panel\" hx-swap=\"outerHTML\">\n    ...\n  \u003C\u002Fform>\n\u003C\u002Fdiv>\n```\n\nListen for HTMX lifecycle events in kebab case from Alpine, such as\n`@htmx:after-swap.window`, because HTML attributes are case-insensitive.\n\nIf Alpine dispatches an event that HTMX should react to, make the trigger\nexplicit:\n\n```html\n\u003Cbutton type=\"button\" x-data @click=\"$dispatch('refresh-results')\">\n  Refresh\n\u003C\u002Fbutton>\n\n\u003Cdiv hx-get=\"{% url 'results' %}\" hx-trigger=\"refresh-results from:body\">\n  ...\n\u003C\u002Fdiv>\n```\n\n## Accessibility\n\n- Keep real buttons as `\u003Cbutton type=\"button\">` unless submitting a form.\n- Bind ARIA state from Alpine state, especially `aria-expanded`,\n  `aria-controls`, `aria-selected`, and `aria-hidden`.\n- Support `@keydown.escape.window` for dismissible overlays.\n- Use `@click.outside` for popovers and menus, paired with a visible trigger.\n- Preserve focus behavior for modals, menus, and swapped HTMX content. If focus\n  trapping is needed, add a focused plain JS module or Alpine plugin deliberately\n  instead of hand-rolling a brittle trap in attributes.\n\n## Security and CSP\n\n- Treat all Alpine expressions as JavaScript running in the user's browser.\n- Do not put secrets, signed tokens, or privileged data into `x-data`,\n  `data-*`, `json_script`, or hidden inputs unless the user is allowed to see\n  them.\n- If strict Content Security Policy without `unsafe-eval` is required, switch\n  deliberately to Alpine's CSP build and retest Alpine expressions. The default\n  `alpinejs\u002Fdist\u002Fcdn.min.js` build is not the CSP build.\n- If Alpine code makes `fetch()` requests, include Django CSRF headers or use\n  existing HTMX\u002FDjango forms instead.\n\n## Validation\n\n- For template-only Alpine changes, run the Django template or view tests that\n  cover the page, plus `npm run lint` if JavaScript modules changed.\n- For HTMX interactions, test the full page and the partial response path.\n- If the project has a frontend build step, run it before relying on static\n  output.\n- Manually verify stateful controls in light and dark mode when changing visible\n  UI behavior.\n","# Alpine.js with Django\n\nUse this skill for local browser state in Django-rendered templates: dropdowns,\nmodals, tabs, disclosures, inline filters, disabled\u002Floading states, small\npreview interactions, and client-only toggles. Use Django views\u002Fforms\u002Fmodels as\nthe source of truth for durable state. Use HTMX when the server needs to return\nfresh HTML.\n\n## Setup checks\n\n- Identify how the project loads Alpine. Prefer the existing static asset or\n  bundling pipeline as the source of truth.\n- Find the base template, layout, or bundled entrypoint that loads HTMX,\n  Alpine, and app JavaScript. Preserve the current ordering unless changing\n  initialization deliberately.\n- Determine whether the loaded Alpine file is self-starting or module-based. Do\n  not call `Alpine.start()` when the project already loads a self-starting\n  Alpine build. If using a module build, register components and start Alpine\n  from the owning entrypoint.\n- Simple Alpine behavior should usually live inline in the Django template with\n  `x-data`.\n- If a reusable component or store is worth extracting, register it before\n  Alpine starts. Check the existing script order before relying on\n  `document.addEventListener(\"alpine:init\", ...)` from an app-wide script.\n- When reusable Alpine registration is needed, add or reuse a script or\n  entrypoint that runs before Alpine starts. Register components and stores\n  inside `document.addEventListener(\"alpine:init\", ...)`, include the file\n  through the project's normal asset path, and avoid double-starting Alpine.\n\n## Ownership rules\n\n- Django owns persistence, authorization, validation, redirects, and rendered\n  HTML.\n- HTMX owns server round trips and DOM swaps.\n- Alpine owns ephemeral state already present in the browser.\n- Plain JavaScript modules or bundled entrypoints own shared DOM behavior that\n  is not naturally scoped to one Alpine component.\n- Do not duplicate the same behavior in Alpine and a plain JS module.\n\n## Template patterns\n\nUse a small `x-data` object near the markup it controls:\n\n```html\n\u003Cdiv\n  x-data=\"{ open: false }\"\n  @keydown.escape.window=\"open = false\"\n  @click.outside=\"open = false\"\n>\n  \u003Cbutton\n    type=\"button\"\n    :aria-expanded=\"open.toString()\"\n    @click.stop=\"open = !open\"\n  >\n    Menu\n  \u003C\u002Fbutton>\n\n  \u003Cdiv x-cloak x-show=\"open\" x-transition>\n    ...\n  \u003C\u002Fdiv>\n\u003C\u002Fdiv>\n```\n\nPrefer Alpine directives over manual DOM manipulation:\n\n- `x-show` for toggling visibility while keeping the element in the DOM.\n- `x-if` on a `\u003Ctemplate>` when the element should be created and destroyed.\n- `x-model` for client-only input state; Django form submission and validation\n  still happen on the server.\n- `:class`, `:disabled`, `:aria-expanded`, and `:hidden` for state-derived\n  attributes.\n- `$watch` for one named state transition; `x-effect` only when the dependency\n  set is simple and intentional.\n- `$dispatch` for browser events between Alpine components or from Alpine to\n  HTMX triggers.\n\nUse `x-cloak` for anything hidden by default. Ensure the base CSS includes the\nrequired `[x-cloak] { display: none !important; }` rule.\n\n## Django data\n\nKeep Django interpolation out of complex JavaScript expressions when possible.\n\nFor simple values, prefer HTML attributes:\n\n```html\n\u003Cdiv\n  data-initial-label=\"{{ object.name }}\"\n  x-data=\"{ label: '' }\"\n  x-init=\"label = $el.dataset.initialLabel\"\n>\n  \u003Cspan x-text=\"label\">\u003C\u002Fspan>\n\u003C\u002Fdiv>\n```\n\nFor structured values, prefer Django's `json_script` and parse it in `x-init`:\n\n```html\n{{ rows|json_script:\"rows-data\" }}\n\n\u003Cdiv\n  x-data=\"{ rows: [] }\"\n  x-init=\"rows = JSON.parse(document.getElementById('rows-data').textContent)\"\n>\n  \u003Ctemplate x-for=\"row in rows\" :key=\"row.id\">\n    \u003Cspan x-text=\"row.name\">\u003C\u002Fspan>\n  \u003C\u002Ftemplate>\n\u003C\u002Fdiv>\n```\n\nAvoid `|safe` inside Alpine expressions. If the browser must display text, use\n`x-text`. Use `x-html` only for trusted, already-sanitized HTML; most HTML should\nbe rendered by Django or returned through HTMX.\n\n## Alpine and HTMX\n\nWhen HTMX swaps a fragment containing `x-data`, Alpine should initialize the new\ncomponent automatically. Do not restart Alpine after HTMX swaps.\n\nKeep persistent Alpine state outside HTMX targets that will be replaced:\n\n```html\n\u003Csection x-data=\"{ panelOpen: false }\">\n  \u003Cbutton type=\"button\" @click=\"panelOpen = !panelOpen\">Filters\u003C\u002Fbutton>\n\n  \u003Cdiv id=\"results\" hx-get=\"{% url 'search_results' %}\" hx-trigger=\"change from:#filters\">\n    ...\n  \u003C\u002Fdiv>\n\u003C\u002Fsection>\n```\n\nUse events as the boundary between HTMX responses and Alpine state. From Django,\nset an `HX-Trigger` or `HX-Trigger-After-Swap` response header, then listen from\nAlpine:\n\n```html\n\u003Cdiv x-data=\"{ open: true }\" @profile-saved.window=\"open = false\">\n  \u003Cform hx-post=\"{% url 'profile_update' %}\" hx-target=\"#profile-panel\" hx-swap=\"outerHTML\">\n    ...\n  \u003C\u002Fform>\n\u003C\u002Fdiv>\n```\n\nListen for HTMX lifecycle events in kebab case from Alpine, such as\n`@htmx:after-swap.window`, because HTML attributes are case-insensitive.\n\nIf Alpine dispatches an event that HTMX should react to, make the trigger\nexplicit:\n\n```html\n\u003Cbutton type=\"button\" x-data @click=\"$dispatch('refresh-results')\">\n  Refresh\n\u003C\u002Fbutton>\n\n\u003Cdiv hx-get=\"{% url 'results' %}\" hx-trigger=\"refresh-results from:body\">\n  ...\n\u003C\u002Fdiv>\n```\n\n## Accessibility\n\n- Keep real buttons as `\u003Cbutton type=\"button\">` unless submitting a form.\n- Bind ARIA state from Alpine state, especially `aria-expanded`,\n  `aria-controls`, `aria-selected`, and `aria-hidden`.\n- Support `@keydown.escape.window` for dismissible overlays.\n- Use `@click.outside` for popovers and menus, paired with a visible trigger.\n- Preserve focus behavior for modals, menus, and swapped HTMX content. If focus\n  trapping is needed, add a focused plain JS module or Alpine plugin deliberately\n  instead of hand-rolling a brittle trap in attributes.\n\n## Security and CSP\n\n- Treat all Alpine expressions as JavaScript running in the user's browser.\n- Do not put secrets, signed tokens, or privileged data into `x-data`,\n  `data-*`, `json_script`, or hidden inputs unless the user is allowed to see\n  them.\n- If strict Content Security Policy without `unsafe-eval` is required, switch\n  deliberately to Alpine's CSP build and retest Alpine expressions. The default\n  `alpinejs\u002Fdist\u002Fcdn.min.js` build is not the CSP build.\n- If Alpine code makes `fetch()` requests, include Django CSRF headers or use\n  existing HTMX\u002FDjango forms instead.\n\n## Validation\n\n- For template-only Alpine changes, run the Django template or view tests that\n  cover the page, plus `npm run lint` if JavaScript modules changed.\n- For HTMX interactions, test the full page and the partial response path.\n- If the project has a frontend build step, run it before relying on static\n  output.\n- Manually verify stateful controls in light and dark mode when changing visible\n  UI behavior.\n",{"name":5,"license":15,"metadata":45,"description":7,"compatibility":50},{"tags":46,"version":47,"category":48,"displayName":49},"alpinejs,django,frontend,htmx","0.1.0","Django","Alpine.js Django","Codex, Claude Code, and other Agent Skills-compatible clients.","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Falpinejs-django",491,"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 14:06:13",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill alpinejs-django",{"tool":67,"command":68},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill alpinejs-django",{"tool":70,"command":71},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill alpinejs-django","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Falpinejs-django\u002FSKILL.md",true,[75],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"assets\u002Fapp-icon.png","ASSET","资产文件",38047,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Falpinejs-django\u002Fassets\u002Fapp-icon.png",[82,91,99,107,115,123],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":90},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":95,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":90},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":103,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":90},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\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":111,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":90},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":119,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":90},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":127,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":90},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]