[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71K91N7D73ET3R7JREQM07B":3,"skill-same:01M71K91N7D73ET3R7JREQM07B":115},{"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":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M71K91N7D73ET3R7JREQM07B","hyperframes-cli",null,"Use the HyperFrames CLI development loop: init, add, catalog, capture, lint, check, snapshot, compare, grade-compare, preview, play, present, beats, keyframes, single or batch render, publish, cloud, cloudrun, feedback, lambda, doctor, browser, info, upgrade, skills, compositions, docs, benchmark, telemetry, transcribe, auth, tts, and remove-background. Also use when diagnosing build or render failures. validate, inspect, and layout are deprecated aliases; use check. Covers local, HeyGen-hosted cloud, AWS Lambda, and Google Cloud Run rendering.","coco-research\u002Fcoco","coco-research","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F68911604?v=4","01M71JRE9C4NM4NSZM4JD0BJTB","Coco Research","01M71JREA0ZMR0PMH3CKA99SN1",631,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fhyperframes\u002Fskills\u002Fhyperframes-cli\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 cli","hyperframes","cli","lambda","info","browser","publish","batch","preview","when","loop","upgrade","init","local","render","inspect","remove","google cloud","auth","aws lambda","2026-11-10 10:12:30",false,"---\nname: hyperframes-cli\ndescription: >\n  Use the HyperFrames CLI development loop: init, add, catalog, capture, lint, check, snapshot,\n  compare, grade-compare, preview, play, present, beats, keyframes, single or batch render, publish,\n  cloud, cloudrun, feedback, lambda, doctor, browser, info, upgrade, skills, compositions, docs,\n  benchmark, telemetry, transcribe, auth, tts, and remove-background. Also use when diagnosing build\n  or render failures. validate, inspect, and layout are deprecated aliases; use check. Covers local,\n  HeyGen-hosted cloud, AWS Lambda, and Google Cloud Run rendering.\n---\n\n# HyperFrames CLI\n\nRun commands as `npx hyperframes ...` unless project instructions provide a wrapper. Obey the wrapper when present. The CLI requires Node.js 22 or newer and FFmpeg.\n\n## Development loop\n\n1. **Scaffold:** `npx hyperframes init \u003Cproject>` or capture a site. In non-TTY mode, pass `--non-interactive --example=\u003Cname>`.\n2. **Author:** write the composition using `\u002Fhyperframes-core`.\n3. **Get fast feedback while editing:** run `npx hyperframes lint` after the first HTML pass and after structural changes.\n4. **Run the final gate:** run `npx hyperframes check`; it reruns lint before opening the browser. Do not prepend a redundant standalone lint invocation. Add `--snapshots` for annotated overview frames and finding crops.\n5. **Inspect sub-compositions:** when `index.html` mounts `data-composition-src`, capture midpoint snapshots and inspect each mounted scene.\n6. **Open the final Studio preview:** run `npx hyperframes preview`, hand the timeline project URL to the user, and ask whether to revise or render.\n7. **Render only after approval:** use draft quality for iteration and high quality for delivery.\n8. **Verify the output:** confirm the file exists, is non-empty, and has a plausible duration.\n\n```bash\n# Fast iteration check; repeat while authoring as needed.\nnpx hyperframes lint\n\n# Required final gate; includes lint.\nnpx hyperframes check\nnpx hyperframes preview\nnpx hyperframes render --quality high --output out.mp4\ntest -s out.mp4\nffprobe -v error -show_format out.mp4\n```\n\n`check` runs lint first, then uses one browser session and one seek pass to audit runtime errors, failed requests, layout, `*.motion.json` assertions, and WCAG contrast. Persistent findings gate the exit code; transient entrance or exit findings are informational. Use `--strict` to gate warnings. `validate`, `inspect`, and `layout` remain aliases for compatibility but must not appear in new instructions or scripts.\n\n## Two different preview surfaces\n\nDo not confuse these states:\n\n| Surface                   | When it may open                                       | Purpose                                                                           |\n| ------------------------- | ------------------------------------------------------ | --------------------------------------------------------------------------------- |\n| Storyboard board          | Before composition checks, only when `storyboard: yes` | Review plan cards and wireframe sketches. Open `?view=storyboard#project\u002F\u003Cname>`. |\n| Final composition preview | After `check` passes                                   | Review the assembled timeline before render. Open `#project\u002F\u003Cname>`.              |\n\nThe early board is not approval of the final video. Rendering always requires the final approval defined by `hyperframes-core\u002Freferences\u002Freview-loop.md`.\n\n## Sub-composition smoke test\n\nStatic audits cannot catch every mount failure. When the project uses sub-compositions, capture at least one visible midpoint for each host slot:\n\n```bash\nnpx hyperframes snapshot --at \u003Ct1>,\u003Ct2>,\u003Ct3>\n```\n\nTreat tiny unstyled content, canvas-sized icons, missing hero elements, or timeline-registration timeouts as render-blocking mount defects. See `hyperframes-core\u002Freferences\u002Fsub-compositions.md` for the corresponding fixes.\n\n## Agent conventions\n\n- Prefer `--json` for agent and CI calls. Server-mode `render`, `preview`, and `play` do not provide ordinary JSON output; `preview --selection --json` and `preview --context --json` are query-mode exceptions.\n- `doctor --json` always exits zero. Gate on its payload:\n\n  ```bash\n  npx hyperframes doctor --json | jq -e '.ok' >\u002Fdev\u002Fnull\n  ```\n\n- Non-TTY mode is automatic. `init` requires `--example` there; use `--non-interactive` to force deterministic behavior on a TTY.\n- Use one `HYPERFRAMES_RUN_ID` for all commands in the same verification loop.\n- Use `--strict`, `--strict-all`, and `--strict-variables` when the corresponding warnings, variables, or CI conditions must gate the render.\n- JSON paths redact the home directory as `$HOME`; do not try to reverse the redaction.\n- When a hosted cloud project approaches or exceeds the 200 MB upload limit, use `cloud render --dry-run --json` and follow the `.hyperframesignore` investigation in `references\u002Fcloud.md`. Never ignore an asset merely because it is large.\n- Never render merely because checks pass. Pause at the final preview and wait for approval.\n\n## Studio-directed edits\n\nWhen the user refers to “this element” or the current selection, query Studio instead of guessing:\n\n```bash\nnpx hyperframes preview --context --json --context-fields selection\n```\n\nUse `selection.target.hfId` when available, otherwise its selector and source file. If the result reports `no-selection`, ask the user to click the element and rerun. Request only the context slices you need; use `--context-detail full` only for computed styles or editable text metadata. Full behavior and failure codes live in `references\u002Fpreview-render.md`.\n\n## Render choices\n\n| Need                                     | Command                                                                       |\n| ---------------------------------------- | ----------------------------------------------------------------------------- |\n| Fast local iteration                     | `npx hyperframes render --quality draft`                                      |\n| Final local delivery                     | `npx hyperframes render --quality high --output out.mp4`                      |\n| Reproducible container render            | `npx hyperframes render --docker --strict --output out.mp4`                   |\n| Local variable-driven batch render       | `npx hyperframes render --batch rows.json --output \"renders\u002F{name}.mp4\"`      |\n| HeyGen-hosted zero-infrastructure render | `npx hyperframes cloud render`                                                |\n| Self-managed distributed AWS render      | `npx hyperframes lambda render \u003Cproject> --width 1920 --height 1080 --wait`   |\n| Self-managed distributed GCP render      | `npx hyperframes cloudrun render \u003Cproject> --width 1920 --height 1080 --wait` |\n\nSkill attribution is automatic — the examples above need no `--skill`. A project scaffolded by a workflow (`hyperframes init --skill=\u003Cworkflow>`) records its owning skill in `hyperframes.json`, and every later render inherits it on anonymous telemetry: re-renders, `npm run render`, and `--batch` alike. Pass `--skill=\u003Cslug>` explicitly only to stamp a project that was not created through a workflow (its first render then persists it).\n\nUse cloud rendering when the user wants hosted rendering without local Chrome, FFmpeg, or AWS. Use Lambda only when AWS ownership is a requirement. Use Cloud Run only when GCP ownership is a requirement. Read the matching reference before running any cloud path.\n\nAfter verifying a successful render, send one feedback report unless telemetry is disabled or the user opted out:\n\n```bash\nnpx hyperframes feedback --rating \u003C0-10> --comment \"\u003Cspecific result or friction>\"\n```\n\nKeep clean-run feedback concise. For any bug or friction, capture a **reproduction packet** before submitting; do not send only a symptom summary. Include the rerunnable command (relative to the project directory — feedback is submitted to a public channel, so do **not** paste absolute paths, home-directory prefixes, or user\u002Fmachine identifiers), expected versus actual behavior, exact error (also strip absolute paths from stack traces — keep basename + line, drop the leading directory), whether output completed\u002Ffell back\u002Ffailed, workaround, and repro-project status. For a rating ≤ 7 that describes a visual defect (black frame, flicker, corrupt output, wrong frame, blank output, other visual anomaly), also include a `COMPOSITION_STRUCTURE:` block — a privacy-preserving structural anatomy (element census + attribute presence + timeline shape) so maintainers can pattern-match against known bug families without the composition ZIP. Agents auto-fill this via the composition-census helper; the human user does not fill it by hand. If the issue did not reproduce again, say so and still include the last failing command and logs. Use `--file-issue` only with consent: it publishes a minimal reproduction to a public URL. The required packet format and privacy warning live in `references\u002Fpreview-render.md`.\n\n## Read the matching reference before running a command\n\nThe following references and owning skills are mandatory command contracts, not optional background reading. Before running a command in the table, read its matching row.\n\n| Need                                                                                   | Reference                             |\n| -------------------------------------------------------------------------------------- | ------------------------------------- |\n| `init`, `capture`, `skills`                                                            | `references\u002Finit-and-scaffold.md`     |\n| `lint`, `check`, motion sidecars, `snapshot`                                           | `references\u002Flint-validate-inspect.md` |\n| `compare`, `grade-compare`, variable-driven `render --batch`                           | `references\u002Fcompare-and-batch.md`     |\n| `beats` for an existing project's Studio beat grid                                     | `references\u002Fbeats.md`                 |\n| `preview`, `play`, `render`, `publish`, Studio context, feedback                       | `references\u002Fpreview-render.md`        |\n| `doctor`, browser management                                                           | `references\u002Fdoctor-browser.md`        |\n| `auth`, HeyGen-hosted cloud rendering, and template variables                          | `references\u002Fcloud.md`                 |\n| AWS Lambda deployment and rendering                                                    | `references\u002Flambda.md`                |\n| Google Cloud Run deployment and rendering                                              | `references\u002Fcloudrun.md`              |\n| `info`, `upgrade`, `compositions`, `docs`, `benchmark`, telemetry, media preprocessing | `references\u002Fupgrade-info-misc.md`     |\n\nFor composition variables, also read `\u002Fhyperframes-core` → `references\u002Fvariables-and-media.md`. For `hyperframes add` and `hyperframes catalog`, use `\u002Fhyperframes-registry`. Before `hyperframes present`, read `\u002Fslideshow`; before `hyperframes keyframes`, read `\u002Fhyperframes-keyframes`. For TTS, transcription, captions, or background removal choices, use `\u002Fmedia-use`.\n\nThe specialized commands are deliberately documented by their owning workflows:\n\n```bash\nnpx hyperframes present \u003Cproject-dir> --port 3004 --no-open\nnpx hyperframes beats \u003Cproject-dir> --json\nnpx hyperframes keyframes \u003Cproject-dir> --json\n```\n\n`present` serves a navigable deck with presenter and audience synchronization. `beats` is the standalone Studio beat-grid utility defined in `references\u002Fbeats.md`. `keyframes` surfaces seek-safe animation and motion-path diagnostics.\n","# HyperFrames CLI\n\nRun commands as `npx hyperframes ...` unless project instructions provide a wrapper. Obey the wrapper when present. The CLI requires Node.js 22 or newer and FFmpeg.\n\n## Development loop\n\n1. **Scaffold:** `npx hyperframes init \u003Cproject>` or capture a site. In non-TTY mode, pass `--non-interactive --example=\u003Cname>`.\n2. **Author:** write the composition using `\u002Fhyperframes-core`.\n3. **Get fast feedback while editing:** run `npx hyperframes lint` after the first HTML pass and after structural changes.\n4. **Run the final gate:** run `npx hyperframes check`; it reruns lint before opening the browser. Do not prepend a redundant standalone lint invocation. Add `--snapshots` for annotated overview frames and finding crops.\n5. **Inspect sub-compositions:** when `index.html` mounts `data-composition-src`, capture midpoint snapshots and inspect each mounted scene.\n6. **Open the final Studio preview:** run `npx hyperframes preview`, hand the timeline project URL to the user, and ask whether to revise or render.\n7. **Render only after approval:** use draft quality for iteration and high quality for delivery.\n8. **Verify the output:** confirm the file exists, is non-empty, and has a plausible duration.\n\n```bash\n# Fast iteration check; repeat while authoring as needed.\nnpx hyperframes lint\n\n# Required final gate; includes lint.\nnpx hyperframes check\nnpx hyperframes preview\nnpx hyperframes render --quality high --output out.mp4\ntest -s out.mp4\nffprobe -v error -show_format out.mp4\n```\n\n`check` runs lint first, then uses one browser session and one seek pass to audit runtime errors, failed requests, layout, `*.motion.json` assertions, and WCAG contrast. Persistent findings gate the exit code; transient entrance or exit findings are informational. Use `--strict` to gate warnings. `validate`, `inspect`, and `layout` remain aliases for compatibility but must not appear in new instructions or scripts.\n\n## Two different preview surfaces\n\nDo not confuse these states:\n\n| Surface                   | When it may open                                       | Purpose                                                                           |\n| ------------------------- | ------------------------------------------------------ | --------------------------------------------------------------------------------- |\n| Storyboard board          | Before composition checks, only when `storyboard: yes` | Review plan cards and wireframe sketches. Open `?view=storyboard#project\u002F\u003Cname>`. |\n| Final composition preview | After `check` passes                                   | Review the assembled timeline before render. Open `#project\u002F\u003Cname>`.              |\n\nThe early board is not approval of the final video. Rendering always requires the final approval defined by `hyperframes-core\u002Freferences\u002Freview-loop.md`.\n\n## Sub-composition smoke test\n\nStatic audits cannot catch every mount failure. When the project uses sub-compositions, capture at least one visible midpoint for each host slot:\n\n```bash\nnpx hyperframes snapshot --at \u003Ct1>,\u003Ct2>,\u003Ct3>\n```\n\nTreat tiny unstyled content, canvas-sized icons, missing hero elements, or timeline-registration timeouts as render-blocking mount defects. See `hyperframes-core\u002Freferences\u002Fsub-compositions.md` for the corresponding fixes.\n\n## Agent conventions\n\n- Prefer `--json` for agent and CI calls. Server-mode `render`, `preview`, and `play` do not provide ordinary JSON output; `preview --selection --json` and `preview --context --json` are query-mode exceptions.\n- `doctor --json` always exits zero. Gate on its payload:\n\n  ```bash\n  npx hyperframes doctor --json | jq -e '.ok' >\u002Fdev\u002Fnull\n  ```\n\n- Non-TTY mode is automatic. `init` requires `--example` there; use `--non-interactive` to force deterministic behavior on a TTY.\n- Use one `HYPERFRAMES_RUN_ID` for all commands in the same verification loop.\n- Use `--strict`, `--strict-all`, and `--strict-variables` when the corresponding warnings, variables, or CI conditions must gate the render.\n- JSON paths redact the home directory as `$HOME`; do not try to reverse the redaction.\n- When a hosted cloud project approaches or exceeds the 200 MB upload limit, use `cloud render --dry-run --json` and follow the `.hyperframesignore` investigation in `references\u002Fcloud.md`. Never ignore an asset merely because it is large.\n- Never render merely because checks pass. Pause at the final preview and wait for approval.\n\n## Studio-directed edits\n\nWhen the user refers to “this element” or the current selection, query Studio instead of guessing:\n\n```bash\nnpx hyperframes preview --context --json --context-fields selection\n```\n\nUse `selection.target.hfId` when available, otherwise its selector and source file. If the result reports `no-selection`, ask the user to click the element and rerun. Request only the context slices you need; use `--context-detail full` only for computed styles or editable text metadata. Full behavior and failure codes live in `references\u002Fpreview-render.md`.\n\n## Render choices\n\n| Need                                     | Command                                                                       |\n| ---------------------------------------- | ----------------------------------------------------------------------------- |\n| Fast local iteration                     | `npx hyperframes render --quality draft`                                      |\n| Final local delivery                     | `npx hyperframes render --quality high --output out.mp4`                      |\n| Reproducible container render            | `npx hyperframes render --docker --strict --output out.mp4`                   |\n| Local variable-driven batch render       | `npx hyperframes render --batch rows.json --output \"renders\u002F{name}.mp4\"`      |\n| HeyGen-hosted zero-infrastructure render | `npx hyperframes cloud render`                                                |\n| Self-managed distributed AWS render      | `npx hyperframes lambda render \u003Cproject> --width 1920 --height 1080 --wait`   |\n| Self-managed distributed GCP render      | `npx hyperframes cloudrun render \u003Cproject> --width 1920 --height 1080 --wait` |\n\nSkill attribution is automatic — the examples above need no `--skill`. A project scaffolded by a workflow (`hyperframes init --skill=\u003Cworkflow>`) records its owning skill in `hyperframes.json`, and every later render inherits it on anonymous telemetry: re-renders, `npm run render`, and `--batch` alike. Pass `--skill=\u003Cslug>` explicitly only to stamp a project that was not created through a workflow (its first render then persists it).\n\nUse cloud rendering when the user wants hosted rendering without local Chrome, FFmpeg, or AWS. Use Lambda only when AWS ownership is a requirement. Use Cloud Run only when GCP ownership is a requirement. Read the matching reference before running any cloud path.\n\nAfter verifying a successful render, send one feedback report unless telemetry is disabled or the user opted out:\n\n```bash\nnpx hyperframes feedback --rating \u003C0-10> --comment \"\u003Cspecific result or friction>\"\n```\n\nKeep clean-run feedback concise. For any bug or friction, capture a **reproduction packet** before submitting; do not send only a symptom summary. Include the rerunnable command (relative to the project directory — feedback is submitted to a public channel, so do **not** paste absolute paths, home-directory prefixes, or user\u002Fmachine identifiers), expected versus actual behavior, exact error (also strip absolute paths from stack traces — keep basename + line, drop the leading directory), whether output completed\u002Ffell back\u002Ffailed, workaround, and repro-project status. For a rating ≤ 7 that describes a visual defect (black frame, flicker, corrupt output, wrong frame, blank output, other visual anomaly), also include a `COMPOSITION_STRUCTURE:` block — a privacy-preserving structural anatomy (element census + attribute presence + timeline shape) so maintainers can pattern-match against known bug families without the composition ZIP. Agents auto-fill this via the composition-census helper; the human user does not fill it by hand. If the issue did not reproduce again, say so and still include the last failing command and logs. Use `--file-issue` only with consent: it publishes a minimal reproduction to a public URL. The required packet format and privacy warning live in `references\u002Fpreview-render.md`.\n\n## Read the matching reference before running a command\n\nThe following references and owning skills are mandatory command contracts, not optional background reading. Before running a command in the table, read its matching row.\n\n| Need                                                                                   | Reference                             |\n| -------------------------------------------------------------------------------------- | ------------------------------------- |\n| `init`, `capture`, `skills`                                                            | `references\u002Finit-and-scaffold.md`     |\n| `lint`, `check`, motion sidecars, `snapshot`                                           | `references\u002Flint-validate-inspect.md` |\n| `compare`, `grade-compare`, variable-driven `render --batch`                           | `references\u002Fcompare-and-batch.md`     |\n| `beats` for an existing project's Studio beat grid                                     | `references\u002Fbeats.md`                 |\n| `preview`, `play`, `render`, `publish`, Studio context, feedback                       | `references\u002Fpreview-render.md`        |\n| `doctor`, browser management                                                           | `references\u002Fdoctor-browser.md`        |\n| `auth`, HeyGen-hosted cloud rendering, and template variables                          | `references\u002Fcloud.md`                 |\n| AWS Lambda deployment and rendering                                                    | `references\u002Flambda.md`                |\n| Google Cloud Run deployment and rendering                                              | `references\u002Fcloudrun.md`              |\n| `info`, `upgrade`, `compositions`, `docs`, `benchmark`, telemetry, media preprocessing | `references\u002Fupgrade-info-misc.md`     |\n\nFor composition variables, also read `\u002Fhyperframes-core` → `references\u002Fvariables-and-media.md`. For `hyperframes add` and `hyperframes catalog`, use `\u002Fhyperframes-registry`. Before `hyperframes present`, read `\u002Fslideshow`; before `hyperframes keyframes`, read `\u002Fhyperframes-keyframes`. For TTS, transcription, captions, or background removal choices, use `\u002Fmedia-use`.\n\nThe specialized commands are deliberately documented by their owning workflows:\n\n```bash\nnpx hyperframes present \u003Cproject-dir> --port 3004 --no-open\nnpx hyperframes beats \u003Cproject-dir> --json\nnpx hyperframes keyframes \u003Cproject-dir> --json\n```\n\n`present` serves a navigable deck with presenter and audience synchronization. `beats` is the standalone Studio beat-grid utility defined in `references\u002Fbeats.md`. `keyframes` surfaces seek-safe animation and motion-path diagnostics.\n",{"name":5,"description":7},"main","cd89f013b617f7eea982a9bbc60e992974fda2aa","systems\u002Fhyperframes\u002Fskills\u002Fhyperframes-cli",15,"https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco","https:\u002F\u002Fcocoresearch.org\u002Fcoco\u002F","https:\u002F\u002Fgithub.com\u002Fcoco-research","https:\u002F\u002Fcocoresearch.org","Local-first, open-source tools for people who work with AI agents: governed memory, agents that check their own work, and data that stays on your machine.","2026-11-11 12:18:13",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add coco-research\u002Fcoco --skill hyperframes-cli",{"tool":65,"command":66},"bunx","bunx skills add coco-research\u002Fcoco --skill hyperframes-cli",{"tool":68,"command":69},"pnpm","pnpm dlx skills add coco-research\u002Fcoco --skill hyperframes-cli","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fhyperframes\u002Fskills\u002Fhyperframes-cli\u002FSKILL.md",true,[73,79,83,87,91,95,99,103,107,111],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fbeats.md","REFERENCE","参考文档",921,"https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fhyperframes\u002Fskills\u002Fhyperframes-cli\u002Freferences\u002Fbeats.md",{"path":80,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fcloud.md",11029,"https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fhyperframes\u002Fskills\u002Fhyperframes-cli\u002Freferences\u002Fcloud.md",{"path":84,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fcloudrun.md",3583,"https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fhyperframes\u002Fskills\u002Fhyperframes-cli\u002Freferences\u002Fcloudrun.md",{"path":88,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fcompare-and-batch.md",4378,"https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fhyperframes\u002Fskills\u002Fhyperframes-cli\u002Freferences\u002Fcompare-and-batch.md",{"path":92,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fdoctor-browser.md",2725,"https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fhyperframes\u002Fskills\u002Fhyperframes-cli\u002Freferences\u002Fdoctor-browser.md",{"path":96,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Finit-and-scaffold.md",5374,"https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fhyperframes\u002Fskills\u002Fhyperframes-cli\u002Freferences\u002Finit-and-scaffold.md",{"path":100,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Flambda.md",16703,"https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fhyperframes\u002Fskills\u002Fhyperframes-cli\u002Freferences\u002Flambda.md",{"path":104,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Flint-validate-inspect.md",12348,"https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fhyperframes\u002Fskills\u002Fhyperframes-cli\u002Freferences\u002Flint-validate-inspect.md",{"path":108,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Fpreview-render.md",25631,"https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fhyperframes\u002Fskills\u002Fhyperframes-cli\u002Freferences\u002Fpreview-render.md",{"path":112,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":113,"sourceHtmlUrl":114},"references\u002Fupgrade-info-misc.md",4212,"https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fhyperframes\u002Fskills\u002Fhyperframes-cli\u002Freferences\u002Fupgrade-info-misc.md",[116,140,150,168,203,222],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":123,"publishedAt":44},"01M71KEJXF9KMT0BWCMRSRFA4M","trading-super-intelligence","Trading Super Intelligence Team. Named real-world personas across 8 cells. Built local-first (LM Studio) and validator-gated. Illustrative composites; see DISCLAIMER.md.","https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fsuperintelligence\u002Ftrading\u002FSKILL.md",[122],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[124,125,126,127,128,129,37,130,131,132,133,134,135,136,137,138,139],"super","trading super intelligence","intelligence","trading","validator","personas","composites","studio","team","across","world","first","gated","2026","lm studio","local-first",{"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":147,"publishedAt":44},"01M71KEFWS3CMAP7DF1P0FWTDE","strategy-super-intelligence","Strategy Super Intelligence Team. Named real-world personas across 7 cells. Built local-first (LM Studio) and validator-gated. Illustrative composites; see DISCLAIMER.md.","https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fsuperintelligence\u002Fstrategy\u002FSKILL.md",[146],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[148,124,149,126,128,129,37,130,131,132,133,134,135,136,137,138,139],"strategy","strategy super intelligence",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":162,"publishedAt":44},"01M71KED56ZEPK2QE84QSQPMT0","risk-compliance-super-intelligence","Risk & Compliance (GRC) Super Intelligence Team. Named real-world personas across 7 cells. Built local-first (LM Studio) and validator-gated. Illustrative composites; see DISCLAIMER.md.","https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fsuperintelligence\u002Frisk-compliance\u002FSKILL.md",[156,157],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":158,"categoryName":159,"taxonomyType":160,"taxonomyTypeDesc":161},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[163,124,164,165,166,126,128,129,37,130,167,131,132,133,134,135,136,137,138,139],"risk","risk compliance super intelligence","compliance","risk compliance","grc",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":187,"publishedAt":44},"01M71KE9A2FWSC74VA96W1EZSN","product-design-super-intelligence","Your product + design brain trust and decision partner. Named personas across 8 cells spanning product strategy, discovery\u002Fresearch, growth\u002Fmetrics, design foundations\u002Fusability, design leadership\u002Fcraft, UX\u002Fcontent, design systems, and a…","https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fsuperintelligence\u002Fproduct-design\u002FSKILL.md",[174,177,180,181,184],{"categoryNo":175,"categoryName":176,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":178,"categoryName":179,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":182,"categoryName":183,"taxonomyType":160,"taxonomyTypeDesc":161},"01JBSEEDCAT000000000000031","产品经理",{"categoryNo":185,"categoryName":186,"taxonomyType":160,"taxonomyTypeDesc":161},"01JBSEEDCAT000000000000032","设计师",[188,189,126,190,124,191,192,193,194,195,196,132,133,197,198,137,199,200,201,202],"design","product","product design","product design super intelligence","foundations","product-design","decision","design systems","usability","leadership","ux","brain","craft","metrics","trust",{"skillNo":204,"name":205,"nameZh":6,"description":206,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":207,"categories":208,"keywords":211,"publishedAt":44},"01M71KE6H9FPSD9TECYFBPXZ8Y","legal-ip-super-intelligence","Your legal, IP, and regulatory brain trust. 31 named personas across 7 cells covering patent strategy, tech licensing, regulatory litigation, AI governance, open-source compliance, privacy law, and antitrust.","https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fsuperintelligence\u002Flegal-ip\u002FSKILL.md",[209,210],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":158,"categoryName":159,"taxonomyType":160,"taxonomyTypeDesc":161},[212,124,213,126,214,215,202,216,129,217,218,219,148,132,133,220,165,221,137,199],"ip","legal ip super intelligence","legal","sep","tech","litigation","ai governance","open","open-source","governance",{"skillNo":223,"name":224,"nameZh":6,"description":225,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":226,"categories":227,"keywords":229,"publishedAt":44},"01M71KE36QRY610V6YVB9JWRND","healthcare-life-sciences-super-intelligence","Your healthcare and life sciences brain trust. 25 named personas across 7 cells covering drug discovery, medtech, biotech strategy, health policy, genomics, clinical trials, and healthcare economics.","https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco\u002Fblob\u002Fmain\u002Fsystems\u002Fsuperintelligence\u002Fhealthcare-life-sciences\u002FSKILL.md",[228],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[230,124,231,232,126,215,202,233,234,129,235,236,148,132,133,237,238,239,240,137],"healthcare","healthcare life sciences super intelligence","life","economics","discovery","policy","clinical","clinical trials","health","trials","genomics"]