[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78ZBA6RHZ8V83QMXSYYYSAK":3,"skill-same:01M78ZBA6RHZ8V83QMXSYYYSAK":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M78ZBA6RHZ8V83QMXSYYYSAK","akari",null,"Create, open, or resume AKARI Video projects. Use when asked to make a video in a folder without `.akari\u002F`, or to check an AKARI project's state.","AkariLabs\u002Fakari-video","AkariLabs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F309052672?v=4","01M78ZAVH5RSSCXA5RVB0RQYMW","01M78ZAVHS38JT84VMB4A3KFFB",214,"MIT","https:\u002F\u002Fgithub.com\u002FAkariLabs\u002Fakari-video\u002Fblob\u002Fmain\u002Fskills\u002Fakari\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: akari\ndescription: Create, open, or resume AKARI Video projects. Use when asked to make a video in a folder without `.akari\u002F`, or to check an AKARI project's state.\n---\n\n# Start or resume AKARI Video\n\n> **Language**: Respond in the user's language — conversation, questions, approval prompts, and the reports and records you write (including decision-log rows) follow the language the user writes in.\n\nFor project editing, read [plan-edit autonomy and gates](..\u002Fplan-edit\u002Fautonomy.md) before proceeding.\n\nThe library defaults to the workspace's `library\u002F`. Without a workspace, use the legacy `~\u002F.akari\u002Fassets\u002F`.\nCheck the first line of `akari-assets list` (or `akari assets list`) for the actual location.\nBelow, `\u003Cライブラリの置き場>` is the existing library-location placeholder; audio belongs in its `audio\u002F` subdirectory.\n\nThis entry point handles only the following 3 branches. Do not duplicate the main skills' procedures here.\nUse the `akari` CLI on PATH. If unavailable, use\n`node \"${AKARI_HOME:-$HOME\u002F.akari}\u002Fapp\u002Fpackages\u002Fakari-launcher\u002Fbin\u002Fakari.mjs\"`;\nif that is also unavailable, run `packages\u002Fakari-launcher\u002Fbin\u002Fakari.mjs` from an actual repository checkout with\n`node`. If none exists, explain what is missing and stop; do not invent paths.\n\n## Tool procedures for external tools (`akari recipe`)\n\nFor work using external tools or generative AI, if a matching recipe exists, run `akari recipe plan \u003Cid>`\nto check connector candidates and gates. Follow the gate procedure when a gate blocks execution.\nExecute with the existing verbs, then run `akari project sync` and record each output as a manifest\n`tool-output` with `recipe: \"\u003Cid>@\u003Cversion>\"`, `connector`, and `inputs_sha256`.\n\n## Recommend a playbook\n\nRecommend at most twice: when starting a project and immediately after the user places new source material.\nRead `.akari\u002Fintake.json` and available `analysis.json` records for target duration, format, speakers, and media kinds.\nRun `akari playbook list --json` (add `--channel \u003Cname>` for the current channel). Compare each entry's\n`category`, `tags` (especially `form`, `length`, and `materials`), and `requires` with that evidence.\nRank up to three matches and explain the concrete evidence for each in chat. For example, portrait source\nmaterial and a target of 60 seconds or less favor vertical explainers or short dramas; a talking head plus\nscreen capture favors an explainer; music-led footage favors an MV. A missing required tool lowers the rank\nand must be mentioned. Link to the playbook's review sheet path when one exists, or state that\n`.akari\u002Freports\u002Fplaybook-apply.html` will be generated by applying it. Never apply a recommendation\nautomatically. After the user chooses, run `akari playbook apply \u003Cid> --into \u003Cproject>`.\n\n## Resume\n\n1. Search for `.akari\u002F` from cwd up through its ancestors. Call the discovered project `\u003Cproject>`.\n   A `.akari\u002Froot.json` with `schema: \"creator-root\u002Fv1\"` marks a workspace, not a video project.\n   If only a workspace is found, proceed to Create or Open according to the request.\n2. Run `akari status \"$PWD\" --json`. Use `next_skill` \u002F `waiting_on` to explain\n   the next action in 1–2 sentences. Report failure or `state_health: inconclusive` as unavailable state;\n   do not infer the workflow stage from fragments of files.\n3. If `next_skill` is present, **read directly by path**:\n   `\u003Cproject>\u002F.claude\u002Fskills\u002F\u003Cnext_skill>\u002FSKILL.md`. If absent, report the missing file rather than inventing a procedure.\n   If `waiting_on` is present, explain that action without skipping the main skill's wait conditions.\n\n## Create\n\nUse when `.akari\u002F` is absent or a new project is explicitly requested. The legacy matcher\n`新規作成を明示された場合` denotes an explicit request for a new project.\n\nEven if no workspace exists, **do not create one without the user's consent** (propose → consent → create).\nThe machine-matched cue `利用者の同意なしに作成しない` means that creation requires the user's consent.\n\n1. Detect a workspace through these 2 routes (either is sufficient).\n   - Check whether `lastRoot` in `\u003CAKARI_HOME>\u002Fcreator-root.json`\n     (default: `~\u002F.akari\u002Fcreator-root.json`) exists.\n   - Search from cwd through its ancestors for `.akari\u002Froot.json`,\n     and verify that `schema` is `\"creator-root\u002Fv1\"`.\n   Read the discovered workspace's marker too. Report damaged JSON or unknown schemas without overwriting them.\n   Before asking where to create the project, infer the content language from the user's conversation and source\n   audio, independently of the UI language. If they appear to disagree, include a content-language choice in the\n   question in step 2 so the user can settle both the destination and language in one reply.\n2. Ask **only 1 question**: “Create this in the workspace `~\u002FAkari\u002F`, or in this folder?\n   If there is no workspace, I will create it with `akari init`.”\n   If an existing workspace was found, replace `~\u002FAkari\u002F` with its actual path.\n   Include the specific destination for the workspace option in the same question:\n   `\u003C作業場>\u002Fchannels\u002F\u003Cchannel>\u002Fvideos\u002F\u003C日付-スラッグ>\u002F` (the existing workspace\u002Fdate-slug placeholders).\n   Use the first entry in `root.json`'s `channels` as `\u003Cchannel>`, or `my-channel` if absent.\n   Suggest a short slug from the date and request; propose a different name if a project already has that name.\n   If this folder is selected, `\u003Ctarget>` is cwd.\n3. After consent, run `akari init` only if the workspace was selected and does not yet exist.\n   Its no-argument ensure operation is idempotent: if a workspace exists, stdout's first line returns its path.\n   If that differs from the approved location, do not create somewhere else on your own.\n4. Before creation, use the selected content language; an explicit choice takes precedence over the inference.\n   Run `akari new \"\u003Ctarget>\"`, adding the --lang option with the BCP 47 code if available.\n   Otherwise write the code to intake.json's language field after creation. Let the CLI add only missing files\n   without overwriting existing ones and enforce the F18 guard against git init inside an existing repository.\n   Main skills remain physical copies; `AKARI-SKILLS-VERSION` records their version at creation.\n   Resolve in order: explicit --lang → intake.json language → analysis.json transcript.language → ja.\n   Use the primary language subtag for pack selection (en-US → en); preserve ja and use en for a missing pack.\n5. Explain the creation report path printed to stdout and that `plan-edit` is next,\n   then **read directly by path**: `\u003Ctarget>\u002F.claude\u002Fskills\u002Fplan-edit\u002FSKILL.md`.\n   Skills created during a session may not appear in discovery. They will appear when the agent is started\n   in that project next time, so read them directly in this session.\n\nThe 1 question above also obtains consent. Do not ask again if the destination has already been explicitly approved.\nIf the CLI cannot run, manual workspace-only creation is limited to the approved location. Create\n`akari.md`, `channels\u002F\u003Cchannel>\u002Fvideos\u002F`, `library\u002F`, `inbox\u002F`,\n`.akari\u002Fmemory\u002F`, and `.akari\u002Fcache\u002F`.\nUse this stub for `akari.md`:\n\n```markdown\n# akari.md\n\nこの作業場（CreatorRoot）の規約・好みを書く場所です。\nAKARI Video のエージェントは動画を作る前に、まずこのファイルを読みます。\n\n## 好み\n\n（まだ何も書かれていません）\n```\n\nAlways follow these 2 rules for manual creation.\n\n1. **Never overwrite any existing file**. If `root.json` or `akari.md` exists, do not write it; return to detection.\n   The machine-matched cue `既存ファイルを一切上書きしない` states this same no-overwrite rule.\n2. **Write `root.json` last**. Place the workspace marker only after all directories and `akari.md` are complete.\n   The machine-matched cue `` `root.json` は最後に書く`` states the ordering rule.\n\nSet `.akari\u002Froot.json` to\n`{\"schema\":\"creator-root\u002Fv1\",\"createdAt\":\u003CISO8601>,\"channels\":[\u003Cchannel>]}`.\nDo not write `\u003CAKARI_HOME>\u002Fcreator-root.json` in the fallback.\nDo not claim project creation is complete without the CLI; report the missing `akari new`.\n\n## Open\n\nUse only the detection procedure from Create to find the workspace. List existing project directories under\n`\u003C作業場>\u002Fchannels\u002F*\u002Fvideos\u002F*` (the existing workspace placeholder) and let the user choose.\nIf none exists, explain that and point to Create.\nSet cwd to the selected project and proceed to Resume. Do not create a workspace during a read-only action.\n","# Start or resume AKARI Video\n\n> **Language**: Respond in the user's language — conversation, questions, approval prompts, and the reports and records you write (including decision-log rows) follow the language the user writes in.\n\nFor project editing, read [plan-edit autonomy and gates](..\u002Fplan-edit\u002Fautonomy.md) before proceeding.\n\nThe library defaults to the workspace's `library\u002F`. Without a workspace, use the legacy `~\u002F.akari\u002Fassets\u002F`.\nCheck the first line of `akari-assets list` (or `akari assets list`) for the actual location.\nBelow, `\u003Cライブラリの置き場>` is the existing library-location placeholder; audio belongs in its `audio\u002F` subdirectory.\n\nThis entry point handles only the following 3 branches. Do not duplicate the main skills' procedures here.\nUse the `akari` CLI on PATH. If unavailable, use\n`node \"${AKARI_HOME:-$HOME\u002F.akari}\u002Fapp\u002Fpackages\u002Fakari-launcher\u002Fbin\u002Fakari.mjs\"`;\nif that is also unavailable, run `packages\u002Fakari-launcher\u002Fbin\u002Fakari.mjs` from an actual repository checkout with\n`node`. If none exists, explain what is missing and stop; do not invent paths.\n\n## Tool procedures for external tools (`akari recipe`)\n\nFor work using external tools or generative AI, if a matching recipe exists, run `akari recipe plan \u003Cid>`\nto check connector candidates and gates. Follow the gate procedure when a gate blocks execution.\nExecute with the existing verbs, then run `akari project sync` and record each output as a manifest\n`tool-output` with `recipe: \"\u003Cid>@\u003Cversion>\"`, `connector`, and `inputs_sha256`.\n\n## Recommend a playbook\n\nRecommend at most twice: when starting a project and immediately after the user places new source material.\nRead `.akari\u002Fintake.json` and available `analysis.json` records for target duration, format, speakers, and media kinds.\nRun `akari playbook list --json` (add `--channel \u003Cname>` for the current channel). Compare each entry's\n`category`, `tags` (especially `form`, `length`, and `materials`), and `requires` with that evidence.\nRank up to three matches and explain the concrete evidence for each in chat. For example, portrait source\nmaterial and a target of 60 seconds or less favor vertical explainers or short dramas; a talking head plus\nscreen capture favors an explainer; music-led footage favors an MV. A missing required tool lowers the rank\nand must be mentioned. Link to the playbook's review sheet path when one exists, or state that\n`.akari\u002Freports\u002Fplaybook-apply.html` will be generated by applying it. Never apply a recommendation\nautomatically. After the user chooses, run `akari playbook apply \u003Cid> --into \u003Cproject>`.\n\n## Resume\n\n1. Search for `.akari\u002F` from cwd up through its ancestors. Call the discovered project `\u003Cproject>`.\n   A `.akari\u002Froot.json` with `schema: \"creator-root\u002Fv1\"` marks a workspace, not a video project.\n   If only a workspace is found, proceed to Create or Open according to the request.\n2. Run `akari status \"$PWD\" --json`. Use `next_skill` \u002F `waiting_on` to explain\n   the next action in 1–2 sentences. Report failure or `state_health: inconclusive` as unavailable state;\n   do not infer the workflow stage from fragments of files.\n3. If `next_skill` is present, **read directly by path**:\n   `\u003Cproject>\u002F.claude\u002Fskills\u002F\u003Cnext_skill>\u002FSKILL.md`. If absent, report the missing file rather than inventing a procedure.\n   If `waiting_on` is present, explain that action without skipping the main skill's wait conditions.\n\n## Create\n\nUse when `.akari\u002F` is absent or a new project is explicitly requested. The legacy matcher\n`新規作成を明示された場合` denotes an explicit request for a new project.\n\nEven if no workspace exists, **do not create one without the user's consent** (propose → consent → create).\nThe machine-matched cue `利用者の同意なしに作成しない` means that creation requires the user's consent.\n\n1. Detect a workspace through these 2 routes (either is sufficient).\n   - Check whether `lastRoot` in `\u003CAKARI_HOME>\u002Fcreator-root.json`\n     (default: `~\u002F.akari\u002Fcreator-root.json`) exists.\n   - Search from cwd through its ancestors for `.akari\u002Froot.json`,\n     and verify that `schema` is `\"creator-root\u002Fv1\"`.\n   Read the discovered workspace's marker too. Report damaged JSON or unknown schemas without overwriting them.\n   Before asking where to create the project, infer the content language from the user's conversation and source\n   audio, independently of the UI language. If they appear to disagree, include a content-language choice in the\n   question in step 2 so the user can settle both the destination and language in one reply.\n2. Ask **only 1 question**: “Create this in the workspace `~\u002FAkari\u002F`, or in this folder?\n   If there is no workspace, I will create it with `akari init`.”\n   If an existing workspace was found, replace `~\u002FAkari\u002F` with its actual path.\n   Include the specific destination for the workspace option in the same question:\n   `\u003C作業場>\u002Fchannels\u002F\u003Cchannel>\u002Fvideos\u002F\u003C日付-スラッグ>\u002F` (the existing workspace\u002Fdate-slug placeholders).\n   Use the first entry in `root.json`'s `channels` as `\u003Cchannel>`, or `my-channel` if absent.\n   Suggest a short slug from the date and request; propose a different name if a project already has that name.\n   If this folder is selected, `\u003Ctarget>` is cwd.\n3. After consent, run `akari init` only if the workspace was selected and does not yet exist.\n   Its no-argument ensure operation is idempotent: if a workspace exists, stdout's first line returns its path.\n   If that differs from the approved location, do not create somewhere else on your own.\n4. Before creation, use the selected content language; an explicit choice takes precedence over the inference.\n   Run `akari new \"\u003Ctarget>\"`, adding the --lang option with the BCP 47 code if available.\n   Otherwise write the code to intake.json's language field after creation. Let the CLI add only missing files\n   without overwriting existing ones and enforce the F18 guard against git init inside an existing repository.\n   Main skills remain physical copies; `AKARI-SKILLS-VERSION` records their version at creation.\n   Resolve in order: explicit --lang → intake.json language → analysis.json transcript.language → ja.\n   Use the primary language subtag for pack selection (en-US → en); preserve ja and use en for a missing pack.\n5. Explain the creation report path printed to stdout and that `plan-edit` is next,\n   then **read directly by path**: `\u003Ctarget>\u002F.claude\u002Fskills\u002Fplan-edit\u002FSKILL.md`.\n   Skills created during a session may not appear in discovery. They will appear when the agent is started\n   in that project next time, so read them directly in this session.\n\nThe 1 question above also obtains consent. Do not ask again if the destination has already been explicitly approved.\nIf the CLI cannot run, manual workspace-only creation is limited to the approved location. Create\n`akari.md`, `channels\u002F\u003Cchannel>\u002Fvideos\u002F`, `library\u002F`, `inbox\u002F`,\n`.akari\u002Fmemory\u002F`, and `.akari\u002Fcache\u002F`.\nUse this stub for `akari.md`:\n\n```markdown\n# akari.md\n\nこの作業場（CreatorRoot）の規約・好みを書く場所です。\nAKARI Video のエージェントは動画を作る前に、まずこのファイルを読みます。\n\n## 好み\n\n（まだ何も書かれていません）\n```\n\nAlways follow these 2 rules for manual creation.\n\n1. **Never overwrite any existing file**. If `root.json` or `akari.md` exists, do not write it; return to detection.\n   The machine-matched cue `既存ファイルを一切上書きしない` states this same no-overwrite rule.\n2. **Write `root.json` last**. Place the workspace marker only after all directories and `akari.md` are complete.\n   The machine-matched cue `` `root.json` は最後に書く`` states the ordering rule.\n\nSet `.akari\u002Froot.json` to\n`{\"schema\":\"creator-root\u002Fv1\",\"createdAt\":\u003CISO8601>,\"channels\":[\u003Cchannel>]}`.\nDo not write `\u003CAKARI_HOME>\u002Fcreator-root.json` in the fallback.\nDo not claim project creation is complete without the CLI; report the missing `akari new`.\n\n## Open\n\nUse only the detection procedure from Create to find the workspace. List existing project directories under\n`\u003C作業場>\u002Fchannels\u002F*\u002Fvideos\u002F*` (the existing workspace placeholder) and let the user choose.\nIf none exists, explain that and point to Create.\nSet cwd to the selected project and proceed to Resume. Do not create a workspace during a read-only action.\n",{"name":5,"description":7},"main","12b63130cc05dfc1efff973508a33f4fe3a27129","skills\u002Fakari",25,"https:\u002F\u002Fgithub.com\u002FAkariLabs\u002Fakari-video","https:\u002F\u002Fakari.video","https:\u002F\u002Fgithub.com\u002FAkariLabs","2026-10-22 01:34:40",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add AkariLabs\u002Fakari-video --skill akari",{"tool":37,"command":38},"bunx","bunx skills add AkariLabs\u002Fakari-video --skill akari",{"tool":40,"command":41},"pnpm","pnpm dlx skills add AkariLabs\u002Fakari-video --skill akari","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAkariLabs\u002Fakari-video\u002Fblob\u002Fmain\u002Fskills\u002Fakari\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"test\u002Fskills-command.test.mjs","SCRIPT","脚本",192,"https:\u002F\u002Fgithub.com\u002FAkariLabs\u002Fakari-video\u002Fblob\u002Fmain\u002Fskills\u002Fakari\u002Ftest\u002Fskills-command.test.mjs",[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M78ZECT6QNHG9XCEJAF779V4","verify-project","Verify an AKARI Video project with the L0 \u002F L1 \u002F L2 verification ladder required by an AKARI Video task contract on the current Theia stack. Read when acceptance criteria specify levels such as L0 or L0+L1, to determine exactly what to run and how at each level.（旧名: verify）","https:\u002F\u002Fgithub.com\u002FAkariLabs\u002Fakari-video\u002Fblob\u002Fmain\u002Fskills\u002Fverify-project\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M78ZE9H36DBKGW1DH7PRZ526","verify-edit","Verify edit.json and optional analysis.json \u002F captions.json \u002F media with a deterministic CLI, then finish QA with frame inspection and reporting after PASS. Use immediately after writing or modifying edit.json, before export, and after applying review feedback.（旧名: edit-lint）","https:\u002F\u002Fgithub.com\u002FAkariLabs\u002Fakari-video\u002Fblob\u002Fmain\u002Fskills\u002Fverify-edit\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M78ZE5CYGEAKZG6M5SEP2B20","setup-remote","Set up remote access to approval reports and previews from another device such as a phone, and send footage to the workspace. Use doctor to assess Tailscale, guide installation and login (human actions), expose the preview server (default 4567) and approval report helper over tailnet-only HTTPS with tailscale serve, connect Taildrop reception to workspace inbox\u002F, and verify access from another device. Use for requests to view reports on a phone, approve remotely, send footage from a phone, or set up remote access. Public internet exposure (funnel) is outside the default scope.","https:\u002F\u002Fgithub.com\u002FAkariLabs\u002Fakari-video\u002Fblob\u002Fmain\u002Fskills\u002Fsetup-remote\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M78ZE2HZR93E1ZJ5GPG2V0K5","setup-project","Set up an AKARI Video project headlessly. Recursively copy `templates\u002Fproject-default\u002F`, record the template version, initialize git only when safe, and generate an HTML creation report. No app launch is needed. Use to create a video project or fill in an existing folder as an AKARI Video project.（旧名: create-project）","https:\u002F\u002Fgithub.com\u002FAkariLabs\u002Fakari-video\u002Fblob\u002Fmain\u002Fskills\u002Fsetup-project\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M78ZDWRXJJF2B98WGQ35W53E","setup-library","Use for first-time AKARI Video setup or when the current project needs more usable assets. This first-run skill checks ffmpeg \u002F whisper-cli (and can install with approval), reads the bundled catalog with akari assets to propose a starter pack, obtains explicit human approval, then acquires, places, validates, and updates INDEX entries. It also covers the audio library (BGM and sound effects): bulk acquisition of first-party AKARI Sounds from GitHub Releases, a free-source candidate HTML list with drop-folder matching or assisted acquisition for missing families, and keep\u002Fdrop decisions in the listening gallery. Use for requests such as \"I want more BGM\" or \"add sound effects to the library\".（旧名: setup-audio-library）","https:\u002F\u002Fgithub.com\u002FAkariLabs\u002Fakari-video\u002Fblob\u002Fmain\u002Fskills\u002Fsetup-library\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M78ZDNSC34WR5NYJYNZ4HC28","setup-connections","Set up and inspect AKARI Video connections: AI-service keys, which models are allowed, cost-approval policy, the tool and media-service state, and 3D settings. Use for first-time setup, adding a provider or key later, checking what is usable (「何が使える？」 'what can I use?'), setting a key such as fal (「fal の鍵を設定したい」), 3D settings (「3D の設定を使いたい」), connection checks, and gates before paid generation or external publication. Model selection belongs to the production skills (they read the ledger and preferences); this skill decides allowed models and the cost policy. Works with `.akari\u002Fconnections.json` and a free, read-only doctor.（旧名: manage-connections）（旧名: connect）","https:\u002F\u002Fgithub.com\u002FAkariLabs\u002Fakari-video\u002Fblob\u002Fmain\u002Fskills\u002Fsetup-connections\u002FSKILL.md",[],[]]