All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Container Assurance Attestation Binding Change Impact TraceUse when a version, rule, source, or stakeholder change may affect container attestation subject binding to produce a before/after change record and impact map for the attestation verification worksheet. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the statement verifies against the exact artifact and expected policy, without treating signature presence alone as trust. Use configured search, fetch, read, b...Votes: 0GitHub stars: 2
- Container Assurance Attestation Binding Closeout Handoff LedgerUse when a container attestation subject binding work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the attestation verification worksheet 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 statement verifies against the exact artifact and expected policy, without treating signature presence alone as trust. Use confi...Votes: 0GitHub stars: 2
- Container Assurance Attestation Binding Completeness ReconciliationUse when the container attestation subject binding workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the attestation verification worksheet 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 statement verifies against the exact artifact and expected policy, without treating signature presence alone as tr...Votes: 0GitHub stars: 2
- Container Assurance Attestation Binding Exception Triage QueueUse when the container attestation subject binding workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the attestation verification worksheet 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 statement verifies against the exact artifact and expected policy, without treating signature presence alone as trust. Use conf...Votes: 0GitHub stars: 2
- Container Assurance Attestation Binding Recovery Readiness DrillUse when the container attestation subject binding workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the attestation verification worksheet 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 statement verifies against the exact artifact and expected policy, without treating signature presence alone as trus...Votes: 0GitHub stars: 2
- Container Assurance Attestation Binding Scenario Sensitivity MatrixUse when the container attestation subject binding team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the attestation verification worksheet with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the statement verifies against the exact artifact and expected policy, without treating signature presence alone as trust. Use configured...Votes: 0GitHub stars: 2
- Container Assurance Attestation Binding Scope Intake GateUse when a new container attestation subject binding request needs a bounded work scope to produce a scoped intake card for the attestation verification worksheet. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the statement verifies against the exact artifact and expected policy, without treating signature presence alone as trust. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and a...Votes: 0GitHub stars: 2
- Container Assurance Attestation Binding Source Provenance LedgerUse when a decision about container attestation subject binding depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the attestation verification worksheet. Success means each material claim has a source, version/date, location, and confidence note; the statement verifies against the exact artifact and expected policy, without treating signature presence alone as trust. Use configured search, fetch, read, browser, test, and write capabilit...Votes: 0GitHub stars: 2
- Container Assurance Attestation Binding Threshold Rule CheckUse when a container attestation subject binding decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the attestation verification worksheet 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 statement verifies against the exact artifact and expected policy, without treating signature presence alone...Votes: 0GitHub stars: 2
- Container Assurance Base Digest Approval Evidence PacketUse when a container base-image identity result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the base-image provenance ledger 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 tested base image is pinned and attributable without relying on a mutable tag. Use configured search, fetch, read, brow...Votes: 0GitHub stars: 2
- Container Assurance Base Digest Change Impact TraceUse 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...Votes: 0GitHub stars: 2
- Container Assurance Base Digest Closeout Handoff LedgerUse 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...Votes: 0GitHub stars: 2
- Container Assurance Base Digest Completeness ReconciliationUse 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...Votes: 0GitHub stars: 2
- Container Assurance Base Digest Exception Triage QueueUse 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...Votes: 0GitHub stars: 2
- Container Assurance Base Digest Recovery Readiness DrillUse 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, ...Votes: 0GitHub stars: 2
- Container Assurance Base Digest Scenario Sensitivity MatrixUse 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...Votes: 0GitHub stars: 2
- Container Assurance Base Digest Scope Intake GateUse 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 ...Votes: 0GitHub stars: 2
- Container Assurance Base Digest Source Provenance LedgerUse 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...Votes: 0GitHub stars: 2
- Container Assurance Base Digest Threshold Rule CheckUse 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...Votes: 0GitHub stars: 2
- Container Assurance Build Inputs Approval Evidence PacketUse when a container build-input provenance result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the build-input manifest 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; the manifest captures material inputs and unexplained network-fetched inputs are flagged. Use configured search, fetch, r...Votes: 0GitHub stars: 2
- Container Assurance Build Inputs Change Impact TraceUse 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...Votes: 0GitHub stars: 2
- Container Assurance Build Inputs Closeout Handoff LedgerUse 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...Votes: 0GitHub stars: 2
- Container Assurance Build Inputs Completeness ReconciliationUse 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...Votes: 0GitHub stars: 2
- Container Assurance Build Inputs Exception Triage QueueUse 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...Votes: 0GitHub stars: 2
- Container Assurance Build Inputs Recovery Readiness DrillUse 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...Votes: 0GitHub stars: 2
- Container Assurance Build Inputs Scenario Sensitivity MatrixUse 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...Votes: 0GitHub stars: 2
- Container Assurance Build Inputs Scope Intake GateUse 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 ...Votes: 0GitHub stars: 2
- Container Assurance Build Inputs Source Provenance LedgerUse 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...Votes: 0GitHub stars: 2
- Container Assurance Build Inputs Threshold Rule CheckUse 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...Votes: 0GitHub stars: 2
- Container Assurance Context Secret Approval Evidence PacketUse when a container build-context secret exposure result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the build-context exclusion report 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; test credentials and sensitive files are excluded from the context and layers. Use configured search, fetch, re...Votes: 0GitHub stars: 2
- Container Assurance Context Secret Change Impact TraceUse when a version, rule, source, or stakeholder change may affect container build-context secret exposure to produce a before/after change record and impact map for the build-context exclusion report. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; test credentials and sensitive files are excluded from the context and layers. Use configured search, fetch, read, browser, test, and write capabilities only when...Votes: 0GitHub stars: 2
- Container Assurance Context Secret Closeout Handoff LedgerUse when a container build-context secret exposure work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the build-context exclusion report 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; test credentials and sensitive files are excluded from the context and layers. Use configured search, fetch, read, browser, test, and ...Votes: 0GitHub stars: 2
- Container Assurance Context Secret Completeness ReconciliationUse when the container build-context secret exposure workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the build-context exclusion report 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; test credentials and sensitive files are excluded from the context and layers. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2
- Container Assurance Context Secret Exception Triage QueueUse when the container build-context secret exposure workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the build-context exclusion report 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; test credentials and sensitive files are excluded from the context and layers. Use configured search, fetch, read, browser, test, and...Votes: 0GitHub stars: 2
- Container Assurance Context Secret Recovery Readiness DrillUse when the container build-context secret exposure workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the build-context exclusion report 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; test credentials and sensitive files are excluded from the context and layers. Use configured search, fetch, read, browser...Votes: 0GitHub stars: 2
- Container Assurance Context Secret Scenario Sensitivity MatrixUse when the container build-context secret exposure team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the build-context exclusion report with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; test credentials and sensitive files are excluded from the context and layers. Use configured search, fetch, read, browser, test, and write...Votes: 0GitHub stars: 2
- Container Assurance Context Secret Scope Intake GateUse when a new container build-context secret exposure request needs a bounded work scope to produce a scoped intake card for the build-context exclusion report. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; test credentials and sensitive files are excluded from the context and layers. 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 Context Secret Source Provenance LedgerUse when a decision about container build-context secret exposure depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the build-context exclusion report. Success means each material claim has a source, version/date, location, and confidence note; test credentials and sensitive files are excluded from the context and layers. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record ...Votes: 0GitHub stars: 2
- Container Assurance Context Secret Threshold Rule CheckUse when a container build-context secret exposure decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the build-context exclusion report 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; test credentials and sensitive files are excluded from the context and layers. Use configured search, fetch, read,...Votes: 0GitHub stars: 2
- Container Assurance Platform Parity Approval Evidence PacketUse when a multi-platform image parity result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the platform manifest 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; each declared platform resolves to the intended artifact and differences are explained. Use configured search, fetch, read, b...Votes: 0GitHub stars: 2
- Container Assurance Platform Parity Change Impact TraceUse 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...Votes: 0GitHub stars: 2
- Container Assurance Platform Parity Closeout Handoff LedgerUse 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...Votes: 0GitHub stars: 2
- Container Assurance Platform Parity Completeness ReconciliationUse 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...Votes: 0GitHub stars: 2
- Container Assurance Platform Parity Exception Triage QueueUse 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...Votes: 0GitHub stars: 2
- Container Assurance Platform Parity Recovery Readiness DrillUse 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...Votes: 0GitHub stars: 2
- Container Assurance Platform Parity Scenario Sensitivity MatrixUse 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...Votes: 0GitHub stars: 2
- Container Assurance Platform Parity Scope Intake GateUse 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...Votes: 0GitHub stars: 2
- Container Assurance Platform Parity Source Provenance LedgerUse 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...Votes: 0GitHub stars: 2
- Container Assurance Platform Parity Threshold Rule CheckUse 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...Votes: 0GitHub stars: 2
- Container Assurance Promotion Chain Approval Evidence PacketUse 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...Votes: 0GitHub stars: 2