Skills deployment-validation-config-validate
๐Ÿ“ฆ

deployment-validation-config-validate

Content revision r2 High Risk โš™๏ธ External commands๐Ÿ“ Filesystem access๐Ÿ”‘ Env variables

Validate Deployment Configuration Safely

Configuration errors can cause failed deployments, security gaps, and inconsistent environments. This skill designs schemas, tests, migrations, runtime checks, and clear configuration documentation.

Supports: Claude Codex Code(CC)
โš ๏ธ 38 Poor

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "deployment-validation-config-validate" from https://skillstore.io/skills/sickn33-deployment-validation-config-validate.md and its manifest at https://skillstore.io/api/skills/sickn33-deployment-validation-config-validate/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Your Agent should still show its plan and request any confirmation required by the security policy.

Test it

Using "deployment-validation-config-validate". Review the production configuration for unsafe settings.

Expected outcome:

Assessment: Debug mode is forbidden, external URLs require HTTPS, passwords need stronger minimum lengths, and secret values must remain redacted.

Using "deployment-validation-config-validate". Plan validation for a database configuration.

Expected outcome:

Validation plan: Require hostname, port, database, user, password, and SSL status. Reject empty names, invalid ports, and incomplete SSL settings.

Using "deployment-validation-config-validate". Design a safe migration for a versioned configuration.

Expected outcome:

Migration plan: Validate the source version, apply ordered changes, validate the result, preserve rollback data, and stop on unknown versions.

Security Audit

High Risk
v5 โ€ข 7/23/2026 Open versioned report

Most command, environment, certificate, and reconnaissance alerts are syntax or identifier false positives. The guidance intentionally discovers and reads .env files and demonstrates persistent file watching. Its encryption example derives keys with a fixed salt, weakening password-based key isolation.

1
Files scanned
505
Lines analyzed
1
Review items
0
False positives ignored

Confirmed security concerns (2)

High
Environment file access
'**/*.ini', '**/*.env*', '**/config.js'
The analyzer explicitly discovers .env files, then reads discovered configuration content while scanning for secrets. Broad scope could expose credentials to the agent or its output.
Medium
Fixed Salt Weakens Derived Encryption Keys
The encryption example derives every key with the same literal PBKDF2 salt, enabling cross-installation key equality and more efficient password precomputation.
The PBKDF2 call directly contains the fixed salt string config-salt. No random salt generation or storage is demonstrated.
Capability review items (1)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

Medium
File system watching
const watcher = chokidar.watch(configPath, {
The example starts a persistent watcher on caller-supplied configPath and reloads changes. Without path boundaries, this can monitor and expose sensitive configuration data.
Audited by: codex View Audit History โ†’
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-deployment-validation-config-validate/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-deployment-validation-config-validate/security.svg)](https://skillstore.io/skills/sickn33-deployment-validation-config-validate?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-deployment-validation-config-validate?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-deployment-validation-config-validate/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-deployment-validation-config-validate.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA ยท BibTeX ยท CFF)

APA citation

sickn33. (2026). deployment-validation-config-validate security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-deployment-validation-config-validate/audits/5

BibTeX citation

@techreport{sickn33-sickn33-deployment-validation-config-validate-2026, author = {sickn33}, title = {deployment-validation-config-validate security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-deployment-validation-config-validate/audits/5}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "deployment-validation-config-validate security audit report (audit version 5)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-23" url: "https://skillstore.io/skills/sickn33-deployment-validation-config-validate/audits/5" identifiers: - type: other value: "skillstore:sickn33-deployment-validation-config-validate:audit:5" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium
55
Architecture
85
Maintainability
87
Content
70
Community
78
Spec Compliance

What You Can Build

Prepare a Deployment Gate

Create environment-aware schema checks and tests that reject unsafe configuration before release.

Add Typed Application Settings

Define required fields, formats, defaults, and useful validation errors for an application.

Review Configuration Security

Identify secret exposure, weak production defaults, unsafe URLs, and missing encryption controls.

Try These Prompts

Inventory Configuration Risks
Review configuration files under {{project_path}}. Identify formats, environments, missing validation, and consistency risks. Do not reveal secret values.
Design a Validation Schema
Create a validation plan for {{config_name}}. Define required fields, types, ranges, secure formats, defaults, and readable error messages.
Build Environment Tests
Design tests for development, staging, and production configuration. Cover valid settings, boundary values, forbidden production options, and missing secrets.
Plan Runtime Validation and Migration
Design runtime reload validation and migrations from {{current_version}} to {{target_version}}. Include rollback, path boundaries, secret handling, and failure behavior.

Best Practices

  • Approve a narrow configuration root and redact secret values before analysis or reporting.
  • Validate configurations before deployment, after migration, and before accepting runtime reloads.
  • Test environment rules with valid cases, boundary values, missing fields, and forbidden production settings.

Avoid

  • Do not scan an entire home directory or repository for environment files without explicit approval.
  • Do not copy illustrative encryption code into production without independent cryptographic review.
  • Do not reload invalid configuration or continue silently after production validation fails.

Frequently Asked Questions

Which configuration formats can this skill address?
It covers JSON, YAML, TOML, INI, environment files, and JavaScript configuration patterns.
Does it modify configuration files automatically?
Only when explicitly requested and permitted. Its primary output is analysis, validation design, tests, migrations, and documentation.
Can it create JSON Schema rules?
Yes. It can define required properties, types, formats, ranges, defaults, and validation error handling.
Does it support environment-specific validation?
Yes. It can distinguish development, staging, and production requirements such as HTTPS, debug restrictions, and password length.
Will secret values appear in the output?
They should not. Restrict file scope and request redacted findings that identify locations without exposing values.
Is the provided encryption example production-ready?
No. It uses a fixed salt and requires cryptographic review, key rotation planning, and stronger metadata validation.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Ref

f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526

Maintenance freshness

7/26/2026

Usage

9 downloads ยท 169 views

File structure

๐Ÿ“„ SKILL.md

More from sickn33

View all
View all