All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Product Ops Sunset Closeout Handoff LedgerUse when a feature sunset and migration work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the sunset readiness 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; affected users and systems are accounted for before a proposed cutoff. Use configured search, fetch, read, browser, test, and write capabilities only when...Votes: 0GitHub stars: 2
- Product Ops Sunset Completeness ReconciliationUse when the feature sunset and migration workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the sunset readiness 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; affected users and systems are accounted for before a proposed cutoff. Use configured search, fetch, read, browser, test, and write capabili...Votes: 0GitHub stars: 2
- Product Ops Sunset Exception Triage QueueUse when the feature sunset and migration workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the sunset readiness 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; affected users and systems are accounted for before a proposed cutoff. Use configured search, fetch, read, browser, test, and write capabilities only whe...Votes: 0GitHub stars: 2
- Product Ops Sunset Recovery Readiness DrillUse when the feature sunset and migration workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the sunset readiness 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; affected users and systems are accounted for before a proposed cutoff. Use configured search, fetch, read, browser, test, and write capabiliti...Votes: 0GitHub stars: 2
- Product Ops Sunset Scenario Sensitivity MatrixUse when the feature sunset and migration team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the sunset readiness plan with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; affected users and systems are accounted for before a proposed cutoff. Use configured search, fetch, read, browser, test, and write capabilities only when rele...Votes: 0GitHub stars: 2
- Product Ops Sunset Scope Intake GateUse when a new feature sunset and migration request needs a bounded work scope to produce a scoped intake card for the sunset readiness plan. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; affected users and systems are accounted for before a proposed cutoff. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, and ...Votes: 0GitHub stars: 2
- Product Ops Sunset Source Provenance LedgerUse when a decision about feature sunset and migration depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the sunset readiness plan. Success means each material claim has a source, version/date, location, and confidence note; affected users and systems are accounted for before a proposed cutoff. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement t...Votes: 0GitHub stars: 2
- Product Ops Sunset Threshold Rule CheckUse when a feature sunset and migration decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the sunset readiness 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; affected users and systems are accounted for before a proposed cutoff. Use configured search, fetch, read, browser, test, and write ca...Votes: 0GitHub stars: 2
- Product Ops Telemetry Approval Evidence PacketUse when a product telemetry result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the metric definition register 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 metric has a stable definition, owner, and privacy-approved collection purpose. Use configured search, fetch, read, browser, test, a...Votes: 0GitHub stars: 2
- Product Ops Telemetry Change Impact TraceUse when a version, rule, source, or stakeholder change may affect product telemetry to produce a before/after change record and impact map for the metric definition register. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each metric has a stable definition, owner, and privacy-approved collection purpose. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and author...Votes: 0GitHub stars: 2
- Product Ops Telemetry Closeout Handoff LedgerUse when a product telemetry work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the metric definition register 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 metric has a stable definition, owner, and privacy-approved collection purpose. Use configured search, fetch, read, browser, test, and write capabilities o...Votes: 0GitHub stars: 2
- Product Ops Telemetry Completeness ReconciliationUse when the product telemetry workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the metric definition register 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 metric has a stable definition, owner, and privacy-approved collection purpose. Use configured search, fetch, read, browser, test, and write ...Votes: 0GitHub stars: 2
- Product Ops Telemetry Exception Triage QueueUse when the product telemetry workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the metric definition register 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 metric has a stable definition, owner, and privacy-approved collection purpose. Use configured search, fetch, read, browser, test, and write capabilities ...Votes: 0GitHub stars: 2
- Product Ops Telemetry Recovery Readiness DrillUse when the product telemetry workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the metric definition register 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 metric has a stable definition, owner, and privacy-approved collection purpose. Use configured search, fetch, read, browser, test, and write ca...Votes: 0GitHub stars: 2
- Product Ops Telemetry Scenario Sensitivity MatrixUse when the product telemetry team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the metric definition register with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each metric has a stable definition, owner, and privacy-approved collection purpose. Use configured search, fetch, read, browser, test, and write capabilities only w...Votes: 0GitHub stars: 2
- Product Ops Telemetry Scope Intake GateUse when a new product telemetry request needs a bounded work scope to produce a scoped intake card for the metric definition register. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each metric has a stable definition, owner, and privacy-approved collection purpose. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused pass...Votes: 0GitHub stars: 2
- Product Ops Telemetry Source Provenance LedgerUse when a decision about product telemetry depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the metric definition register. Success means each material claim has a source, version/date, location, and confidence note; each metric has a stable definition, owner, and privacy-approved collection purpose. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refi...Votes: 0GitHub stars: 2
- Product Ops Telemetry Threshold Rule CheckUse when a product telemetry decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the metric definition register 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 metric has a stable definition, owner, and privacy-approved collection purpose. Use configured search, fetch, read, browser, test, and ...Votes: 0GitHub stars: 2
- Strategy Drawdown And Attribution AnalysisUse when a task involves explaining a strategy's losses by time, exposure, instrument, and cost component to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform production, financia...Votes: 0GitHub stars: 2
- Usage Based Pricing Capability Surface MapUse when the actual capability boundary of Usage-based pricing analysis needs to be distinguished from assumptions. Produce a capability map for Usage-based pricing analysis 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 meter definition, billable unit, co...Votes: 0GitHub stars: 2
- Usage Based Pricing Change Impact AssessmentUse when a proposed Usage-based pricing analysis version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Usage-based pricing analysis 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 meter definition, billable unit, ...Votes: 0GitHub stars: 2
- Usage Based Pricing Failure Triage RecordUse when a reproducible Usage-based pricing analysis symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Usage-based pricing analysis 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 meter definition, billable unit, cohort boundary, cost basis, and forec...Votes: 0GitHub stars: 2
- Usage Based Pricing Input Output ContractUse when the accepted inputs or produced outputs for Usage-based pricing analysis need a checkable boundary. Produce an input/output contract for Usage-based pricing analysis 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 meter definition, billable unit, cohort boundary, cost basis, a...Votes: 0GitHub stars: 2
- Usage Based Pricing Integration Parity TraceUse when Usage-based pricing analysis exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Usage-based pricing analysis 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 meter definition, billable unit, cohort boundary, cost basis, and forecast uncer...Votes: 0GitHub stars: 2
- Usage Based Pricing Performance EnvelopeUse when Usage-based pricing analysis must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Usage-based pricing analysis 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 meter definition, billable unit, cohort boundary, cos...Votes: 0GitHub stars: 2
- Usage Based Pricing Permission Boundary ReviewUse when Usage-based pricing analysis may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Usage-based pricing analysis 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 meter definition, billable unit, cohort bo...Votes: 0GitHub stars: 2
- Usage Based Pricing Release Handoff RecordUse when a Usage-based pricing analysis review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Usage-based pricing analysis 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 meter definition, billable unit, co...Votes: 0GitHub stars: 2
- Usage Based Pricing Reproducibility Fixture PlanUse when a Usage-based pricing analysis result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Usage-based pricing analysis 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 meter d...Votes: 0GitHub stars: 2
- Usage Based Pricing Version CompatibilityUse when a Usage-based pricing analysis integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Usage-based pricing analysis 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 meter definition, billable uni...Votes: 0GitHub stars: 2
- Hospitality Ops Events Approval Evidence PacketUse when a event production operations result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the event readiness checklist 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 critical dependency has a current status and an accountable decision owner. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Hospitality Ops Events Change Impact TraceUse when a version, rule, source, or stakeholder change may affect event production operations to produce a before/after change record and impact map for the event readiness checklist. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; every critical dependency has a current status and an accountable decision owner. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and ...Votes: 0GitHub stars: 2
- Hospitality Ops Events Closeout Handoff LedgerUse when a event production operations work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the event readiness checklist 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 critical dependency has a current status and an accountable decision owner. Use configured search, fetch, read, browser, test, and write capabili...Votes: 0GitHub stars: 2
- Hospitality Ops Events Completeness ReconciliationUse when the event production operations workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the event readiness checklist 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 critical dependency has a current status and an accountable decision owner. Use configured search, fetch, read, browser, test, and ...Votes: 0GitHub stars: 2
- Hospitality Ops Events Exception Triage QueueUse when the event production operations workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the event readiness checklist 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 critical dependency has a current status and an accountable decision owner. Use configured search, fetch, read, browser, test, and write capabil...Votes: 0GitHub stars: 2
- Hospitality Ops Events Recovery Readiness DrillUse when the event production operations workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the event readiness checklist 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 critical dependency has a current status and an accountable decision owner. Use configured search, fetch, read, browser, test, and wr...Votes: 0GitHub stars: 2
- Hospitality Ops Events Scenario Sensitivity MatrixUse when the event production operations team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the event readiness checklist with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; every critical dependency has a current status and an accountable decision owner. Use configured search, fetch, read, browser, test, and write capabilities ...Votes: 0GitHub stars: 2
- Hospitality Ops Events Scope Intake GateUse when a new event production operations request needs a bounded work scope to produce a scoped intake card for the event readiness checklist. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; every critical dependency has a current status and an accountable decision owner. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focuse...Votes: 0GitHub stars: 2
- Hospitality Ops Events Source Provenance LedgerUse when a decision about event production operations depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the event readiness checklist. Success means each material claim has a source, version/date, location, and confidence note; every critical dependency has a current status and an accountable decision owner. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limi...Votes: 0GitHub stars: 2
- Hospitality Ops Events Threshold Rule CheckUse when a event production operations decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the event readiness checklist 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 critical dependency has a current status and an accountable decision owner. Use configured search, fetch, read, browser, test...Votes: 0GitHub stars: 2
- Hospitality Ops Food Records Approval Evidence PacketUse when a food-safety record administration result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the food-safety log exception 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; missing or out-of-range records are escalated to qualified staff and never auto-corrected. Use configured search, f...Votes: 0GitHub stars: 2
- Hospitality Ops Food Records Change Impact TraceUse when a version, rule, source, or stakeholder change may affect food-safety record administration to produce a before/after change record and impact map for the food-safety log exception report. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; missing or out-of-range records are escalated to qualified staff and never auto-corrected. Use configured search, fetch, read, browser, test, and write capabilities o...Votes: 0GitHub stars: 2
- Hospitality Ops Food Records Closeout Handoff LedgerUse when a food-safety record administration work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the food-safety log exception 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; missing or out-of-range records are escalated to qualified staff and never auto-corrected. Use configured search, fetch, read, browser, te...Votes: 0GitHub stars: 2
- Hospitality Ops Food Records Completeness ReconciliationUse when the food-safety record administration workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the food-safety log exception 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; missing or out-of-range records are escalated to qualified staff and never auto-corrected. Use configured search, fetch, rea...Votes: 0GitHub stars: 2
- Hospitality Ops Food Records Exception Triage QueueUse when the food-safety record administration workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the food-safety log exception 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; missing or out-of-range records are escalated to qualified staff and never auto-corrected. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Hospitality Ops Food Records Recovery Readiness DrillUse when the food-safety record administration workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the food-safety log exception 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; missing or out-of-range records are escalated to qualified staff and never auto-corrected. Use configured search, fetch, read,...Votes: 0GitHub stars: 2
- Hospitality Ops Food Records Scenario Sensitivity MatrixUse when the food-safety record administration team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the food-safety log exception report with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; missing or out-of-range records are escalated to qualified staff and never auto-corrected. Use configured search, fetch, read, browser, test, a...Votes: 0GitHub stars: 2
- Hospitality Ops Food Records Scope Intake GateUse when a new food-safety record administration request needs a bounded work scope to produce a scoped intake card for the food-safety log exception report. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; missing or out-of-range records are escalated to qualified staff and never auto-corrected. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refi...Votes: 0GitHub stars: 2
- Hospitality Ops Food Records Source Provenance LedgerUse when a decision about food-safety record administration depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the food-safety log exception report. Success means each material claim has a source, version/date, location, and confidence note; missing or out-of-range records are escalated to qualified staff and never auto-corrected. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized....Votes: 0GitHub stars: 2
- Hospitality Ops Food Records Threshold Rule CheckUse when a food-safety record administration decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the food-safety log exception 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; missing or out-of-range records are escalated to qualified staff and never auto-corrected. Use configured search, fetc...Votes: 0GitHub stars: 2
- Hospitality Ops Frontdesk Approval Evidence PacketUse when a front-desk shift operations result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the shift handoff log 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 unresolved issue has an owner, timestamp, and safe escalation route. Use configured search, fetch, read, browser, test, and write c...Votes: 0GitHub stars: 2