All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Insure Ops Reinsurance Scenario Sensitivity MatrixUse when the reinsurance treaty and bordereaux reconciliation team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the bordereaux exception register with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; all variances are quantified and contractual interpretation is referred to reinsurance counsel or owner. Use configured search, fet...Votes: 0GitHub stars: 2
- Insure Ops Reinsurance Scope Intake GateUse when a new reinsurance treaty and bordereaux reconciliation request needs a bounded work scope to produce a scoped intake card for the bordereaux exception register. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; all variances are quantified and contractual interpretation is referred to reinsurance counsel or owner. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. R...Votes: 0GitHub stars: 2
- Insure Ops Reinsurance Source Provenance LedgerUse when a decision about reinsurance treaty and bordereaux reconciliation depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the bordereaux exception register. Success means each material claim has a source, version/date, location, and confidence note; all variances are quantified and contractual interpretation is referred to reinsurance counsel or owner. Use configured search, fetch, read, browser, test, and write capabilities only whe...Votes: 0GitHub stars: 2
- Insure Ops Reinsurance Threshold Rule CheckUse when a reinsurance treaty and bordereaux reconciliation decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the bordereaux exception 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; all variances are quantified and contractual interpretation is referred to reinsurance counsel or owner. U...Votes: 0GitHub stars: 2
- Insure Ops Reserve Data Approval Evidence PacketUse when a actuarial reserving data preparation result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the reserving data quality 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; inputs reconcile to the declared valuation basis and no actuarial estimate is certified. Use configured search, fet...Votes: 0GitHub stars: 2
- Insure Ops Reserve Data Change Impact TraceUse when a version, rule, source, or stakeholder change may affect actuarial reserving data preparation to produce a before/after change record and impact map for the reserving data quality report. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; inputs reconcile to the declared valuation basis and no actuarial estimate is certified. Use configured search, fetch, read, browser, test, and write capabilities onl...Votes: 0GitHub stars: 2
- Insure Ops Reserve Data Closeout Handoff LedgerUse when a actuarial reserving data preparation work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the reserving data quality 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; inputs reconcile to the declared valuation basis and no actuarial estimate is certified. Use configured search, fetch, read, browser, test...Votes: 0GitHub stars: 2
- Insure Ops Reserve Data Completeness ReconciliationUse when the actuarial reserving data preparation workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the reserving data quality 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; inputs reconcile to the declared valuation basis and no actuarial estimate is certified. Use configured search, fetch, read,...Votes: 0GitHub stars: 2
- Insure Ops Reserve Data Exception Triage QueueUse when the actuarial reserving data preparation workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the reserving data quality 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; inputs reconcile to the declared valuation basis and no actuarial estimate is certified. Use configured search, fetch, read, browser, tes...Votes: 0GitHub stars: 2
- Insure Ops Reserve Data Recovery Readiness DrillUse when the actuarial reserving data preparation workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the reserving data quality 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; inputs reconcile to the declared valuation basis and no actuarial estimate is certified. Use configured search, fetch, read, b...Votes: 0GitHub stars: 2
- Insure Ops Reserve Data Scenario Sensitivity MatrixUse when the actuarial reserving data preparation team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the reserving data quality report with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; inputs reconcile to the declared valuation basis and no actuarial estimate is certified. Use configured search, fetch, read, browser, test, and...Votes: 0GitHub stars: 2
- Insure Ops Reserve Data Scope Intake GateUse when a new actuarial reserving data preparation request needs a bounded work scope to produce a scoped intake card for the reserving data quality report. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; inputs reconcile to the declared valuation basis and no actuarial estimate is certified. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refine...Votes: 0GitHub stars: 2
- Insure Ops Reserve Data Source Provenance LedgerUse when a decision about actuarial reserving data preparation depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the reserving data quality report. Success means each material claim has a source, version/date, location, and confidence note; inputs reconcile to the declared valuation basis and no actuarial estimate is certified. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. R...Votes: 0GitHub stars: 2
- Insure Ops Reserve Data Threshold Rule CheckUse when a actuarial reserving data preparation decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the reserving data quality 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; inputs reconcile to the declared valuation basis and no actuarial estimate is certified. Use configured search, fetch,...Votes: 0GitHub stars: 2
- Insure Ops Risk Survey Approval Evidence PacketUse when a risk-survey evidence administration result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the risk-survey evidence map 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; observations are attributed and no hazard rating or coverage recommendation is generated. Use configured search, fetch, r...Votes: 0GitHub stars: 2
- Insure Ops Risk Survey Change Impact TraceUse when a version, rule, source, or stakeholder change may affect risk-survey evidence administration to produce a before/after change record and impact map for the risk-survey evidence map. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; observations are attributed and no hazard rating or coverage recommendation is generated. Use configured search, fetch, read, browser, test, and write capabilities only whe...Votes: 0GitHub stars: 2
- Insure Ops Risk Survey Closeout Handoff LedgerUse when a risk-survey evidence administration work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the risk-survey evidence map 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; observations are attributed and no hazard rating or coverage recommendation is generated. Use configured search, fetch, read, browser, test, and...Votes: 0GitHub stars: 2
- Insure Ops Risk Survey Completeness ReconciliationUse when the risk-survey evidence administration workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the risk-survey evidence map 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; observations are attributed and no hazard rating or coverage recommendation is generated. Use configured search, fetch, read, brow...Votes: 0GitHub stars: 2
- Insure Ops Risk Survey Exception Triage QueueUse when the risk-survey evidence administration workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the risk-survey evidence map 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; observations are attributed and no hazard rating or coverage recommendation is generated. Use configured search, fetch, read, browser, test, an...Votes: 0GitHub stars: 2
- Insure Ops Risk Survey Recovery Readiness DrillUse when the risk-survey evidence administration workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the risk-survey evidence map 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; observations are attributed and no hazard rating or coverage recommendation is generated. Use configured search, fetch, read, browse...Votes: 0GitHub stars: 2
- Insure Ops Risk Survey Scenario Sensitivity MatrixUse when the risk-survey evidence administration team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the risk-survey evidence map with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; observations are attributed and no hazard rating or coverage recommendation is generated. Use configured search, fetch, read, browser, test, and writ...Votes: 0GitHub stars: 2
- Insure Ops Risk Survey Scope Intake GateUse when a new risk-survey evidence administration request needs a bounded work scope to produce a scoped intake card for the risk-survey evidence map. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; observations are attributed and no hazard rating or coverage recommendation is generated. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement ...Votes: 0GitHub stars: 2
- Insure Ops Risk Survey Source Provenance LedgerUse when a decision about risk-survey evidence administration depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the risk-survey evidence map. Success means each material claim has a source, version/date, location, and confidence note; observations are attributed and no hazard rating or coverage recommendation is generated. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record...Votes: 0GitHub stars: 2
- Insure Ops Risk Survey Threshold Rule CheckUse when a risk-survey evidence administration decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the risk-survey evidence map 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; observations are attributed and no hazard rating or coverage recommendation is generated. Use configured search, fetch, read...Votes: 0GitHub stars: 2
- Insure Ops Submission Approval Evidence PacketUse when a insurance submission intake result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the submission completeness 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; missing fields and source conflicts are listed without recommending acceptance or rejection. Use configured search, fetc...Votes: 0GitHub stars: 2
- Insure Ops Submission Change Impact TraceUse when a version, rule, source, or stakeholder change may affect insurance submission intake to produce a before/after change record and impact map for the submission completeness checklist. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; missing fields and source conflicts are listed without recommending acceptance or rejection. Use configured search, fetch, read, browser, test, and write capabilities only...Votes: 0GitHub stars: 2
- Insure Ops Submission Closeout Handoff LedgerUse when a insurance submission intake work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the submission completeness 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; missing fields and source conflicts are listed without recommending acceptance or rejection. Use configured search, fetch, read, browser, test,...Votes: 0GitHub stars: 2
- Insure Ops Submission Completeness ReconciliationUse when the insurance submission intake workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the submission completeness 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; missing fields and source conflicts are listed without recommending acceptance or rejection. Use configured search, fetch, read, ...Votes: 0GitHub stars: 2
- Insure Ops Submission Exception Triage QueueUse when the insurance submission intake workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the submission completeness 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; missing fields and source conflicts are listed without recommending acceptance or rejection. Use configured search, fetch, read, browser, test...Votes: 0GitHub stars: 2
- Insure Ops Submission Recovery Readiness DrillUse when the insurance submission intake workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the submission completeness 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; missing fields and source conflicts are listed without recommending acceptance or rejection. Use configured search, fetch, read, br...Votes: 0GitHub stars: 2
- Insure Ops Submission Scenario Sensitivity MatrixUse when the insurance submission intake team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the submission completeness checklist with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; missing fields and source conflicts are listed without recommending acceptance or rejection. Use configured search, fetch, read, browser, test, and ...Votes: 0GitHub stars: 2
- Insure Ops Submission Scope Intake GateUse when a new insurance submission intake request needs a bounded work scope to produce a scoped intake card for the submission completeness checklist. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; missing fields and source conflicts are listed without recommending acceptance or rejection. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinem...Votes: 0GitHub stars: 2
- Insure Ops Submission Source Provenance LedgerUse when a decision about insurance submission intake depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the submission completeness checklist. Success means each material claim has a source, version/date, location, and confidence note; missing fields and source conflicts are listed without recommending acceptance or rejection. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Re...Votes: 0GitHub stars: 2
- Insure Ops Submission Threshold Rule CheckUse when a insurance submission intake decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the submission completeness 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; missing fields and source conflicts are listed without recommending acceptance or rejection. Use configured search, fetch, ...Votes: 0GitHub stars: 2
- Google Admin Audit Log ReviewUse when a task involves reviewing Google Workspace audit logs for an authorized administrative question with narrow time and actor filters to identify the research or operational question, target population or system, relevant version, sensitive data, and approval boundary before acting. Use current primary sources, produce a traceable artifact, and verify it against explicit criteria. Trigger for planning, analysis, review, or troubleshooting in this focused domain; do not execute external ...Votes: 0GitHub stars: 2
- Legal Ops Approvals Approval Evidence PacketUse when a legal approval routing result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the approval route 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; all required reviewers have a recorded disposition on the same version. Use configured search, fetch, read, browser, test, and write capabilitie...Votes: 0GitHub stars: 2
- Legal Ops Approvals Change Impact TraceUse when a version, rule, source, or stakeholder change may affect legal approval routing to produce a before/after change record and impact map for the approval route. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; all required reviewers have a recorded disposition on the same version. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidenc...Votes: 0GitHub stars: 2
- Legal Ops Approvals Closeout Handoff LedgerUse when a legal approval routing work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the approval route 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; all required reviewers have a recorded disposition on the same version. Use configured search, fetch, read, browser, test, and write capabilities only when relevant an...Votes: 0GitHub stars: 2
- Legal Ops Approvals Completeness ReconciliationUse when the legal approval routing workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the approval route 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; all required reviewers have a recorded disposition on the same version. Use configured search, fetch, read, browser, test, and write capabilities only wh...Votes: 0GitHub stars: 2
- Legal Ops Approvals Exception Triage QueueUse when the legal approval routing workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the approval route 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; all required reviewers have a recorded disposition on the same version. Use configured search, fetch, read, browser, test, and write capabilities only when relevant a...Votes: 0GitHub stars: 2
- Legal Ops Approvals Recovery Readiness DrillUse when the legal approval routing workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the approval route 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; all required reviewers have a recorded disposition on the same version. Use configured search, fetch, read, browser, test, and write capabilities only when...Votes: 0GitHub stars: 2
- Legal Ops Approvals Scenario Sensitivity MatrixUse when the legal approval routing team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the approval route with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; all required reviewers have a recorded disposition on the same version. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and aut...Votes: 0GitHub stars: 2
- Legal Ops Approvals Scope Intake GateUse when a new legal approval routing request needs a bounded work scope to produce a scoped intake card for the approval route. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; all required reviewers have a recorded disposition on the same version. 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 approva...Votes: 0GitHub stars: 2
- Legal Ops Approvals Source Provenance LedgerUse when a decision about legal approval routing depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the approval route. Success means each material claim has a source, version/date, location, and confidence note; all required reviewers have a recorded disposition on the same version. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focu...Votes: 0GitHub stars: 2
- Legal Ops Approvals Threshold Rule CheckUse when a legal approval routing decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the approval route 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; all required reviewers have a recorded disposition on the same version. Use configured search, fetch, read, browser, test, and write capabilities o...Votes: 0GitHub stars: 2
- Legal Ops Clause Playbooks Approval Evidence PacketUse when a clause playbooks result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the clause deviation 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 deviation is tied to an approved position or marked for attorney decision. Use configured search, fetch, read, browser, test, and write capabil...Votes: 0GitHub stars: 2
- Legal Ops Clause Playbooks Change Impact TraceUse when a version, rule, source, or stakeholder change may affect clause playbooks to produce a before/after change record and impact map for the clause deviation. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each deviation is tied to an approved position or marked for attorney decision. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evi...Votes: 0GitHub stars: 2
- Legal Ops Clause Playbooks Closeout Handoff LedgerUse when a clause playbooks work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the clause deviation 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 deviation is tied to an approved position or marked for attorney decision. Use configured search, fetch, read, browser, test, and write capabilities only when relevan...Votes: 0GitHub stars: 2
- Legal Ops Clause Playbooks Completeness ReconciliationUse when the clause playbooks workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the clause deviation 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 deviation is tied to an approved position or marked for attorney decision. Use configured search, fetch, read, browser, test, and write capabilities onl...Votes: 0GitHub stars: 2
- Legal Ops Clause Playbooks Exception Triage QueueUse when the clause playbooks workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the clause deviation 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 deviation is tied to an approved position or marked for attorney decision. Use configured search, fetch, read, browser, test, and write capabilities only when releva...Votes: 0GitHub stars: 2