[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7139GJSAC337NF3VKPD12YA":3,"skill-same:01M7139GJSAC337NF3VKPD12YA":118},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M7139GJSAC337NF3VKPD12YA","hyperframes-registry",null,"Install, discover, and wire registry blocks and components into HyperFrames compositions. Use when running hyperframes add or hyperframes catalog, installing one item or every block matching a tag, wiring an installed item into index.html, or working with hyperframes.json. Covers discovery, install locations, block sub-composition wiring, component snippet merging, and authoring a new block or component to contribute upstream (idea → scaffold → validate → PR).","EthanYoQ\u002FSkill-hub","EthanYoQ","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F257484394?v=4","01M70C9QKWR1YS0S7V26DNB18H","Ethan","01M70C9QMER047R5ANZZA6KC2P",11,"MIT","https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F07-media-content\u002Fhyperframes-registry\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"hyperframes registry","hyperframes","registry","upstream","discovery","pr","contribute","running","idea","html","add","authoring","install","component","wiring","components","when","new","discover","Composition","2026-11-10 10:12:30",false,"---\nname: hyperframes-registry\ndescription: Install, discover, and wire registry blocks and components into HyperFrames compositions. Use when running hyperframes add or hyperframes catalog, installing one item or every block matching a tag, wiring an installed item into index.html, or working with hyperframes.json. Covers discovery, install locations, block sub-composition wiring, component snippet merging, and authoring a new block or component to contribute upstream (idea → scaffold → validate → PR).\n---\n\n# HyperFrames Registry\n\nThe registry provides reusable blocks and components installable via `hyperframes add \u003Cname>`.\n\n- **Blocks** — standalone sub-compositions (own dimensions, duration, timeline). Included via `data-composition-src` in a host composition.\n- **Components** — effect snippets (no own dimensions). Pasted directly into a host composition's HTML.\n\n## Quick reference\n\n```bash\nhyperframes add data-chart              # install a block\nhyperframes add grain-overlay           # install a component\nhyperframes add captions                # install every block tagged captions\nhyperframes add shimmer-sweep --dir .   # target a specific project\nhyperframes add data-chart --json       # machine-readable output\nhyperframes add data-chart --no-clipboard  # skip clipboard (CI\u002Fheadless)\n```\n\nAfter install, the CLI prints which files were written and a snippet to paste into your host composition. The snippet is a starting point — you'll need to add `data-composition-id` (must match the block's internal composition ID), `data-start`, and `data-track-index` attributes when wiring blocks.\n\nThe positional value is resolved as an exact item name first. If no item matches and the value is a tag, the command installs every block with that tag. Registry dependencies are installed before the requested item. `hyperframes add` works only for blocks and components; for examples, use `hyperframes init \u003Cdir> --example \u003Cname>` instead.\n\n## Install locations\n\nBlocks install to `compositions\u002F\u003Cname>.html` by default. Components install to `compositions\u002Fcomponents\u002F\u003Cname>.html` by default.\n\nThese paths are configurable in `hyperframes.json`:\n\n```json\n{\n  \"registry\": \"https:\u002F\u002Fraw.githubusercontent.com\u002Fheygen-com\u002Fhyperframes\u002Fmain\u002Fregistry\",\n  \"paths\": {\n    \"blocks\": \"compositions\",\n    \"components\": \"compositions\u002Fcomponents\",\n    \"assets\": \"assets\"\n  }\n}\n```\n\nSee [install-locations.md](.\u002Freferences\u002Finstall-locations.md) for full details.\n\n## Wiring blocks\n\nBlocks are standalone compositions — include them via `data-composition-src` in your host `index.html`:\n\n```html\n\u003Cdiv\n  data-composition-id=\"data-chart\"\n  data-composition-src=\"compositions\u002Fdata-chart.html\"\n  data-start=\"2\"\n  data-duration=\"15\"\n  data-track-index=\"1\"\n  data-width=\"1920\"\n  data-height=\"1080\"\n>\u003C\u002Fdiv>\n```\n\nKey attributes:\n\n- `data-composition-src` — path to the block HTML file\n- `data-composition-id` — must match the block's internal ID\n- `data-start` — when the block appears in the host timeline (seconds)\n- `data-duration` — how long the block plays\n- `data-width` \u002F `data-height` — block canvas dimensions\n- `data-track-index` — layer ordering (higher = in front)\n\nSee [wiring-blocks.md](.\u002Freferences\u002Fwiring-blocks.md) for full details.\n\n## Wiring components\n\nComponents are snippets — paste their HTML into your composition's markup, their CSS into your style block, and their JS into your script (if any):\n\n1. Read the installed file (e.g., `compositions\u002Fcomponents\u002Fgrain-overlay.html`)\n2. Copy the HTML elements into your composition's `\u003Cdiv data-composition-id=\"...\">`\n3. Copy the `\u003Cstyle>` block into your composition's styles\n4. Copy any `\u003Cscript>` content into your composition's script (before your timeline code)\n5. If the component exposes GSAP timeline integration (see the comment block in the snippet), add those calls to your timeline\n\nSee [wiring-components.md](.\u002Freferences\u002Fwiring-components.md) for full details.\n\n## Discovery\n\nUse the CLI as the primary discovery surface. **Search by intent before browsing:** the registry holds more items than you can scan by eye, so listing them and matching on names or tags is the slow path, and it fails whenever the author's wording differs from yours.\n\n```bash\n# Rank the whole catalog against what the beat should do\nnpx hyperframes catalog --query \"reveal a headline one line at a time\"\nnpx hyperframes add caption-clip-wipe\n```\n\nSearch is local and sends nothing. By default it ranks on vocabulary shared with the item's name, title and description, so it only finds items that reuse your words; `--on-device` ranks by meaning instead, after a one-time model download. With `--json` the envelope names which tier answered, so check that rather than assuming a ranking happened.\n\n**Always query in English, whatever language the video is in.** The catalog is written in English and both tiers index it that way (the on-device model is English-only too). A query in another script produces no searchable terms and returns nothing at all. This is easy to get wrong on a Japanese or Chinese project, where the brief, the captions and the narration are all in that language and the query naturally follows: describe the _move_ in English, then write the on-screen copy in whatever language the video needs. If a query does come back with `No searchable words in query`, that is this rule, not a missing component, and it is not worth a gap report.\n\nInstallability is applied after ranking, not before it: a name the vectors carry but this registry cannot serve is dropped from the results and counted in `dropped`, so a non-zero `dropped` means the two are different generations. See `\u002Fhyperframes-cli` for the offline tier, the consent gates, and how to refresh a stale index.\n\nTo browse or filter instead of search:\n\n```bash\nnpx hyperframes catalog\nnpx hyperframes catalog --type block\nnpx hyperframes catalog --type component\nnpx hyperframes catalog --type block --tag social\nnpx hyperframes catalog --json\nnpx hyperframes catalog --human-friendly\n```\n\nThe normal table and `--json` modes only list matches; install a selected name with `hyperframes add \u003Cname>`. `--human-friendly` opens an interactive picker and installs the selected item immediately. In CI or agent workflows, prefer `--json` followed by an explicit `add`.\n\n### Report what the catalog does not have\n\nWhen the search comes back and nothing in it does the job, say so before you hand-author the move:\n\n```bash\nnpx hyperframes feedback --search-miss \"\u003Cthe query you ran>\" --wanted \"\u003Cthe move you needed>\" --tier on-device\n```\n\n`catalog --query` prints this line for you, pre-filled, and `--json` carries it as `report_gap` — so it is already in hand at the moment you decide nothing fits.\n\n**Report whenever nothing in the results does the job, on either tier.** Do not wait for the on-device tier to have answered: it needs a consented 33 MB download, so an agent run is on `words` unless it explicitly opted in, and gating on `on-device` would silence almost every report. The `--tier` value rides along so a vocabulary miss stays distinguishable from a meaning miss when these are read. Describe the effect you wanted, not the item name you imagined: what comes back is a list of moves worth building, and a report naming a non-existent item teaches nothing. This is the only path that sends a query anywhere, which is exactly why it is a separate deliberate command rather than something the search does on its own. It carries no rating and never lands in the rating metric.\n\nThis is the whole demand signal for the catalog. Skipping it means the gap you hit gets guessed at from install counts instead, which cannot see a move nobody could install.\n\nIf the CLI cannot reach the configured registry, inspect the raw manifest as a fallback:\n\n```bash\ncurl -s https:\u002F\u002Fraw.githubusercontent.com\u002Fheygen-com\u002Fhyperframes\u002Fmain\u002Fregistry\u002Fregistry.json\n```\n\nA registry the CLI cannot reach does **not** empty the catalog for **discovery**: a previously fetched manifest keeps serving past its 24h refresh window whenever revalidation fails, so `catalog` and `catalog --query` still list and rank against the last copy on disk.\n\n**`add` still needs the network, even for an item you installed yesterday.** Only manifests are cached; the item's actual files are fetched on every install. So offline you can search, and you can see what an item is, but installing it fails at the file fetch. Do not promise a user an offline install.\n\nEach item's `registry-item.json` contains: name, type, title, description, tags, dimensions (blocks only), duration (blocks only), and file list.\n\nSee [discovery.md](.\u002Freferences\u002Fdiscovery.md) for details on filtering by type and tags.\n\n## Contributing a new block or component\n\nTo author a NEW registry item (caption style, VFX block, transition, lower third, or a reusable component) and ship it as an upstream PR — not install an existing one — follow the full idea → scaffold → build → validate → preview → ship workflow in [contributing.md](.\u002Freferences\u002Fcontributing.md). Copy-paste starter templates (caption \u002F VFX \u002F component \u002F `registry-item.json`) are in [templates.md](.\u002Freferences\u002Ftemplates.md).\n","# HyperFrames Registry\n\nThe registry provides reusable blocks and components installable via `hyperframes add \u003Cname>`.\n\n- **Blocks** — standalone sub-compositions (own dimensions, duration, timeline). Included via `data-composition-src` in a host composition.\n- **Components** — effect snippets (no own dimensions). Pasted directly into a host composition's HTML.\n\n## Quick reference\n\n```bash\nhyperframes add data-chart              # install a block\nhyperframes add grain-overlay           # install a component\nhyperframes add captions                # install every block tagged captions\nhyperframes add shimmer-sweep --dir .   # target a specific project\nhyperframes add data-chart --json       # machine-readable output\nhyperframes add data-chart --no-clipboard  # skip clipboard (CI\u002Fheadless)\n```\n\nAfter install, the CLI prints which files were written and a snippet to paste into your host composition. The snippet is a starting point — you'll need to add `data-composition-id` (must match the block's internal composition ID), `data-start`, and `data-track-index` attributes when wiring blocks.\n\nThe positional value is resolved as an exact item name first. If no item matches and the value is a tag, the command installs every block with that tag. Registry dependencies are installed before the requested item. `hyperframes add` works only for blocks and components; for examples, use `hyperframes init \u003Cdir> --example \u003Cname>` instead.\n\n## Install locations\n\nBlocks install to `compositions\u002F\u003Cname>.html` by default. Components install to `compositions\u002Fcomponents\u002F\u003Cname>.html` by default.\n\nThese paths are configurable in `hyperframes.json`:\n\n```json\n{\n  \"registry\": \"https:\u002F\u002Fraw.githubusercontent.com\u002Fheygen-com\u002Fhyperframes\u002Fmain\u002Fregistry\",\n  \"paths\": {\n    \"blocks\": \"compositions\",\n    \"components\": \"compositions\u002Fcomponents\",\n    \"assets\": \"assets\"\n  }\n}\n```\n\nSee [install-locations.md](.\u002Freferences\u002Finstall-locations.md) for full details.\n\n## Wiring blocks\n\nBlocks are standalone compositions — include them via `data-composition-src` in your host `index.html`:\n\n```html\n\u003Cdiv\n  data-composition-id=\"data-chart\"\n  data-composition-src=\"compositions\u002Fdata-chart.html\"\n  data-start=\"2\"\n  data-duration=\"15\"\n  data-track-index=\"1\"\n  data-width=\"1920\"\n  data-height=\"1080\"\n>\u003C\u002Fdiv>\n```\n\nKey attributes:\n\n- `data-composition-src` — path to the block HTML file\n- `data-composition-id` — must match the block's internal ID\n- `data-start` — when the block appears in the host timeline (seconds)\n- `data-duration` — how long the block plays\n- `data-width` \u002F `data-height` — block canvas dimensions\n- `data-track-index` — layer ordering (higher = in front)\n\nSee [wiring-blocks.md](.\u002Freferences\u002Fwiring-blocks.md) for full details.\n\n## Wiring components\n\nComponents are snippets — paste their HTML into your composition's markup, their CSS into your style block, and their JS into your script (if any):\n\n1. Read the installed file (e.g., `compositions\u002Fcomponents\u002Fgrain-overlay.html`)\n2. Copy the HTML elements into your composition's `\u003Cdiv data-composition-id=\"...\">`\n3. Copy the `\u003Cstyle>` block into your composition's styles\n4. Copy any `\u003Cscript>` content into your composition's script (before your timeline code)\n5. If the component exposes GSAP timeline integration (see the comment block in the snippet), add those calls to your timeline\n\nSee [wiring-components.md](.\u002Freferences\u002Fwiring-components.md) for full details.\n\n## Discovery\n\nUse the CLI as the primary discovery surface. **Search by intent before browsing:** the registry holds more items than you can scan by eye, so listing them and matching on names or tags is the slow path, and it fails whenever the author's wording differs from yours.\n\n```bash\n# Rank the whole catalog against what the beat should do\nnpx hyperframes catalog --query \"reveal a headline one line at a time\"\nnpx hyperframes add caption-clip-wipe\n```\n\nSearch is local and sends nothing. By default it ranks on vocabulary shared with the item's name, title and description, so it only finds items that reuse your words; `--on-device` ranks by meaning instead, after a one-time model download. With `--json` the envelope names which tier answered, so check that rather than assuming a ranking happened.\n\n**Always query in English, whatever language the video is in.** The catalog is written in English and both tiers index it that way (the on-device model is English-only too). A query in another script produces no searchable terms and returns nothing at all. This is easy to get wrong on a Japanese or Chinese project, where the brief, the captions and the narration are all in that language and the query naturally follows: describe the _move_ in English, then write the on-screen copy in whatever language the video needs. If a query does come back with `No searchable words in query`, that is this rule, not a missing component, and it is not worth a gap report.\n\nInstallability is applied after ranking, not before it: a name the vectors carry but this registry cannot serve is dropped from the results and counted in `dropped`, so a non-zero `dropped` means the two are different generations. See `\u002Fhyperframes-cli` for the offline tier, the consent gates, and how to refresh a stale index.\n\nTo browse or filter instead of search:\n\n```bash\nnpx hyperframes catalog\nnpx hyperframes catalog --type block\nnpx hyperframes catalog --type component\nnpx hyperframes catalog --type block --tag social\nnpx hyperframes catalog --json\nnpx hyperframes catalog --human-friendly\n```\n\nThe normal table and `--json` modes only list matches; install a selected name with `hyperframes add \u003Cname>`. `--human-friendly` opens an interactive picker and installs the selected item immediately. In CI or agent workflows, prefer `--json` followed by an explicit `add`.\n\n### Report what the catalog does not have\n\nWhen the search comes back and nothing in it does the job, say so before you hand-author the move:\n\n```bash\nnpx hyperframes feedback --search-miss \"\u003Cthe query you ran>\" --wanted \"\u003Cthe move you needed>\" --tier on-device\n```\n\n`catalog --query` prints this line for you, pre-filled, and `--json` carries it as `report_gap` — so it is already in hand at the moment you decide nothing fits.\n\n**Report whenever nothing in the results does the job, on either tier.** Do not wait for the on-device tier to have answered: it needs a consented 33 MB download, so an agent run is on `words` unless it explicitly opted in, and gating on `on-device` would silence almost every report. The `--tier` value rides along so a vocabulary miss stays distinguishable from a meaning miss when these are read. Describe the effect you wanted, not the item name you imagined: what comes back is a list of moves worth building, and a report naming a non-existent item teaches nothing. This is the only path that sends a query anywhere, which is exactly why it is a separate deliberate command rather than something the search does on its own. It carries no rating and never lands in the rating metric.\n\nThis is the whole demand signal for the catalog. Skipping it means the gap you hit gets guessed at from install counts instead, which cannot see a move nobody could install.\n\nIf the CLI cannot reach the configured registry, inspect the raw manifest as a fallback:\n\n```bash\ncurl -s https:\u002F\u002Fraw.githubusercontent.com\u002Fheygen-com\u002Fhyperframes\u002Fmain\u002Fregistry\u002Fregistry.json\n```\n\nA registry the CLI cannot reach does **not** empty the catalog for **discovery**: a previously fetched manifest keeps serving past its 24h refresh window whenever revalidation fails, so `catalog` and `catalog --query` still list and rank against the last copy on disk.\n\n**`add` still needs the network, even for an item you installed yesterday.** Only manifests are cached; the item's actual files are fetched on every install. So offline you can search, and you can see what an item is, but installing it fails at the file fetch. Do not promise a user an offline install.\n\nEach item's `registry-item.json` contains: name, type, title, description, tags, dimensions (blocks only), duration (blocks only), and file list.\n\nSee [discovery.md](.\u002Freferences\u002Fdiscovery.md) for details on filtering by type and tags.\n\n## Contributing a new block or component\n\nTo author a NEW registry item (caption style, VFX block, transition, lower third, or a reusable component) and ship it as an upstream PR — not install an existing one — follow the full idea → scaffold → build → validate → preview → ship workflow in [contributing.md](.\u002Freferences\u002Fcontributing.md). Copy-paste starter templates (caption \u002F VFX \u002F component \u002F `registry-item.json`) are in [templates.md](.\u002Freferences\u002Ftemplates.md).\n",{"name":5,"description":7},"mine","1e7390741dffd3d5041fca4ebc056071ee3ba137","skills\u002F07-media-content\u002Fhyperframes-registry",5,"https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub","https:\u002F\u002Fgithub.com\u002FEthanYoQ","www.orz.md","Part Marketer, Part AI Explorer.","2026-11-07 14:52:29",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add EthanYoQ\u002FSkill-hub --skill hyperframes-registry",{"tool":64,"command":65},"bunx","bunx skills add EthanYoQ\u002FSkill-hub --skill hyperframes-registry",{"tool":67,"command":68},"pnpm","pnpm dlx skills add EthanYoQ\u002FSkill-hub --skill hyperframes-registry","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F07-media-content\u002Fhyperframes-registry\u002FSKILL.md",true,[72,78,82,86,90,94,98,102,106,110,114],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"examples\u002Fadd-block.md","REFERENCE","参考文档",1232,"https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F07-media-content\u002Fhyperframes-registry\u002Fexamples\u002Fadd-block.md",{"path":79,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":80,"sourceHtmlUrl":81},"examples\u002Fadd-component.md",1473,"https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F07-media-content\u002Fhyperframes-registry\u002Fexamples\u002Fadd-component.md",{"path":83,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fcomponent-quality-bar.md",16390,"https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F07-media-content\u002Fhyperframes-registry\u002Freferences\u002Fcomponent-quality-bar.md",{"path":87,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fcontributing.md",6402,"https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F07-media-content\u002Fhyperframes-registry\u002Freferences\u002Fcontributing.md",{"path":91,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fdemo-html-pattern.md",1884,"https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F07-media-content\u002Fhyperframes-registry\u002Freferences\u002Fdemo-html-pattern.md",{"path":95,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fdiscovery.md",18225,"https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F07-media-content\u002Fhyperframes-registry\u002Freferences\u002Fdiscovery.md",{"path":99,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Finstall-locations.md",1519,"https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F07-media-content\u002Fhyperframes-registry\u002Freferences\u002Finstall-locations.md",{"path":103,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fplaceholder-material.md",9006,"https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F07-media-content\u002Fhyperframes-registry\u002Freferences\u002Fplaceholder-material.md",{"path":107,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Ftemplates.md",11451,"https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F07-media-content\u002Fhyperframes-registry\u002Freferences\u002Ftemplates.md",{"path":111,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":112,"sourceHtmlUrl":113},"references\u002Fwiring-blocks.md",2641,"https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F07-media-content\u002Fhyperframes-registry\u002Freferences\u002Fwiring-blocks.md",{"path":115,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":116,"sourceHtmlUrl":117},"references\u002Fwiring-components.md",1723,"https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F07-media-content\u002Fhyperframes-registry\u002Freferences\u002Fwiring-components.md",[119,146,177,201,219,234],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":126,"publishedAt":44},"01M713CBDSYARG4PXFXK2R2NNN","xhs-pharma-social-listening","Run evidence-disciplined Xiaohongshu social listening for foreign pharma employee pain points. Use when the user asks to collect and analyze notes\u002Fcomments about pharma companies, aliases, roles, compliance, medical affairs, or AI topics, then produce a cited and scored sampled-insight report. Includes independent-evidence counting, MediaCrawler batch collection, and CAPTCHA\u002F461 fallback to Agent Reach\u002FOpenCLI.","https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F10-business-industry\u002Fxhs-pharma-social-listening\u002FSKILL.md",[125],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[127,128,129,130,131,132,40,133,134,135,136,137,138,139,140,141,142,143,144,145],"social","xhs pharma social listening","social listening","xhs","medical","counting","collection","batch","analyze","notes","run","opencli","fallback","captcha","agent reach","evidence","for","collect","produce",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":158,"publishedAt":44},"01M713C8Q76ZP0WXXBRAFKS6EE","healthcare-phi-compliance","Protected Health Information (PHI) and Personally Identifiable Information (PII) compliance patterns for healthcare applications. Covers data classification, access control, audit trails, encryption, and common leak vectors. Use when code touches PHI or PII in a healthcare system, or when auditing access control, audit trails, or leak vectors.","https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F10-business-industry\u002Fhealthcare-phi-compliance\u002FSKILL.md",[152,153],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":154,"categoryName":155,"taxonomyType":156,"taxonomyTypeDesc":157},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[159,160,161,162,163,164,165,166,40,167,168,169,170,171,172,173,143,174,175,176],"healthcare","phi","compliance","healthcare phi compliance","pii","compliance patterns","information","access","encryption","code","common","audit","data","patterns","Access Control","system","applications","Auditing Access Control",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":184,"publishedAt":44},"01M713C5R2GE43X45T2K75TB76","healthcare-eval-harness","Patient safety evaluation harness for healthcare application deployments. Automated test suites for CDSS accuracy, PHI exposure, clinical workflow integrity, and integration compliance. Blocks deployments on safety failures. Use when a healthcare deployment must be gated on patient-safety tests for CDSS accuracy, PHI exposure, and workflow integrity.","https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F10-business-industry\u002Fhealthcare-eval-harness\u002FSKILL.md",[183],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[159,185,186,187,188,189,190,40,191,192,193,194,160,143,195,196,197,198,199,200],"eval","harness","healthcare eval harness","eval harness","clinical","patient","workflow","Evaluation","Safety","integrity","deployment","accuracy","tests","deployments","use","super",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":208,"publishedAt":44},"01M713C2J17S91VYR7A8M696VR","healthcare-emr-patterns","EMR\u002FEHR development patterns for healthcare applications. Clinical safety, encounter workflows, prescription generation, clinical decision support integration, and accessibility-first UI for medical data entry. Use when building EMR or EHR features such as encounter workflows, prescription generation, or clinical data entry UI.","https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F10-business-industry\u002Fhealthcare-emr-patterns\u002FSKILL.md",[207],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[159,209,172,210,211,131,189,212,40,213,214,215,193,171,216,217,218,143,175,199],"EMR","healthcare emr patterns","decision","workflows","support","clinical decision support","features","ui","as","development",{"skillNo":220,"name":221,"nameZh":6,"description":222,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":223,"categories":224,"keywords":226,"publishedAt":44},"01M713BZERTXV0N8X6SW9DDVWZ","healthcare-cdss-patterns","Clinical Decision Support System (CDSS) development patterns. Drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), alert severity classification, and integration into EMR workflows. Use when building clinical decision support — drug interaction checks, dose validation, clinical scoring, or alert severity.","https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F10-business-industry\u002Fhealthcare-cdss-patterns\u002FSKILL.md",[225],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[159,172,227,211,189,209,212,40,228,229,213,214,230,218,174,231,199,232,200,233],"healthcare cdss patterns","scoring","interaction","severity","classification","alert","decision support",{"skillNo":235,"name":236,"nameZh":6,"description":237,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":238,"categories":239,"keywords":241,"publishedAt":44},"01M713BVK3PQR7V4ZKYGMWMXJD","dxy-task-clarify","用户的请求含糊、缺背景、缺资料说明、缺读者或用途时使用。先用少量带选项的追问把任务问清楚，写成任务卡，用户确认后再执行。尤其适用于医生、科研人员和药企各岗位的工作，例如「帮我分析一下这些数据」「帮我准备明天的拜访」「写个总结」「做个 PPT」「回一下这封邮件」「整理一下会议纪要」「整理一下这些文献」「帮我准备下周的讲课」「写个病例汇报」「帮我写个提示词」。用户说「先问我」「帮我理清需求」「我不知道怎么描述」「我不会问 AI」时也使用。用途、资料、读者都已说清的请求，纯翻译，以及写代码、改代码，不使用。","https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Fskills\u002F10-business-industry\u002Fdxy-task-clarify\u002FSKILL.md",[240],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[242,243,244,245,246,247,248,249],"clarify","dxy task clarify","task","pptx","整理","翻译","数据","总结"]