DevOps & Cloud

Deployment, cloud, containers, CI/CD, monitoring, and infrastructure

skills in category: 19,580
pages available: 816

Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.

Open in full browser

Browse devops & cloud skills

Showing 1,873–1,896 of 19,580 skills

Docker Project ContainerizationAUse when a task involves containerizing an existing application with a maintainable Docker image and a reproducible local workflow to identify the intended outcome, affected account or artifact, exact product version, sensitive data, and permission boundary before acting. Use current primary documentation for version-sensitive details, produce a reviewable result, and verify it against explicit criteria. Trigger for planning, configuration, implementation, or troubleshooting in this focused a...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Registry Immutability Threshold Rule CheckAUse when a container registry tag and retention controls decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the registry mutation-risk review showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; critical releases remain retrievable by digest and write authority is clearly bounded. Use configured search,...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Registry Immutability Source Provenance LedgerAUse when a decision about container registry tag and retention controls depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the registry mutation-risk review. Success means each material claim has a source, version/date, location, and confidence note; critical releases remain retrievable by digest and write authority is clearly bounded. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and author...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Registry Immutability Scope Intake GateAUse when a new container registry tag and retention controls request needs a bounded work scope to produce a scoped intake card for the registry mutation-risk review. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; critical releases remain retrievable by digest and write authority is clearly bounded. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Registry Immutability Scenario Sensitivity MatrixAUse when the container registry tag and retention controls team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the registry mutation-risk review with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; critical releases remain retrievable by digest and write authority is clearly bounded. Use configured search, fetch, read, browser, te...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Registry Immutability Recovery Readiness DrillAUse when the container registry tag and retention controls workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the registry mutation-risk review with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; critical releases remain retrievable by digest and write authority is clearly bounded. Use configured search, fetch, ...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Registry Immutability Exception Triage QueueAUse when the container registry tag and retention controls workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the registry mutation-risk review with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; critical releases remain retrievable by digest and write authority is clearly bounded. Use configured search, fetch, read, brows...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Registry Immutability Completeness ReconciliationAUse when the container registry tag and retention controls workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the registry mutation-risk review with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; critical releases remain retrievable by digest and write authority is clearly bounded. Use configured search, fetch...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Registry Immutability Closeout Handoff LedgerAUse when a container registry tag and retention controls work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the registry mutation-risk review with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; critical releases remain retrievable by digest and write authority is clearly bounded. Use configured search, fetch, read, browse...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Registry Immutability Change Impact TraceAUse when a version, rule, source, or stakeholder change may affect container registry tag and retention controls to produce a before/after change record and impact map for the registry mutation-risk review. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; critical releases remain retrievable by digest and write authority is clearly bounded. Use configured search, fetch, read, browser, test, and write capabilit...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Registry Immutability Approval Evidence PacketAUse when a container registry tag and retention controls result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the registry mutation-risk review containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; critical releases remain retrievable by digest and write authority is clearly bounded. Use configured sear...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Promotion Chain Threshold Rule CheckAUse when a container artifact promotion and rollback decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the image-promotion chain record showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; each environment references the approved immutable digest and rollback remains a reviewed proposal. Use configured...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Promotion Chain Source Provenance LedgerAUse when a decision about container artifact promotion and rollback depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the image-promotion chain record. Success means each material claim has a source, version/date, location, and confidence note; each environment references the approved immutable digest and rollback remains a reviewed proposal. Use configured search, fetch, read, browser, test, and write capabilities only when relevant an...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Promotion Chain Scope Intake GateAUse when a new container artifact promotion and rollback request needs a bounded work scope to produce a scoped intake card for the image-promotion chain record. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each environment references the approved immutable digest and rollback remains a reviewed proposal. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidenc...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Promotion Chain Scenario Sensitivity MatrixAUse when the container artifact promotion and rollback team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the image-promotion chain record with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each environment references the approved immutable digest and rollback remains a reviewed proposal. Use configured search, fetch, read, bro...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Promotion Chain Recovery Readiness DrillAUse when the container artifact promotion and rollback workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the image-promotion chain record with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; each environment references the approved immutable digest and rollback remains a reviewed proposal. Use configured search,...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Promotion Chain Exception Triage QueueAUse when the container artifact promotion and rollback workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the image-promotion chain record with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; each environment references the approved immutable digest and rollback remains a reviewed proposal. Use configured search, fetch, rea...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Promotion Chain Completeness ReconciliationAUse when the container artifact promotion and rollback workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the image-promotion chain record with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; each environment references the approved immutable digest and rollback remains a reviewed proposal. Use configured searc...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Promotion Chain Closeout Handoff LedgerAUse when a container artifact promotion and rollback work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the image-promotion chain record with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; each environment references the approved immutable digest and rollback remains a reviewed proposal. Use configured search, fetch, read...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Promotion Chain Change Impact TraceAUse when a version, rule, source, or stakeholder change may affect container artifact promotion and rollback to produce a before/after change record and impact map for the image-promotion chain record. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each environment references the approved immutable digest and rollback remains a reviewed proposal. Use configured search, fetch, read, browser, test, and write c...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Promotion Chain Approval Evidence PacketAUse when a container artifact promotion and rollback result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the image-promotion chain record containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; each environment references the approved immutable digest and rollback remains a reviewed proposal. Use configu...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Platform Parity Threshold Rule CheckAUse when a multi-platform image parity decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the platform manifest comparison showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; each declared platform resolves to the intended artifact and differences are explained. Use configured search, fetch, read, brow...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Platform Parity Source Provenance LedgerAUse when a decision about multi-platform image parity depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the platform manifest comparison. Success means each material claim has a source, version/date, location, and confidence note; each declared platform resolves to the intended artifact and differences are explained. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evide...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Platform Parity Scope Intake GateAUse when a new multi-platform image parity request needs a bounded work scope to produce a scoped intake card for the platform manifest comparison. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each declared platform resolves to the intended artifact and differences are explained. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to thr...devopsrustgoVotes: 0GitHub stars: 2