All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Container Assurance Promotion Chain Change Impact TraceUse 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...Votes: 0GitHub stars: 2
- Container Assurance Promotion Chain Closeout Handoff LedgerUse 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...Votes: 0GitHub stars: 2
- Container Assurance Promotion Chain Completeness ReconciliationUse 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...Votes: 0GitHub stars: 2
- Container Assurance Promotion Chain Exception Triage QueueUse 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...Votes: 0GitHub stars: 2
- Container Assurance Promotion Chain Recovery Readiness DrillUse 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,...Votes: 0GitHub stars: 2
- Container Assurance Promotion Chain Scenario Sensitivity MatrixUse 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...Votes: 0GitHub stars: 2
- Container Assurance Promotion Chain Scope Intake GateUse 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...Votes: 0GitHub stars: 2
- Container Assurance Promotion Chain Source Provenance LedgerUse 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...Votes: 0GitHub stars: 2
- Container Assurance Promotion Chain Threshold Rule CheckUse 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...Votes: 0GitHub stars: 2
- Container Assurance Registry Immutability Approval Evidence PacketUse 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...Votes: 0GitHub stars: 2
- Container Assurance Registry Immutability Change Impact TraceUse 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...Votes: 0GitHub stars: 2
- Container Assurance Registry Immutability Closeout Handoff LedgerUse 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...Votes: 0GitHub stars: 2
- Container Assurance Registry Immutability Completeness ReconciliationUse 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...Votes: 0GitHub stars: 2
- Container Assurance Registry Immutability Exception Triage QueueUse 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...Votes: 0GitHub stars: 2
- Container Assurance Registry Immutability Recovery Readiness DrillUse 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, ...Votes: 0GitHub stars: 2
- Container Assurance Registry Immutability Scenario Sensitivity MatrixUse 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...Votes: 0GitHub stars: 2
- Container Assurance Registry Immutability Scope Intake GateUse 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...Votes: 0GitHub stars: 2
- Container Assurance Registry Immutability Source Provenance LedgerUse 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...Votes: 0GitHub stars: 2
- Container Assurance Registry Immutability Threshold Rule CheckUse 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,...Votes: 0GitHub stars: 2
- Container Assurance Runtime Capability Approval Evidence PacketUse when a container runtime capability drift result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the runtime privilege comparison 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; the test runtime does not exceed approved privileges and deviations are owner-routed. Use configured search, fetch, re...Votes: 0GitHub stars: 2
- Container Assurance Runtime Capability Change Impact TraceUse when a version, rule, source, or stakeholder change may affect container runtime capability drift to produce a before/after change record and impact map for the runtime privilege comparison. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the test runtime does not exceed approved privileges and deviations are owner-routed. Use configured search, fetch, read, browser, test, and write capabilities only when...Votes: 0GitHub stars: 2
- Container Assurance Runtime Capability Closeout Handoff LedgerUse when a container runtime capability drift work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the runtime privilege 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; the test runtime does not exceed approved privileges and deviations are owner-routed. Use configured search, fetch, read, browser, test, and ...Votes: 0GitHub stars: 2
- Container Assurance Runtime Capability Completeness ReconciliationUse when the container runtime capability drift workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the runtime privilege 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; the test runtime does not exceed approved privileges and deviations are owner-routed. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2
- Container Assurance Runtime Capability Exception Triage QueueUse when the container runtime capability drift workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the runtime privilege 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; the test runtime does not exceed approved privileges and deviations are owner-routed. Use configured search, fetch, read, browser, test, and...Votes: 0GitHub stars: 2
- Container Assurance Runtime Capability Recovery Readiness DrillUse when the container runtime capability drift workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the runtime privilege 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; the test runtime does not exceed approved privileges and deviations are owner-routed. Use configured search, fetch, read, browser...Votes: 0GitHub stars: 2
- Container Assurance Runtime Capability Scenario Sensitivity MatrixUse when the container runtime capability drift team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the runtime privilege comparison with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the test runtime does not exceed approved privileges and deviations are owner-routed. Use configured search, fetch, read, browser, test, and write...Votes: 0GitHub stars: 2
- Container Assurance Runtime Capability Scope Intake GateUse when a new container runtime capability drift request needs a bounded work scope to produce a scoped intake card for the runtime privilege comparison. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the test runtime does not exceed approved privileges and deviations are owner-routed. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement t...Votes: 0GitHub stars: 2
- Container Assurance Runtime Capability Source Provenance LedgerUse when a decision about container runtime capability drift depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the runtime privilege comparison. Success means each material claim has a source, version/date, location, and confidence note; the test runtime does not exceed approved privileges and deviations are owner-routed. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record ...Votes: 0GitHub stars: 2
- Container Assurance Runtime Capability Threshold Rule CheckUse when a container runtime capability drift decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the runtime privilege 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; the test runtime does not exceed approved privileges and deviations are owner-routed. Use configured search, fetch, read,...Votes: 0GitHub stars: 2
- Container Assurance Sandbox Egress Approval Evidence PacketUse when a container sandbox network egress result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the sandbox egress evidence sheet 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; only declared destinations are reachable in the test and credentials do not leak through denied paths. Use configured s...Votes: 0GitHub stars: 2
- Container Assurance Sandbox Egress Change Impact TraceUse when a version, rule, source, or stakeholder change may affect container sandbox network egress to produce a before/after change record and impact map for the sandbox egress evidence sheet. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; only declared destinations are reachable in the test and credentials do not leak through denied paths. Use configured search, fetch, read, browser, test, and write capabi...Votes: 0GitHub stars: 2
- Container Assurance Sandbox Egress Closeout Handoff LedgerUse when a container sandbox network egress work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the sandbox egress evidence sheet 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; only declared destinations are reachable in the test and credentials do not leak through denied paths. Use configured search, fetch, read, bro...Votes: 0GitHub stars: 2
- Container Assurance Sandbox Egress Completeness ReconciliationUse when the container sandbox network egress workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the sandbox egress evidence sheet 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; only declared destinations are reachable in the test and credentials do not leak through denied paths. Use configured search, fe...Votes: 0GitHub stars: 2
- Container Assurance Sandbox Egress Exception Triage QueueUse when the container sandbox network egress workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the sandbox egress evidence sheet 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; only declared destinations are reachable in the test and credentials do not leak through denied paths. Use configured search, fetch, read, br...Votes: 0GitHub stars: 2
- Container Assurance Sandbox Egress Recovery Readiness DrillUse when the container sandbox network egress workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the sandbox egress evidence sheet 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; only declared destinations are reachable in the test and credentials do not leak through denied paths. Use configured search, fetc...Votes: 0GitHub stars: 2
- Container Assurance Sandbox Egress Scenario Sensitivity MatrixUse when the container sandbox network egress team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the sandbox egress evidence sheet with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; only declared destinations are reachable in the test and credentials do not leak through denied paths. Use configured search, fetch, read, browser,...Votes: 0GitHub stars: 2
- Container Assurance Sandbox Egress Scope Intake GateUse when a new container sandbox network egress request needs a bounded work scope to produce a scoped intake card for the sandbox egress evidence sheet. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; only declared destinations are reachable in the test and credentials do not leak through denied paths. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, li...Votes: 0GitHub stars: 2
- Container Assurance Sandbox Egress Source Provenance LedgerUse when a decision about container sandbox network egress depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the sandbox egress evidence sheet. Success means each material claim has a source, version/date, location, and confidence note; only declared destinations are reachable in the test and credentials do not leak through denied paths. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and aut...Votes: 0GitHub stars: 2
- Container Assurance Sandbox Egress Threshold Rule CheckUse when a container sandbox network egress decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the sandbox egress evidence sheet 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; only declared destinations are reachable in the test and credentials do not leak through denied paths. Use configured sear...Votes: 0GitHub stars: 2
- Container Assurance Sbom Subject Approval Evidence PacketUse when a container SBOM subject binding result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the SBOM-to-image binding 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; the SBOM subject matches the exact image digest and platform under review. Use configured search, fetch, read, browser, te...Votes: 0GitHub stars: 2
- Container Assurance Sbom Subject Change Impact TraceUse when a version, rule, source, or stakeholder change may affect container SBOM subject binding to produce a before/after change record and impact map for the SBOM-to-image binding record. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the SBOM subject matches the exact image digest and platform under review. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and a...Votes: 0GitHub stars: 2
- Container Assurance Sbom Subject Closeout Handoff LedgerUse when a container SBOM subject binding work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the SBOM-to-image binding 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; the SBOM subject matches the exact image digest and platform under review. Use configured search, fetch, read, browser, test, and write capabilit...Votes: 0GitHub stars: 2
- Container Assurance Sbom Subject Completeness ReconciliationUse when the container SBOM subject binding workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the SBOM-to-image binding 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; the SBOM subject matches the exact image digest and platform under review. Use configured search, fetch, read, browser, test, and w...Votes: 0GitHub stars: 2
- Container Assurance Sbom Subject Exception Triage QueueUse when the container SBOM subject binding workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the SBOM-to-image binding 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; the SBOM subject matches the exact image digest and platform under review. Use configured search, fetch, read, browser, test, and write capabili...Votes: 0GitHub stars: 2
- Container Assurance Sbom Subject Recovery Readiness DrillUse when the container SBOM subject binding workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the SBOM-to-image binding 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; the SBOM subject matches the exact image digest and platform under review. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2
- Container Assurance Sbom Subject Scenario Sensitivity MatrixUse when the container SBOM subject binding team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the SBOM-to-image binding record with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the SBOM subject matches the exact image digest and platform under review. Use configured search, fetch, read, browser, test, and write capabilities o...Votes: 0GitHub stars: 2
- Container Assurance Sbom Subject Scope Intake GateUse when a new container SBOM subject binding request needs a bounded work scope to produce a scoped intake card for the SBOM-to-image binding record. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the SBOM subject matches the exact image digest and platform under review. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused...Votes: 0GitHub stars: 2
- Container Assurance Sbom Subject Source Provenance LedgerUse when a decision about container SBOM subject binding depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the SBOM-to-image binding record. Success means each material claim has a source, version/date, location, and confidence note; the SBOM subject matches the exact image digest and platform under review. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit...Votes: 0GitHub stars: 2
- Container Assurance Sbom Subject Threshold Rule CheckUse when a container SBOM subject binding decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the SBOM-to-image binding 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; the SBOM subject matches the exact image digest and platform under review. Use configured search, fetch, read, browser, test,...Votes: 0GitHub stars: 2
- Docker Agent ConfigurationUse when a task involves authoring or reviewing a Docker Agent configuration for models, providers, tools, and multi-agent teams 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 are...Votes: 0GitHub stars: 2