All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Backend Ops Authorization Boundary Scenario Sensitivity MatrixUse when the backend authorization boundaries team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the authorization decision table with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; allow and deny cases are tested at each boundary without using real customer credentials. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2
- Backend Ops Authorization Boundary Scope Intake GateUse when a new backend authorization boundaries request needs a bounded work scope to produce a scoped intake card for the authorization decision table. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; allow and deny cases are tested at each boundary without using real customer credentials. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement...Votes: 0GitHub stars: 2
- Backend Ops Authorization Boundary Source Provenance LedgerUse when a decision about backend authorization boundaries depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the authorization decision table. Success means each material claim has a source, version/date, location, and confidence note; allow and deny cases are tested at each boundary without using real customer credentials. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Recor...Votes: 0GitHub stars: 2
- Backend Ops Authorization Boundary Threshold Rule CheckUse when a backend authorization boundaries decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the authorization decision 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; allow and deny cases are tested at each boundary without using real customer credentials. Use configured search, fetch, rea...Votes: 0GitHub stars: 2
- Backend Ops Cache Consistency Approval Evidence PacketUse when a service cache consistency behavior result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the cache invalidation 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; the measured stale interval stays within the approved contract or remains a documented risk. Use configured search, ...Votes: 0GitHub stars: 2
- Backend Ops Cache Consistency Change Impact TraceUse when a version, rule, source, or stakeholder change may affect service cache consistency behavior to produce a before/after change record and impact map for the cache invalidation test record. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the measured stale interval stays within the approved contract or remains a documented risk. Use configured search, fetch, read, browser, test, and write capabilities ...Votes: 0GitHub stars: 2
- Backend Ops Cache Consistency Closeout Handoff LedgerUse when a service cache consistency behavior work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the cache invalidation 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; the measured stale interval stays within the approved contract or remains a documented risk. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Backend Ops Cache Consistency Completeness ReconciliationUse when the service cache consistency behavior workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the cache invalidation 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; the measured stale interval stays within the approved contract or remains a documented risk. Use configured search, fetch, re...Votes: 0GitHub stars: 2
- Backend Ops Cache Consistency Exception Triage QueueUse when the service cache consistency behavior workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the cache invalidation 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; the measured stale interval stays within the approved contract or remains a documented risk. Use configured search, fetch, read, browser, ...Votes: 0GitHub stars: 2
- Backend Ops Cache Consistency Recovery Readiness DrillUse when the service cache consistency behavior workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the cache invalidation 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; the measured stale interval stays within the approved contract or remains a documented risk. Use configured search, fetch, read...Votes: 0GitHub stars: 2
- Backend Ops Cache Consistency Scenario Sensitivity MatrixUse when the service cache consistency behavior team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the cache invalidation test record with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the measured stale interval stays within the approved contract or remains a documented risk. Use configured search, fetch, read, browser, test, ...Votes: 0GitHub stars: 2
- Backend Ops Cache Consistency Scope Intake GateUse when a new service cache consistency behavior request needs a bounded work scope to produce a scoped intake card for the cache invalidation test record. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the measured stale interval stays within the approved contract or remains a documented risk. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit ref...Votes: 0GitHub stars: 2
- Backend Ops Cache Consistency Source Provenance LedgerUse when a decision about service cache consistency behavior depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the cache invalidation test record. Success means each material claim has a source, version/date, location, and confidence note; the measured stale interval stays within the approved contract or remains a documented risk. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized...Votes: 0GitHub stars: 2
- Backend Ops Cache Consistency Threshold Rule CheckUse when a service cache consistency behavior decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the cache invalidation 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; the measured stale interval stays within the approved contract or remains a documented risk. Use configured search, fet...Votes: 0GitHub stars: 2
- Backend Ops Error Retry Contract Approval Evidence PacketUse when a backend error and retry contracts result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the error-handling behavior table 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; retryable and terminal cases produce bounded behavior without duplicate side effects. Use configured search, fetch, re...Votes: 0GitHub stars: 2
- Backend Ops Error Retry Contract Change Impact TraceUse when a version, rule, source, or stakeholder change may affect backend error and retry contracts to produce a before/after change record and impact map for the error-handling behavior table. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; retryable and terminal cases produce bounded behavior without duplicate side effects. Use configured search, fetch, read, browser, test, and write capabilities only when...Votes: 0GitHub stars: 2
- Backend Ops Error Retry Contract Closeout Handoff LedgerUse when a backend error and retry contracts work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the error-handling behavior 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; retryable and terminal cases produce bounded behavior without duplicate side effects. Use configured search, fetch, read, browser, test, and ...Votes: 0GitHub stars: 2
- Backend Ops Error Retry Contract Completeness ReconciliationUse when the backend error and retry contracts workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the error-handling behavior 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; retryable and terminal cases produce bounded behavior without duplicate side effects. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2
- Backend Ops Error Retry Contract Exception Triage QueueUse when the backend error and retry contracts workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the error-handling behavior 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; retryable and terminal cases produce bounded behavior without duplicate side effects. Use configured search, fetch, read, browser, test, and...Votes: 0GitHub stars: 2
- Backend Ops Error Retry Contract Recovery Readiness DrillUse when the backend error and retry contracts workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the error-handling behavior 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; retryable and terminal cases produce bounded behavior without duplicate side effects. Use configured search, fetch, read, browser...Votes: 0GitHub stars: 2
- Backend Ops Error Retry Contract Scenario Sensitivity MatrixUse when the backend error and retry contracts team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the error-handling behavior table with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; retryable and terminal cases produce bounded behavior without duplicate side effects. Use configured search, fetch, read, browser, test, and write...Votes: 0GitHub stars: 2
- Backend Ops Error Retry Contract Scope Intake GateUse when a new backend error and retry contracts request needs a bounded work scope to produce a scoped intake card for the error-handling behavior table. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; retryable and terminal cases produce bounded behavior without duplicate side effects. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement t...Votes: 0GitHub stars: 2
- Backend Ops Error Retry Contract Source Provenance LedgerUse when a decision about backend error and retry contracts depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the error-handling behavior table. Success means each material claim has a source, version/date, location, and confidence note; retryable and terminal cases produce bounded behavior without duplicate side effects. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record ...Votes: 0GitHub stars: 2
- Backend Ops Error Retry Contract Threshold Rule CheckUse when a backend error and retry contracts decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the error-handling behavior 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; retryable and terminal cases produce bounded behavior without duplicate side effects. Use configured search, fetch, read,...Votes: 0GitHub stars: 2
- Backend Ops Event Delivery Approval Evidence PacketUse when a backend event delivery contracts result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the event-delivery acceptance 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; delivery guarantees and compatibility assumptions are explicit and testable. Use configured search, fetch, read, bro...Votes: 0GitHub stars: 2
- Backend Ops Event Delivery Change Impact TraceUse when a version, rule, source, or stakeholder change may affect backend event delivery contracts to produce a before/after change record and impact map for the event-delivery acceptance matrix. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; delivery guarantees and compatibility assumptions are explicit and testable. Use configured search, fetch, read, browser, test, and write capabilities only when releva...Votes: 0GitHub stars: 2
- Backend Ops Event Delivery Closeout Handoff LedgerUse when a backend event delivery contracts work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the event-delivery acceptance 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; delivery guarantees and compatibility assumptions are explicit and testable. Use configured search, fetch, read, browser, test, and write c...Votes: 0GitHub stars: 2
- Backend Ops Event Delivery Completeness ReconciliationUse when the backend event delivery contracts workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the event-delivery acceptance 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; delivery guarantees and compatibility assumptions are explicit and testable. Use configured search, fetch, read, browser, tes...Votes: 0GitHub stars: 2
- Backend Ops Event Delivery Exception Triage QueueUse when the backend event delivery contracts workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the event-delivery acceptance 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; delivery guarantees and compatibility assumptions are explicit and testable. Use configured search, fetch, read, browser, test, and write ...Votes: 0GitHub stars: 2
- Backend Ops Event Delivery Recovery Readiness DrillUse when the backend event delivery contracts workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the event-delivery acceptance 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; delivery guarantees and compatibility assumptions are explicit and testable. Use configured search, fetch, read, browser, test,...Votes: 0GitHub stars: 2
- Backend Ops Event Delivery Scenario Sensitivity MatrixUse when the backend event delivery contracts team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the event-delivery acceptance matrix with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; delivery guarantees and compatibility assumptions are explicit and testable. Use configured search, fetch, read, browser, test, and write capabi...Votes: 0GitHub stars: 2
- Backend Ops Event Delivery Scope Intake GateUse when a new backend event delivery contracts request needs a bounded work scope to produce a scoped intake card for the event-delivery acceptance matrix. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; delivery guarantees and compatibility assumptions are explicit and testable. 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
- Backend Ops Event Delivery Source Provenance LedgerUse when a decision about backend event delivery contracts depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the event-delivery acceptance matrix. Success means each material claim has a source, version/date, location, and confidence note; delivery guarantees and compatibility assumptions are explicit and testable. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidenc...Votes: 0GitHub stars: 2
- Backend Ops Event Delivery Threshold Rule CheckUse when a backend event delivery contracts decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the event-delivery acceptance 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; delivery guarantees and compatibility assumptions are explicit and testable. Use configured search, fetch, read, browse...Votes: 0GitHub stars: 2
- Backend Ops Idempotent Jobs Approval Evidence PacketUse when a idempotent background-job processing result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the replay-safety test plan 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; duplicate delivery does not duplicate the declared side effect in an isolated test. Use configured search, fetch, read, b...Votes: 0GitHub stars: 2
- Backend Ops Idempotent Jobs Change Impact TraceUse when a version, rule, source, or stakeholder change may affect idempotent background-job processing to produce a before/after change record and impact map for the replay-safety test plan. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; duplicate delivery does not duplicate the declared side effect in an isolated test. Use configured search, fetch, read, browser, test, and write capabilities only when rele...Votes: 0GitHub stars: 2
- Backend Ops Idempotent Jobs Closeout Handoff LedgerUse when a idempotent background-job processing work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the replay-safety test plan 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; duplicate delivery does not duplicate the declared side effect in an isolated test. Use configured search, fetch, read, browser, test, and write...Votes: 0GitHub stars: 2
- Backend Ops Idempotent Jobs Completeness ReconciliationUse when the idempotent background-job processing workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the replay-safety test plan 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; duplicate delivery does not duplicate the declared side effect in an isolated test. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Backend Ops Idempotent Jobs Exception Triage QueueUse when the idempotent background-job processing workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the replay-safety test plan 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; duplicate delivery does not duplicate the declared side effect in an isolated test. Use configured search, fetch, read, browser, test, and writ...Votes: 0GitHub stars: 2
- Backend Ops Idempotent Jobs Recovery Readiness DrillUse when the idempotent background-job processing workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the replay-safety test plan 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; duplicate delivery does not duplicate the declared side effect in an isolated test. Use configured search, fetch, read, browser, tes...Votes: 0GitHub stars: 2
- Backend Ops Idempotent Jobs Scenario Sensitivity MatrixUse when the idempotent background-job processing team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the replay-safety test plan with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; duplicate delivery does not duplicate the declared side effect in an isolated test. Use configured search, fetch, read, browser, test, and write capa...Votes: 0GitHub stars: 2
- Backend Ops Idempotent Jobs Scope Intake GateUse when a new idempotent background-job processing request needs a bounded work scope to produce a scoped intake card for the replay-safety test plan. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; duplicate delivery does not duplicate the declared side effect in an isolated test. 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
- Backend Ops Idempotent Jobs Source Provenance LedgerUse when a decision about idempotent background-job processing depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the replay-safety test plan. Success means each material claim has a source, version/date, location, and confidence note; duplicate delivery does not duplicate the declared side effect in an isolated test. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evide...Votes: 0GitHub stars: 2
- Backend Ops Idempotent Jobs Threshold Rule CheckUse when a idempotent background-job processing decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the replay-safety test plan 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; duplicate delivery does not duplicate the declared side effect in an isolated test. Use configured search, fetch, read, brow...Votes: 0GitHub stars: 2
- Backend Ops Observability Redaction Approval Evidence PacketUse when a backend observability and log redaction result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the log-field review 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; diagnostic fields remain useful while restricted values are absent from the approved sample. Use configured search, fe...Votes: 0GitHub stars: 2
- Backend Ops Observability Redaction Change Impact TraceUse when a version, rule, source, or stakeholder change may affect backend observability and log redaction to produce a before/after change record and impact map for the log-field review matrix. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; diagnostic fields remain useful while restricted values are absent from the approved sample. Use configured search, fetch, read, browser, test, and write capabilities on...Votes: 0GitHub stars: 2
- Backend Ops Observability Redaction Closeout Handoff LedgerUse when a backend observability and log redaction work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the log-field review 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; diagnostic fields remain useful while restricted values are absent from the approved sample. Use configured search, fetch, read, browser, tes...Votes: 0GitHub stars: 2
- Backend Ops Observability Redaction Completeness ReconciliationUse when the backend observability and log redaction workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the log-field review 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; diagnostic fields remain useful while restricted values are absent from the approved sample. Use configured search, fetch, read...Votes: 0GitHub stars: 2
- Backend Ops Observability Redaction Exception Triage QueueUse when the backend observability and log redaction workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the log-field review 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; diagnostic fields remain useful while restricted values are absent from the approved sample. Use configured search, fetch, read, browser, te...Votes: 0GitHub stars: 2
- Backend Ops Observability Redaction Recovery Readiness DrillUse when the backend observability and log redaction workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the log-field review 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; diagnostic fields remain useful while restricted values are absent from the approved sample. Use configured search, fetch, read, ...Votes: 0GitHub stars: 2