[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AWB16YHTW19GCCEPQX0YW0":3,"skill-same:01M7AWB16YHTW19GCCEPQX0YW0":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"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":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7AWB16YHTW19GCCEPQX0YW0","atlas-package-cloner",null,"Use Atlas to initialize Nim projects, install or update Atlas-managed dependencies, configure dependency directories, inspect Atlas-generated nim.cfg paths, handle Atlas overrides, features, plugins, lockfiles, and local Nim environments. Use when setting up or repairing Nim dependency workflows that use Atlas instead of Nimble's global package path.","Vyrnexis\u002Fnim-agent-template","Vyrnexis","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F315210836?v=4","01M7AWARQX2P2CQ25GD7S71DHH","01M7AWARRJ3WF9DRPNJ6S1W9CG",5,"MIT","https:\u002F\u002Fgithub.com\u002FVyrnexis\u002Fnim-agent-template\u002Fblob\u002Fmain\u002Fskills\u002Fatlas-package-cloner\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: atlas-package-cloner\ndescription: Use Atlas to initialize Nim projects, install or update Atlas-managed dependencies, configure dependency directories, inspect Atlas-generated nim.cfg paths, handle Atlas overrides, features, plugins, lockfiles, and local Nim environments. Use when setting up or repairing Nim dependency workflows that use Atlas instead of Nimble's global package path.\n---\n\n# Atlas Package Cloner\n\n# Rules\n\n## Project State\n\n- Treat either root `atlas.config` or `\u003Cdeps>\u002Fatlas.config` as Atlas config. Atlas prefers root\n  `atlas.config` when present, but `atlas init` creates `deps\u002Fatlas.config` by default.\n- Use `atlas init` from the project root to initialize Atlas state.\n- Use `atlas init --deps=DIR` or `atlas --deps=DIR init` when the project intentionally uses a\n  dependency directory other than `deps\u002F`.\n- After initialization, inspect `\u003Cdeps>\u002Fatlas.config`; the default config records `deps`,\n  `nameOverrides`, `urlOverrides`, `pkgOverrides`, `plugins`, `resolver`, and `graph`.\n- Do not assume `atlas init` creates `nim.cfg`. Atlas has code paths that patch `nim.cfg` when\n  dependency operations need compiler paths.\n\n## Commands\n\n- Use `atlas use \u003Curl|pkgname>` to add a dependency.\n- Use `atlas install` when the Nimble file already contains requirements and Atlas should\n  materialize the dependency graph.\n- Use `atlas update [filter]` to refresh dependency refs. Prefer a filter when only one dependency\n  needs an update.\n- Use `atlas link \u003Cpath>` only for local project linking tasks; be prepared to inspect generated\n  link files and the linked project's dependency graph state.\n- Use `atlas pin [atlas.lock]` to pin current dependency checkouts.\n- Use `atlas rep [atlas.lock]` to replay a lockfile. `atlas replay` and `atlas reproduce` are aliases.\n- Use `atlas --noexec rep [atlas.lock]` when replay should avoid build actions that may run\n  arbitrary code.\n- Use `atlas env \u003Cnimversion>` for project-local Nim environments, for example `atlas env 1.6.12`\n  or `atlas env devel`.\n\n## Package Names, URLs, And Indexes\n\n- Package names are resolved through Atlas' package lookup table, populated from `packages.json`, plus configured `nameOverrides`.\n- URL inputs are parsed as URLs and can be rewritten with `urlOverrides`.\n- Forge aliases are valid package references:\n\n| Alias | Expands to |\n|-------|------------|\n| `gh:user\u002Frepo` or `github:user\u002Frepo` | `https:\u002F\u002Fgithub.com\u002Fuser\u002Frepo` |\n| `gl:user\u002Frepo` or `gitlab:user\u002Frepo` | `https:\u002F\u002Fgitlab.com\u002Fuser\u002Frepo` |\n| `srht:user\u002Frepo` or `sourcehut:user\u002Frepo` | `https:\u002F\u002Fgit.sr.ht\u002F~user\u002Frepo` |\n| `cb:user\u002Frepo`, `cberg:user\u002Frepo`, or `codeberg:user\u002Frepo` | `https:\u002F\u002Fcodeberg.org\u002Fuser\u002Frepo` |\n\n- Atlas downloads `packages.json` into the package cache by default, using `packages.nim-lang.org`\n  with GitHub fallback.\n- Use `--packagesRepo` only when the workflow needs the full `nim-lang\u002Fpackages` git repository behavior.\n- Use `--forceGitToHttps` when dependency URLs need `git:\u002F\u002F` rewritten to `https:\u002F\u002F`.\n- If a package name or URL resolves incorrectly, fix `nameOverrides`, `urlOverrides`, or\n  `pkgOverrides` in `\u003Cdeps>\u002Fatlas.config` instead of editing generated paths by hand.\n\n## Generated nim.cfg Paths\n\n- Atlas' `nim.cfg` patcher uses this section shape:\n\n```text\n############# begin Atlas config section ##########\n--noNimblePath\n--path:\"deps\u002Fpkg\"\n############# end Atlas config section   ##########\n```\n\n- Inspect the Atlas section in `nim.cfg` when imports fail.\n- Preserve user-written content outside the Atlas begin\u002Fend section.\n- Do not hand-edit generated `--path` entries as the first fix. Correct the dependency graph,\n  package metadata, or config overrides instead.\n\n## Resolution And Overrides\n\n- Atlas supports `MinVer`, `SemVer`, and `MaxVer` resolver algorithms.\n- The generated default config uses `SemVer`.\n- Set resolver policy in `\u003Cdeps>\u002Fatlas.config` or with `--resolver=minver|semver|maxver` when the\n  task requires a specific policy.\n- Use `nameOverrides` for package-name-to-URL mapping.\n- Use `urlOverrides` for URL rewrite rules.\n- Use `pkgOverrides` when multiple URLs conflict for the same package shortname.\n- Keep overrides in Atlas config so future `install`, `use`, `update`, and `rep` commands remain\n  repeatable.\n\n## Features\n\n- Atlas supports Nimble `feature` statements.\n- Pass feature flags explicitly with `--feature=\u003Cfeature>`. Pass multiple `--feature` options when\n  multiple features are required, or use `--features=\u003Clist>` for a comma- or space-separated list.\n- Use `--allFeatures` only when every declared feature should be enabled.\n- Use `--keepFeatures` or `-k` when the command should reuse feature defines from the current `nim.cfg`.\n- Feature request flags populate runtime context; they are not saved as fields in `atlas.config`.\n- In Nimble requirements, feature syntax has the shape `require \"somelib[testing]\"`.\n\n## Plugins And Build Actions\n\n- Atlas plugins are `*.nims` files read from the project-relative directory configured by the `plugins` field.\n- Treat plugin execution as potentially arbitrary code execution because plugins can call external tools.\n- Inspect the configured plugin directory before enabling plugins or replaying dependencies with execution enabled.\n- Use `--noexec` when the task only needs dependency graph setup or lockfile replay and build actions should not run.\n\n## Virtual Nim Environments\n\n- `atlas env \u003Cversion>` creates a project-local Nim environment under the dependency directory.\n- After a successful env setup, activate it explicitly:\n  - Unix: `source deps\u002Fnim-\u003Cversion>\u002Factivate.sh`\n  - Windows: `deps\\nim-\u003Cversion>\\activate.bat`\n- Do not assume the virtual Nim environment is active in later shell sessions.\n\n# Workflow\n\n1. Inspect the project root.\n   Look for `*.nimble`, `nim.cfg`, `atlas.lock`, `deps\u002F`, and any custom dependency directory.\n2. Locate Atlas config.\n   Check root `atlas.config` first, then `\u003Cdeps>\u002Fatlas.config`; if `--deps` or `--confdir` is in\n   use, inspect that configured location.\n3. Choose the Atlas command.\n   Use `init`, `use`, `install`, `update`, `link`, `pin`, `rep`, or `env` according to the task.\n   Run commands from the project root unless `--project=path` is intentional.\n4. Check policy before changing dependencies.\n   Read resolver, overrides, plugins, feature needs, lockfile state, and existing Nimble requirements.\n5. Run the smallest Atlas operation.\n   Use filters for targeted updates and `--noexec` when arbitrary build actions should not run.\n6. Verify generated state.\n   Inspect `\u003Cdeps>\u002Fatlas.config`, `project.nimble`, `nim.cfg`, and `atlas.lock` as applicable.\n   Compile or test the smallest Nim target that imports the affected package.\n7. Preserve reproducibility.\n   If the dependency set must remain stable, run `atlas pin` after successful setup and keep the\n   lockfile with the project when that is the repository policy.\n\n## Task Examples\n\n- For a new project that adds a dependency, read `references\u002Fstart_project.md`.\n- For custom dependency directories and overrides, read `references\u002Fcustom_deps_and_overrides.md`.\n- For feature flags, lockfiles, and replay, read `references\u002Ffeatures_and_replay.md`.\n\n# Common Mistakes\n\n| Mistake | Why it is wrong |\n|---------|-----------------|\n| Looking only for root `atlas.config` | Verified `atlas init` writes `deps\u002Fatlas.config` by default even though root config is preferred when present. |\n| Assuming `atlas init` creates `nim.cfg` | Verified `init` creates Atlas config only; dependency operations are what drive path patching. |\n| Editing generated `nim.cfg` paths first | Atlas can regenerate that section; fix config, package metadata, or dependency resolution instead. |\n| Enabling plugins without inspection | Plugins are NimScript files and may execute external commands. |\n\n## References\n\n- `references\u002Fstart_project.md` — Atlas adoption: project setup, dependency addition, and compile flow.\n- `references\u002Fcustom_deps_and_overrides.md` — Custom dependency directories and URL overrides.\n- `references\u002Ffeatures_and_replay.md` — Optional features and lockfile replay commands.\n","# Atlas Package Cloner\n\n# Rules\n\n## Project State\n\n- Treat either root `atlas.config` or `\u003Cdeps>\u002Fatlas.config` as Atlas config. Atlas prefers root\n  `atlas.config` when present, but `atlas init` creates `deps\u002Fatlas.config` by default.\n- Use `atlas init` from the project root to initialize Atlas state.\n- Use `atlas init --deps=DIR` or `atlas --deps=DIR init` when the project intentionally uses a\n  dependency directory other than `deps\u002F`.\n- After initialization, inspect `\u003Cdeps>\u002Fatlas.config`; the default config records `deps`,\n  `nameOverrides`, `urlOverrides`, `pkgOverrides`, `plugins`, `resolver`, and `graph`.\n- Do not assume `atlas init` creates `nim.cfg`. Atlas has code paths that patch `nim.cfg` when\n  dependency operations need compiler paths.\n\n## Commands\n\n- Use `atlas use \u003Curl|pkgname>` to add a dependency.\n- Use `atlas install` when the Nimble file already contains requirements and Atlas should\n  materialize the dependency graph.\n- Use `atlas update [filter]` to refresh dependency refs. Prefer a filter when only one dependency\n  needs an update.\n- Use `atlas link \u003Cpath>` only for local project linking tasks; be prepared to inspect generated\n  link files and the linked project's dependency graph state.\n- Use `atlas pin [atlas.lock]` to pin current dependency checkouts.\n- Use `atlas rep [atlas.lock]` to replay a lockfile. `atlas replay` and `atlas reproduce` are aliases.\n- Use `atlas --noexec rep [atlas.lock]` when replay should avoid build actions that may run\n  arbitrary code.\n- Use `atlas env \u003Cnimversion>` for project-local Nim environments, for example `atlas env 1.6.12`\n  or `atlas env devel`.\n\n## Package Names, URLs, And Indexes\n\n- Package names are resolved through Atlas' package lookup table, populated from `packages.json`, plus configured `nameOverrides`.\n- URL inputs are parsed as URLs and can be rewritten with `urlOverrides`.\n- Forge aliases are valid package references:\n\n| Alias | Expands to |\n|-------|------------|\n| `gh:user\u002Frepo` or `github:user\u002Frepo` | `https:\u002F\u002Fgithub.com\u002Fuser\u002Frepo` |\n| `gl:user\u002Frepo` or `gitlab:user\u002Frepo` | `https:\u002F\u002Fgitlab.com\u002Fuser\u002Frepo` |\n| `srht:user\u002Frepo` or `sourcehut:user\u002Frepo` | `https:\u002F\u002Fgit.sr.ht\u002F~user\u002Frepo` |\n| `cb:user\u002Frepo`, `cberg:user\u002Frepo`, or `codeberg:user\u002Frepo` | `https:\u002F\u002Fcodeberg.org\u002Fuser\u002Frepo` |\n\n- Atlas downloads `packages.json` into the package cache by default, using `packages.nim-lang.org`\n  with GitHub fallback.\n- Use `--packagesRepo` only when the workflow needs the full `nim-lang\u002Fpackages` git repository behavior.\n- Use `--forceGitToHttps` when dependency URLs need `git:\u002F\u002F` rewritten to `https:\u002F\u002F`.\n- If a package name or URL resolves incorrectly, fix `nameOverrides`, `urlOverrides`, or\n  `pkgOverrides` in `\u003Cdeps>\u002Fatlas.config` instead of editing generated paths by hand.\n\n## Generated nim.cfg Paths\n\n- Atlas' `nim.cfg` patcher uses this section shape:\n\n```text\n############# begin Atlas config section ##########\n--noNimblePath\n--path:\"deps\u002Fpkg\"\n############# end Atlas config section   ##########\n```\n\n- Inspect the Atlas section in `nim.cfg` when imports fail.\n- Preserve user-written content outside the Atlas begin\u002Fend section.\n- Do not hand-edit generated `--path` entries as the first fix. Correct the dependency graph,\n  package metadata, or config overrides instead.\n\n## Resolution And Overrides\n\n- Atlas supports `MinVer`, `SemVer`, and `MaxVer` resolver algorithms.\n- The generated default config uses `SemVer`.\n- Set resolver policy in `\u003Cdeps>\u002Fatlas.config` or with `--resolver=minver|semver|maxver` when the\n  task requires a specific policy.\n- Use `nameOverrides` for package-name-to-URL mapping.\n- Use `urlOverrides` for URL rewrite rules.\n- Use `pkgOverrides` when multiple URLs conflict for the same package shortname.\n- Keep overrides in Atlas config so future `install`, `use`, `update`, and `rep` commands remain\n  repeatable.\n\n## Features\n\n- Atlas supports Nimble `feature` statements.\n- Pass feature flags explicitly with `--feature=\u003Cfeature>`. Pass multiple `--feature` options when\n  multiple features are required, or use `--features=\u003Clist>` for a comma- or space-separated list.\n- Use `--allFeatures` only when every declared feature should be enabled.\n- Use `--keepFeatures` or `-k` when the command should reuse feature defines from the current `nim.cfg`.\n- Feature request flags populate runtime context; they are not saved as fields in `atlas.config`.\n- In Nimble requirements, feature syntax has the shape `require \"somelib[testing]\"`.\n\n## Plugins And Build Actions\n\n- Atlas plugins are `*.nims` files read from the project-relative directory configured by the `plugins` field.\n- Treat plugin execution as potentially arbitrary code execution because plugins can call external tools.\n- Inspect the configured plugin directory before enabling plugins or replaying dependencies with execution enabled.\n- Use `--noexec` when the task only needs dependency graph setup or lockfile replay and build actions should not run.\n\n## Virtual Nim Environments\n\n- `atlas env \u003Cversion>` creates a project-local Nim environment under the dependency directory.\n- After a successful env setup, activate it explicitly:\n  - Unix: `source deps\u002Fnim-\u003Cversion>\u002Factivate.sh`\n  - Windows: `deps\\nim-\u003Cversion>\\activate.bat`\n- Do not assume the virtual Nim environment is active in later shell sessions.\n\n# Workflow\n\n1. Inspect the project root.\n   Look for `*.nimble`, `nim.cfg`, `atlas.lock`, `deps\u002F`, and any custom dependency directory.\n2. Locate Atlas config.\n   Check root `atlas.config` first, then `\u003Cdeps>\u002Fatlas.config`; if `--deps` or `--confdir` is in\n   use, inspect that configured location.\n3. Choose the Atlas command.\n   Use `init`, `use`, `install`, `update`, `link`, `pin`, `rep`, or `env` according to the task.\n   Run commands from the project root unless `--project=path` is intentional.\n4. Check policy before changing dependencies.\n   Read resolver, overrides, plugins, feature needs, lockfile state, and existing Nimble requirements.\n5. Run the smallest Atlas operation.\n   Use filters for targeted updates and `--noexec` when arbitrary build actions should not run.\n6. Verify generated state.\n   Inspect `\u003Cdeps>\u002Fatlas.config`, `project.nimble`, `nim.cfg`, and `atlas.lock` as applicable.\n   Compile or test the smallest Nim target that imports the affected package.\n7. Preserve reproducibility.\n   If the dependency set must remain stable, run `atlas pin` after successful setup and keep the\n   lockfile with the project when that is the repository policy.\n\n## Task Examples\n\n- For a new project that adds a dependency, read `references\u002Fstart_project.md`.\n- For custom dependency directories and overrides, read `references\u002Fcustom_deps_and_overrides.md`.\n- For feature flags, lockfiles, and replay, read `references\u002Ffeatures_and_replay.md`.\n\n# Common Mistakes\n\n| Mistake | Why it is wrong |\n|---------|-----------------|\n| Looking only for root `atlas.config` | Verified `atlas init` writes `deps\u002Fatlas.config` by default even though root config is preferred when present. |\n| Assuming `atlas init` creates `nim.cfg` | Verified `init` creates Atlas config only; dependency operations are what drive path patching. |\n| Editing generated `nim.cfg` paths first | Atlas can regenerate that section; fix config, package metadata, or dependency resolution instead. |\n| Enabling plugins without inspection | Plugins are NimScript files and may execute external commands. |\n\n## References\n\n- `references\u002Fstart_project.md` — Atlas adoption: project setup, dependency addition, and compile flow.\n- `references\u002Fcustom_deps_and_overrides.md` — Custom dependency directories and URL overrides.\n- `references\u002Ffeatures_and_replay.md` — Optional features and lockfile replay commands.\n",{"name":5,"description":7},"main","060e1c453fdad0410a2b385f59275494911d9a4b","skills\u002Fatlas-package-cloner",2,"https:\u002F\u002Fgithub.com\u002FVyrnexis\u002Fnim-agent-template","https:\u002F\u002Fgithub.com\u002FVyrnexis","https:\u002F\u002Fvyrnexis.github.io","2026-10-27 00:06:43",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Vyrnexis\u002Fnim-agent-template --skill atlas-package-cloner",{"tool":37,"command":38},"bunx","bunx skills add Vyrnexis\u002Fnim-agent-template --skill atlas-package-cloner",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Vyrnexis\u002Fnim-agent-template --skill atlas-package-cloner","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FVyrnexis\u002Fnim-agent-template\u002Fblob\u002Fmain\u002Fskills\u002Fatlas-package-cloner\u002FSKILL.md",true,[45,51,55],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Fcustom_deps_and_overrides.md","REFERENCE","参考文档",1044,"https:\u002F\u002Fgithub.com\u002FVyrnexis\u002Fnim-agent-template\u002Fblob\u002Fmain\u002Fskills\u002Fatlas-package-cloner\u002Freferences\u002Fcustom_deps_and_overrides.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Ffeatures_and_replay.md",822,"https:\u002F\u002Fgithub.com\u002FVyrnexis\u002Fnim-agent-template\u002Fblob\u002Fmain\u002Fskills\u002Fatlas-package-cloner\u002Freferences\u002Ffeatures_and_replay.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fstart_project.md",625,"https:\u002F\u002Fgithub.com\u002FVyrnexis\u002Fnim-agent-template\u002Fblob\u002Fmain\u002Fskills\u002Fatlas-package-cloner\u002Freferences\u002Fstart_project.md",[60,67,74,81,88,95],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7AWEDMYZVEFGPQYGCVC4NQN","run-tests","Runs the project unit tests and validation suites.","https:\u002F\u002Fgithub.com\u002FVyrnexis\u002Fnim-agent-template\u002Fblob\u002Fmain\u002Fskills\u002Frun-tests\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M7AWE9HNJ36TDH5NPDVCEAHC","nimonyplugins","Build and debug Nimony compile-time plugins for code generation and DSL rewrites. Use when replacing Nim macros with Nimony plugins, writing or reviewing template, for-loop, module, type, or import plugins, or diagnosing NIF traversal and generated output.","https:\u002F\u002Fgithub.com\u002FVyrnexis\u002Fnim-agent-template\u002Fblob\u002Fmain\u002Fskills\u002Fnimonyplugins\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M7AWE4F7EJ1H837ETBHESE2T","nim-testing","Write and run deterministic Nim tests, including isolated test files, expected-exception checks, multi-configuration builds, and sanitizer integration. Use when setting up a Nim test suite, testing failure behavior, running tests across debug\u002Frelease\u002Fdanger modes, or adding AddressSanitizer support.","https:\u002F\u002Fgithub.com\u002FVyrnexis\u002Fnim-agent-template\u002Fblob\u002Fmain\u002Fskills\u002Fnim-testing\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7AWE0S8C3Y39VGR54R23FZD","nim-style-guide","Write clear, consistent Nim code in a simple stdlib-aligned style, covering imports, naming, proc vs func vs template choices, local variables, constructors, formatting, and control flow. Use when writing new Nim code or reviewing a Nim module for readability, consistency, and low-noise style decisions.","https:\u002F\u002Fgithub.com\u002FVyrnexis\u002Fnim-agent-template\u002Fblob\u002Fmain\u002Fskills\u002Fnim-style-guide\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M7AWDWZAD6RQ547RT96RHA5B","nim-ownership-hooks","Implement and review Nim ARC\u002FORC ownership hooks for types that manually manage resources, including move-only, deep-copy, refcounted, and copy-on-write patterns. Use when a Nim type owns pointers, buffers, file descriptors, or custom heap memory and you need correct `=destroy`, `=copy`, `=dup`, `=sink`, or move semantics.","https:\u002F\u002Fgithub.com\u002FVyrnexis\u002Fnim-agent-template\u002Fblob\u002Fmain\u002Fskills\u002Fnim-ownership-hooks\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M7AWDQ5JGN9XNNJ9FKJQ14GP","nim-mcp-tools","Use for Nim symbol navigation, diagnostics, and type resolution. MANDATORY: Use specialized MCP tools (nimFindSymbols, nimFindReferences, nimListSymbols, nimCheckFile, nimCheckProject, nimFindTypeDefinition) first; fall back to grep only on error or user confirmation.","https:\u002F\u002Fgithub.com\u002FVyrnexis\u002Fnim-agent-template\u002Fblob\u002Fmain\u002Fskills\u002Fnim-mcp-tools\u002FSKILL.md",[],[]]