convert-to-docker

Validate Docker availability, detect runtime drift, and build-test Guardian Core containers.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/guardian-intelligence/guardian-core --skill convert-to-docker-guardian-intelligence
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: convert-to-docker
Source: https://github.com/guardian-intelligence/guardian-core/tree/main/.claude/skills/convert-to-docker
Command: npx skills add https://github.com/guardian-intelligence/guardian-core --skill convert-to-docker-guardian-intelligence

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guardian Core often requires Docker-based deployment; this skill verifies Docker readiness and eliminates runtime drift to ensure consistent, containerized operation across environments.

Core Features & Use Cases

  • Verify Docker availability on the host (docker --version, docker info).
  • Detect runtime command drift across the project using search patterns against container/system/run/images references.
  • Validate Docker image build and perform a smoke test to confirm container responsiveness.
  • Validate documentation and skill references align with Docker-based deployment.

Quick Start

Run the following steps to verify Docker alignment for Guardian Core.

  • Check Docker is installed and running: docker --version && docker info
  • Scan for runtime command drift: rg -n 'container\s+(system|run|builder|images)' -S . --hidden --glob '!.git'
  • Build and smoke test: ./container/build.sh and docker run -i --entrypoint /bin/echo guardian-core-agent:latest "Container OK"
  • Confirm docs and skills reference Docker usage: rg -n "Docker|docker" -S README.md docs CLAUDE.md .claude/skills --hidden

Frequently Asked Questions about convert-to-docker

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

FAQPage Schema
How do I validate my Docker setup for Guardian Core deployment?

Runtime command drift occurs when legacy execution commands conflict with Docker-based deployment. You can detect this drift by searching your project for patterns matching `container\s+(system|run|builder|images)` to identify and clean outdated references.

What steps are needed to convert a project to Docker and test the container?

Converting to Docker requires checking Docker availability, scanning for runtime drift, building the image via `./container/build.sh`, and running a smoke test like `docker run -i --entrypoint /bin/echo guardian-core-agent:latest "Container OK"` to verify responsiveness.

Does Guardian Core require Docker to run consistently across environments?

Yes, Guardian Core requires Docker-based deployment to eliminate runtime drift and ensure consistent, containerized operation across different environments. This skill verifies Docker readiness and enforces that alignment.

Why does my Guardian Core Docker documentation audit fail consistency checks?

Documentation consistency checks fail when project files do not align with Docker-based deployment. You must audit README.md, docs, CLAUDE.md, and .claude/skills directories to ensure all references match Docker usage.

Can I clean up legacy runtime drift without breaking my Docker container?

Yes, you can clean legacy runtime drift by searching for outdated container system or run references and removing them. Building and smoke testing the Guardian Core Docker image afterward ensures the container remains responsive and unbroken.