All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Aas Secure Delivery Dependency Reachability Closeout Handoff LedgerUse when a dependency vulnerability reachability triage work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the dependency reachability evidence table 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; priority reflects verified exposure rather than severity label alone. Use configured search, fetch, read, browser, test, ...Votes: 0GitHub stars: 2
- Aas Secure Delivery Dependency Reachability Completeness ReconciliationUse when the dependency vulnerability reachability triage workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the dependency reachability evidence table 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; priority reflects verified exposure rather than severity label alone. Use configured search, fetch, read, b...Votes: 0GitHub stars: 2
- Aas Secure Delivery Dependency Reachability Exception Triage QueueUse when the dependency vulnerability reachability triage workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the dependency reachability evidence table 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; priority reflects verified exposure rather than severity label alone. Use configured search, fetch, read, browser, test,...Votes: 0GitHub stars: 2
- Aas Secure Delivery Dependency Reachability Recovery Readiness DrillUse when the dependency vulnerability reachability triage workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the dependency reachability evidence table 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; priority reflects verified exposure rather than severity label alone. Use configured search, fetch, read, bro...Votes: 0GitHub stars: 2
- Aas Secure Delivery Dependency Reachability Scenario Sensitivity MatrixUse when the dependency vulnerability reachability triage team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the dependency reachability evidence table with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; priority reflects verified exposure rather than severity label alone. Use configured search, fetch, read, browser, test, and w...Votes: 0GitHub stars: 2
- Aas Secure Delivery Dependency Reachability Scope Intake GateUse when a new dependency vulnerability reachability triage request needs a bounded work scope to produce a scoped intake card for the dependency reachability evidence table. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; priority reflects verified exposure rather than severity label alone. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refineme...Votes: 0GitHub stars: 2
- Aas Secure Delivery Dependency Reachability Source Provenance LedgerUse when a decision about dependency vulnerability reachability triage depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the dependency reachability evidence table. Success means each material claim has a source, version/date, location, and confidence note; priority reflects verified exposure rather than severity label alone. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Rec...Votes: 0GitHub stars: 2
- Aas Secure Delivery Dependency Reachability Threshold Rule CheckUse when a dependency vulnerability reachability triage decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the dependency reachability evidence table 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; priority reflects verified exposure rather than severity label alone. Use configured search, fetch, r...Votes: 0GitHub stars: 2
- Aas Secure Delivery Extension Permissions Approval Evidence PacketUse when a third-party extension permission review result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the extension permission inventory 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; every granted capability has a task need and update authority is identified. Use configured search, fetch, read...Votes: 0GitHub stars: 2
- Aas Secure Delivery Extension Permissions Change Impact TraceUse when a version, rule, source, or stakeholder change may affect third-party extension permission review to produce a before/after change record and impact map for the extension permission inventory. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; every granted capability has a task need and update authority is identified. Use configured search, fetch, read, browser, test, and write capabilities only when r...Votes: 0GitHub stars: 2
- Aas Secure Delivery Extension Permissions Closeout Handoff LedgerUse when a third-party extension permission review work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the extension permission inventory 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; every granted capability has a task need and update authority is identified. Use configured search, fetch, read, browser, test, and wr...Votes: 0GitHub stars: 2
- Aas Secure Delivery Extension Permissions Completeness ReconciliationUse when the third-party extension permission review workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the extension permission inventory 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; every granted capability has a task need and update authority is identified. Use configured search, fetch, read, browser...Votes: 0GitHub stars: 2
- Aas Secure Delivery Extension Permissions Exception Triage QueueUse when the third-party extension permission review workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the extension permission inventory 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; every granted capability has a task need and update authority is identified. Use configured search, fetch, read, browser, test, and w...Votes: 0GitHub stars: 2
- Aas Secure Delivery Extension Permissions Recovery Readiness DrillUse when the third-party extension permission review workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the extension permission inventory 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; every granted capability has a task need and update authority is identified. Use configured search, fetch, read, browser, ...Votes: 0GitHub stars: 2
- Aas Secure Delivery Extension Permissions Scenario Sensitivity MatrixUse when the third-party extension permission review team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the extension permission inventory with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; every granted capability has a task need and update authority is identified. Use configured search, fetch, read, browser, test, and write c...Votes: 0GitHub stars: 2
- Aas Secure Delivery Extension Permissions Scope Intake GateUse when a new third-party extension permission review request needs a bounded work scope to produce a scoped intake card for the extension permission inventory. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; every granted capability has a task need and update authority is identified. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to ...Votes: 0GitHub stars: 2
- Aas Secure Delivery Extension Permissions Source Provenance LedgerUse when a decision about third-party extension permission review depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the extension permission inventory. Success means each material claim has a source, version/date, location, and confidence note; every granted capability has a task need and update authority is identified. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record ev...Votes: 0GitHub stars: 2
- Aas Secure Delivery Extension Permissions Threshold Rule CheckUse when a third-party extension permission review decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the extension permission inventory 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; every granted capability has a task need and update authority is identified. Use configured search, fetch, read, b...Votes: 0GitHub stars: 2
- Aas Secure Delivery Oauth Scope Drift Approval Evidence PacketUse when a OAuth scope drift review result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the OAuth scope-to-feature map 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 scope has a current purpose and unused privilege is flagged for owner review. Use configured search, fetch, read, browser, te...Votes: 0GitHub stars: 2
- Aas Secure Delivery Oauth Scope Drift Change Impact TraceUse when a version, rule, source, or stakeholder change may affect OAuth scope drift review to produce a before/after change record and impact map for the OAuth scope-to-feature map. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each scope has a current purpose and unused privilege is flagged for owner review. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and a...Votes: 0GitHub stars: 2
- Aas Secure Delivery Oauth Scope Drift Closeout Handoff LedgerUse when a OAuth scope drift review work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the OAuth scope-to-feature map 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 scope has a current purpose and unused privilege is flagged for owner review. Use configured search, fetch, read, browser, test, and write capabilit...Votes: 0GitHub stars: 2
- Aas Secure Delivery Oauth Scope Drift Completeness ReconciliationUse when the OAuth scope drift review workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the OAuth scope-to-feature map 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 scope has a current purpose and unused privilege is flagged for owner review. Use configured search, fetch, read, browser, test, and w...Votes: 0GitHub stars: 2
- Aas Secure Delivery Oauth Scope Drift Exception Triage QueueUse when the OAuth scope drift review workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the OAuth scope-to-feature map 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 scope has a current purpose and unused privilege is flagged for owner review. Use configured search, fetch, read, browser, test, and write capabili...Votes: 0GitHub stars: 2
- Aas Secure Delivery Oauth Scope Drift Recovery Readiness DrillUse when the OAuth scope drift review workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the OAuth scope-to-feature map 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 scope has a current purpose and unused privilege is flagged for owner review. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2
- Aas Secure Delivery Oauth Scope Drift Scenario Sensitivity MatrixUse when the OAuth scope drift review team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the OAuth scope-to-feature map with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each scope has a current purpose and unused privilege is flagged for owner review. Use configured search, fetch, read, browser, test, and write capabilities o...Votes: 0GitHub stars: 2
- Aas Secure Delivery Oauth Scope Drift Scope Intake GateUse when a new OAuth scope drift review request needs a bounded work scope to produce a scoped intake card for the OAuth scope-to-feature map. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each scope has a current purpose and unused privilege is flagged for owner 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
- Aas Secure Delivery Oauth Scope Drift Source Provenance LedgerUse when a decision about OAuth scope drift review depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the OAuth scope-to-feature map. Success means each material claim has a source, version/date, location, and confidence note; each scope has a current purpose and unused privilege is flagged for owner review. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit...Votes: 0GitHub stars: 2
- Aas Secure Delivery Oauth Scope Drift Threshold Rule CheckUse when a OAuth scope drift review decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the OAuth scope-to-feature map 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 scope has a current purpose and unused privilege is flagged for owner review. Use configured search, fetch, read, browser, test,...Votes: 0GitHub stars: 2
- Aas Secure Delivery Oidc Federation Approval Evidence PacketUse when a CI workload identity federation result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the workload-identity trust 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; only the intended workflow receives a short-lived token and long-lived credentials are absent. Use configured search, f...Votes: 0GitHub stars: 2
- Aas Secure Delivery Oidc Federation Change Impact TraceUse when a version, rule, source, or stakeholder change may affect CI workload identity federation to produce a before/after change record and impact map for the workload-identity trust review. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; only the intended workflow receives a short-lived token and long-lived credentials are absent. Use configured search, fetch, read, browser, test, and write capabilities o...Votes: 0GitHub stars: 2
- Aas Secure Delivery Oidc Federation Closeout Handoff LedgerUse when a CI workload identity federation work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the workload-identity trust 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; only the intended workflow receives a short-lived token and long-lived credentials are absent. Use configured search, fetch, read, browser, te...Votes: 0GitHub stars: 2
- Aas Secure Delivery Oidc Federation Completeness ReconciliationUse when the CI workload identity federation workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the workload-identity trust 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; only the intended workflow receives a short-lived token and long-lived credentials are absent. Use configured search, fetch, rea...Votes: 0GitHub stars: 2
- Aas Secure Delivery Oidc Federation Exception Triage QueueUse when the CI workload identity federation workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the workload-identity trust 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; only the intended workflow receives a short-lived token and long-lived credentials are absent. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Aas Secure Delivery Oidc Federation Recovery Readiness DrillUse when the CI workload identity federation workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the workload-identity trust 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; only the intended workflow receives a short-lived token and long-lived credentials are absent. Use configured search, fetch, read,...Votes: 0GitHub stars: 2
- Aas Secure Delivery Oidc Federation Scenario Sensitivity MatrixUse when the CI workload identity federation team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the workload-identity trust review with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; only the intended workflow receives a short-lived token and long-lived credentials are absent. Use configured search, fetch, read, browser, test, a...Votes: 0GitHub stars: 2
- Aas Secure Delivery Oidc Federation Scope Intake GateUse when a new CI workload identity federation request needs a bounded work scope to produce a scoped intake card for the workload-identity trust review. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; only the intended workflow receives a short-lived token and long-lived credentials are absent. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refi...Votes: 0GitHub stars: 2
- Aas Secure Delivery Oidc Federation Source Provenance LedgerUse when a decision about CI workload identity federation depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the workload-identity trust review. Success means each material claim has a source, version/date, location, and confidence note; only the intended workflow receives a short-lived token and long-lived credentials are absent. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized....Votes: 0GitHub stars: 2
- Aas Secure Delivery Oidc Federation Threshold Rule CheckUse when a CI workload identity federation decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the workload-identity trust 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; only the intended workflow receives a short-lived token and long-lived credentials are absent. Use configured search, fetc...Votes: 0GitHub stars: 2
- Aas Secure Delivery Request Signing Approval Evidence PacketUse when a API request signing canonicalization result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the request-signing interoperability fixture 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; producer and verifier derive the same canonical bytes for declared edge cases. Use configured search, fe...Votes: 0GitHub stars: 2
- Aas Secure Delivery Request Signing Change Impact TraceUse when a version, rule, source, or stakeholder change may affect API request signing canonicalization to produce a before/after change record and impact map for the request-signing interoperability fixture. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; producer and verifier derive the same canonical bytes for declared edge cases. Use configured search, fetch, read, browser, test, and write capabilities on...Votes: 0GitHub stars: 2
- Aas Secure Delivery Request Signing Closeout Handoff LedgerUse when a API request signing canonicalization work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the request-signing interoperability fixture 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; producer and verifier derive the same canonical bytes for declared edge cases. Use configured search, fetch, read, browser, tes...Votes: 0GitHub stars: 2
- Aas Secure Delivery Request Signing Completeness ReconciliationUse when the API request signing canonicalization workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the request-signing interoperability fixture 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; producer and verifier derive the same canonical bytes for declared edge cases. Use configured search, fetch, read...Votes: 0GitHub stars: 2
- Aas Secure Delivery Request Signing Exception Triage QueueUse when the API request signing canonicalization workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the request-signing interoperability fixture 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; producer and verifier derive the same canonical bytes for declared edge cases. Use configured search, fetch, read, browser, te...Votes: 0GitHub stars: 2
- Aas Secure Delivery Request Signing Recovery Readiness DrillUse when the API request signing canonicalization workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the request-signing interoperability fixture 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; producer and verifier derive the same canonical bytes for declared edge cases. Use configured search, fetch, read, ...Votes: 0GitHub stars: 2
- Aas Secure Delivery Request Signing Scenario Sensitivity MatrixUse when the API request signing canonicalization team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the request-signing interoperability fixture with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; producer and verifier derive the same canonical bytes for declared edge cases. Use configured search, fetch, read, browser, test, an...Votes: 0GitHub stars: 2
- Aas Secure Delivery Request Signing Scope Intake GateUse when a new API request signing canonicalization request needs a bounded work scope to produce a scoped intake card for the request-signing interoperability fixture. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; producer and verifier derive the same canonical bytes for declared edge cases. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refin...Votes: 0GitHub stars: 2
- Aas Secure Delivery Request Signing Source Provenance LedgerUse when a decision about API request signing canonicalization depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the request-signing interoperability fixture. Success means each material claim has a source, version/date, location, and confidence note; producer and verifier derive the same canonical bytes for declared edge cases. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. ...Votes: 0GitHub stars: 2
- Aas Secure Delivery Request Signing Threshold Rule CheckUse when a API request signing canonicalization decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the request-signing interoperability fixture 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; producer and verifier derive the same canonical bytes for declared edge cases. Use configured search, fetch...Votes: 0GitHub stars: 2
- Aas Secure Delivery Security Header Approval Evidence PacketUse when a web response security header regression result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the response-header 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; required headers appear on in-scope responses without breaking declared flows. Use configured search, fetch, read, ...Votes: 0GitHub stars: 2
- Aas Secure Delivery Security Header Change Impact TraceUse when a version, rule, source, or stakeholder change may affect web response security header regression to produce a before/after change record and impact map for the response-header comparison. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; required headers appear on in-scope responses without breaking declared flows. Use configured search, fetch, read, browser, test, and write capabilities only when rel...Votes: 0GitHub stars: 2