[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B2QEXNPG6KEP7DPH3FEN2T":3,"skill-same:01M7B2QEXNPG6KEP7DPH3FEN2T":48},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7B2QEXNPG6KEP7DPH3FEN2T","nasiko-control-plane",null,"Manage the experimental Nasiko CLI lifecycle through ECC — read-only status checks, consent-gated install of the pinned qualified version with dry-run preview, and ownership-checked uninstall, under explicit telemetry and secrets boundaries. Use when the user asks to install, inspect, or remove the Nasiko CLI or check whether it is present.","lytong760-cell\u002Fcompiler_ko","lytong760-cell","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F289977458?v=4","01M7B1YD239K88PFQRD4PVC9DW","Nguyên Games","01M7B1YD2RM70TZ71QNQ0XTN4R",2,"MIT","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fnasiko-control-plane\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: nasiko-control-plane\ndescription: Manage the experimental Nasiko CLI lifecycle through ECC — read-only status checks, consent-gated install of the pinned qualified version with dry-run preview, and ownership-checked uninstall, under explicit telemetry and secrets boundaries. Use when the user asks to install, inspect, or remove the Nasiko CLI or check whether it is present.\n---\n\n# Nasiko CLI Lifecycle Bridge\n\nUse this skill when a user explicitly asks ECC to install, inspect, or remove\nthe qualified Nasiko CLI. This skill does not operate a Nasiko control plane.\n\n## Safety contract\n\n- Begin with `ecc nasiko status --json`. Status is read-only.\n- Installation always requires explicit user consent and `--yes`.\n- Install only an ECC-qualified pinned version, currently `v0.1.0`.\n- Preview first with `ecc nasiko install --version v0.1.0 --dry-run --json`.\n- Install with `ecc nasiko install --version v0.1.0 --yes --json` only after the\n  user reviews the version, registry origin, digest, and destination.\n- Remove only a still-qualified ECC-managed binary with\n  `ecc nasiko uninstall --version v0.1.0 --yes --json`. Preview removal with\n  `--dry-run` first.\n- The qualified source is `https:\u002F\u002Fgithub.com\u002FNasiko-Labs\u002Fnasiko`, licensed\n  under Apache-2.0; artifact and extracted-binary SHA-256 values are pinned.\n- Never replace the qualified command with a downloaded shell or PowerShell\n  bootstrap script.\n- Never put secrets or credentials in command arguments, logs, skill output,\n  install metadata, or ECC state.\n- Nasiko telemetry and any sharing with Nasiko or Ito must be opt-in and\n  separately disclosed. Installation is not telemetry consent.\n\n## Lifecycle boundary\n\nThe initial ECC bridge supports qualified installation, read-only status, and\nownership-checked uninstall. Use the canonical Nasiko CLI directly for connection, authentication,\nlaunch, deployment, or shutdown until those verbs have their own verified ECC\ncontracts. Do not guess CLI verbs.\n\nInstalling the CLI does not prove that a control-plane server is running, an\nagent is governed, routing or ACLs work, observability is complete, telemetry\nwas enabled, or Ito compute is connected. Report each state separately.\n\n## Failure behavior\n\n- If the platform, architecture, version, manifest, digest, archive, binary, or\n  destination fails validation, stop without executing the artifact.\n- Do not fall back to `latest`.\n- Do not search arbitrary `PATH` entries. Use ECC's qualified location or an\n  explicit absolute `ECC_NASIKO_CLI_EXECUTABLE` for development verification.\n- Do not treat a partial or ambiguous installation as success.\n","# Nasiko CLI Lifecycle Bridge\n\nUse this skill when a user explicitly asks ECC to install, inspect, or remove\nthe qualified Nasiko CLI. This skill does not operate a Nasiko control plane.\n\n## Safety contract\n\n- Begin with `ecc nasiko status --json`. Status is read-only.\n- Installation always requires explicit user consent and `--yes`.\n- Install only an ECC-qualified pinned version, currently `v0.1.0`.\n- Preview first with `ecc nasiko install --version v0.1.0 --dry-run --json`.\n- Install with `ecc nasiko install --version v0.1.0 --yes --json` only after the\n  user reviews the version, registry origin, digest, and destination.\n- Remove only a still-qualified ECC-managed binary with\n  `ecc nasiko uninstall --version v0.1.0 --yes --json`. Preview removal with\n  `--dry-run` first.\n- The qualified source is `https:\u002F\u002Fgithub.com\u002FNasiko-Labs\u002Fnasiko`, licensed\n  under Apache-2.0; artifact and extracted-binary SHA-256 values are pinned.\n- Never replace the qualified command with a downloaded shell or PowerShell\n  bootstrap script.\n- Never put secrets or credentials in command arguments, logs, skill output,\n  install metadata, or ECC state.\n- Nasiko telemetry and any sharing with Nasiko or Ito must be opt-in and\n  separately disclosed. Installation is not telemetry consent.\n\n## Lifecycle boundary\n\nThe initial ECC bridge supports qualified installation, read-only status, and\nownership-checked uninstall. Use the canonical Nasiko CLI directly for connection, authentication,\nlaunch, deployment, or shutdown until those verbs have their own verified ECC\ncontracts. Do not guess CLI verbs.\n\nInstalling the CLI does not prove that a control-plane server is running, an\nagent is governed, routing or ACLs work, observability is complete, telemetry\nwas enabled, or Ito compute is connected. Report each state separately.\n\n## Failure behavior\n\n- If the platform, architecture, version, manifest, digest, archive, binary, or\n  destination fails validation, stop without executing the artifact.\n- Do not fall back to `latest`.\n- Do not search arbitrary `PATH` entries. Use ECC's qualified location or an\n  explicit absolute `ECC_NASIKO_CLI_EXECUTABLE` for development verification.\n- Do not treat a partial or ambiguous installation as success.\n",{"name":5,"description":7},"main","c32dc0b68600587f78aff3310f3bbd4212173ab3",".kilo\u002Fskills\u002Fnasiko-control-plane",1,"https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko","https:\u002F\u002Fko-lang.ai.studio","https:\u002F\u002Fgithub.com\u002Flytong760-cell","hanaminikata.com","hello ","2026-11-05 18:26:32",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add lytong760-cell\u002Fcompiler_ko --skill nasiko-control-plane",{"tool":40,"command":41},"bunx","bunx skills add lytong760-cell\u002Fcompiler_ko --skill nasiko-control-plane",{"tool":43,"command":44},"pnpm","pnpm dlx skills add lytong760-cell\u002Fcompiler_ko --skill nasiko-control-plane","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fnasiko-control-plane\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7B36K22Z7155PTGEGTSDNJ4","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fx-api\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7B36HCAE9ESGBVS6J0FR52F","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7B36DYH4ZFJ3GZHPAEMVQAY","workspace-surface-audit","Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows. Use when the user wants help setting up Claude Code or understanding what capabilities are actually available in their environment.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fworkspace-surface-audit\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7B36A1QXMEZT8VZMFVQNR5E","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwizard\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7B364EK3N88VQQJ6HFATJQE","windows-desktop-e2e","E2E testing for Windows native desktop apps (WPF, WinForms, Win32\u002FMFC, Qt) using pywinauto and Windows UI Automation. Use when writing E2E tests for a Windows native desktop app with pywinauto or UI Automation.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwindows-desktop-e2e\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7B360YF7GGNAF21KT4QB5PG","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[]]