A small but telling release landed on September 23, 2026: docker/skills tagged version 0.3.0 and, over the same few days, reorganised its installation docs by distribution model and retired a duplicate docs site after migrating to Docker Docs. The repository is a set of portable SKILL.md directories that compliant coding agents discover automatically. It covers containerising projects, build strategies, Compose patterns, running and deploying Docker Agents, the lifecycle, networking and credentials of Docker Sandboxes, and a docker-destructive-guardrails skill.
The same week, NVIDIA/skills, which describes itself as agent skills for NVIDIA products that install into Claude Code, Codex and other coding agents, added BioNeMo Libraries to its product taxonomy and synced BioNeMo skills on September 23, then Jetson device skills on September 24. Anthropic's official plugin directory, anthropics/claude-plugins-official, is also on this week's trending lists.
The shift here is ownership. Until recently, what a coding agent "knew" about Docker or CUDA came from pretraining data and whatever instructions a team pasted into its own repo. Vendor-maintained skill packs make the vendor responsible for current, correct usage guidance, versioned and released like an SDK. That fixes a real failure mode: agents confidently writing Dockerfiles or build flags that were best practice two years ago. A skill that encodes destructive-operation guardrails is also a safety control that the vendor, not each user, keeps current.
It also creates a new supply-chain surface. A skill is instructions an agent will follow with the developer's permissions, so installing a skill pack deserves the same scrutiny as adding a dependency: pin versions, read the diff on upgrade, and prefer vendor-owned repos over look-alike forks. Watch whether the agent harnesses add signing or provenance checks for skills. Right now, discovery through standard paths is convenient precisely because it is unauthenticated.
Official vendor skill packs make agent know-how versioned and vendor-maintained -- a real quality gain -- but a skill is executable guidance, so treat skill packs as dependencies with pinning, review and provenance.