Docker API

Inspect and control local Docker containers via CLI commands.

6|3|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/lordmacu/nexo-rs --skill docker-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Docker API
Source: https://github.com/lordmacu/nexo-rs/tree/main/skills/docker-api
Command: npx skills add https://github.com/lordmacu/nexo-rs --skill docker-api

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires docker, and includes scripts (resource) components.

What problem does it solve?

This Skill allows users to inspect and control local Docker containers, streamlining container management tasks.

Core Features & Use Cases

  • Container Management: Inspect and control local Docker containers with commands like status, ps, inspect, logs, stats, start, stop, and restart.
  • Container Names: Valid container names are regex-validated to block shell injection.
  • Write-Gated Operations: Lifecycle actions (start/stop/restart) are gated by the DOCKER_API_ALLOW_WRITE environment variable.

Quick Start

Use the Docker API to get the status of a container: status container_name.

Frequently Asked Questions about Docker API

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage Docker container lifecycle locally?

Manage Docker container lifecycle locally by executing CLI commands to start, stop, and restart containers. The Docker API requires proper local configuration to execute these operations and monitor container status.

How do I check Docker container status and logs via command line?

Check Docker container status and logs by executing the `status`, `ps`, `logs`, and `stats` CLI commands. These inspect and monitor local Docker containers to provide operational visibility during runtime.

Do I need Docker installed to use this container management tool?

Yes, Docker must be installed and properly configured as a prerequisite. This tool interacts with local Docker containers using CLI commands, requiring direct access to the Docker environment.

How is shell injection blocked when inspecting Docker containers?

Shell injection is blocked by regex-validating all container names before executing Docker commands. This validation ensures that only properly formatted container names are processed during lifecycle operations.

Why are start, stop, and restart commands not working for my Docker containers?

Start, stop, and restart commands are write-gated and require the `DOCKER_API_ALLOW_WRITE` environment variable to be set. This safety mechanism prevents accidental container lifecycle changes.