All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Hospitality Ops Restaurant Change Impact TraceUse when a version, rule, source, or stakeholder change may affect restaurant service coordination to produce a before/after change record and impact map for the service readiness board. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; staffing and availability are current and no customer promise is made from stale data. Use configured search, fetch, read, browser, test, and write capabilities only when releva...Votes: 0GitHub stars: 2
- Hospitality Ops Restaurant Closeout Handoff LedgerUse when a restaurant service coordination work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the service readiness board 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; staffing and availability are current and no customer promise is made from stale data. Use configured search, fetch, read, browser, test, and write c...Votes: 0GitHub stars: 2
- Hospitality Ops Restaurant Completeness ReconciliationUse when the restaurant service coordination workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the service readiness board 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; staffing and availability are current and no customer promise is made from stale data. Use configured search, fetch, read, browser, tes...Votes: 0GitHub stars: 2
- Hospitality Ops Restaurant Exception Triage QueueUse when the restaurant service coordination workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the service readiness board 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; staffing and availability are current and no customer promise is made from stale data. Use configured search, fetch, read, browser, test, and write ...Votes: 0GitHub stars: 2
- Hospitality Ops Restaurant Recovery Readiness DrillUse when the restaurant service coordination workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the service readiness board 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; staffing and availability are current and no customer promise is made from stale data. Use configured search, fetch, read, browser, test,...Votes: 0GitHub stars: 2
- Hospitality Ops Restaurant Scenario Sensitivity MatrixUse when the restaurant service coordination team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the service readiness board with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; staffing and availability are current and no customer promise is made from stale data. Use configured search, fetch, read, browser, test, and write capabi...Votes: 0GitHub stars: 2
- Hospitality Ops Restaurant Scope Intake GateUse when a new restaurant service coordination request needs a bounded work scope to produce a scoped intake card for the service readiness board. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; staffing and availability are current and no customer promise is made from stale data. 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
- Hospitality Ops Restaurant Source Provenance LedgerUse when a decision about restaurant service coordination depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the service readiness board. Success means each material claim has a source, version/date, location, and confidence note; staffing and availability are current and no customer promise is made from stale data. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidenc...Votes: 0GitHub stars: 2
- Hospitality Ops Restaurant Threshold Rule CheckUse when a restaurant service coordination decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the service readiness board 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; staffing and availability are current and no customer promise is made from stale data. Use configured search, fetch, read, browse...Votes: 0GitHub stars: 2
- Hospitality Ops Revenue Ops Approval Evidence PacketUse when a hospitality revenue operations result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the revenue variance brief 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; comparisons use consistent denominators and no unapproved price change is proposed as final. Use configured search, fetch, read,...Votes: 0GitHub stars: 2
- Hospitality Ops Revenue Ops Change Impact TraceUse when a version, rule, source, or stakeholder change may affect hospitality revenue operations to produce a before/after change record and impact map for the revenue variance brief. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; comparisons use consistent denominators and no unapproved price change is proposed as final. Use configured search, fetch, read, browser, test, and write capabilities only when re...Votes: 0GitHub stars: 2
- Hospitality Ops Revenue Ops Closeout Handoff LedgerUse when a hospitality revenue operations work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the revenue variance brief 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; comparisons use consistent denominators and no unapproved price change is proposed as final. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2
- Hospitality Ops Revenue Ops Completeness ReconciliationUse when the hospitality revenue operations workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the revenue variance brief 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; comparisons use consistent denominators and no unapproved price change is proposed as final. Use configured search, fetch, read, browser,...Votes: 0GitHub stars: 2
- Hospitality Ops Revenue Ops Exception Triage QueueUse when the hospitality revenue operations workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the revenue variance brief 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; comparisons use consistent denominators and no unapproved price change is proposed as final. Use configured search, fetch, read, browser, test, and wr...Votes: 0GitHub stars: 2
- Hospitality Ops Revenue Ops Recovery Readiness DrillUse when the hospitality revenue operations workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the revenue variance brief 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; comparisons use consistent denominators and no unapproved price change is proposed as final. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Hospitality Ops Revenue Ops Scenario Sensitivity MatrixUse when the hospitality revenue operations team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the revenue variance brief with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; comparisons use consistent denominators and no unapproved price change is proposed as final. Use configured search, fetch, read, browser, test, and write ca...Votes: 0GitHub stars: 2
- Hospitality Ops Revenue Ops Scope Intake GateUse when a new hospitality revenue operations request needs a bounded work scope to produce a scoped intake card for the revenue variance brief. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; comparisons use consistent denominators and no unapproved price change is proposed as final. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to t...Votes: 0GitHub stars: 2
- Hospitality Ops Revenue Ops Source Provenance LedgerUse when a decision about hospitality revenue operations depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the revenue variance brief. Success means each material claim has a source, version/date, location, and confidence note; comparisons use consistent denominators and no unapproved price change is proposed as final. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evi...Votes: 0GitHub stars: 2
- Hospitality Ops Revenue Ops Threshold Rule CheckUse when a hospitality revenue operations decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the revenue variance brief 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; comparisons use consistent denominators and no unapproved price change is proposed as final. Use configured search, fetch, read, br...Votes: 0GitHub stars: 2
- Hospitality Ops Travel Approval Evidence PacketUse when a travel itinerary coordination result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the travel option 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; every listed option is dated, available only if confirmed, and marked with verification time. Use configured search, fetch, rea...Votes: 0GitHub stars: 2
- Hospitality Ops Travel Change Impact TraceUse when a version, rule, source, or stakeholder change may affect travel itinerary coordination to produce a before/after change record and impact map for the travel option comparison. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; every listed option is dated, available only if confirmed, and marked with verification time. Use configured search, fetch, read, browser, test, and write capabilities only when ...Votes: 0GitHub stars: 2
- Hospitality Ops Travel Closeout Handoff LedgerUse when a travel itinerary coordination work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the travel option 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; every listed option is dated, available only if confirmed, and marked with verification time. Use configured search, fetch, read, browser, test, and w...Votes: 0GitHub stars: 2
- Hospitality Ops Travel Completeness ReconciliationUse when the travel itinerary coordination workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the travel option 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; every listed option is dated, available only if confirmed, and marked with verification time. Use configured search, fetch, read, browse...Votes: 0GitHub stars: 2
- Hospitality Ops Travel Exception Triage QueueUse when the travel itinerary coordination workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the travel option 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; every listed option is dated, available only if confirmed, and marked with verification time. Use configured search, fetch, read, browser, test, and ...Votes: 0GitHub stars: 2
- Hospitality Ops Travel Recovery Readiness DrillUse when the travel itinerary coordination workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the travel option 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; every listed option is dated, available only if confirmed, and marked with verification time. Use configured search, fetch, read, browser,...Votes: 0GitHub stars: 2
- Hospitality Ops Travel Scenario Sensitivity MatrixUse when the travel itinerary coordination team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the travel option comparison with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; every listed option is dated, available only if confirmed, and marked with verification time. Use configured search, fetch, read, browser, test, and write ...Votes: 0GitHub stars: 2
- Hospitality Ops Travel Scope Intake GateUse when a new travel itinerary coordination request needs a bounded work scope to produce a scoped intake card for the travel option comparison. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; every listed option is dated, available only if confirmed, and marked with verification time. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to...Votes: 0GitHub stars: 2
- Hospitality Ops Travel Source Provenance LedgerUse when a decision about travel itinerary coordination depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the travel option comparison. Success means each material claim has a source, version/date, location, and confidence note; every listed option is dated, available only if confirmed, and marked with verification time. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record e...Votes: 0GitHub stars: 2
- Hospitality Ops Travel Threshold Rule CheckUse when a travel itinerary coordination decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the travel option 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; every listed option is dated, available only if confirmed, and marked with verification time. Use configured search, fetch, read, ...Votes: 0GitHub stars: 2
- Retail Ops Catalog Approval Evidence PacketUse when a product catalog and listing quality result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the catalog quality 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; every proposed correction maps to an evidence source and no listing is published automatically. Use configured se...Votes: 0GitHub stars: 2
- Retail Ops Catalog Change Impact TraceUse when a version, rule, source, or stakeholder change may affect product catalog and listing quality to produce a before/after change record and impact map for the catalog quality exception report. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; every proposed correction maps to an evidence source and no listing is published automatically. Use configured search, fetch, read, browser, test, and write capabil...Votes: 0GitHub stars: 2
- Retail Ops Catalog Closeout Handoff LedgerUse when a product catalog and listing quality work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the catalog quality 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; every proposed correction maps to an evidence source and no listing is published automatically. Use configured search, fetch, read, brow...Votes: 0GitHub stars: 2
- Retail Ops Catalog Completeness ReconciliationUse when the product catalog and listing quality workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the catalog quality 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; every proposed correction maps to an evidence source and no listing is published automatically. Use configured search, fet...Votes: 0GitHub stars: 2
- Retail Ops Catalog Exception Triage QueueUse when the product catalog and listing quality workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the catalog quality 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; every proposed correction maps to an evidence source and no listing is published automatically. Use configured search, fetch, read, bro...Votes: 0GitHub stars: 2
- Retail Ops Catalog Recovery Readiness DrillUse when the product catalog and listing quality workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the catalog quality 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; every proposed correction maps to an evidence source and no listing is published automatically. Use configured search, fetch...Votes: 0GitHub stars: 2
- Retail Ops Catalog Scenario Sensitivity MatrixUse when the product catalog and listing quality team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the catalog quality exception report with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; every proposed correction maps to an evidence source and no listing is published automatically. Use configured search, fetch, read, browser, ...Votes: 0GitHub stars: 2
- Retail Ops Catalog Scope Intake GateUse when a new product catalog and listing quality request needs a bounded work scope to produce a scoped intake card for the catalog quality exception report. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; every proposed correction maps to an evidence source and no listing is published automatically. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, lim...Votes: 0GitHub stars: 2
- Retail Ops Catalog Source Provenance LedgerUse when a decision about product catalog and listing quality depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the catalog quality exception report. Success means each material claim has a source, version/date, location, and confidence note; every proposed correction maps to an evidence source and no listing is published automatically. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and auth...Votes: 0GitHub stars: 2
- Retail Ops Catalog Threshold Rule CheckUse when a product catalog and listing quality decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the catalog quality 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; every proposed correction maps to an evidence source and no listing is published automatically. Use configured searc...Votes: 0GitHub stars: 2
- Retail Ops Fraud Review Approval Evidence PacketUse when a retail transaction anomaly review result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the transaction review queue 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; signals are presented as review leads rather than proof and no transaction is blocked automatically. Use configured search,...Votes: 0GitHub stars: 2
- Retail Ops Fraud Review Change Impact TraceUse when a version, rule, source, or stakeholder change may affect retail transaction anomaly review to produce a before/after change record and impact map for the transaction review queue. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; signals are presented as review leads rather than proof and no transaction is blocked automatically. Use configured search, fetch, read, browser, test, and write capabilities...Votes: 0GitHub stars: 2
- Retail Ops Fraud Review Closeout Handoff LedgerUse when a retail transaction anomaly review work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the transaction review queue 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; signals are presented as review leads rather than proof and no transaction is blocked automatically. Use configured search, fetch, read, browser, ...Votes: 0GitHub stars: 2
- Retail Ops Fraud Review Completeness ReconciliationUse when the retail transaction anomaly review workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the transaction review queue 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; signals are presented as review leads rather than proof and no transaction is blocked automatically. Use configured search, fetch, r...Votes: 0GitHub stars: 2
- Retail Ops Fraud Review Exception Triage QueueUse when the retail transaction anomaly review workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the transaction review queue 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; signals are presented as review leads rather than proof and no transaction is blocked automatically. Use configured search, fetch, read, browser,...Votes: 0GitHub stars: 2
- Retail Ops Fraud Review Recovery Readiness DrillUse when the retail transaction anomaly review workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the transaction review queue 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; signals are presented as review leads rather than proof and no transaction is blocked automatically. Use configured search, fetch, rea...Votes: 0GitHub stars: 2
- Retail Ops Fraud Review Scenario Sensitivity MatrixUse when the retail transaction anomaly review team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the transaction review queue with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; signals are presented as review leads rather than proof and no transaction is blocked automatically. Use configured search, fetch, read, browser, test,...Votes: 0GitHub stars: 2
- Retail Ops Fraud Review Scope Intake GateUse when a new retail transaction anomaly review request needs a bounded work scope to produce a scoped intake card for the transaction review queue. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; signals are presented as review leads rather than proof and no transaction is blocked automatically. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit re...Votes: 0GitHub stars: 2
- Retail Ops Fraud Review Source Provenance LedgerUse when a decision about retail transaction anomaly review depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the transaction review queue. Success means each material claim has a source, version/date, location, and confidence note; signals are presented as review leads rather than proof and no transaction is blocked automatically. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorize...Votes: 0GitHub stars: 2
- Retail Ops Fraud Review Threshold Rule CheckUse when a retail transaction anomaly review decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the transaction review queue 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; signals are presented as review leads rather than proof and no transaction is blocked automatically. Use configured search, fe...Votes: 0GitHub stars: 2
- Retail Ops Fulfillment Approval Evidence PacketUse when a order and fulfillment exception management result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the fulfillment exception 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; each exception has a source timestamp and an owner; no shipment or customer message is initiated. Use configu...Votes: 0GitHub stars: 2