validate-container-compliance

Name: validate-container-compliance
Availability: InStock
Author: Edgame

Validate container compliance with ModuleImplementationGuide standards and configuration rules.

Updated Aug 27, 2026

Search Tags:#security #compliance #container #config-validation #tenant-isolation #event-naming

Ready to run

npx skills add https://github.com/Edgame2/castiel2 --skill validate-container-compliance

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: validate-container-compliance
Source: https://github.com/Edgame2/castiel2/tree/main/.cursor/skills/validate-container-compliance
Command: npx skills add https://github.com/Edgame2/castiel2 --skill validate-container-compliance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures containers comply with defined rules and ModuleImplementationGuide standards, preventing misconfigurations and non-compliant deployments.

Core Features & Use Cases

No hardcoded values: detects port and URL hardcoding to enforce config via environment variables.
Tenant isolation: validates tenantId usage in queries and ensures proper request handling.
Configuration structure: checks presence and correct usage of config/default.yaml and config/schema.json.
Event naming convention: enforces domain.entity.action style for events.
Service-to-service auth patterns: validates Authorization headers and X-Tenant-ID usage for inter-service calls.
Error handling: requires AppError usage and proper HTTP status codes, with safe error reporting.

Quick Start

Run the validate-container-compliance skill to audit the current container codebase and flag non-conforming patterns.

Frequently Asked Questions about validate-container-compliance

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

FAQPage Schema

How do I check for hardcoded values and tenant isolation gaps before deploying a container?▼

Container compliance validation automatically detects hardcoded ports and URLs, verifies tenantId usage in queries, and enforces environment variable configuration to prevent misconfigurations before deployment.

What is the best way to enforce event naming conventions and service-to-service auth patterns in my codebase?▼

Event naming convention enforcement checks for domain.entity.action style events, while service-to-service auth validation inspects Authorization headers and X-Tenant-ID usage to secure inter-service communication patterns.

How do I validate required configuration files like default.yaml and schema.json during code review?▼

Configuration structure validation checks the presence and correct usage of config/default.yaml and config/schema.json files, ensuring your container configuration structure meets project guidelines during code review.

Does container compliance validation check for proper error handling and HTTP status codes?▼

Container compliance validation requires AppError usage and proper HTTP status codes with safe error reporting, ensuring your error handling patterns meet ModuleImplementationGuide standards.

Can I audit my existing container codebase for misconfigurations and non-conforming patterns?▼

You can audit your current container codebase to flag non-conforming patterns, catching misnamed events, weak service-to-service auth, and configuration gaps before they reach deployment.

When do I need to run container compliance checks in my deployment workflow?▼

Run container compliance checks during code review, container validation, and deployment readiness stages to catch hardcoded values, tenant isolation gaps, and misconfigurations before they impact production.