All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Finance Ops Expenses Closeout Handoff LedgerUse when a expense policy administration work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the expense exception 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; each exception is classified against the current policy and no reimbursement is approved automatically. Use configured search, fetch, read, browser, te...Votes: 0GitHub stars: 2
- Finance Ops Expenses Completeness ReconciliationUse when the expense policy administration workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the expense exception 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; each exception is classified against the current policy and no reimbursement is approved automatically. Use configured search, fetch, rea...Votes: 0GitHub stars: 2
- Finance Ops Expenses Exception Triage QueueUse when the expense policy administration workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the expense exception 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; each exception is classified against the current policy and no reimbursement is approved automatically. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Finance Ops Expenses Recovery Readiness DrillUse when the expense policy administration workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the expense exception 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; each exception is classified against the current policy and no reimbursement is approved automatically. Use configured search, fetch, read,...Votes: 0GitHub stars: 2
- Finance Ops Expenses Scenario Sensitivity MatrixUse when the expense policy administration team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the expense exception queue with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each exception is classified against the current policy and no reimbursement is approved automatically. Use configured search, fetch, read, browser, test, a...Votes: 0GitHub stars: 2
- Finance Ops Expenses Scope Intake GateUse when a new expense policy administration request needs a bounded work scope to produce a scoped intake card for the expense exception queue. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each exception is classified against the current policy and no reimbursement is approved automatically. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refi...Votes: 0GitHub stars: 2
- Finance Ops Expenses Source Provenance LedgerUse when a decision about expense policy administration depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the expense exception queue. Success means each material claim has a source, version/date, location, and confidence note; each exception is classified against the current policy and no reimbursement is approved automatically. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized....Votes: 0GitHub stars: 2
- Finance Ops Expenses Threshold Rule CheckUse when a expense policy administration decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the expense exception 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; each exception is classified against the current policy and no reimbursement is approved automatically. Use configured search, fetc...Votes: 0GitHub stars: 2
- Finance Ops Forecast Approval Evidence PacketUse when a budget and forecast result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the forecast 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; each variance bridges to a driver and forecast assumptions are dated and owned. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2
- Finance Ops Forecast Change Impact TraceUse when a version, rule, source, or stakeholder change may affect budget and forecast to produce a before/after change record and impact map for the forecast variance brief. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each variance bridges to a driver and forecast assumptions are dated and owned. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. ...Votes: 0GitHub stars: 2
- Finance Ops Forecast Closeout Handoff LedgerUse when a budget and forecast work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the forecast 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; each variance bridges to a driver and forecast assumptions are dated and owned. Use configured search, fetch, read, browser, test, and write capabilities only wh...Votes: 0GitHub stars: 2
- Finance Ops Forecast Completeness ReconciliationUse when the budget and forecast workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the forecast 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; each variance bridges to a driver and forecast assumptions are dated and owned. Use configured search, fetch, read, browser, test, and write capabi...Votes: 0GitHub stars: 2
- Finance Ops Forecast Exception Triage QueueUse when the budget and forecast workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the forecast 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; each variance bridges to a driver and forecast assumptions are dated and owned. Use configured search, fetch, read, browser, test, and write capabilities only w...Votes: 0GitHub stars: 2
- Finance Ops Forecast Recovery Readiness DrillUse when the budget and forecast workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the forecast 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; each variance bridges to a driver and forecast assumptions are dated and owned. Use configured search, fetch, read, browser, test, and write capabili...Votes: 0GitHub stars: 2
- Finance Ops Forecast Scenario Sensitivity MatrixUse when the budget and forecast team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the forecast variance brief with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each variance bridges to a driver and forecast assumptions are dated and owned. Use configured search, fetch, read, browser, test, and write capabilities only when re...Votes: 0GitHub stars: 2
- Finance Ops Forecast Scope Intake GateUse when a new budget and forecast request needs a bounded work scope to produce a scoped intake card for the forecast variance brief. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each variance bridges to a driver and forecast assumptions are dated and owned. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, an...Votes: 0GitHub stars: 2
- Finance Ops Forecast Source Provenance LedgerUse when a decision about budget and forecast depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the forecast variance brief. Success means each material claim has a source, version/date, location, and confidence note; each variance bridges to a driver and forecast assumptions are dated and owned. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement...Votes: 0GitHub stars: 2
- Finance Ops Forecast Threshold Rule CheckUse when a budget and forecast decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the forecast 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; each variance bridges to a driver and forecast assumptions are dated and owned. Use configured search, fetch, read, browser, test, and write ...Votes: 0GitHub stars: 2
- Finance Ops Insurance Approval Evidence PacketUse when a insurance claim administration result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the claim evidence 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 statement is sourced and coverage or settlement decisions remain with the authorized professional. Use configured search, ...Votes: 0GitHub stars: 2
- Finance Ops Insurance Change Impact TraceUse when a version, rule, source, or stakeholder change may affect insurance claim administration to produce a before/after change record and impact map for the claim evidence register. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each statement is sourced and coverage or settlement decisions remain with the authorized professional. Use configured search, fetch, read, browser, test, and write capabilities ...Votes: 0GitHub stars: 2
- Finance Ops Insurance Closeout Handoff LedgerUse when a insurance claim administration work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the claim evidence 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 statement is sourced and coverage or settlement decisions remain with the authorized professional. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Finance Ops Insurance Completeness ReconciliationUse when the insurance claim administration workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the claim evidence 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 statement is sourced and coverage or settlement decisions remain with the authorized professional. Use configured search, fetch, re...Votes: 0GitHub stars: 2
- Finance Ops Insurance Exception Triage QueueUse when the insurance claim administration workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the claim evidence 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 statement is sourced and coverage or settlement decisions remain with the authorized professional. Use configured search, fetch, read, browser, ...Votes: 0GitHub stars: 2
- Finance Ops Insurance Recovery Readiness DrillUse when the insurance claim administration workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the claim evidence 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 statement is sourced and coverage or settlement decisions remain with the authorized professional. Use configured search, fetch, read...Votes: 0GitHub stars: 2
- Finance Ops Insurance Scenario Sensitivity MatrixUse when the insurance claim administration team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the claim evidence register with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each statement is sourced and coverage or settlement decisions remain with the authorized professional. Use configured search, fetch, read, browser, test, ...Votes: 0GitHub stars: 2
- Finance Ops Insurance Scope Intake GateUse when a new insurance claim administration request needs a bounded work scope to produce a scoped intake card for the claim evidence register. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each statement is sourced and coverage or settlement decisions remain with the authorized professional. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit ref...Votes: 0GitHub stars: 2
- Finance Ops Insurance Source Provenance LedgerUse when a decision about insurance claim administration depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the claim evidence register. Success means each material claim has a source, version/date, location, and confidence note; each statement is sourced and coverage or settlement decisions remain with the authorized professional. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized...Votes: 0GitHub stars: 2
- Finance Ops Insurance Threshold Rule CheckUse when a insurance claim administration decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the claim evidence 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 statement is sourced and coverage or settlement decisions remain with the authorized professional. Use configured search, fet...Votes: 0GitHub stars: 2
- Finance Ops Payables Approval Evidence PacketUse when a accounts payable result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the payables batch 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 invoice line is matched or explicitly exceptioned with an accountable reviewer. Use configured search, fetch, read, browser, test, and write capa...Votes: 0GitHub stars: 2
- Finance Ops Payables Change Impact TraceUse when a version, rule, source, or stakeholder change may affect accounts payable to produce a before/after change record and impact map for the payables batch. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each invoice line is matched or explicitly exceptioned with an accountable reviewer. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record ...Votes: 0GitHub stars: 2
- Finance Ops Payables Closeout Handoff LedgerUse when a accounts payable work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the payables batch 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 invoice line is matched or explicitly exceptioned with an accountable reviewer. Use configured search, fetch, read, browser, test, and write capabilities only when rele...Votes: 0GitHub stars: 2
- Finance Ops Payables Completeness ReconciliationUse when the accounts payable workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the payables batch 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 invoice line is matched or explicitly exceptioned with an accountable reviewer. Use configured search, fetch, read, browser, test, and write capabilities ...Votes: 0GitHub stars: 2
- Finance Ops Payables Exception Triage QueueUse when the accounts payable workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the payables batch 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 invoice line is matched or explicitly exceptioned with an accountable reviewer. Use configured search, fetch, read, browser, test, and write capabilities only when rel...Votes: 0GitHub stars: 2
- Finance Ops Payables Recovery Readiness DrillUse when the accounts payable workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the payables batch 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 invoice line is matched or explicitly exceptioned with an accountable reviewer. Use configured search, fetch, read, browser, test, and write capabilities on...Votes: 0GitHub stars: 2
- Finance Ops Payables Scenario Sensitivity MatrixUse when the accounts payable team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the payables batch with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each invoice line is matched or explicitly exceptioned with an accountable reviewer. Use configured search, fetch, read, browser, test, and write capabilities only when relevant ...Votes: 0GitHub stars: 2
- Finance Ops Payables Scope Intake GateUse when a new accounts payable request needs a bounded work scope to produce a scoped intake card for the payables batch. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each invoice line is matched or explicitly exceptioned with an accountable reviewer. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, and seek ...Votes: 0GitHub stars: 2
- Finance Ops Payables Source Provenance LedgerUse when a decision about accounts payable depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the payables batch. Success means each material claim has a source, version/date, location, and confidence note; each invoice line is matched or explicitly exceptioned with an accountable reviewer. 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
- Finance Ops Payables Threshold Rule CheckUse when a accounts payable decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the payables batch 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 invoice line is matched or explicitly exceptioned with an accountable reviewer. Use configured search, fetch, read, browser, test, and write capabil...Votes: 0GitHub stars: 2
- Finance Ops Receivables Approval Evidence PacketUse when a accounts receivable result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the receivables aging view 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; open balance reconciles to invoices, receipts, credits, and documented disputes. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2
- Finance Ops Receivables Change Impact TraceUse when a version, rule, source, or stakeholder change may affect accounts receivable to produce a before/after change record and impact map for the receivables aging view. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; open balance reconciles to invoices, receipts, credits, and documented disputes. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. ...Votes: 0GitHub stars: 2
- Finance Ops Receivables Closeout Handoff LedgerUse when a accounts receivable work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the receivables aging view 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; open balance reconciles to invoices, receipts, credits, and documented disputes. Use configured search, fetch, read, browser, test, and write capabilities only wh...Votes: 0GitHub stars: 2
- Finance Ops Receivables Completeness ReconciliationUse when the accounts receivable workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the receivables aging view 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; open balance reconciles to invoices, receipts, credits, and documented disputes. Use configured search, fetch, read, browser, test, and write capabi...Votes: 0GitHub stars: 2
- Finance Ops Receivables Exception Triage QueueUse when the accounts receivable workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the receivables aging view 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; open balance reconciles to invoices, receipts, credits, and documented disputes. Use configured search, fetch, read, browser, test, and write capabilities only w...Votes: 0GitHub stars: 2
- Finance Ops Receivables Recovery Readiness DrillUse when the accounts receivable workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the receivables aging view 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; open balance reconciles to invoices, receipts, credits, and documented disputes. Use configured search, fetch, read, browser, test, and write capabili...Votes: 0GitHub stars: 2
- Finance Ops Receivables Scenario Sensitivity MatrixUse when the accounts receivable team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the receivables aging view with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; open balance reconciles to invoices, receipts, credits, and documented disputes. Use configured search, fetch, read, browser, test, and write capabilities only when re...Votes: 0GitHub stars: 2
- Finance Ops Receivables Scope Intake GateUse when a new accounts receivable request needs a bounded work scope to produce a scoped intake card for the receivables aging view. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; open balance reconciles to invoices, receipts, credits, and documented disputes. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, an...Votes: 0GitHub stars: 2
- Finance Ops Receivables Source Provenance LedgerUse when a decision about accounts receivable depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the receivables aging view. Success means each material claim has a source, version/date, location, and confidence note; open balance reconciles to invoices, receipts, credits, and documented disputes. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement...Votes: 0GitHub stars: 2
- Finance Ops Receivables Threshold Rule CheckUse when a accounts receivable decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the receivables aging view 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; open balance reconciles to invoices, receipts, credits, and documented disputes. Use configured search, fetch, read, browser, test, and write ...Votes: 0GitHub stars: 2
- Finance Ops Revenue Approval Evidence PacketUse when a revenue contract operations result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the revenue-support 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 accounting question links to source terms and is escalated when judgment is required. Use configured search, fetch, read, br...Votes: 0GitHub stars: 2
- Finance Ops Revenue Change Impact TraceUse when a version, rule, source, or stakeholder change may affect revenue contract operations to produce a before/after change record and impact map for the revenue-support register. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each accounting question links to source terms and is escalated when judgment is required. Use configured search, fetch, read, browser, test, and write capabilities only when relev...Votes: 0GitHub stars: 2