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,897–1,920 of 19,580 skills

Container Assurance Platform Parity Scenario Sensitivity MatrixAUse when the multi-platform image parity team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the platform manifest comparison with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each declared platform resolves to the intended artifact and differences are explained. Use configured search, fetch, read, browser, test, and write capa...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Platform Parity Recovery Readiness DrillAUse when the multi-platform image parity workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the platform manifest comparison 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 declared platform resolves to the intended artifact and differences are explained. Use configured search, fetch, read, browser, tes...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Platform Parity Exception Triage QueueAUse when the multi-platform image parity workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the platform manifest comparison 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 declared platform resolves to the intended artifact and differences are explained. Use configured search, fetch, read, browser, test, and writ...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Platform Parity Completeness ReconciliationAUse when the multi-platform image parity workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the platform manifest comparison 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 declared platform resolves to the intended artifact and differences are explained. Use configured search, fetch, read, browser, t...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Platform Parity Closeout Handoff LedgerAUse when a multi-platform image parity work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the platform manifest comparison 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 declared platform resolves to the intended artifact and differences are explained. Use configured search, fetch, read, browser, test, and write...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Platform Parity Change Impact TraceAUse when a version, rule, source, or stakeholder change may affect multi-platform image parity to produce a before/after change record and impact map for the platform manifest comparison. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each declared platform resolves to the intended artifact and differences are explained. Use configured search, fetch, read, browser, test, and write capabilities only when rele...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Build Inputs Threshold Rule CheckAUse when a container build-input provenance decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the build-input manifest 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; the manifest captures material inputs and unexplained network-fetched inputs are flagged. Use configured search, fetch, read...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Build Inputs Source Provenance LedgerAUse when a decision about container build-input provenance depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the build-input manifest review. Success means each material claim has a source, version/date, location, and confidence note; the manifest captures material inputs and unexplained network-fetched inputs are flagged. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Build Inputs Scope Intake GateAUse when a new container build-input provenance request needs a bounded work scope to produce a scoped intake card for the build-input manifest review. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the manifest captures material inputs and unexplained network-fetched inputs are flagged. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement ...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Build Inputs Scenario Sensitivity MatrixAUse when the container build-input provenance team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the build-input manifest review with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the manifest captures material inputs and unexplained network-fetched inputs are flagged. Use configured search, fetch, read, browser, test, and writ...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Build Inputs Recovery Readiness DrillAUse when the container build-input provenance workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the build-input manifest 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; the manifest captures material inputs and unexplained network-fetched inputs are flagged. Use configured search, fetch, read, browse...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Build Inputs Exception Triage QueueAUse when the container build-input provenance workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the build-input manifest 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; the manifest captures material inputs and unexplained network-fetched inputs are flagged. Use configured search, fetch, read, browser, test, an...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Build Inputs Completeness ReconciliationAUse when the container build-input provenance workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the build-input manifest 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; the manifest captures material inputs and unexplained network-fetched inputs are flagged. Use configured search, fetch, read, brow...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Build Inputs Closeout Handoff LedgerAUse when a container build-input provenance work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the build-input manifest 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; the manifest captures material inputs and unexplained network-fetched inputs are flagged. Use configured search, fetch, read, browser, test, and...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Build Inputs Change Impact TraceAUse when a version, rule, source, or stakeholder change may affect container build-input provenance to produce a before/after change record and impact map for the build-input manifest review. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the manifest captures material inputs and unexplained network-fetched inputs are flagged. Use configured search, fetch, read, browser, test, and write capabilities only whe...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Base Digest Threshold Rule CheckAUse when a container base-image identity decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the base-image provenance ledger 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; the tested base image is pinned and attributable without relying on a mutable tag. Use configured search, fetch, read, browser...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Base Digest Source Provenance LedgerAUse when a decision about container base-image identity depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the base-image provenance ledger. Success means each material claim has a source, version/date, location, and confidence note; the tested base image is pinned and attributable without relying on a mutable tag. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Base Digest Scope Intake GateAUse when a new container base-image identity request needs a bounded work scope to produce a scoped intake card for the base-image provenance ledger. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the tested base image is pinned and attributable without relying on a mutable tag. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three ...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Base Digest Scenario Sensitivity MatrixAUse when the container base-image identity team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the base-image provenance ledger with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the tested base image is pinned and attributable without relying on a mutable tag. Use configured search, fetch, read, browser, test, and write capabil...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Base Digest Recovery Readiness DrillAUse when the container base-image identity workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the base-image provenance ledger 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; the tested base image is pinned and attributable without relying on a mutable tag. Use configured search, fetch, read, browser, test, ...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Base Digest Exception Triage QueueAUse when the container base-image identity workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the base-image provenance ledger 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; the tested base image is pinned and attributable without relying on a mutable tag. Use configured search, fetch, read, browser, test, and write c...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Base Digest Completeness ReconciliationAUse when the container base-image identity workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the base-image provenance ledger 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; the tested base image is pinned and attributable without relying on a mutable tag. Use configured search, fetch, read, browser, test...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Base Digest Closeout Handoff LedgerAUse when a container base-image identity work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the base-image provenance ledger 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; the tested base image is pinned and attributable without relying on a mutable tag. Use configured search, fetch, read, browser, test, and write ca...devopsrustgoVotes: 0GitHub stars: 2
Container Assurance Base Digest Change Impact TraceAUse when a version, rule, source, or stakeholder change may affect container base-image identity to produce a before/after change record and impact map for the base-image provenance ledger. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the tested base image is pinned and attributable without relying on a mutable tag. Use configured search, fetch, read, browser, test, and write capabilities only when relevan...devopsrustgoVotes: 0GitHub stars: 2