[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6BYYV8JWYH5MZSZDBYEVH9D":3,"skill-same:01M6BYYV8JWYH5MZSZDBYEVH9D":85},{"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":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M6BYYV8JWYH5MZSZDBYEVH9D","deno",null,"Use when writing, running, configuring, reviewing, or debugging code in a Deno project, or when scaffolding a new one. Covers dependency management with deno install and deno add, package.json and node_modules support, npm and JSR packages, permissions, where configuration belongs across package.json, tsconfig.json and deno.json, workspaces, the built-in toolchain (fmt, lint, test, check, bench, compile), and publishing.","Tsukina-7mochi\u002Fdotfiles","Tsukina-7mochi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F60507815?v=4","01M6BYYM9MPF2KA728H1H58RPV","Mooncake Sugar","01M6BYYMEBS6KWSG5N5PW2YZ8B",1,"MIT","https:\u002F\u002Fgithub.com\u002FTsukina-7mochi\u002Fdotfiles\u002Fblob\u002Fmain\u002Fconfig\u002Fagents\u002Fskills\u002Fdeno\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31],"writing","support","test","debugging","packages","lint","code","permissions","npm","compile","package","json","node","2026-11-10 10:12:30",false,"---\nname: deno\ndescription: Use when writing, running, configuring, reviewing, or debugging code in a Deno project, or when scaffolding a new one. Covers dependency management with deno install and deno add, package.json and node_modules support, npm and JSR packages, permissions, where configuration belongs across package.json, tsconfig.json and deno.json, workspaces, the built-in toolchain (fmt, lint, test, check, bench, compile), and publishing.\nlicense: MIT\nmetadata:\n  author: denoland\n  version: \"1.0\"\n---\n\n# Deno\n\nA JavaScript and TypeScript runtime with a package manager, formatter, linter,\ntest runner, type checker, and bundler in one binary. Runs TypeScript directly.\n\nNeeds Deno 2.9+. Check with `deno --version`, update with `deno upgrade`.\n\n## Deno works the way npm and bun do\n\nDeno is not a separate ecosystem to port code into:\n\n- `deno install` reads an existing `package.json` and writes a real\n  `node_modules`.\n- `deno add express` installs from **npm**. Unprefixed names default to npm.\n- `deno task build` runs `scripts.build` from `package.json` or `tasks.build`\n  from `deno.json`. If both define it, `deno.json` wins.\n- Node built-ins work prefixed or not: `node:fs` and `fs` both resolve.\n- `deno main.js` runs a file. `deno run` is optional.\n- Deno reads `tsconfig.json`.\n\nDon't tell users to rewrite imports, adopt JSR, or restructure as a\nprecondition. The two real differences are **permissions** and **npm lifecycle\nscripts not running by default**.\n\nSingle-file scripts need no build step and no `tsconfig.json`. Applications and\nframework projects keep their normal setup.\n\nTo convert an existing project, see the `migrate-to-deno` skill.\n\n## Dependency management\n\n```bash\ndeno install                  # install everything declared\ndeno add express              # from npm (unprefixed = npm)\ndeno add jsr:@std\u002Fpath        # from JSR\ndeno add -D vitest            # dev dependency (package.json only)\ndeno remove express\ndeno outdated                 # list outdated deps\ndeno update                   # alias for `deno outdated --update`\ndeno update --latest          # ignore existing semver ranges\ndeno list                     # declared deps + resolved versions (npm ls)\ndeno why express              # why a package is in the tree\ndeno audit                    # vulnerability audit\ndeno ci                       # clean reproducible install for CI\ndx cowsay hello               # run a package binary without installing (npx)\n```\n\n`deno ci` is the CI command, not `deno install`: it requires `deno.lock`,\ndeletes `node_modules`, installs strictly from the lockfile, and fails if the\nlockfile is stale. `--prod` skips devDependencies.\n\n`dx` is `npx` \u002F `bunx` \u002F `pnpm dlx`, and an alias for `deno x`. It runs **with\nthe sandbox disabled**, so treat it with the same care as `npx`.\n\nDeno won't install a version published less than a day ago, limiting the window\nfor a compromised release. Override with `--min-dep-age`, which takes minutes\n(`120`), an ISO-8601 duration (`P7D`), a cutoff date, or `0` to disable:\n\n```bash\ndeno add --min-dep-age=0 npm:some-package\n```\n\nLifecycle scripts (`postinstall`) don't run by default — a common surprise when\na native addon looks broken after install. Approve once per project:\n\n```bash\ndeno approve-scripts                              # interactive picker\ndeno install --allow-scripts=npm:better-sqlite3\n```\n\n### Where configuration goes\n\n| File            | Holds                                         |\n| --------------- | --------------------------------------------- |\n| `package.json`  | dependencies, scripts                         |\n| `tsconfig.json` | TypeScript compiler options                   |\n| `deno.json`     | Deno config: `fmt`, `lint`, tasks, workspaces |\n\n**Put dependencies in `package.json`** — every other tool reads it, and Deno\nresolves it natively. Use `deno.json` for dependencies only when there is no\n`package.json`: a standalone script, or a JSR package. Likewise prefer\n`tsconfig.json` over `compilerOptions` in `deno.json`, so `tsc` and editors see\nthe same settings.\n\nCommit `deno.lock`. Deno seeds it from an existing `package-lock.json`,\n`yarn.lock`, `bun.lock`, or pnpm lockfile, preserving pins.\n\n### node_modules layout\n\nDeno uses pnpm's isolated layout: real files in `node_modules\u002F.deno\u002F`, exposed\nby symlinks, so a package can't import what it never declared. For a tool that\nneeds npm's flat hoisted tree:\n\n```json\n{ \"nodeModulesLinker\": \"hoisted\" }\n```\n\n`nodeModulesDir` applies only to projects without a `package.json`, so it is\nrarely the right knob.\n\n## Permissions\n\nDeno grants no filesystem, network, environment, or subprocess access unless\nasked.\n\n```bash\ndeno run --allow-net=api.example.com --allow-read=.\u002Fdata main.ts\ndeno run -A main.ts          # allow everything\n```\n\n| Flag                     | Short | Grants                      |\n| ------------------------ | ----- | --------------------------- |\n| `--allow-read[=paths]`   | `-R`  | filesystem read             |\n| `--allow-write[=paths]`  | `-W`  | filesystem write            |\n| `--allow-net[=hosts]`    | `-N`  | network                     |\n| `--allow-env[=names]`    | `-E`  | environment variables       |\n| `--allow-sys[=apis]`     | `-S`  | OS information              |\n| `--allow-import[=hosts]` | `-I`  | imports from remote hosts   |\n| `--allow-run[=bins]`     | —     | subprocesses                |\n| `--allow-ffi[=paths]`    | —     | native libraries (unstable) |\n| `--allow-all`            | `-A`  | everything                  |\n\n`-S` is `--allow-sys`, not `--allow-run`. Every flag takes an allowlist —\n`--allow-net=example.com:443` beats bare `--allow-net`. Matching `--deny-*`\nflags always win.\n\nOn `Requires net access to \"...\"`, add that specific permission. `-A` is fine\nfor trusted first-party code and during migration, but a poor default to commit\nin a task.\n\n## Configuration\n\n`deno.json` (or `.jsonc`) is auto-discovered from the current directory upward.\n\n```json\n{\n  \"tasks\": {\n    \"dev\": \"deno watch -A main.ts\",\n    \"start\": \"deno run -A main.ts\"\n  },\n  \"fmt\": { \"exclude\": [\"build\u002F\"] },\n  \"lint\": { \"rules\": { \"exclude\": [\"no-explicit-any\"] } },\n  \"exclude\": [\"build\u002F\", \"dist\u002F\"]\n}\n```\n\nTop-level `exclude` applies to every subcommand; per-tool `exclude` narrows it.\n\n`deno.json` also accepts `imports`, an import map pointing bare specifiers at\nreal ones. That is how a project without `package.json` declares dependencies,\nand how a JSR package declares its own alongside `name`, `version`, `exports`.\n\n### Workspaces\n\nnpm, Yarn, and Bun workspaces work out of the box — Deno reads `package.json`\n`\"workspaces\"` directly. pnpm is the exception: `pnpm-workspace.yaml` is\nmigrated into `deno.json` on first run, which must then be re-run.\n\n```json\n{ \"workspace\": [\".\u002Fpackages\u002Fcore\", \".\u002Fpackages\u002Fcli\"] }\n```\n\nMembers are explicit or single-level globs (`\"packages\u002F*\"`); `**` and negation\nare unsupported. Run a task across members with `deno task --filter '*' build`.\n\n## Packages: npm and JSR\n\n**Prefer npm** — it is where the ecosystem is, and `deno add express` is the\nnormal case. Reach for JSR for the standard library (`@std\u002F*`), or to publish\nTypeScript that consumers get types for without a build step. Mixing is fine.\n\n```bash\ndeno add jsr:@std\u002Fpath npm:express\ndeno doc jsr:@std\u002Fpath        # read a package's API from the terminal\n```\n\nDeno once used full URL imports (`https:\u002F\u002Fdeno.land\u002Fx\u002F...`). They still run but\naren't recommended; to modernize, `deno add` the package and import the bare\nspecifier.\n\n## Built-in tooling\n\n```bash\ndeno fmt              # format (--check for CI)\ndeno lint             # lint (--fix, --rules)\ndeno test             # tests (--watch, --parallel, --coverage=dir)\ndeno check main.ts    # type-check without running\ndeno bench            # benchmarks\ndeno coverage         # coverage report from --coverage output\ndeno compile main.ts  # single-file executable (--target cross-compiles)\ndeno doc mod.ts       # docs (--html for a site)\ndeno info main.ts     # module graph and cache info\n```\n\nThese cover prettier, eslint, jest\u002Fvitest, tsc, and pkg\u002Fnexe with no config or\ndependencies — but they are **not** drop-in replacements. Parity is incomplete,\nso moving an established project is real work. **There is no need to migrate:**\nkeep prettier, eslint, and vitest, and use Deno as runtime and package manager.\nPrefer the built-in tools for new projects.\n\nSuppress with `\u002F\u002F deno-lint-ignore \u003Crule>`, `\u002F\u002F deno-lint-ignore-file`,\n`\u002F\u002F deno-fmt-ignore`, `\u002F\u002F deno-fmt-ignore-file`. In Markdown,\n`\u003C!-- deno-fmt-ignore -->` before a code block protects illustrative snippets\nthat aren't valid standalone code.\n\n## Running code\n\n```bash\ndeno main.ts                 # deno run is optional\ndeno watch main.ts           # reload on change (replaces nodemon)\ndeno task dev                # task from package.json or deno.json\ndeno repl\ndeno eval \"console.log(1)\"\n```\n\n`deno watch` hot-replaces modules, restarting if that fails; it aliases\n`deno run --watch-hmr`.\n\nAn HTTP server needs no dependencies:\n\n```ts\nDeno.serve((_req) => new Response(\"Hello\"));\n```\n\n## Starting a new project\n\nScaffold rather than hand-writing the files:\n\n```bash\ndeno init my-project          # script + test + deno.json\ndeno init --empty my-project  # just main.ts and deno.json\ndeno init --lib my-lib        # library laid out for JSR\ndeno create vite my-app       # scaffold from a package initializer\n```\n\n`deno create` is `npm create` \u002F `yarn create` and covers that ecosystem\n(`deno create astro`, etc). Unprefixed names are npm; `--jsr` selects JSR.\n\n## Publishing\n\n**To npm the regular flow still works** — `npm publish`, or `deno pack` to build\nthe tarball first. `deno publish` targets JSR only, from a `deno.json` with\n`name`, `version`, and `exports`:\n\n```bash\ndeno publish --dry-run\ndeno publish\n```\n\nProvenance attestation is automatic on GitHub Actions. `deno bump-version patch`\nbumps the version, across every member at a workspace root.\n\nGuide: \u003Chttps:\u002F\u002Fdocs.deno.com\u002Fruntime\u002Freference\u002Fcli\u002Fpublish\u002F>\n\n## Reviewing Deno code\n\n- `-A` committed in a task where a scoped grant would work.\n- `deno.lock` uncommitted, or CI running `deno install` instead of `deno ci`.\n- Inline `jsr:`\u002F`npm:` specifiers in a project with a `package.json` — use\n  `deno add` so the version lives in one place. Fine in standalone scripts.\n- A specifier with no version constraint.\n- Dependencies or compiler options in `deno.json` when `package.json` or\n  `tsconfig.json` exists.\n- Missing `deno fmt --check`, `deno lint`, `deno check` in CI.\n\n## Further reading\n\n- \u003Chttps:\u002F\u002Fdocs.deno.com> — runtime documentation\n- \u003Chttps:\u002F\u002Fdocs.deno.com\u002Fapi\u002F> — `Deno.*` API reference\n- `references\u002FCLI.md` — fuller subcommand and flag reference\n- `deno \u003Csubcommand> --help` — authoritative and version-accurate; check it\n  before guessing at a flag.\n","# Deno\n\nA JavaScript and TypeScript runtime with a package manager, formatter, linter,\ntest runner, type checker, and bundler in one binary. Runs TypeScript directly.\n\nNeeds Deno 2.9+. Check with `deno --version`, update with `deno upgrade`.\n\n## Deno works the way npm and bun do\n\nDeno is not a separate ecosystem to port code into:\n\n- `deno install` reads an existing `package.json` and writes a real\n  `node_modules`.\n- `deno add express` installs from **npm**. Unprefixed names default to npm.\n- `deno task build` runs `scripts.build` from `package.json` or `tasks.build`\n  from `deno.json`. If both define it, `deno.json` wins.\n- Node built-ins work prefixed or not: `node:fs` and `fs` both resolve.\n- `deno main.js` runs a file. `deno run` is optional.\n- Deno reads `tsconfig.json`.\n\nDon't tell users to rewrite imports, adopt JSR, or restructure as a\nprecondition. The two real differences are **permissions** and **npm lifecycle\nscripts not running by default**.\n\nSingle-file scripts need no build step and no `tsconfig.json`. Applications and\nframework projects keep their normal setup.\n\nTo convert an existing project, see the `migrate-to-deno` skill.\n\n## Dependency management\n\n```bash\ndeno install                  # install everything declared\ndeno add express              # from npm (unprefixed = npm)\ndeno add jsr:@std\u002Fpath        # from JSR\ndeno add -D vitest            # dev dependency (package.json only)\ndeno remove express\ndeno outdated                 # list outdated deps\ndeno update                   # alias for `deno outdated --update`\ndeno update --latest          # ignore existing semver ranges\ndeno list                     # declared deps + resolved versions (npm ls)\ndeno why express              # why a package is in the tree\ndeno audit                    # vulnerability audit\ndeno ci                       # clean reproducible install for CI\ndx cowsay hello               # run a package binary without installing (npx)\n```\n\n`deno ci` is the CI command, not `deno install`: it requires `deno.lock`,\ndeletes `node_modules`, installs strictly from the lockfile, and fails if the\nlockfile is stale. `--prod` skips devDependencies.\n\n`dx` is `npx` \u002F `bunx` \u002F `pnpm dlx`, and an alias for `deno x`. It runs **with\nthe sandbox disabled**, so treat it with the same care as `npx`.\n\nDeno won't install a version published less than a day ago, limiting the window\nfor a compromised release. Override with `--min-dep-age`, which takes minutes\n(`120`), an ISO-8601 duration (`P7D`), a cutoff date, or `0` to disable:\n\n```bash\ndeno add --min-dep-age=0 npm:some-package\n```\n\nLifecycle scripts (`postinstall`) don't run by default — a common surprise when\na native addon looks broken after install. Approve once per project:\n\n```bash\ndeno approve-scripts                              # interactive picker\ndeno install --allow-scripts=npm:better-sqlite3\n```\n\n### Where configuration goes\n\n| File            | Holds                                         |\n| --------------- | --------------------------------------------- |\n| `package.json`  | dependencies, scripts                         |\n| `tsconfig.json` | TypeScript compiler options                   |\n| `deno.json`     | Deno config: `fmt`, `lint`, tasks, workspaces |\n\n**Put dependencies in `package.json`** — every other tool reads it, and Deno\nresolves it natively. Use `deno.json` for dependencies only when there is no\n`package.json`: a standalone script, or a JSR package. Likewise prefer\n`tsconfig.json` over `compilerOptions` in `deno.json`, so `tsc` and editors see\nthe same settings.\n\nCommit `deno.lock`. Deno seeds it from an existing `package-lock.json`,\n`yarn.lock`, `bun.lock`, or pnpm lockfile, preserving pins.\n\n### node_modules layout\n\nDeno uses pnpm's isolated layout: real files in `node_modules\u002F.deno\u002F`, exposed\nby symlinks, so a package can't import what it never declared. For a tool that\nneeds npm's flat hoisted tree:\n\n```json\n{ \"nodeModulesLinker\": \"hoisted\" }\n```\n\n`nodeModulesDir` applies only to projects without a `package.json`, so it is\nrarely the right knob.\n\n## Permissions\n\nDeno grants no filesystem, network, environment, or subprocess access unless\nasked.\n\n```bash\ndeno run --allow-net=api.example.com --allow-read=.\u002Fdata main.ts\ndeno run -A main.ts          # allow everything\n```\n\n| Flag                     | Short | Grants                      |\n| ------------------------ | ----- | --------------------------- |\n| `--allow-read[=paths]`   | `-R`  | filesystem read             |\n| `--allow-write[=paths]`  | `-W`  | filesystem write            |\n| `--allow-net[=hosts]`    | `-N`  | network                     |\n| `--allow-env[=names]`    | `-E`  | environment variables       |\n| `--allow-sys[=apis]`     | `-S`  | OS information              |\n| `--allow-import[=hosts]` | `-I`  | imports from remote hosts   |\n| `--allow-run[=bins]`     | —     | subprocesses                |\n| `--allow-ffi[=paths]`    | —     | native libraries (unstable) |\n| `--allow-all`            | `-A`  | everything                  |\n\n`-S` is `--allow-sys`, not `--allow-run`. Every flag takes an allowlist —\n`--allow-net=example.com:443` beats bare `--allow-net`. Matching `--deny-*`\nflags always win.\n\nOn `Requires net access to \"...\"`, add that specific permission. `-A` is fine\nfor trusted first-party code and during migration, but a poor default to commit\nin a task.\n\n## Configuration\n\n`deno.json` (or `.jsonc`) is auto-discovered from the current directory upward.\n\n```json\n{\n  \"tasks\": {\n    \"dev\": \"deno watch -A main.ts\",\n    \"start\": \"deno run -A main.ts\"\n  },\n  \"fmt\": { \"exclude\": [\"build\u002F\"] },\n  \"lint\": { \"rules\": { \"exclude\": [\"no-explicit-any\"] } },\n  \"exclude\": [\"build\u002F\", \"dist\u002F\"]\n}\n```\n\nTop-level `exclude` applies to every subcommand; per-tool `exclude` narrows it.\n\n`deno.json` also accepts `imports`, an import map pointing bare specifiers at\nreal ones. That is how a project without `package.json` declares dependencies,\nand how a JSR package declares its own alongside `name`, `version`, `exports`.\n\n### Workspaces\n\nnpm, Yarn, and Bun workspaces work out of the box — Deno reads `package.json`\n`\"workspaces\"` directly. pnpm is the exception: `pnpm-workspace.yaml` is\nmigrated into `deno.json` on first run, which must then be re-run.\n\n```json\n{ \"workspace\": [\".\u002Fpackages\u002Fcore\", \".\u002Fpackages\u002Fcli\"] }\n```\n\nMembers are explicit or single-level globs (`\"packages\u002F*\"`); `**` and negation\nare unsupported. Run a task across members with `deno task --filter '*' build`.\n\n## Packages: npm and JSR\n\n**Prefer npm** — it is where the ecosystem is, and `deno add express` is the\nnormal case. Reach for JSR for the standard library (`@std\u002F*`), or to publish\nTypeScript that consumers get types for without a build step. Mixing is fine.\n\n```bash\ndeno add jsr:@std\u002Fpath npm:express\ndeno doc jsr:@std\u002Fpath        # read a package's API from the terminal\n```\n\nDeno once used full URL imports (`https:\u002F\u002Fdeno.land\u002Fx\u002F...`). They still run but\naren't recommended; to modernize, `deno add` the package and import the bare\nspecifier.\n\n## Built-in tooling\n\n```bash\ndeno fmt              # format (--check for CI)\ndeno lint             # lint (--fix, --rules)\ndeno test             # tests (--watch, --parallel, --coverage=dir)\ndeno check main.ts    # type-check without running\ndeno bench            # benchmarks\ndeno coverage         # coverage report from --coverage output\ndeno compile main.ts  # single-file executable (--target cross-compiles)\ndeno doc mod.ts       # docs (--html for a site)\ndeno info main.ts     # module graph and cache info\n```\n\nThese cover prettier, eslint, jest\u002Fvitest, tsc, and pkg\u002Fnexe with no config or\ndependencies — but they are **not** drop-in replacements. Parity is incomplete,\nso moving an established project is real work. **There is no need to migrate:**\nkeep prettier, eslint, and vitest, and use Deno as runtime and package manager.\nPrefer the built-in tools for new projects.\n\nSuppress with `\u002F\u002F deno-lint-ignore \u003Crule>`, `\u002F\u002F deno-lint-ignore-file`,\n`\u002F\u002F deno-fmt-ignore`, `\u002F\u002F deno-fmt-ignore-file`. In Markdown,\n`\u003C!-- deno-fmt-ignore -->` before a code block protects illustrative snippets\nthat aren't valid standalone code.\n\n## Running code\n\n```bash\ndeno main.ts                 # deno run is optional\ndeno watch main.ts           # reload on change (replaces nodemon)\ndeno task dev                # task from package.json or deno.json\ndeno repl\ndeno eval \"console.log(1)\"\n```\n\n`deno watch` hot-replaces modules, restarting if that fails; it aliases\n`deno run --watch-hmr`.\n\nAn HTTP server needs no dependencies:\n\n```ts\nDeno.serve((_req) => new Response(\"Hello\"));\n```\n\n## Starting a new project\n\nScaffold rather than hand-writing the files:\n\n```bash\ndeno init my-project          # script + test + deno.json\ndeno init --empty my-project  # just main.ts and deno.json\ndeno init --lib my-lib        # library laid out for JSR\ndeno create vite my-app       # scaffold from a package initializer\n```\n\n`deno create` is `npm create` \u002F `yarn create` and covers that ecosystem\n(`deno create astro`, etc). Unprefixed names are npm; `--jsr` selects JSR.\n\n## Publishing\n\n**To npm the regular flow still works** — `npm publish`, or `deno pack` to build\nthe tarball first. `deno publish` targets JSR only, from a `deno.json` with\n`name`, `version`, and `exports`:\n\n```bash\ndeno publish --dry-run\ndeno publish\n```\n\nProvenance attestation is automatic on GitHub Actions. `deno bump-version patch`\nbumps the version, across every member at a workspace root.\n\nGuide: \u003Chttps:\u002F\u002Fdocs.deno.com\u002Fruntime\u002Freference\u002Fcli\u002Fpublish\u002F>\n\n## Reviewing Deno code\n\n- `-A` committed in a task where a scoped grant would work.\n- `deno.lock` uncommitted, or CI running `deno install` instead of `deno ci`.\n- Inline `jsr:`\u002F`npm:` specifiers in a project with a `package.json` — use\n  `deno add` so the version lives in one place. Fine in standalone scripts.\n- A specifier with no version constraint.\n- Dependencies or compiler options in `deno.json` when `package.json` or\n  `tsconfig.json` exists.\n- Missing `deno fmt --check`, `deno lint`, `deno check` in CI.\n\n## Further reading\n\n- \u003Chttps:\u002F\u002Fdocs.deno.com> — runtime documentation\n- \u003Chttps:\u002F\u002Fdocs.deno.com\u002Fapi\u002F> — `Deno.*` API reference\n- `references\u002FCLI.md` — fuller subcommand and flag reference\n- `deno \u003Csubcommand> --help` — authoritative and version-accurate; check it\n  before guessing at a flag.\n",{"name":5,"license":15,"metadata":37,"description":7},{"author":38,"version":39},"denoland","1.0","main","e3bd571a552fccb7992acf5ea2c345daaf1fabe4","config\u002Fagents\u002Fskills\u002Fdeno",0,"https:\u002F\u002Fgithub.com\u002FTsukina-7mochi\u002Fdotfiles","https:\u002F\u002Fgithub.com\u002FTsukina-7mochi","loves sweet things\r\n(website WIP)","2026-11-12 16:00:19",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add Tsukina-7mochi\u002Fdotfiles --skill deno",{"tool":54,"command":55},"bunx","bunx skills add Tsukina-7mochi\u002Fdotfiles --skill deno",{"tool":57,"command":58},"pnpm","pnpm dlx skills add Tsukina-7mochi\u002Fdotfiles --skill deno","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTsukina-7mochi\u002Fdotfiles\u002Fblob\u002Fmain\u002Fconfig\u002Fagents\u002Fskills\u002Fdeno\u002FSKILL.md",true,[62,67,73,76,80],{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":43,"sourceHtmlUrl":66},"assets\u002F.gitkeep","ASSET","资产文件","https:\u002F\u002Fgithub.com\u002Fbitflight-devops\u002Fskilllint\u002Fblob\u002Fmain\u002Fpackages\u002Fskilllint\u002Ftests\u002Ffixtures\u002Fproviders\u002Fagentskills\u002Ffailing-examples\u002FFM010\u002Finvalid-name-pattern\u002Fskills\u002Fmy-skill\u002Fassets\u002F.gitkeep",{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"eval_queries.json","REFERENCE","参考文档",16,"https:\u002F\u002Fgithub.com\u002Fbitflight-devops\u002Fskilllint\u002Fblob\u002Fmain\u002Fpackages\u002Fskilllint\u002Ftests\u002Ffixtures\u002Fproviders\u002Fagentskills\u002Ffailing-examples\u002FFM010\u002Finvalid-name-pattern\u002Fskills\u002Fmy-skill\u002Feval_queries.json",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":43,"sourceHtmlUrl":75},"references\u002F.gitkeep","https:\u002F\u002Fgithub.com\u002Fbitflight-devops\u002Fskilllint\u002Fblob\u002Fmain\u002Fpackages\u002Fskilllint\u002Ftests\u002Ffixtures\u002Fproviders\u002Fagentskills\u002Ffailing-examples\u002FFM010\u002Finvalid-name-pattern\u002Fskills\u002Fmy-skill\u002Freferences\u002F.gitkeep",{"path":77,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002FCLI.md",10730,"https:\u002F\u002Fgithub.com\u002FTsukina-7mochi\u002Fdotfiles\u002Fblob\u002Fmain\u002Fconfig\u002Fagents\u002Fskills\u002Fdeno\u002Freferences\u002FCLI.md",{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":43,"sourceHtmlUrl":84},"scripts\u002F.gitkeep","SCRIPT","脚本","https:\u002F\u002Fgithub.com\u002Fbitflight-devops\u002Fskilllint\u002Fblob\u002Fmain\u002Fpackages\u002Fskilllint\u002Ftests\u002Ffixtures\u002Fproviders\u002Fagentskills\u002Ffailing-examples\u002FFM010\u002Finvalid-name-pattern\u002Fskills\u002Fmy-skill\u002Fscripts\u002F.gitkeep",[]]