[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A5X09RVB28PE4RZCHFARAE":3,"skill-same:01M7A5X09RVB28PE4RZCHFARAE":45},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7A5X09RVB28PE4RZCHFARAE","nix-debugger",null,"Find why a Nix build rebuilt, cascaded, ran slow, or failed without naming an error: nix-dag plan scoring, whence provenance, full build logs, drvPath eval before build, in-flight daemon builds, and generation-to-generation unit diffs. Use when something rebuilt that should not have, a deploy triggered a restart or handoff, a build is slower than expected, or a failure excerpt does not contain the error.","harivansh-afk\u002Floom-index-e2e","harivansh-afk","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F73809867?v=4","01M7A5RBDGB0YMBHVWXCS0VYE7","hari","01M7A5RBEKV38Y878XPTCR4SJ3",0,"MIT","https:\u002F\u002Fgithub.com\u002Fharivansh-afk\u002Floom-index-e2e\u002Fblob\u002Fmain\u002Fskills\u002Fnix\u002Fdebugger\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: nix-debugger\ndescription: \"Find why a Nix build rebuilt, cascaded, ran slow, or failed without naming an error: nix-dag plan scoring, whence provenance, full build logs, drvPath eval before build, in-flight daemon builds, and generation-to-generation unit diffs. Use when something rebuilt that should not have, a deploy triggered a restart or handoff, a build is slower than expected, or a failure excerpt does not contain the error.\"\n---\n\n## Nix debugger\n\nSomething rebuilt, and you want to know why. The cause is usually a store path\ncarried in a place nobody thinks of as an input: an environment variable or an\n`ExecStart` line. Measure before forming a theory; each tool below answers one\nquestion from data that already exists.\n\n## Rank what invalidates the rest: `nix-dag`\n\n`nix-dag \u003Cinstallable>` scores a build plan from evaluation alone. No builder,\nseconds rather than hours. It prints the critical path, the width per level, and\na ranking of nodes whose dependents reach them only through an environment\nvariable naming the store path.\n\nIn **index**:\n\n```\nnix-dag .#whence\n  929 derivations, 5466 edges\n  critical path  165 nodes\n  parallelism    165 levels, widest 163 at level 111, median 2\n\n  1. python3-3.14.6\n     sole 4 of 85 direct  blast 125  own deps 600\n     4 of 85 dependents name it only in pythonInterpreter and reach it no\n     other way: drop that and they stop rebuilding when this changes\n```\n\nRead the **sole** count, not blast. A compiler with a thousand dependents is\nnormal and uninteresting; a node reached only through `pythonInterpreter` is a\nrebuild nobody asked for.\n\nThen check the top entry is built here. The ranking is cost per change and\ncannot see how often a node moves, so a node pinned to an upstream input that\nalready invalidates the graph another way costs nothing however high it ranks.\nOne session skipped this check and filed a defect against a nixpkgs-pinned JDK,\nthen retracted it.\n\n`--top N` widens the ranking, `--json` makes it machine-readable, and\n`--from-json \u003Cdump>` reads a captured `nix derivation show --recursive` instead\nof evaluating, so you can score a plan from a host you cannot evaluate on.\n\n## Read the whole build log, not the excerpt: `nix log`\n\nThe excerpt nix prints on failure is a fixed tail. When a chatty phase precedes\nthe error, the error scrolls off and the excerpt shows nothing but noise. This\nhas sent sessions after the wrong layer.\n\n```sh\nnix log \u002Fnix\u002Fstore\u002Ff7d1ak6zackgdmkxn9b1pgrinqcwwrgf-whence.drv > \u002Ftmp\u002Fwhence-build.log 2>&1\n```\n\nGet the derivation path from `nix eval --raw .#\u003Cattr>.drvPath`, or from the\n`logFile` and `drvPath` fields of `nix store builds --json`.\n\nA crate whose log stops at the compiler invocation with no diagnostic is usually\na store problem, not a compile error.\n\nA worked instance, 2026-07-29. ix#8885's `nix` job failed. Neither `gh run view\n--log-failed` nor the full 4,348 line `gh run view --log` contains the word\n`error` anywhere; both end in hundreds of lines of `added 117 signatures` from a\ncache-push phase that ran after the build failed, plus a pointer to a file on an\nunnamed host. The cause was on line 634 of an 85 KB log on `hil-compute-2`:\n\n```\nerror: Cannot build '\u002Fnix\u002Fstore\u002Flwpynj4...-cargo-unit-nextest-ix-vm-guest.drv'.\n       >   panicked at \u002Fbuild\u002Fvm-guest-daemon-0.1.0\u002Fsrc\u002Fvsock.rs:276:10:\n       >   AF_VSOCK connect: ENODEV\n```\n\nThat is not truncation, it is a filter that kept the chattiest phase and dropped\nthe diagnostic, so the job reads as failed with no stated reason under a wall of\nsuccessful-looking output. Two habits follow. The store excerpt names your next\ncommand itself (`For full logs, run: nix log \u003Cdrv>`). And a wrapper's own log\nusually lives on the host that ran the job rather than dying with an ephemeral\nrunner, so `full log (unfiltered, on this runner)` means find the host, not give\nup. Filed as ix#9086.\n\n## Evaluate before you build\n\nAn attribute costs minutes; its closure costs hours. `nix eval --raw\n.#\u003Cattr>.drvPath` proves the expression is sound without building anything.\n\nIn **both repos**, one eval finds every host's eval errors at once, across a\nwhole fleet:\n\n```sh\nnix eval --json .#nixosConfigurations \\\n  --apply 'cs: builtins.mapAttrs (n: c: c.config.system.build.toplevel.drvPath) cs'\n```\n\nThat eval is not free of builds: import-from-derivation pulls a couple of small\ngenerated files through a builder first, so a few `building '...'` lines before\nthe result are expected rather than a sign it went wrong.\n\nDo not use a deploy as a linter. A prod deploy here measured 74 minutes and\nfailed on a single eval error; the fix exposed the next one, three times over.\nThe command above would have found all three locally.\n\n## See what the daemon is doing: `nix store builds`\n\n```sh\nnix store builds --json\n```\n\nLists every in-flight build and substitution machine-wide, with `pid`,\n`startTime`, `user`, `logFile`, and a `why` chain naming the root goal that\nwanted this path and the cause (`requested`, `outputsMissing`,\n`outputInvalid`). Patched nix; it reads `\u002Fnix\u002Fvar\u002Fnix\u002Fstatus` directly rather\nthan connecting to a daemon, so it works when the daemon is wedged. Gated on the\n`build-status-dir` experimental feature at both the writer and the reader, so an\nempty array can mean the feature is off rather than idle.\n\n## Which .nix file put this here: `whence`\n\n```\nwhence ripgrep\n  ripgrep 15.2.0\n    ix\u002Findex\u002Fusers\u002Fandrewgazelka\u002Fprofiles\u002Fworkstation.nix:? @ 0b85b77\n    defined via:\n      ix\u002Findex\u002Fusers\u002Fandrewgazelka\u002Fprofiles\u002Fworkstation.nix\n      ix\u002Findex\u002Fmodules\u002Fhome\u002Fcli-baseline.nix\n```\n\n`whence \u003Cpath|pname>` reads the live generation's `provenance.json` with zero\nevaluation. It covers deployed files and installed packages.\n\nIt only knows generations that ship that manifest: the home-manager profile and,\non darwin, `\u002Frun\u002Fcurrent-system`. Fleet NixOS hosts ship neither the manifest nor\nthe binary, so `whence` on `hil-compute-2` is a command-not-found and the\nquestion there needs the eval-time route instead.\n\nThat route is `options.\u003Cname>.definitionsWithLocations`, which names every file\nthat set an option.\n\nIn **both repos**:\n\n```sh\nnix eval --json .#nixosConfigurations --apply \\\n  'cs: map (d: d.file) (builtins.head (builtins.attrValues cs)).options.networking.firewall.enable.definitionsWithLocations'\n# [\"\u002Fnix\u002Fstore\u002Fg469d8rgcg594b5hla5q1r1bkwh596f0-source\u002Fnix\u002Fmodules\u002Fbase\u002Fnetworking.nix\"]\n```\n\n## A store-path bump is not a change: diff two generations\n\nWhen a deploy restarts a service or triggers a handoff, the first cut is whether\nthe unit actually changed or only its store hashes moved. Unit files live under\n`\u002Fnix\u002Fvar\u002Fnix\u002Fprofiles\u002Fsystem-\u003CN>-link\u002Fetc\u002Fsystemd\u002Fsystem\u002F`.\n\n```sh\nu=etc\u002Fsystemd\u002Fsystem\u002Fix-cas-fabric-server@.service\nnorm() { sed -E \"s|\u002Fnix\u002Fstore\u002F[a-z0-9]{32}-|H-|g\" \"$1\"; }\ndiff \u003C(norm \u002Fnix\u002Fvar\u002Fnix\u002Fprofiles\u002Fsystem-1446-link\u002F$u) \\\n     \u003C(norm \u002Fnix\u002Fvar\u002Fnix\u002Fprofiles\u002Fsystem-1447-link\u002F$u)\n```\n\nRaw, that pair differs on one line: an `ExecStart` store hash. Normalized, it is\nbyte identical. Nothing about the service changed.\n\nMeasured on `hil-compute-2` over the 60 most recent generations, that unit\nchanged in 34 of 59 consecutive pairs, and 29 of the 34 normalized to byte\nidentical. The 5 real changes were `NonBlocking=true`, `TimeoutStopSec` 35s to\n45s, `TasksMax` 1024 to 464, an added `ExecCondition`, and a gcc minor bump\ninside `LD_LIBRARY_PATH`. A change to that unit costs a fabric handoff, and\nhandoff cost is why fleet auto-deploy runs on a 6 hour timer rather than per\ncommit, so 29 of those 34 deploys paid the timer's whole reason for nothing.\n\nThe two findings take different fixes. A semantic change earns its restart. A\npure path bump means the unit is carrying a store path it does not need to\ncarry, and `nix-dag` on the same closure will name the edge that puts it there.\n","## Nix debugger\n\nSomething rebuilt, and you want to know why. The cause is usually a store path\ncarried in a place nobody thinks of as an input: an environment variable or an\n`ExecStart` line. Measure before forming a theory; each tool below answers one\nquestion from data that already exists.\n\n## Rank what invalidates the rest: `nix-dag`\n\n`nix-dag \u003Cinstallable>` scores a build plan from evaluation alone. No builder,\nseconds rather than hours. It prints the critical path, the width per level, and\na ranking of nodes whose dependents reach them only through an environment\nvariable naming the store path.\n\nIn **index**:\n\n```\nnix-dag .#whence\n  929 derivations, 5466 edges\n  critical path  165 nodes\n  parallelism    165 levels, widest 163 at level 111, median 2\n\n  1. python3-3.14.6\n     sole 4 of 85 direct  blast 125  own deps 600\n     4 of 85 dependents name it only in pythonInterpreter and reach it no\n     other way: drop that and they stop rebuilding when this changes\n```\n\nRead the **sole** count, not blast. A compiler with a thousand dependents is\nnormal and uninteresting; a node reached only through `pythonInterpreter` is a\nrebuild nobody asked for.\n\nThen check the top entry is built here. The ranking is cost per change and\ncannot see how often a node moves, so a node pinned to an upstream input that\nalready invalidates the graph another way costs nothing however high it ranks.\nOne session skipped this check and filed a defect against a nixpkgs-pinned JDK,\nthen retracted it.\n\n`--top N` widens the ranking, `--json` makes it machine-readable, and\n`--from-json \u003Cdump>` reads a captured `nix derivation show --recursive` instead\nof evaluating, so you can score a plan from a host you cannot evaluate on.\n\n## Read the whole build log, not the excerpt: `nix log`\n\nThe excerpt nix prints on failure is a fixed tail. When a chatty phase precedes\nthe error, the error scrolls off and the excerpt shows nothing but noise. This\nhas sent sessions after the wrong layer.\n\n```sh\nnix log \u002Fnix\u002Fstore\u002Ff7d1ak6zackgdmkxn9b1pgrinqcwwrgf-whence.drv > \u002Ftmp\u002Fwhence-build.log 2>&1\n```\n\nGet the derivation path from `nix eval --raw .#\u003Cattr>.drvPath`, or from the\n`logFile` and `drvPath` fields of `nix store builds --json`.\n\nA crate whose log stops at the compiler invocation with no diagnostic is usually\na store problem, not a compile error.\n\nA worked instance, 2026-07-29. ix#8885's `nix` job failed. Neither `gh run view\n--log-failed` nor the full 4,348 line `gh run view --log` contains the word\n`error` anywhere; both end in hundreds of lines of `added 117 signatures` from a\ncache-push phase that ran after the build failed, plus a pointer to a file on an\nunnamed host. The cause was on line 634 of an 85 KB log on `hil-compute-2`:\n\n```\nerror: Cannot build '\u002Fnix\u002Fstore\u002Flwpynj4...-cargo-unit-nextest-ix-vm-guest.drv'.\n       >   panicked at \u002Fbuild\u002Fvm-guest-daemon-0.1.0\u002Fsrc\u002Fvsock.rs:276:10:\n       >   AF_VSOCK connect: ENODEV\n```\n\nThat is not truncation, it is a filter that kept the chattiest phase and dropped\nthe diagnostic, so the job reads as failed with no stated reason under a wall of\nsuccessful-looking output. Two habits follow. The store excerpt names your next\ncommand itself (`For full logs, run: nix log \u003Cdrv>`). And a wrapper's own log\nusually lives on the host that ran the job rather than dying with an ephemeral\nrunner, so `full log (unfiltered, on this runner)` means find the host, not give\nup. Filed as ix#9086.\n\n## Evaluate before you build\n\nAn attribute costs minutes; its closure costs hours. `nix eval --raw\n.#\u003Cattr>.drvPath` proves the expression is sound without building anything.\n\nIn **both repos**, one eval finds every host's eval errors at once, across a\nwhole fleet:\n\n```sh\nnix eval --json .#nixosConfigurations \\\n  --apply 'cs: builtins.mapAttrs (n: c: c.config.system.build.toplevel.drvPath) cs'\n```\n\nThat eval is not free of builds: import-from-derivation pulls a couple of small\ngenerated files through a builder first, so a few `building '...'` lines before\nthe result are expected rather than a sign it went wrong.\n\nDo not use a deploy as a linter. A prod deploy here measured 74 minutes and\nfailed on a single eval error; the fix exposed the next one, three times over.\nThe command above would have found all three locally.\n\n## See what the daemon is doing: `nix store builds`\n\n```sh\nnix store builds --json\n```\n\nLists every in-flight build and substitution machine-wide, with `pid`,\n`startTime`, `user`, `logFile`, and a `why` chain naming the root goal that\nwanted this path and the cause (`requested`, `outputsMissing`,\n`outputInvalid`). Patched nix; it reads `\u002Fnix\u002Fvar\u002Fnix\u002Fstatus` directly rather\nthan connecting to a daemon, so it works when the daemon is wedged. Gated on the\n`build-status-dir` experimental feature at both the writer and the reader, so an\nempty array can mean the feature is off rather than idle.\n\n## Which .nix file put this here: `whence`\n\n```\nwhence ripgrep\n  ripgrep 15.2.0\n    ix\u002Findex\u002Fusers\u002Fandrewgazelka\u002Fprofiles\u002Fworkstation.nix:? @ 0b85b77\n    defined via:\n      ix\u002Findex\u002Fusers\u002Fandrewgazelka\u002Fprofiles\u002Fworkstation.nix\n      ix\u002Findex\u002Fmodules\u002Fhome\u002Fcli-baseline.nix\n```\n\n`whence \u003Cpath|pname>` reads the live generation's `provenance.json` with zero\nevaluation. It covers deployed files and installed packages.\n\nIt only knows generations that ship that manifest: the home-manager profile and,\non darwin, `\u002Frun\u002Fcurrent-system`. Fleet NixOS hosts ship neither the manifest nor\nthe binary, so `whence` on `hil-compute-2` is a command-not-found and the\nquestion there needs the eval-time route instead.\n\nThat route is `options.\u003Cname>.definitionsWithLocations`, which names every file\nthat set an option.\n\nIn **both repos**:\n\n```sh\nnix eval --json .#nixosConfigurations --apply \\\n  'cs: map (d: d.file) (builtins.head (builtins.attrValues cs)).options.networking.firewall.enable.definitionsWithLocations'\n# [\"\u002Fnix\u002Fstore\u002Fg469d8rgcg594b5hla5q1r1bkwh596f0-source\u002Fnix\u002Fmodules\u002Fbase\u002Fnetworking.nix\"]\n```\n\n## A store-path bump is not a change: diff two generations\n\nWhen a deploy restarts a service or triggers a handoff, the first cut is whether\nthe unit actually changed or only its store hashes moved. Unit files live under\n`\u002Fnix\u002Fvar\u002Fnix\u002Fprofiles\u002Fsystem-\u003CN>-link\u002Fetc\u002Fsystemd\u002Fsystem\u002F`.\n\n```sh\nu=etc\u002Fsystemd\u002Fsystem\u002Fix-cas-fabric-server@.service\nnorm() { sed -E \"s|\u002Fnix\u002Fstore\u002F[a-z0-9]{32}-|H-|g\" \"$1\"; }\ndiff \u003C(norm \u002Fnix\u002Fvar\u002Fnix\u002Fprofiles\u002Fsystem-1446-link\u002F$u) \\\n     \u003C(norm \u002Fnix\u002Fvar\u002Fnix\u002Fprofiles\u002Fsystem-1447-link\u002F$u)\n```\n\nRaw, that pair differs on one line: an `ExecStart` store hash. Normalized, it is\nbyte identical. Nothing about the service changed.\n\nMeasured on `hil-compute-2` over the 60 most recent generations, that unit\nchanged in 34 of 59 consecutive pairs, and 29 of the 34 normalized to byte\nidentical. The 5 real changes were `NonBlocking=true`, `TimeoutStopSec` 35s to\n45s, `TasksMax` 1024 to 464, an added `ExecCondition`, and a gcc minor bump\ninside `LD_LIBRARY_PATH`. A change to that unit costs a fabric handoff, and\nhandoff cost is why fleet auto-deploy runs on a 6 hour timer rather than per\ncommit, so 29 of those 34 deploys paid the timer's whole reason for nothing.\n\nThe two findings take different fixes. A semantic change earns its restart. A\npure path bump means the unit is carrying a store path it does not need to\ncarry, and `nix-dag` on the same closure will name the edge that puts it there.\n",{"name":5,"description":7},"main","bed3e79e169c9952618f13b255bbe21164bd8bc1","skills\u002Fnix\u002Fdebugger","https:\u002F\u002Fgithub.com\u002Fharivansh-afk\u002Floom-index-e2e","https:\u002F\u002Fgithub.com\u002Fharivansh-afk","hari.cafe","2026-08-05 23:54:30",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add harivansh-afk\u002Floom-index-e2e --skill nix-debugger",{"tool":37,"command":38},"bunx","bunx skills add harivansh-afk\u002Floom-index-e2e --skill nix-debugger",{"tool":40,"command":41},"pnpm","pnpm dlx skills add harivansh-afk\u002Floom-index-e2e --skill nix-debugger","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fharivansh-afk\u002Floom-index-e2e\u002Fblob\u002Fmain\u002Fskills\u002Fnix\u002Fdebugger\u002FSKILL.md",true,[],[46,53,60,67,74,80],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7A62MBAXZSSHSTKTJF9M9T0","pdf-processing","Extract text and tables from PDF files","https:\u002F\u002Fgithub.com\u002Fharivansh-afk\u002Floom-index-e2e\u002Fblob\u002Fmain\u002Fviews\u002Fhome-manager\u002Ftests\u002Fmodules\u002Fprograms\u002Fopencode\u002Fskills-bulk\u002Fpdf-processing\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7A62K1VTVFVSPV9V49PKK4N","git-release","Create consistent releases and changelogs","https:\u002F\u002Fgithub.com\u002Fharivansh-afk\u002Floom-index-e2e\u002Fblob\u002Fmain\u002Fviews\u002Fhome-manager\u002Ftests\u002Fmodules\u002Fprograms\u002Fopencode\u002Fskills-bulk\u002Fgit-release\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7A62HPD2TYCNA8MSV4PRGRP","data-analysis","Help analyze datasets and results","https:\u002F\u002Fgithub.com\u002Fharivansh-afk\u002Floom-index-e2e\u002Fblob\u002Fmain\u002Fviews\u002Fhome-manager\u002Ftests\u002Fmodules\u002Fprograms\u002Fopencode\u002Fskill-dir\u002Fdata-analysis\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7A62G35PP698FP9TEZWYZ3V","release-notes","Draft release notes from commits and merged pull requests.","https:\u002F\u002Fgithub.com\u002Fharivansh-afk\u002Floom-index-e2e\u002Fblob\u002Fmain\u002Fviews\u002Fhome-manager\u002Ftests\u002Fmodules\u002Fprograms\u002Fgithub-copilot-cli\u002Fskills\u002Frelease-notes\u002FSKILL.md",[],[],{"skillNo":75,"name":62,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7A62EJX21A1E72WR5CX6W3M","Summarize structured outputs and highlight regressions.","https:\u002F\u002Fgithub.com\u002Fharivansh-afk\u002Floom-index-e2e\u002Fblob\u002Fmain\u002Fviews\u002Fhome-manager\u002Ftests\u002Fmodules\u002Fprograms\u002Fgithub-copilot-cli\u002Fskills\u002Fdata-analysis\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7A62DC2X7X7AYFPF1DG2NBC","skill-one","Example skill for tests.","https:\u002F\u002Fgithub.com\u002Fharivansh-afk\u002Floom-index-e2e\u002Fblob\u002Fmain\u002Fviews\u002Fhome-manager\u002Ftests\u002Fmodules\u002Fprograms\u002Fcodex\u002Fskills-dir\u002Fskill-one\u002FSKILL.md",[],[]]