All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Aas Saas Entitlement Parity Approval Evidence PacketUse when a subscription entitlement parity result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the entitlement-to-plan reconciliation 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; granted features match the declared plan state and exceptions are routed for review. Use configured search, fetch, ...Votes: 0GitHub stars: 2
- Aas Saas Entitlement Parity Change Impact TraceUse when a version, rule, source, or stakeholder change may affect subscription entitlement parity to produce a before/after change record and impact map for the entitlement-to-plan reconciliation. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; granted features match the declared plan state and exceptions are routed for review. Use configured search, fetch, read, browser, test, and write capabilities only wh...Votes: 0GitHub stars: 2
- Aas Saas Entitlement Parity Closeout Handoff LedgerUse when a subscription entitlement parity work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the entitlement-to-plan reconciliation 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; granted features match the declared plan state and exceptions are routed for review. Use configured search, fetch, read, browser, test, an...Votes: 0GitHub stars: 2
- Aas Saas Entitlement Parity Completeness ReconciliationUse when the subscription entitlement parity workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the entitlement-to-plan reconciliation 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; granted features match the declared plan state and exceptions are routed for review. Use configured search, fetch, read, bro...Votes: 0GitHub stars: 2
- Aas Saas Entitlement Parity Exception Triage QueueUse when the subscription entitlement parity workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the entitlement-to-plan reconciliation 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; granted features match the declared plan state and exceptions are routed for review. Use configured search, fetch, read, browser, test, a...Votes: 0GitHub stars: 2
- Aas Saas Entitlement Parity Recovery Readiness DrillUse when the subscription entitlement parity workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the entitlement-to-plan reconciliation 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; granted features match the declared plan state and exceptions are routed for review. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2
- Aas Saas Entitlement Parity Scenario Sensitivity MatrixUse when the subscription entitlement parity team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the entitlement-to-plan reconciliation with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; granted features match the declared plan state and exceptions are routed for review. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2
- Aas Saas Entitlement Parity Scope Intake GateUse when a new subscription entitlement parity request needs a bounded work scope to produce a scoped intake card for the entitlement-to-plan reconciliation. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; granted features match the declared plan state and exceptions are routed for review. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement...Votes: 0GitHub stars: 2
- Aas Saas Entitlement Parity Source Provenance LedgerUse when a decision about subscription entitlement parity depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the entitlement-to-plan reconciliation. Success means each material claim has a source, version/date, location, and confidence note; granted features match the declared plan state and exceptions are routed for review. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Recor...Votes: 0GitHub stars: 2
- Aas Saas Entitlement Parity Threshold Rule CheckUse when a subscription entitlement parity decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the entitlement-to-plan reconciliation 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; granted features match the declared plan state and exceptions are routed for review. Use configured search, fetch, rea...Votes: 0GitHub stars: 2
- Aas Saas Meter Duplicates Approval Evidence PacketUse when a usage-meter duplicate event reconciliation result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the metered-usage reconciliation 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 retried event is counted according to the declared idempotency rule. Use configured search, fetch, read, bro...Votes: 0GitHub stars: 2
- Aas Saas Meter Duplicates Change Impact TraceUse when a version, rule, source, or stakeholder change may affect usage-meter duplicate event reconciliation to produce a before/after change record and impact map for the metered-usage reconciliation. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; a retried event is counted according to the declared idempotency rule. Use configured search, fetch, read, browser, test, and write capabilities only when releva...Votes: 0GitHub stars: 2
- Aas Saas Meter Duplicates Closeout Handoff LedgerUse when a usage-meter duplicate event reconciliation work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the metered-usage reconciliation 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 retried event is counted according to the declared idempotency rule. Use configured search, fetch, read, browser, test, and write c...Votes: 0GitHub stars: 2
- Aas Saas Meter Duplicates Completeness ReconciliationUse when the usage-meter duplicate event reconciliation workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the metered-usage reconciliation 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 retried event is counted according to the declared idempotency rule. Use configured search, fetch, read, browser, tes...Votes: 0GitHub stars: 2
- Aas Saas Meter Duplicates Exception Triage QueueUse when the usage-meter duplicate event reconciliation workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the metered-usage reconciliation 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 retried event is counted according to the declared idempotency rule. Use configured search, fetch, read, browser, test, and write ...Votes: 0GitHub stars: 2
- Aas Saas Meter Duplicates Recovery Readiness DrillUse when the usage-meter duplicate event reconciliation workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the metered-usage reconciliation 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 retried event is counted according to the declared idempotency rule. Use configured search, fetch, read, browser, test,...Votes: 0GitHub stars: 2
- Aas Saas Meter Duplicates Scenario Sensitivity MatrixUse when the usage-meter duplicate event reconciliation team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the metered-usage reconciliation with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; a retried event is counted according to the declared idempotency rule. Use configured search, fetch, read, browser, test, and write capabi...Votes: 0GitHub stars: 2
- Aas Saas Meter Duplicates Scope Intake GateUse when a new usage-meter duplicate event reconciliation request needs a bounded work scope to produce a scoped intake card for the metered-usage reconciliation. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; a retried event is counted according to the declared idempotency rule. 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
- Aas Saas Meter Duplicates Source Provenance LedgerUse when a decision about usage-meter duplicate event reconciliation depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the metered-usage reconciliation. Success means each material claim has a source, version/date, location, and confidence note; a retried event is counted according to the declared idempotency rule. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidenc...Votes: 0GitHub stars: 2
- Aas Saas Meter Duplicates Threshold Rule CheckUse when a usage-meter duplicate event reconciliation decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the metered-usage reconciliation 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 retried event is counted according to the declared idempotency rule. Use configured search, fetch, read, browse...Votes: 0GitHub stars: 2
- Aas Saas Pricing Test Guard Approval Evidence PacketUse when a SaaS pricing experiment guardrails result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the pricing experiment review card 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 test is not launched and guardrails cover fairness, billing clarity, and rollback. Use configured search, fetch,...Votes: 0GitHub stars: 2
- Aas Saas Pricing Test Guard Change Impact TraceUse when a version, rule, source, or stakeholder change may affect SaaS pricing experiment guardrails to produce a before/after change record and impact map for the pricing experiment review card. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the test is not launched and guardrails cover fairness, billing clarity, and rollback. Use configured search, fetch, read, browser, test, and write capabilities only w...Votes: 0GitHub stars: 2
- Aas Saas Pricing Test Guard Closeout Handoff LedgerUse when a SaaS pricing experiment guardrails work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the pricing experiment review card 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 test is not launched and guardrails cover fairness, billing clarity, and rollback. Use configured search, fetch, read, browser, test, a...Votes: 0GitHub stars: 2
- Aas Saas Pricing Test Guard Completeness ReconciliationUse when the SaaS pricing experiment guardrails workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the pricing experiment review card 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 test is not launched and guardrails cover fairness, billing clarity, and rollback. Use configured search, fetch, read, br...Votes: 0GitHub stars: 2
- Aas Saas Pricing Test Guard Exception Triage QueueUse when the SaaS pricing experiment guardrails workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the pricing experiment review card 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 test is not launched and guardrails cover fairness, billing clarity, and rollback. Use configured search, fetch, read, browser, test, ...Votes: 0GitHub stars: 2
- Aas Saas Pricing Test Guard Recovery Readiness DrillUse when the SaaS pricing experiment guardrails workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the pricing experiment review card 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 test is not launched and guardrails cover fairness, billing clarity, and rollback. Use configured search, fetch, read, brow...Votes: 0GitHub stars: 2
- Aas Saas Pricing Test Guard Scenario Sensitivity MatrixUse when the SaaS pricing experiment guardrails team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the pricing experiment review card with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the test is not launched and guardrails cover fairness, billing clarity, and rollback. Use configured search, fetch, read, browser, test, and wr...Votes: 0GitHub stars: 2
- Aas Saas Pricing Test Guard Scope Intake GateUse when a new SaaS pricing experiment guardrails request needs a bounded work scope to produce a scoped intake card for the pricing experiment review card. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the test is not launched and guardrails cover fairness, billing clarity, and rollback. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinemen...Votes: 0GitHub stars: 2
- Aas Saas Pricing Test Guard Source Provenance LedgerUse when a decision about SaaS pricing experiment guardrails depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the pricing experiment review card. Success means each material claim has a source, version/date, location, and confidence note; the test is not launched and guardrails cover fairness, billing clarity, and rollback. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Reco...Votes: 0GitHub stars: 2
- Aas Saas Pricing Test Guard Threshold Rule CheckUse when a SaaS pricing experiment guardrails decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the pricing experiment review card 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 test is not launched and guardrails cover fairness, billing clarity, and rollback. Use configured search, fetch, re...Votes: 0GitHub stars: 2
- Aas Saas Proration Cases Approval Evidence PacketUse when a subscription proration edge cases result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the proration scenario 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; calculated amounts reconcile to the declared rules without submitting a live invoice. Use configured search, fetch, read, b...Votes: 0GitHub stars: 2
- Aas Saas Proration Cases Change Impact TraceUse when a version, rule, source, or stakeholder change may affect subscription proration edge cases to produce a before/after change record and impact map for the proration scenario table. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; calculated amounts reconcile to the declared rules without submitting a live invoice. Use configured search, fetch, read, browser, test, and write capabilities only when rele...Votes: 0GitHub stars: 2
- Aas Saas Proration Cases Closeout Handoff LedgerUse when a subscription proration edge cases work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the proration scenario 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; calculated amounts reconcile to the declared rules without submitting a live invoice. Use configured search, fetch, read, browser, test, and write...Votes: 0GitHub stars: 2
- Aas Saas Proration Cases Completeness ReconciliationUse when the subscription proration edge cases workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the proration scenario 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; calculated amounts reconcile to the declared rules without submitting a live invoice. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Aas Saas Proration Cases Exception Triage QueueUse when the subscription proration edge cases workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the proration scenario 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; calculated amounts reconcile to the declared rules without submitting a live invoice. Use configured search, fetch, read, browser, test, and writ...Votes: 0GitHub stars: 2
- Aas Saas Proration Cases Recovery Readiness DrillUse when the subscription proration edge cases workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the proration scenario 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; calculated amounts reconcile to the declared rules without submitting a live invoice. Use configured search, fetch, read, browser, tes...Votes: 0GitHub stars: 2
- Aas Saas Proration Cases Scenario Sensitivity MatrixUse when the subscription proration edge cases team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the proration scenario table with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; calculated amounts reconcile to the declared rules without submitting a live invoice. Use configured search, fetch, read, browser, test, and write capa...Votes: 0GitHub stars: 2
- Aas Saas Proration Cases Scope Intake GateUse when a new subscription proration edge cases request needs a bounded work scope to produce a scoped intake card for the proration scenario table. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; calculated amounts reconcile to the declared rules without submitting a live invoice. 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
- Aas Saas Proration Cases Source Provenance LedgerUse when a decision about subscription proration edge cases depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the proration scenario table. Success means each material claim has a source, version/date, location, and confidence note; calculated amounts reconcile to the declared rules without submitting a live invoice. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evide...Votes: 0GitHub stars: 2
- Aas Saas Proration Cases Threshold Rule CheckUse when a subscription proration edge cases decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the proration scenario 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; calculated amounts reconcile to the declared rules without submitting a live invoice. Use configured search, fetch, read, brow...Votes: 0GitHub stars: 2
- Aas Saas Refund Credit Bridge Approval Evidence PacketUse when a refund and credit-note reconciliation result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the refund-to-ledger bridge 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 adjustment maps to an auditable transaction or remains explicitly unmatched. Use configured search, fetch, read, br...Votes: 0GitHub stars: 2
- Aas Saas Refund Credit Bridge Change Impact TraceUse when a version, rule, source, or stakeholder change may affect refund and credit-note reconciliation to produce a before/after change record and impact map for the refund-to-ledger bridge. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each adjustment maps to an auditable transaction or remains explicitly unmatched. Use configured search, fetch, read, browser, test, and write capabilities only when relev...Votes: 0GitHub stars: 2
- Aas Saas Refund Credit Bridge Closeout Handoff LedgerUse when a refund and credit-note reconciliation work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the refund-to-ledger bridge 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 adjustment maps to an auditable transaction or remains explicitly unmatched. Use configured search, fetch, read, browser, test, and write ...Votes: 0GitHub stars: 2
- Aas Saas Refund Credit Bridge Completeness ReconciliationUse when the refund and credit-note reconciliation workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the refund-to-ledger bridge 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 adjustment maps to an auditable transaction or remains explicitly unmatched. Use configured search, fetch, read, browser, te...Votes: 0GitHub stars: 2
- Aas Saas Refund Credit Bridge Exception Triage QueueUse when the refund and credit-note reconciliation workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the refund-to-ledger bridge 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 adjustment maps to an auditable transaction or remains explicitly unmatched. Use configured search, fetch, read, browser, test, and write...Votes: 0GitHub stars: 2
- Aas Saas Refund Credit Bridge Recovery Readiness DrillUse when the refund and credit-note reconciliation workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the refund-to-ledger bridge 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 adjustment maps to an auditable transaction or remains explicitly unmatched. Use configured search, fetch, read, browser, test...Votes: 0GitHub stars: 2
- Aas Saas Refund Credit Bridge Scenario Sensitivity MatrixUse when the refund and credit-note reconciliation team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the refund-to-ledger bridge with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each adjustment maps to an auditable transaction or remains explicitly unmatched. Use configured search, fetch, read, browser, test, and write capab...Votes: 0GitHub stars: 2
- Aas Saas Refund Credit Bridge Scope Intake GateUse when a new refund and credit-note reconciliation request needs a bounded work scope to produce a scoped intake card for the refund-to-ledger bridge. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each adjustment maps to an auditable transaction or remains explicitly unmatched. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to thre...Votes: 0GitHub stars: 2
- Aas Saas Refund Credit Bridge Source Provenance LedgerUse when a decision about refund and credit-note reconciliation depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the refund-to-ledger bridge. Success means each material claim has a source, version/date, location, and confidence note; each adjustment maps to an auditable transaction or remains explicitly unmatched. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record eviden...Votes: 0GitHub stars: 2
- Aas Saas Refund Credit Bridge Threshold Rule CheckUse when a refund and credit-note reconciliation decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the refund-to-ledger bridge 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 adjustment maps to an auditable transaction or remains explicitly unmatched. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2