[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718YM8CXNM2A86RXNWDAEK3":3,"skill-same:01M718YM8CXNM2A86RXNWDAEK3":58},{"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":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":40,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":43,"updatedAt":44,"install":45,"resources":57},"01M718YM8CXNM2A86RXNWDAEK3","effect-v3-to-v4",null,"Use this skill when migrating a codebase from Effect v3 to Effect v4, upgrading `effect` or any `@effect\u002F*` package across the v3\u002Fv4 boundary.","agustinusnathaniel\u002Fxtarter","agustinusnathaniel","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F17046154?v=4","01M718YGB8QW647KSBHW6FJE60","Agustinus Nathaniel","01M718YGBYNAB67B9CAY3AH3HH",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagustinusnathaniel\u002Fxtarter\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Feffect-v3-to-v4\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28],"effect","effect v3 to v4","v3","true","package","use","when","across","boundary","codebase","2026-11-10 10:12:30",false,"---\nname: effect-v3-to-v4\ndescription: Use this skill when migrating a codebase from Effect v3 to Effect v4, upgrading `effect` or any `@effect\u002F*` package across the v3\u002Fv4 boundary.\ndisable-model-invocation: true\n---\n\n# Effect v3 to v4 Migration\n\nDrive an Effect v3 → v4 migration from the generated migration reference that ships in the Effect repo. Every rename, removal, and signature change is answered by upstream data — do not guess replacements.\n\n## Workflow\n\nWork through these steps in order; each one is detailed in the section named.\n\n1. **Set up and validate the local checkouts** — two shallow clones; verify any pre-existing `.repos\u002Feffect` before trusting it. See **Setup: Local Checkouts**.\n2. **Read `MIGRATION.md`** and `ls .repos\u002Feffect\u002Fmigration\u002F` for the background and guide index. See **Reading Order**.\n3. **Migrate `package.json`** — remove consolidated packages, align every remaining Effect package on one v4 version. Do this before type-checking, or the first run drowns in unresolved-import noise from packages that no longer exist. See **Repo-Level Changes**.\n4. **Run the project's type-check** (e.g. `tsc --noEmit`) to get the initial error inventory.\n5. **Iterate until the type-check is clean.** For each error, resolve the API through the lookup discipline — search `migration\u002Fv3-to-v4.md` for the symbol, escalate per **Reading Order** — then fix the call site, delegating per-file fixes to sub-agents per **Delegating to Sub-Agents**. Never silence an error instead of resolving it; see **Hard Prohibitions**.\n6. **Finish** — type-check clean; run tests and report their outcome honestly (not a gate); write the final summary. See **Done Condition**.\n\n## Setup: Local Checkouts\n\nThe migration is driven from two shallow, single-branch clones of the canonical Effect repo:\n\n```sh\ngit clone --depth 1 --single-branch https:\u002F\u002Fgithub.com\u002FEffect-TS\u002Feffect .repos\u002Feffect\ngit clone --depth 1 --single-branch --branch v3 https:\u002F\u002Fgithub.com\u002FEffect-TS\u002Feffect .repos\u002Feffect-v3\n```\n\n- `.repos\u002Feffect` — v4 (`main`). Contains `MIGRATION.md`, the `migration\u002F` guides, and the v4 source.\n- `.repos\u002Feffect-v3` — v3 (`v3` branch). Escalation-only reference for old semantics.\n\nEach clone is independently re-runnable and separately deletable. Do not use `git worktree` to share one clone between branches.\n\n### Validate an existing checkout before trusting it\n\n`.\u002F.repos\u002Feffect` may already exist, cloned from the archived `Effect-TS\u002Feffect-smol` repo by older setup instructions. That checkout is dead: it is stale and does not contain `migration\u002Fv3-to-v4.md`. Verify before using:\n\n```sh\ngit -C .repos\u002Feffect remote get-url origin   # must be the canonical Effect-TS\u002Feffect repo\nnode -p \"require('.\u002F.repos\u002Feffect\u002Fpackages\u002Feffect\u002Fpackage.json').version\"   # must be 4.x\n```\n\nIf the origin points at `effect-smol`, or the version is not `4.x`, delete the directory and re-clone as above.\n\n## Reading Order\n\n1. **Front-load `MIGRATION.md` once** (`.repos\u002Feffect\u002FMIGRATION.md`).\n2. **`migration\u002Fv3-to-v4.md` — the first stop for every API.** The generated reference covers every removed or changed API. Search it (see below); never read it whole.\n3. **A per-topic guide** (`.repos\u002Feffect\u002Fmigration\u002F*.md`) when the mapping implies a rewrite rather than a rename — e.g. `Context.Tag` → `Context.Service` is a structural change, not a symbol swap. Reach these on demand from the `MIGRATION.md` index, not front-loaded.\n4. **v4 source** (`.repos\u002Feffect\u002Fpackages\u002F*\u002Fsrc\u002F`, including `unstable\u002F`) to confirm a replacement's real signature before writing code against it.\n5. **v3 source** (`.repos\u002Feffect-v3`) as escalation only — for when unsure about the old v3 semantics.\n\n## Never Read the Reference Doc Whole\n\n**This is the single most important rule in this skill.** `migration\u002Fv3-to-v4.md` is ~16,000 lines \u002F ~350k tokens. Reading it in one pass blows the context window and takes the migration with it.\n\nAlways search it and read only matched lines plus surrounding context. The file has four sections — **Import Map**, **No Counterpart Imports**, **Removed Modules**, and **API Reference** (one `` ### `\u003Cv3 module path>` `` heading per module). Entries are grep-able one-liners of the form `` - `Old.symbol` -> `New.symbol`: \u003Crationale> ``, and removals are explicit `` -> `none` `` entries with a stated alternative.\n\nConcrete recipes:\n\n```sh\n# Look up a specific v3 symbol\nrg -n 'AnthropicTokenizer\\.layer' .repos\u002Feffect\u002Fmigration\u002Fv3-to-v4.md\n\n# Read a whole module's section via its heading\nrg -n -A 40 '^### `@effect\u002Fplatform\u002FFileSystem`' .repos\u002Feffect\u002Fmigration\u002Fv3-to-v4.md\n\n# Resolve a v3 import path in the Import Map\nrg -n '^@effect\u002Fplatform\u002FFileSystem ' .repos\u002Feffect\u002Fmigration\u002Fv3-to-v4.md\n\n# List every module section for a package\nrg -n '^### `@effect\u002Fcluster\u002F' .repos\u002Feffect\u002Fmigration\u002Fv3-to-v4.md\n```\n\nLook up APIs as you encounter them, one search at a time. A miss in the Import Map is not a dead end — check the **Removed Modules** and **No Counterpart Imports** sections before concluding anything.\n\n## Repo-Level Changes\n\nFaithful per-API lookup alone still yields a broken `package.json`. Handle these once, up front:\n\n- **Package consolidation.** `@effect\u002Fplatform`, `@effect\u002Frpc`, `@effect\u002Fcluster`, and others merged into the core `effect` package — remove them from `package.json` and rewrite their imports per the Import Map. Packages that remain separate (`@effect\u002Fplatform-*`, `@effect\u002Fsql-*`, `@effect\u002Fai-*`, `@effect\u002Fopentelemetry`, `@effect\u002Fvitest`, …) stay as dependencies.\n- **Version alignment.** All Effect ecosystem packages share one version number in v4. Every remaining `effect` \u002F `@effect\u002F*` dependency must be on the same matching version.\n- **Unstable modules.** Some functionality only exists under `effect\u002Funstable\u002F*` import paths (e.g. `effect\u002Funstable\u002Fhttp`, `effect\u002Funstable\u002Frpc`). These are correct v4 imports — use them where the reference maps to them; they may receive breaking changes in minor releases.\n\n## Delegating to Sub-Agents\n\nPer-file migration work is context-hungry; do it in sub-agents so the main session's context survives the whole migration.\n\n- Spawn one sub-agent per file (or per module), giving it the specific v3 symbols to resolve in that file.\n- The sub-agent returns the edit and the mappings it used; the main session keeps the error inventory and the running summary.\n- Sub-agents inherit the same lookup discipline (**Reading Order**, the `rg` recipes) and **Hard Prohibitions**.\n- The reference doc is never read whole in a sub-agent either — a blown sub-agent context still costs the migration that file.\n\n## Hard Prohibitions\n\n- **Never reintroduce a v3-shaped compatibility layer.** Writing a `v3-compat.ts` that re-exports old names makes type errors vanish and permanently freezes the codebase between versions. Migrate call sites to the v4 API.\n- **No `any`, no `as` casts** to silence a post-migration type error. Such an error is usually evidence the replacement has a different shape; casting deletes that information. Go back to the reference or the v4 source.\n- **No invented APIs.** Every replacement must trace to the reference doc, a topic guide, or the v4 source.\n\n## Done Condition\n\n**The project type-checks against v4.** A v4 migration is fundamentally a type-level exercise; unresolved imports and changed signatures surface there and nowhere else. Run the project's type-check (e.g. `tsc --noEmit`) until clean.\n\nRunning the test suite is recommended, and its outcome must be reported honestly — but it is **not** a gate. A repo mid-migration often has tests that cannot run for unrelated reasons; do not weaken tests to make them pass.\n\nThe final summary must state: the type-check result, the test result (or why tests were not run), every constructed replacement, and any gaps that were reported rather than bridged.\n","# Effect v3 to v4 Migration\n\nDrive an Effect v3 → v4 migration from the generated migration reference that ships in the Effect repo. Every rename, removal, and signature change is answered by upstream data — do not guess replacements.\n\n## Workflow\n\nWork through these steps in order; each one is detailed in the section named.\n\n1. **Set up and validate the local checkouts** — two shallow clones; verify any pre-existing `.repos\u002Feffect` before trusting it. See **Setup: Local Checkouts**.\n2. **Read `MIGRATION.md`** and `ls .repos\u002Feffect\u002Fmigration\u002F` for the background and guide index. See **Reading Order**.\n3. **Migrate `package.json`** — remove consolidated packages, align every remaining Effect package on one v4 version. Do this before type-checking, or the first run drowns in unresolved-import noise from packages that no longer exist. See **Repo-Level Changes**.\n4. **Run the project's type-check** (e.g. `tsc --noEmit`) to get the initial error inventory.\n5. **Iterate until the type-check is clean.** For each error, resolve the API through the lookup discipline — search `migration\u002Fv3-to-v4.md` for the symbol, escalate per **Reading Order** — then fix the call site, delegating per-file fixes to sub-agents per **Delegating to Sub-Agents**. Never silence an error instead of resolving it; see **Hard Prohibitions**.\n6. **Finish** — type-check clean; run tests and report their outcome honestly (not a gate); write the final summary. See **Done Condition**.\n\n## Setup: Local Checkouts\n\nThe migration is driven from two shallow, single-branch clones of the canonical Effect repo:\n\n```sh\ngit clone --depth 1 --single-branch https:\u002F\u002Fgithub.com\u002FEffect-TS\u002Feffect .repos\u002Feffect\ngit clone --depth 1 --single-branch --branch v3 https:\u002F\u002Fgithub.com\u002FEffect-TS\u002Feffect .repos\u002Feffect-v3\n```\n\n- `.repos\u002Feffect` — v4 (`main`). Contains `MIGRATION.md`, the `migration\u002F` guides, and the v4 source.\n- `.repos\u002Feffect-v3` — v3 (`v3` branch). Escalation-only reference for old semantics.\n\nEach clone is independently re-runnable and separately deletable. Do not use `git worktree` to share one clone between branches.\n\n### Validate an existing checkout before trusting it\n\n`.\u002F.repos\u002Feffect` may already exist, cloned from the archived `Effect-TS\u002Feffect-smol` repo by older setup instructions. That checkout is dead: it is stale and does not contain `migration\u002Fv3-to-v4.md`. Verify before using:\n\n```sh\ngit -C .repos\u002Feffect remote get-url origin   # must be the canonical Effect-TS\u002Feffect repo\nnode -p \"require('.\u002F.repos\u002Feffect\u002Fpackages\u002Feffect\u002Fpackage.json').version\"   # must be 4.x\n```\n\nIf the origin points at `effect-smol`, or the version is not `4.x`, delete the directory and re-clone as above.\n\n## Reading Order\n\n1. **Front-load `MIGRATION.md` once** (`.repos\u002Feffect\u002FMIGRATION.md`).\n2. **`migration\u002Fv3-to-v4.md` — the first stop for every API.** The generated reference covers every removed or changed API. Search it (see below); never read it whole.\n3. **A per-topic guide** (`.repos\u002Feffect\u002Fmigration\u002F*.md`) when the mapping implies a rewrite rather than a rename — e.g. `Context.Tag` → `Context.Service` is a structural change, not a symbol swap. Reach these on demand from the `MIGRATION.md` index, not front-loaded.\n4. **v4 source** (`.repos\u002Feffect\u002Fpackages\u002F*\u002Fsrc\u002F`, including `unstable\u002F`) to confirm a replacement's real signature before writing code against it.\n5. **v3 source** (`.repos\u002Feffect-v3`) as escalation only — for when unsure about the old v3 semantics.\n\n## Never Read the Reference Doc Whole\n\n**This is the single most important rule in this skill.** `migration\u002Fv3-to-v4.md` is ~16,000 lines \u002F ~350k tokens. Reading it in one pass blows the context window and takes the migration with it.\n\nAlways search it and read only matched lines plus surrounding context. The file has four sections — **Import Map**, **No Counterpart Imports**, **Removed Modules**, and **API Reference** (one `` ### `\u003Cv3 module path>` `` heading per module). Entries are grep-able one-liners of the form `` - `Old.symbol` -> `New.symbol`: \u003Crationale> ``, and removals are explicit `` -> `none` `` entries with a stated alternative.\n\nConcrete recipes:\n\n```sh\n# Look up a specific v3 symbol\nrg -n 'AnthropicTokenizer\\.layer' .repos\u002Feffect\u002Fmigration\u002Fv3-to-v4.md\n\n# Read a whole module's section via its heading\nrg -n -A 40 '^### `@effect\u002Fplatform\u002FFileSystem`' .repos\u002Feffect\u002Fmigration\u002Fv3-to-v4.md\n\n# Resolve a v3 import path in the Import Map\nrg -n '^@effect\u002Fplatform\u002FFileSystem ' .repos\u002Feffect\u002Fmigration\u002Fv3-to-v4.md\n\n# List every module section for a package\nrg -n '^### `@effect\u002Fcluster\u002F' .repos\u002Feffect\u002Fmigration\u002Fv3-to-v4.md\n```\n\nLook up APIs as you encounter them, one search at a time. A miss in the Import Map is not a dead end — check the **Removed Modules** and **No Counterpart Imports** sections before concluding anything.\n\n## Repo-Level Changes\n\nFaithful per-API lookup alone still yields a broken `package.json`. Handle these once, up front:\n\n- **Package consolidation.** `@effect\u002Fplatform`, `@effect\u002Frpc`, `@effect\u002Fcluster`, and others merged into the core `effect` package — remove them from `package.json` and rewrite their imports per the Import Map. Packages that remain separate (`@effect\u002Fplatform-*`, `@effect\u002Fsql-*`, `@effect\u002Fai-*`, `@effect\u002Fopentelemetry`, `@effect\u002Fvitest`, …) stay as dependencies.\n- **Version alignment.** All Effect ecosystem packages share one version number in v4. Every remaining `effect` \u002F `@effect\u002F*` dependency must be on the same matching version.\n- **Unstable modules.** Some functionality only exists under `effect\u002Funstable\u002F*` import paths (e.g. `effect\u002Funstable\u002Fhttp`, `effect\u002Funstable\u002Frpc`). These are correct v4 imports — use them where the reference maps to them; they may receive breaking changes in minor releases.\n\n## Delegating to Sub-Agents\n\nPer-file migration work is context-hungry; do it in sub-agents so the main session's context survives the whole migration.\n\n- Spawn one sub-agent per file (or per module), giving it the specific v3 symbols to resolve in that file.\n- The sub-agent returns the edit and the mappings it used; the main session keeps the error inventory and the running summary.\n- Sub-agents inherit the same lookup discipline (**Reading Order**, the `rg` recipes) and **Hard Prohibitions**.\n- The reference doc is never read whole in a sub-agent either — a blown sub-agent context still costs the migration that file.\n\n## Hard Prohibitions\n\n- **Never reintroduce a v3-shaped compatibility layer.** Writing a `v3-compat.ts` that re-exports old names makes type errors vanish and permanently freezes the codebase between versions. Migrate call sites to the v4 API.\n- **No `any`, no `as` casts** to silence a post-migration type error. Such an error is usually evidence the replacement has a different shape; casting deletes that information. Go back to the reference or the v4 source.\n- **No invented APIs.** Every replacement must trace to the reference doc, a topic guide, or the v4 source.\n\n## Done Condition\n\n**The project type-checks against v4.** A v4 migration is fundamentally a type-level exercise; unresolved imports and changed signatures surface there and nowhere else. Run the project's type-check (e.g. `tsc --noEmit`) until clean.\n\nRunning the test suite is recommended, and its outcome must be reported honestly — but it is **not** a gate. A repo mid-migration often has tests that cannot run for unrelated reasons; do not weaken tests to make them pass.\n\nThe final summary must state: the type-check result, the test result (or why tests were not run), every constructed replacement, and any gaps that were reported rather than bridged.\n",{"name":5,"description":7,"disable-model-invocation":34},true,"main","54ceeb165943628361fbc1a0a920988b32b59331",".agents\u002Fskills\u002Feffect-v3-to-v4",1,"https:\u002F\u002Fgithub.com\u002Fagustinusnathaniel\u002Fxtarter","https:\u002F\u002Fxtarter.sznm.dev","https:\u002F\u002Fgithub.com\u002Fagustinusnathaniel","https:\u002F\u002Fagustinusnathaniel.com","1.01 ^365 = 37.7","2026-11-07 03:32:08",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":34},[47,50,53],{"tool":48,"command":49},"npx","npx skills add agustinusnathaniel\u002Fxtarter --skill effect-v3-to-v4",{"tool":51,"command":52},"bunx","bunx skills add agustinusnathaniel\u002Fxtarter --skill effect-v3-to-v4",{"tool":54,"command":55},"pnpm","pnpm dlx skills add agustinusnathaniel\u002Fxtarter --skill effect-v3-to-v4","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagustinusnathaniel\u002Fxtarter\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Feffect-v3-to-v4\u002FSKILL.md",[],[59,89,113,132,143,169],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":70,"publishedAt":29},"01M718Z7JPG0V4022NBCPHEW4W","xtarterize","Apply production-grade conformance configurations (linting, type checking, CI, editor settings, AI skills, release tooling) to JS\u002FTS projects. Scans package.json and config files to auto-detect framework, bundler, and styling, then resolves applicable tasks. Use when user mentions \"xtarterize\", \"conformance\", \"setup linting\", \"add CI\", \"configure project\", \"init xtarterize\", or any task name like \"lint\u002Fbiome\", \"ts\u002Fstrict\", or \"ci\u002Fworkflow\".","https:\u002F\u002Fgithub.com\u002Fagustinusnathaniel\u002Fxtarter\u002Fblob\u002Fmain\u002Fskills\u002Fxtarterize\u002FSKILL.md",[65],{"categoryNo":66,"categoryName":67,"taxonomyType":68,"taxonomyTypeDesc":69},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[61,71,72,73,74,75,76,77,78,25,79,80,81,82,83,84,85,86,87,88],"ai skills","projects","project","ci","init","auto-detect","files","auto","configure","workflow","tasks","biome","linting","release","config","conformance","styling","bundler",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":96,"publishedAt":29},"01M718Z4WSH10F33BMKJBSRTT0","create-xtarter-app","Scaffold new JS\u002FTS projects from curated starter templates pre-configured with Biome, TypeScript strict mode, Git hooks, GitHub Actions workflows, VS Code settings, and AI agent skills. Use when user wants to create a new project, scaffold an app from a template, or mentions \"create-xtarter-app\", \"npx create-xtarter-app\", \"scaffold\", \"starter template\", or a template name like \"next-tailwind\", \"vite-chakra\", \"vite-tailwind\", or \"next-chakra\".","https:\u002F\u002Fgithub.com\u002Fagustinusnathaniel\u002Fxtarter\u002Fblob\u002Fmain\u002Fskills\u002Fcreate-xtarter-app\u002FSKILL.md",[95],{"categoryNo":66,"categoryName":67,"taxonomyType":68,"taxonomyTypeDesc":69},[97,98,99,72,73,100,101,102,103,104,105,106,107,25,108,82,109,110,111,112],"app","create","create xtarter app","Tailwind","actions","mode","hooks","github actions","new","ai agent","workflows","code","chakra","next","template","typescript",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":120,"publishedAt":29},"01M718Z3EVKF68MH1C8SCT1103","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.","https:\u002F\u002Fgithub.com\u002Fagustinusnathaniel\u002Fxtarter\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrite-a-skill\u002FSKILL.md",[119],{"categoryNo":66,"categoryName":67,"taxonomyType":68,"taxonomyTypeDesc":69},[121,122,123,124,22,125,105,24,25,126,127,98,128,129,130,131],"write a skill","write","resources","new agent","progressive","progressive disclosure","with","structure","build","new skill","user",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":139,"publishedAt":29},"01M718Z1D79ZNSHRGNTVYC47Q4","template-skill","Replace with description of the skill and when Claude should use it.","https:\u002F\u002Fgithub.com\u002Fagustinusnathaniel\u002Fxtarter\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftemplate-skill\u002FSKILL.md",[138],{"categoryNo":66,"categoryName":67,"taxonomyType":68,"taxonomyTypeDesc":69},[111,140,127,141,22,24,25,142],"template skill","replace","it",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":147,"licenseFileUrl":148,"sourceHtmlUrl":149,"categories":150,"keywords":152,"publishedAt":29},"01M718YXSFZA8KG6NTTE77GNE9","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagustinusnathaniel\u002Fxtarter\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagustinusnathaniel\u002Fxtarter\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fskill-creator\u002FSKILL.md",[151],{"categoryNo":66,"categoryName":67,"taxonomyType":68,"taxonomyTypeDesc":69},[153,154,155,156,157,105,25,158,98,159,160,161,162,163,164,165,166,167,168,22],"skill creator","creator","performance","improve","run evals","analysis","optimize","variance analysis","run","edit","benchmark","existing skill","evals","for","accuracy","scratch",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":175,"publishedAt":29},"01M718YTZEGNHGEXNPEPS6BYQY","opensrc","Fetch dependency source code to give AI agents deeper implementation context. Use when the agent needs to understand how a library works internally, read source code for a package, fetch implementation details for a dependency, or explore how an npm\u002FPyPI\u002Fcrates.io package is built. Triggers include \"fetch source for\", \"read the source of\", \"how does X work internally\", \"get the implementation of\", \"opensrc path\", or any task requiring access to dependency source code beyond types and docs.","https:\u002F\u002Fgithub.com\u002Fagustinusnathaniel\u002Fxtarter\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fopensrc\u002FSKILL.md",[],[171,176,177,178,179,166,180,181,22,182,23,24,183,25,184,108,185,186,187,188],"fetch","types","get","deeper","explore","triggers","pypi","access","Bash","ai agents","task","io","work"]