safeguard

Classify deployment environments and determine Docker, Non-Docker, or Hybrid paradigms.

3|2|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/fluxforgeai/ARTEMIS --skill safeguard-fluxforgeai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: safeguard
Source: https://github.com/fluxforgeai/ARTEMIS/tree/main/.claude/skills/safeguard
Command: npx skills add https://github.com/fluxforgeai/ARTEMIS --skill safeguard-fluxforgeai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates evidence-based classification of a project's deployment environment (Profile Zero/A/B/C) and determines the deployment paradigm (Docker, Non-Docker, or Hybrid), producing a persistent profile consumed by downstream skills.

Core Features & Use Cases

  • Automated Detection Matrix: Scans repositories for 12 deployment indicators including Dockerfiles, compose files, CI/CD configs, SIGTERM handling, long-lived workers, health endpoints, and rollback mechanisms.
  • Three Modes: detect for full profiling and artifact generation, check for drift validation against an existing profile, and recommend for prioritized remediation guidance.
  • Persistent Artifacts & Safety: Writes a profile document to docs/analysis, updates .wrought safeguard fields, supports interactive clarification checkpoints, and optionally routes gaps into the findings pipeline.

Quick Start

Run /safeguard detect to scan the repository and generate an environment profile document.

Frequently Asked Questions about safeguard

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

FAQPage Schema
How do I classify a project's deployment environment using Docker and CI/CD indicators?

Classify a project's deployment environment by scanning repositories for 12 indicators including Dockerfiles, compose files, CI/CD configs, and SIGTERM handling to generate a persistent environment profile document.

What is the difference between Docker, Non-Docker, and Hybrid deployment paradigms?

Deployment paradigms are determined by detecting specific repository indicators; Docker relies on container files, Non-Docker uses process managers, and Hybrid combines both patterns to define the deployment strategy.

How do I validate deployment configuration drift against an existing environment profile?

Validate deployment drift by running a check mode that compares current repository indicators against an existing environment profile, ensuring your Docker and CI/CD configurations match the documented baseline.

Can I use automated detection for long-lived workers and health endpoints in my repository?

Automated detection supports scanning for long-lived workers, health endpoints, rollback mechanisms, and SIGTERM handling to accurately classify your deployment environment and generate remediation recommendations.

What steps are needed to generate remediation guidance for deployment environment gaps?

Generate remediation guidance by running a recommend mode that identifies deployment environment gaps and routes them into a findings pipeline, producing exportable recommendation documents for your project.

When should I not use automated deployment environment classification for my project?

Avoid automated deployment classification when a repository lacks deployment indicators like Dockerfiles, compose files, or CI/CD pipelines, as the scan requires these artifacts to determine the environment profile accurately.