helderberto/agent-skills

deps-audit

Check dependencies for known vulnerabilities and staleness.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/helderberto/agent-skills --skill deps-audit

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Dependency Audit

Detect the package manager from its lockfile and run that ecosystem's audit + outdated tooling. Prefer the project's own audit task if it defines one. Never assume npm.

EcosystemLockfileAuditOutdated
npmpackage-lock.jsonnpm auditnpm outdated
pnpmpnpm-lock.yamlpnpm auditpnpm outdated
yarnyarn.lockyarn npm audit (berry) / yarn audityarn outdated
Pythonrequirements*.txt / uv.lock / poetry.lockpip-auditpip list --outdated
Gogo.sumgovulncheck ./...go list -m -u all
RustCargo.lockcargo auditcargo outdated

Audit tool missing → say which to install and stop. Lockfile missing → install to generate it, then retry.

Report

  1. Vulnerabilities, critical/high first: package@version, advisory id (CVE/GHSA/RUSTSEC), one line, the ecosystem's fix command.
  2. Outdated packages: package / current / latest / major vs minor.
  3. Obviously unused deps (grep imports in the source dir).

Action by severity: critical → fix now, blocks merge; high → before next release; moderate → this sprint; low → when convenient. Then major updates > unused > minor.

Related by task

from this repository

More skills

All skills
helderberto
Community

codebase-design

Shared vocabulary for designing deep modules. Use when designing or improving a module's interface, placing a seam, making code more testable, or when another skill needs it. Don't use for codebase-wide audits (/architecture-audit) or UI components (/frontend-ui-engineering).

installs
1
GitHub stars
17
Updated
Oct 19
helderberto
Community

debug

Disciplined diagnosis loop for hard bugs and performance regressions. Use when user says "diagnose" or "debug this", or reports something broken, throwing, failing, or slow. Don't use to build a feature or fix an understood bug test-first (/tdd).

installs
1
GitHub stars
17
Updated
Oct 19
helderberto
Community

frontend-ui-engineering

Front-load UI construction decisions — component boundary and prop API, state placement, required states, responsiveness, accessibility. Use when creating or refactoring a component, page, or design-system primitive. Don't use for pure logic (/tdd), throwaway exploration (/prototype), or auditing finished UI (/a11y-audit).

installs
1
GitHub stars
17
Updated
Oct 19
helderberto
Community

harden

Harden code where untrusted input enters the system. Use when implementing auth, handling user input, storing sensitive data, integrating external APIs, adding file uploads or LLM features, or crossing any trust boundary. Don't use for secret scanning (/safe-repo) or dependency CVEs (/deps-audit).

installs
1
GitHub stars
17
Updated
Oct 19