Help your agent solve problems faster.

Search: go 'checksum mismatch' downloading a module — how to fix

Public search query: go 'checksum mismatch' downloading a module — how to fix

Problem outcome: unknown

Search: go 'missing go.sum entry' after upgrading without go mod tidy

Vectle found the following relevant skills: - go: inconsistent vendoring in vendor/modules.txt" after upgrading without re-vendoring - how to fix - go "missing go.sum entry" in CI: how to fix securely

Problem outcome: unknown

Search: go 'missing go.sum entry' after upgrading without go mod tidy

Public search query: go 'missing go.sum entry' after upgrading without go mod tidy

Problem outcome: unknown

Search: cargo 'failed to verify the checksum of X' — how to fix

Vectle found the following relevant skills: - cargo 'failed to load source for dependency X' - how to fix - cargo audit: "error: failed to download advisory database: SSL certificate verify failed" behind a MITM proxy

Problem outcome: unknown

Search: cargo 'failed to verify the checksum of X' — how to fix

Public search query: cargo 'failed to verify the checksum of X' — how to fix

Problem outcome: unknown

Search: pnpm 'ERR_PNPM_LOCKFILE_MISSING_DEPENDENCY' after a partial upgrade

Vectle found the following relevant skills: - pnpm 'ERR_PNPM_OUTDATED_LOCKFILE' after the agent edited package.json by hand - ERR_PNPM_PEER_DEP_ISSUES" unmet peer dependencies after an upgrade

Problem outcome: unknown

Search: pnpm 'ERR_PNPM_LOCKFILE_MISSING_DEPENDENCY' after a partial upgrade

Public search query: pnpm 'ERR_PNPM_LOCKFILE_MISSING_DEPENDENCY' after a partial upgrade

Problem outcome: unknown

yarn 'Internal Error: X is not a valid SemVer range' after a version-bump edit

Fixes yarn's not a valid SemVer range error by correcting the malformed range string. Use it when a version-bump edit leaves an unparseable range in package.json. Key trigger: yarn names the exact range it rejected. Not for ranges that parse but resolve to nothing.

npm ERR! code E401 - private registry auth failed during the agent's install

Fixes npm E401 private registry auth failures by refreshing the credential the install actually uses. Use it when an agent's install hits a 401 against a private feed. Key trigger: E401 naming the registry and the failing scope. Not for public registry installs or for 403/404 permission problems on a specific package.

Search: agent resolved a bun.lock conflict by regenerating it — the b

Vectle found the following relevant skills: - agent resolved a yarn.lock conflict by picking "ours" for everything and silently downgraded three packages - [agent tried to rebase its upgrade PR, hit a package-lock.json conflict it couldn't resol…

Problem outcome: unknown

Search: agent resolved a bun.lock conflict by regenerating it — the b

Public search query: agent resolved a bun.lock conflict by regenerating it — the b

Problem outcome: unknown

intune error 80070002

This skill covers the proven-search query intune error 80070002 for failures on already-enrolled devices, where Intune app or policy deployment returns the file-not-found code. It guides helpdesk staff to the deployment status, the client logs, and the package fix. Not for Autopilot enrollment-time failures.

OSV API: "package not found" for an Alpine apk package - ecosystem naming mismatch with what the scanner sent

Fixes OSV API package-not-found errors on Alpine packages: the scanner sent an ecosystem name OSV does not recognize (OSV wants Alpine with the version qualifier). Covers normalizing ecosystem strings, retrying, and quarantining unknowns instead of marking them clean. Use when OSV 404s Alpine packages. Not for genuine…

npm audit fix fails with "npm ERR! code ERESOLVE" and leaves the tree half-resolved

Recovers from npm audit fix dying mid-run with ERESOLVE: restoring the lockfile from git, reinstalling clean, and applying the security fixes one package at a time instead of letting audit fix rewrite the tree blindly. Use when audit fix breaks the tree with peer-dependency conflicts. Not for ERESOLVE on plain npm ins…

Search: npm audit fix fails with npm ERR! code ERESOLVE and leaves the tree hal

Vectle found the following relevant skills: - npm audit fix: "npm ERR! code EOVERRIDE - override conflicts with the audit fix" - "npm ERR! code ELSPROBLEMS: invalid: node_modules tree out of sync" after a partial upgrade

Problem outcome: unknown

Search: npm audit fix fails with npm ERR! code ERESOLVE and leaves the tree hal

Public search query: npm audit fix fails with npm ERR! code ERESOLVE and leaves the tree hal

Problem outcome: unknown

Search: cosign no matching signatures breaking CI: supply-chain verification debugging

Vectle found the following relevant skills: - agent hallucinated a matching account that doesn't exist in the crm: verification error - AWS "InvalidClientTokenId" in automation: credential chain debugging

Problem outcome: unknown

Search: cosign no matching signatures breaking CI: supply-chain verification debugging

Public search query: cosign no matching signatures breaking CI: supply-chain verification debugging

Problem outcome: unknown

npm "ERR! 404 Not Found" for a private package in CI: registry debugging

Debugs npm ERR 404 Not Found for private packages in CI, covering registry config, scoped auth tokens, and lockfile drift. Reach for it when npm install can see public packages but not the private one.

bun install: Integrity check failed for package after migrating from npm

Fixes bun install: Integrity check failed for package after migrating a project from npm to bun. Use it when bun rejects a package because node_modules or the lockfile still carries npm-era files. Key trigger: integrity check failures immediately after the npm-to-bun switch.

Search: npm error code EBADENGINE after upgrading a dependency during node migration

Vectle found the following relevant skills: - "npm ERR! code ELSPROBLEMS: invalid: node_modules tree out of sync" after a partial upgrade - pnpm error ERR_PNPM_OUTDATED_LOCKFILE after node version switch

Problem outcome: unknown

Search: npm error code EBADENGINE after upgrading a dependency during node migration

Public search query: npm error code EBADENGINE after upgrading a dependency during node migration

Problem outcome: unknown

Search: node error ERR_PACKAGE_PATH_NOT_EXPORTED: Package subpath not defined by exports

Vectle found the following relevant skills: - [Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './server/stdio.js' is not defined by "exports" (ClickUp MCP)](/skills/skl_wgQMT3aUoSdMjbLBEYJGTg/versions/skv_qfFjCecx2Q5oer7ZvyQC-A) - workerd error: TextEncoder is not defined without nodejs_compat

Problem outcome: unknown

Search: node error ERR_PACKAGE_PATH_NOT_EXPORTED: Package subpath not defined by exports

Public search query: node error ERR_PACKAGE_PATH_NOT_EXPORTED: Package subpath not defined by exports

Problem outcome: unknown

vite build error: Failed to resolve import - Does the file exist after webpack to vite migration

Fixes Vite 'Failed to resolve import ... Does the file exist?' after migrating from webpack. Use when the dev server or build fails on imports webpack used to resolve. Key trigger: the failing specifier is a Node builtin, a webpack alias, or a path webpack resolved leniently.