All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Aas Secure Delivery Security Header Closeout Handoff LedgerUse when a web response security header regression work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the response-header 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; required headers appear on in-scope responses without breaking declared flows. Use configured search, fetch, read, browser, test, and writ...Votes: 0GitHub stars: 2
- Aas Secure Delivery Security Header Completeness ReconciliationUse when the web response security header regression workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the response-header 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; required headers appear on in-scope responses without breaking declared flows. Use configured search, fetch, read, browser, ...Votes: 0GitHub stars: 2
- Aas Secure Delivery Security Header Exception Triage QueueUse when the web response security header regression workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the response-header 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; required headers appear on in-scope responses without breaking declared flows. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2
- Aas Secure Delivery Security Header Recovery Readiness DrillUse when the web response security header regression workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the response-header 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; required headers appear on in-scope responses without breaking declared flows. Use configured search, fetch, read, browser, te...Votes: 0GitHub stars: 2
- Aas Secure Delivery Security Header Scenario Sensitivity MatrixUse when the web response security header regression team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the response-header comparison with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; required headers appear on in-scope responses without breaking declared flows. Use configured search, fetch, read, browser, test, and write cap...Votes: 0GitHub stars: 2
- Aas Secure Delivery Security Header Scope Intake GateUse when a new web response security header regression request needs a bounded work scope to produce a scoped intake card for the response-header comparison. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; required headers appear on in-scope responses without breaking declared flows. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to th...Votes: 0GitHub stars: 2
- Aas Secure Delivery Security Header Source Provenance LedgerUse when a decision about web response security header regression depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the response-header comparison. Success means each material claim has a source, version/date, location, and confidence note; required headers appear on in-scope responses without breaking declared flows. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evid...Votes: 0GitHub stars: 2
- Aas Secure Delivery Security Header Threshold Rule CheckUse when a web response security header regression decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the response-header 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; required headers appear on in-scope responses without breaking declared flows. Use configured search, fetch, read, bro...Votes: 0GitHub stars: 2
- Aas Secure Delivery Tenant Authz Approval Evidence PacketUse when a multi-tenant authorization boundaries result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the tenant isolation test 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; cross-tenant access is denied across direct, indirect, and asynchronous paths. Use configured search, fetch, read, ...Votes: 0GitHub stars: 2
- Aas Secure Delivery Tenant Authz Change Impact TraceUse when a version, rule, source, or stakeholder change may affect multi-tenant authorization boundaries to produce a before/after change record and impact map for the tenant isolation test record. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; cross-tenant access is denied across direct, indirect, and asynchronous paths. Use configured search, fetch, read, browser, test, and write capabilities only when rel...Votes: 0GitHub stars: 2
- Aas Secure Delivery Tenant Authz Closeout Handoff LedgerUse when a multi-tenant authorization boundaries work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the tenant isolation test 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; cross-tenant access is denied across direct, indirect, and asynchronous paths. Use configured search, fetch, read, browser, test, and writ...Votes: 0GitHub stars: 2
- Aas Secure Delivery Tenant Authz Completeness ReconciliationUse when the multi-tenant authorization boundaries workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the tenant isolation test 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; cross-tenant access is denied across direct, indirect, and asynchronous paths. Use configured search, fetch, read, browser, ...Votes: 0GitHub stars: 2
- Aas Secure Delivery Tenant Authz Exception Triage QueueUse when the multi-tenant authorization boundaries workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the tenant isolation test 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; cross-tenant access is denied across direct, indirect, and asynchronous paths. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2
- Aas Secure Delivery Tenant Authz Recovery Readiness DrillUse when the multi-tenant authorization boundaries workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the tenant isolation test 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; cross-tenant access is denied across direct, indirect, and asynchronous paths. Use configured search, fetch, read, browser, te...Votes: 0GitHub stars: 2
- Aas Secure Delivery Tenant Authz Scenario Sensitivity MatrixUse when the multi-tenant authorization boundaries team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the tenant isolation test record with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; cross-tenant access is denied across direct, indirect, and asynchronous paths. Use configured search, fetch, read, browser, test, and write cap...Votes: 0GitHub stars: 2
- Aas Secure Delivery Tenant Authz Scope Intake GateUse when a new multi-tenant authorization boundaries request needs a bounded work scope to produce a scoped intake card for the tenant isolation test record. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; cross-tenant access is denied across direct, indirect, and asynchronous paths. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to th...Votes: 0GitHub stars: 2
- Aas Secure Delivery Tenant Authz Source Provenance LedgerUse when a decision about multi-tenant authorization boundaries depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the tenant isolation test record. Success means each material claim has a source, version/date, location, and confidence note; cross-tenant access is denied across direct, indirect, and asynchronous paths. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evid...Votes: 0GitHub stars: 2
- Aas Secure Delivery Tenant Authz Threshold Rule CheckUse when a multi-tenant authorization boundaries decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the tenant isolation test 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; cross-tenant access is denied across direct, indirect, and asynchronous paths. Use configured search, fetch, read, bro...Votes: 0GitHub stars: 2
- Aas Secure Delivery Vulnerability Response Approval Evidence PacketUse when a application vulnerability response coordination result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the vulnerability response handoff 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; a responsible owner and safe next step are assigned without publishing sensitive details. Use configure...Votes: 0GitHub stars: 2
- Aas Secure Delivery Vulnerability Response Change Impact TraceUse when a version, rule, source, or stakeholder change may affect application vulnerability response coordination to produce a before/after change record and impact map for the vulnerability response handoff. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; a responsible owner and safe next step are assigned without publishing sensitive details. Use configured search, fetch, read, browser, test, and write cap...Votes: 0GitHub stars: 2
- Aas Secure Delivery Vulnerability Response Closeout Handoff LedgerUse when a application vulnerability response coordination work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the vulnerability response handoff 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; a responsible owner and safe next step are assigned without publishing sensitive details. Use configured search, fetch, read, ...Votes: 0GitHub stars: 2
- Aas Secure Delivery Vulnerability Response Completeness ReconciliationUse when the application vulnerability response coordination workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the vulnerability response handoff 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; a responsible owner and safe next step are assigned without publishing sensitive details. Use configured search,...Votes: 0GitHub stars: 2
- Aas Secure Delivery Vulnerability Response Exception Triage QueueUse when the application vulnerability response coordination workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the vulnerability response handoff 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; a responsible owner and safe next step are assigned without publishing sensitive details. Use configured search, fetch, read,...Votes: 0GitHub stars: 2
- Aas Secure Delivery Vulnerability Response Recovery Readiness DrillUse when the application vulnerability response coordination workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the vulnerability response handoff 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; a responsible owner and safe next step are assigned without publishing sensitive details. Use configured search, f...Votes: 0GitHub stars: 2
- Aas Secure Delivery Vulnerability Response Scenario Sensitivity MatrixUse when the application vulnerability response coordination team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the vulnerability response handoff with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; a responsible owner and safe next step are assigned without publishing sensitive details. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2
- Aas Secure Delivery Vulnerability Response Scope Intake GateUse when a new application vulnerability response coordination request needs a bounded work scope to produce a scoped intake card for the vulnerability response handoff. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; a responsible owner and safe next step are assigned without publishing sensitive details. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence,...Votes: 0GitHub stars: 2
- Aas Secure Delivery Vulnerability Response Source Provenance LedgerUse when a decision about application vulnerability response coordination depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the vulnerability response handoff. Success means each material claim has a source, version/date, location, and confidence note; a responsible owner and safe next step are assigned without publishing sensitive details. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and ...Votes: 0GitHub stars: 2
- Aas Secure Delivery Vulnerability Response Threshold Rule CheckUse when a application vulnerability response coordination decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the vulnerability response handoff 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; a responsible owner and safe next step are assigned without publishing sensitive details. Use configured s...Votes: 0GitHub stars: 2
- Aas Secure Delivery Webhook Replay Approval Evidence PacketUse when a webhook signature and replay protection result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the webhook verification test matrix 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; valid events are accepted once and tampered or replayed events are rejected. Use configured search, fetch, re...Votes: 0GitHub stars: 2
- Aas Secure Delivery Webhook Replay Change Impact TraceUse when a version, rule, source, or stakeholder change may affect webhook signature and replay protection to produce a before/after change record and impact map for the webhook verification test matrix. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; valid events are accepted once and tampered or replayed events are rejected. Use configured search, fetch, read, browser, test, and write capabilities only when...Votes: 0GitHub stars: 2
- Aas Secure Delivery Webhook Replay Closeout Handoff LedgerUse when a webhook signature and replay protection work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the webhook verification test matrix 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; valid events are accepted once and tampered or replayed events are rejected. Use configured search, fetch, read, browser, test, and ...Votes: 0GitHub stars: 2
- Aas Secure Delivery Webhook Replay Completeness ReconciliationUse when the webhook signature and replay protection workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the webhook verification test matrix 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; valid events are accepted once and tampered or replayed events are rejected. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2
- Aas Secure Delivery Webhook Replay Exception Triage QueueUse when the webhook signature and replay protection workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the webhook verification test matrix 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; valid events are accepted once and tampered or replayed events are rejected. Use configured search, fetch, read, browser, test, and...Votes: 0GitHub stars: 2
- Aas Secure Delivery Webhook Replay Recovery Readiness DrillUse when the webhook signature and replay protection workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the webhook verification test matrix 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; valid events are accepted once and tampered or replayed events are rejected. Use configured search, fetch, read, browser...Votes: 0GitHub stars: 2
- Aas Secure Delivery Webhook Replay Scenario Sensitivity MatrixUse when the webhook signature and replay protection team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the webhook verification test matrix with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; valid events are accepted once and tampered or replayed events are rejected. Use configured search, fetch, read, browser, test, and write...Votes: 0GitHub stars: 2
- Aas Secure Delivery Webhook Replay Scope Intake GateUse when a new webhook signature and replay protection request needs a bounded work scope to produce a scoped intake card for the webhook verification test matrix. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; valid events are accepted once and tampered or replayed events are rejected. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement t...Votes: 0GitHub stars: 2
- Aas Secure Delivery Webhook Replay Source Provenance LedgerUse when a decision about webhook signature and replay protection depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the webhook verification test matrix. Success means each material claim has a source, version/date, location, and confidence note; valid events are accepted once and tampered or replayed events are rejected. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record ...Votes: 0GitHub stars: 2
- Aas Secure Delivery Webhook Replay Threshold Rule CheckUse when a webhook signature and replay protection decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the webhook verification test matrix 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; valid events are accepted once and tampered or replayed events are rejected. Use configured search, fetch, read,...Votes: 0GitHub stars: 2
- Application Security ReviewUse when reviewing application code, APIs, dependencies, or configuration for security weaknesses, especially around identity, authorization, untrusted input, sensitive data, or external integrations to map trust boundaries, test relevant controls safely, and report evidence-based risks with practical mitigations. Trigger for a requested security review or a high-risk software change; this is not an authorization to exploit systems or alter production.Votes: 0GitHub stars: 2
- Audit Logging Capability Surface MapUse when the actual capability boundary of Centralized audit logging needs to be distinguished from assumptions. Produce a capability map for Centralized audit logging covering the requested behavior, verified support, exclusions, and unknowns. Success means each in-scope capability is tied to local configuration, a version-matched authoritative reference, or an observed non-production result, and all unknowns remain explicit. The review is bounded to event source, actor identity, tamper boun...Votes: 0GitHub stars: 2
- Audit Logging Change Impact AssessmentUse when a proposed Centralized audit logging version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Centralized audit logging with baseline, affected dependencies, validation needs, and recovery boundary. Success means affected dependencies and compatibility assumptions are evidenced, unknown consumers are named as unknown, and no migration or rollout is implied. The review is bounded to event source, actor identity, tamper bo...Votes: 0GitHub stars: 2
- Audit Logging Failure Triage RecordUse when a reproducible Centralized audit logging symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Centralized audit logging with symptom, environment, evidence, hypothesis, and next safe check. Success means the diagnosis distinguishes observation from inference, each proposed check is reversible and scoped, and unresolved causes remain open. The review is bounded to event source, actor identity, tamper boundary, retention, access, and review ...Votes: 0GitHub stars: 2
- Audit Logging Input Output ContractUse when the accepted inputs or produced outputs for Centralized audit logging need a checkable boundary. Produce an input/output contract for Centralized audit logging with types, required fields, exclusions, and representative approved fixtures. Success means the contract names its source and version, boundary cases are visible, and no private or unapproved payload is needed to explain the result. The review is bounded to event source, actor identity, tamper boundary, retention, access, and...Votes: 0GitHub stars: 2
- Audit Logging Integration Parity TraceUse when Centralized audit logging exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Centralized audit logging showing source, transformation, destination, and observed result. Success means each material field or state transition has a traceable mapping and observed mismatches are separated from assumptions. The review is bounded to event source, actor identity, tamper boundary, retention, access, and review evidence....Votes: 0GitHub stars: 2
- Audit Logging Performance EnvelopeUse when Centralized audit logging must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Centralized audit logging with test conditions, baseline, observed range, and limitations. Success means conditions and measurements are reproducible, the comparison uses the stated budget, and limitations or resource costs are visible. The review is bounded to event source, actor identity, tamper boundary, retention, a...Votes: 0GitHub stars: 2
- Audit Logging Permission Boundary ReviewUse when Centralized audit logging may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Centralized audit logging showing identity, requested capability, data scope, and approval gate. Success means every sensitive capability has a named authorization boundary, unnecessary data and privileges are called out, and no action is treated as approved by implication. The review is bounded to event source, actor identity, tamper boundary, r...Votes: 0GitHub stars: 2
- Audit Logging Release Handoff RecordUse when a Centralized audit logging review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Centralized audit logging with version, evidence, open issues, approval state, and safe next step. Success means the receiver can distinguish verified facts, proposals, approvals, and unknowns, and no publication, deployment, write, or contact is claimed unless independently confirmed. The review is bounded to event source, actor identity, tamper boun...Votes: 0GitHub stars: 2
- Audit Logging Reproducibility Fixture PlanUse when a Centralized audit logging result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Centralized audit logging defining fixture identity, environment, expected observations, and cleanup boundary. Success means another reviewer can identify the fixture and environment, distinguish expected from observed behavior, and repeat the check without an unapproved external effect. The review is bounded to event source,...Votes: 0GitHub stars: 2
- Audit Logging Version CompatibilityUse when a Centralized audit logging integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Centralized audit logging with exact versions, supported combinations, and open questions. Success means the tested version tuple is explicit, each compatibility claim has a dated source or local result, and unsupported combinations are not presented as working. The review is bounded to event source, actor identity, tamper...Votes: 0GitHub stars: 2
- Aws Cloudtrail Capability Surface MapUse when the actual capability boundary of AWS CloudTrail audit evidence needs to be distinguished from assumptions. Produce a capability map for AWS CloudTrail audit evidence covering the requested behavior, verified support, exclusions, and unknowns. Success means each in-scope capability is tied to local configuration, a version-matched authoritative reference, or an observed non-production result, and all unknowns remain explicit. The review is bounded to trail identity, event scope, dest...Votes: 0GitHub stars: 2