Skills deployment-procedures
๐Ÿ“ฆ

deployment-procedures

Content revision r2 Safe โš™๏ธ External commands

Plan Safer Production Deployments

Production releases can fail when teams skip preparation, monitoring, or rollback planning. This skill structures deployment decisions around verification, controlled execution, and recovery.

Supports: Claude Codex Code(CC)
๐Ÿฅ‰ 78 Bronze

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-procedures" from https://skillstore.io/skills/sickn33-deployment-procedures.md and its manifest at https://skillstore.io/api/skills/sickn33-deployment-procedures/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

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

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Test it

Using "deployment-procedures". Prepare a checklist for a web application release on a managed platform.

Expected outcome:

  • Confirm tests, review approval, and the production build.
  • Verify environment settings, migration readiness, backups, and rollback ownership.
  • Deploy while health dashboards and error logs remain visible.
  • Test critical user flows and observe performance before confirming the release.

Using "deployment-procedures". Choose a strategy for a high-risk change that needs rapid rollback.

Expected outcome:

Use blue-green deployment when parallel environments are affordable. It supports validation before traffic switching and rapid recovery by restoring the previous environment.

Using "deployment-procedures". Define rollback gates for a customer-facing service.

Expected outcome:

  • Rollback immediately if the service becomes unavailable or critical user flows fail.
  • Rollback when new critical errors exceed the agreed threshold.
  • Evaluate rollback when performance degrades by more than 50 percent.
  • Assign one decision owner and record the outcome for later review.

Security Audit

Safe
v5 โ€ข 7/23/2026 Open versioned report

All three static findings are false positives caused by Markdown code fences around text diagrams in SKILL.md. The skill contains deployment guidance but no executable scripts, command invocation logic, prompt injection, credential handling, or exfiltration behavior. No semantic security findings were identified.

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

Risk Factors

โš™๏ธ External commands (3)
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
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-procedures/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-procedures/security.svg)](https://skillstore.io/skills/sickn33-deployment-procedures?utm_source=security_passport_badge)

HTML badge

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

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-deployment-procedures.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-procedures security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-deployment-procedures/audits/5

BibTeX citation

@techreport{sickn33-sickn33-deployment-procedures-2026, author = {sickn33}, title = {deployment-procedures security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-deployment-procedures/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-procedures 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-procedures/audits/5" identifiers: - type: other value: "skillstore:sickn33-deployment-procedures:audit:5" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance

What You Can Build

Prepare a routine release

Create a platform-aware checklist with preparation, backup, deployment, verification, and communication steps.

Select a rollout strategy

Compare rolling, blue-green, and canary approaches against service risk and rollback needs.

Define incident recovery gates

Set measurable rollback triggers and organize investigation priorities for a production release.

Try These Prompts

Create a deployment checklist
Create a deployment checklist for [application] on [platform]. Include preparation, backup, deployment, verification, rollback, monitoring, and team communication.
Choose a rollout strategy
Compare rolling, blue-green, and canary deployment for [service]. Recommend one based on [risk], [traffic], [capacity], and [rollback requirement].
Define verification and rollback gates
Design post-deployment checks for [critical flows]. Define measurable success thresholds, observation windows, rollback triggers, owners, and communication steps.
Review an end-to-end release plan
Review this release plan for [system]: [plan]. Identify missing prerequisites, unsafe assumptions, migration risks, monitoring gaps, and rollback weaknesses. Propose a safer sequence.

Best Practices

  • Provide the platform, architecture, change scope, maintenance window, and available rollback method.
  • Define measurable health, error, flow, and performance thresholds before deployment begins.
  • Test backups and rollback procedures before relying on them during an incident.

Avoid

  • Requesting one universal command sequence without describing the platform or application.
  • Deploying before tests, backups, monitoring, communication, and rollback ownership are ready.
  • Treating a restart as sufficient investigation when service health remains uncertain.

Frequently Asked Questions

Does this skill deploy applications automatically?
No. It provides planning and decision guidance but does not run commands or access infrastructure.
Which platforms does it cover?
It discusses managed hosting, VPS deployments, Docker, Kubernetes, static hosting, microservices, and serverless systems at a general level.
Can it plan database migrations?
It can include migration readiness and rollback questions. It cannot validate migration safety or database compatibility.
Does it provide provider-specific commands?
No. The guidance emphasizes principles and must be adapted to each provider and environment.
How does it determine when to roll back?
It uses service availability, critical errors, user-flow failures, and performance degradation as decision signals.
What information should I provide?
Provide the platform, application type, change scope, risks, monitoring signals, rollback options, maintenance window, and responsible owners.

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

7 downloads ยท 104 views

File structure

๐Ÿ“„ SKILL.md

More from sickn33

View all
View all