devs:deps-core
Comprehensive dependency management expertise covering TypeScript (npm, yarn, pnpm, bun), Rust (cargo), and Python (pip, poetry, uv). Use when working on projects requiring: (1) Dependency auditing and listing, (2) Checking for outdated packages, (3) Security vulnerability scanning, (4) Finding release notes and changelogs, (5) Preparing upgrade reports with breaking change analysis, (6) Inspecting transient dependencies in lock files, (7) Installing or uninstalling packages, (8) Clearing package caches, (9) Monorepo workspace dependency management, or (10) Cross-ecosystem dependency health checks.
What this skill does
# Dependency Management Comprehensive guidance for managing dependencies across TypeScript, Rust, and Python ecosystems. ## Core Principle **Commands over inference.** Always run the actual package manager command to get information rather than reading manifest or lock files and inferring state. The package manager is the authority on what is installed, what is outdated, and what is vulnerable. - `npm ls` tells you what is installed — `package.json` tells you what should be installed. These can differ. - `cargo tree` shows the resolved dependency graph — `Cargo.toml` shows declared dependencies. - `pip list` shows what is in the environment — `requirements.txt` shows what was requested. Reading manifest files is useful for understanding project structure and intent, but command output is the source of truth for current state. ## Ecosystem Detection If you are dispatched with a specific ecosystem (e.g., "typescript"), skip detection and load the relevant reference directly. If you need to detect the ecosystem, scan the project root for these files: | Files Found | Ecosystem | Package Manager | |---|---|---| | `package.json` + `package-lock.json` | TypeScript/JS | npm | | `package.json` + `yarn.lock` | TypeScript/JS | yarn | | `package.json` + `pnpm-lock.yaml` | TypeScript/JS | pnpm | | `package.json` + `bun.lockb` | TypeScript/JS | bun | | `package.json` (no lock file) | TypeScript/JS | npm (default, warn about missing lock file) | | `Cargo.toml` | Rust | cargo | | `pyproject.toml` with `[tool.poetry]` section | Python | poetry | | `pyproject.toml` with `[tool.uv]` section or `uv.lock` present | Python | uv | | `pyproject.toml` (no poetry/uv markers) | Python | pip | | `requirements.txt` (no `pyproject.toml`) | Python | pip | ## Monorepo Detection Check for workspace configurations: | Indicator | Type | |---|---| | `package.json` with `"workspaces"` field | npm/yarn workspace | | `pnpm-workspace.yaml` | pnpm workspace | | `Cargo.toml` with `[workspace]` section | cargo workspace | When a monorepo is detected: - Report it to the user - Ask whether to operate on the workspace root or a specific package (unless already scoped) - Use workspace-aware commands where available ## Task Reference Once you know the ecosystem, load the appropriate reference file for specific commands: | Task | What It Does | Reference | |---|---|---| | **Locate dependencies** | List all direct and dev dependencies from manifest files | [typescript.md](references/typescript.md), [rust.md](references/rust.md), [python.md](references/python.md) | | **Check for updates** | Compare installed versions against latest available | Per-ecosystem reference | | **Security audit** | Scan for known vulnerabilities (CVEs, advisories) | Per-ecosystem reference | | **Find release notes** | Locate changelogs or release notes for a package version | Per-ecosystem reference | | **Upgrade report** | Identify breaking changes, deprecated APIs, migration guides | Per-ecosystem reference | | **Transient dependencies** | Inspect lock files and dependency trees for indirect deps | Per-ecosystem reference | | **List installed** | Show what is actually installed (not just declared) | Per-ecosystem reference | | **Install / uninstall** | Add or remove packages with correct flags | Per-ecosystem reference | | **Clear caches** | Clean package manager caches and stores | Per-ecosystem reference | ## Additional Principles - **Security audits before upgrades** — know what is vulnerable before changing versions - **Never upgrade without understanding breaking changes** — check changelogs first - **Lock file changes should be committed separately** from code changes when possible - **Prefer exact versions in applications**, semver ranges in libraries - **Check the lock file, not just the manifest** — what is declared and what is installed can differ
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.