All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Legal Ops Clause Playbooks Recovery Readiness DrillUse when the clause playbooks workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the clause deviation 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 deviation is tied to an approved position or marked for attorney decision. Use configured search, fetch, read, browser, test, and write capabilities only ...Votes: 0GitHub stars: 2
- Legal Ops Clause Playbooks Scenario Sensitivity MatrixUse when the clause playbooks team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the clause deviation with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; 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...Votes: 0GitHub stars: 2
- Legal Ops Clause Playbooks Scope Intake GateUse when a new clause playbooks request needs a bounded work scope to produce a scoped intake card for the clause deviation. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are 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 relevant and authorized. Record evidence, limit refinement to three focused passes, and seek app...Votes: 0GitHub stars: 2
- Legal Ops Clause Playbooks Source Provenance LedgerUse when a decision about clause playbooks depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the clause deviation. Success means each material claim has a source, version/date, location, and confidence note; 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 evidence, limit refinement to three ...Votes: 0GitHub stars: 2
- Legal Ops Clause Playbooks Threshold Rule CheckUse when a clause playbooks decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the clause deviation 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 deviation is tied to an approved position or marked for attorney decision. Use configured search, fetch, read, browser, test, and write capabiliti...Votes: 0GitHub stars: 2
- Legal Ops Contract Lifecycle Approval Evidence PacketUse when a contract lifecycle result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the contract record 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 current version, open issues, approver, and next milestone are unambiguous. Use configured search, fetch, read, browser, test, and write capabi...Votes: 0GitHub stars: 2
- Legal Ops Contract Lifecycle Change Impact TraceUse when a version, rule, source, or stakeholder change may affect contract lifecycle to produce a before/after change record and impact map for the contract record. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the current version, open issues, approver, and next milestone are unambiguous. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record ev...Votes: 0GitHub stars: 2
- Legal Ops Contract Lifecycle Closeout Handoff LedgerUse when a contract lifecycle work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the contract record 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 current version, open issues, approver, and next milestone are unambiguous. Use configured search, fetch, read, browser, test, and write capabilities only when releva...Votes: 0GitHub stars: 2
- Legal Ops Contract Lifecycle Completeness ReconciliationUse when the contract lifecycle workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the contract record 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 current version, open issues, approver, and next milestone are unambiguous. Use configured search, fetch, read, browser, test, and write capabilities on...Votes: 0GitHub stars: 2
- Legal Ops Contract Lifecycle Exception Triage QueueUse when the contract lifecycle workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the contract record 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 current version, open issues, approver, and next milestone are unambiguous. Use configured search, fetch, read, browser, test, and write capabilities only when relev...Votes: 0GitHub stars: 2
- Legal Ops Contract Lifecycle Recovery Readiness DrillUse when the contract lifecycle workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the contract record 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 current version, open issues, approver, and next milestone are unambiguous. Use configured search, fetch, read, browser, test, and write capabilities only...Votes: 0GitHub stars: 2
- Legal Ops Contract Lifecycle Scenario Sensitivity MatrixUse when the contract lifecycle team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the contract record with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the current version, open issues, approver, and next milestone are unambiguous. Use configured search, fetch, read, browser, test, and write capabilities only when relevant an...Votes: 0GitHub stars: 2
- Legal Ops Contract Lifecycle Scope Intake GateUse when a new contract lifecycle request needs a bounded work scope to produce a scoped intake card for the contract record. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the current version, open issues, approver, and next milestone are unambiguous. 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 ap...Votes: 0GitHub stars: 2
- Legal Ops Contract Lifecycle Source Provenance LedgerUse when a decision about contract lifecycle depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the contract record. Success means each material claim has a source, version/date, location, and confidence note; the current version, open issues, approver, and next milestone are unambiguous. 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
- Legal Ops Contract Lifecycle Threshold Rule CheckUse when a contract lifecycle decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the contract record 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 current version, open issues, approver, and next milestone are unambiguous. Use configured search, fetch, read, browser, test, and write capabilit...Votes: 0GitHub stars: 2
- Legal Ops Due Diligence Approval Evidence PacketUse when a due diligence result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the diligence item 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 requested item is linked to evidence, a gap status, and an accountable reviewer. Use configured search, fetch, read, browser, test, and write capabi...Votes: 0GitHub stars: 2
- Legal Ops Due Diligence Change Impact TraceUse when a version, rule, source, or stakeholder change may affect due diligence to produce a before/after change record and impact map for the diligence item. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each requested item is linked to evidence, a gap status, and an accountable reviewer. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record ev...Votes: 0GitHub stars: 2
- Legal Ops Due Diligence Closeout Handoff LedgerUse when a due diligence work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the diligence item 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 requested item is linked to evidence, a gap status, and an accountable reviewer. Use configured search, fetch, read, browser, test, and write capabilities only when releva...Votes: 0GitHub stars: 2
- Legal Ops Due Diligence Completeness ReconciliationUse when the due diligence workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the diligence item 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 requested item is linked to evidence, a gap status, and an accountable reviewer. Use configured search, fetch, read, browser, test, and write capabilities on...Votes: 0GitHub stars: 2
- Legal Ops Due Diligence Exception Triage QueueUse when the due diligence workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the diligence item 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 requested item is linked to evidence, a gap status, and an accountable reviewer. Use configured search, fetch, read, browser, test, and write capabilities only when relev...Votes: 0GitHub stars: 2
- Legal Ops Due Diligence Recovery Readiness DrillUse when the due diligence workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the diligence item 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 requested item is linked to evidence, a gap status, and an accountable reviewer. Use configured search, fetch, read, browser, test, and write capabilities only...Votes: 0GitHub stars: 2
- Legal Ops Due Diligence Scenario Sensitivity MatrixUse when the due diligence team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the diligence item with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each requested item is linked to evidence, a gap status, and an accountable reviewer. Use configured search, fetch, read, browser, test, and write capabilities only when relevant an...Votes: 0GitHub stars: 2
- Legal Ops Due Diligence Scope Intake GateUse when a new due diligence request needs a bounded work scope to produce a scoped intake card for the diligence item. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each requested item is linked to evidence, a gap status, and 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 ap...Votes: 0GitHub stars: 2
- Legal Ops Due Diligence Source Provenance LedgerUse when a decision about due diligence depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the diligence item. Success means each material claim has a source, version/date, location, and confidence note; each requested item is linked to evidence, a gap status, and an accountable reviewer. 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
- Legal Ops Due Diligence Threshold Rule CheckUse when a due diligence decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the diligence item 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 requested item is linked to evidence, a gap status, and an accountable reviewer. Use configured search, fetch, read, browser, test, and write capabilit...Votes: 0GitHub stars: 2
- Legal Ops Entity Records Approval Evidence PacketUse when a entity and corporate records result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the entity record index 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 indexed record has a known entity, date, status, and authoritative storage location. Use configured search, fetch, read, browser...Votes: 0GitHub stars: 2
- Legal Ops Entity Records Change Impact TraceUse when a version, rule, source, or stakeholder change may affect entity and corporate records to produce a before/after change record and impact map for the entity record index. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each indexed record has a known entity, date, status, and authoritative storage location. Use configured search, fetch, read, browser, test, and write capabilities only when relevant a...Votes: 0GitHub stars: 2
- Legal Ops Entity Records Closeout Handoff LedgerUse when a entity and corporate records work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the entity record index 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 indexed record has a known entity, date, status, and authoritative storage location. Use configured search, fetch, read, browser, test, and write capab...Votes: 0GitHub stars: 2
- Legal Ops Entity Records Completeness ReconciliationUse when the entity and corporate records workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the entity record index 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 indexed record has a known entity, date, status, and authoritative storage location. Use configured search, fetch, read, browser, test, a...Votes: 0GitHub stars: 2
- Legal Ops Entity Records Exception Triage QueueUse when the entity and corporate records workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the entity record index 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 indexed record has a known entity, date, status, and authoritative storage location. Use configured search, fetch, read, browser, test, and write capa...Votes: 0GitHub stars: 2
- Legal Ops Entity Records Recovery Readiness DrillUse when the entity and corporate records workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the entity record index 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 indexed record has a known entity, date, status, and authoritative storage location. Use configured search, fetch, read, browser, test, and...Votes: 0GitHub stars: 2
- Legal Ops Entity Records Scenario Sensitivity MatrixUse when the entity and corporate records team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the entity record index with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each indexed record has a known entity, date, status, and authoritative storage location. Use configured search, fetch, read, browser, test, and write capabiliti...Votes: 0GitHub stars: 2
- Legal Ops Entity Records Scope Intake GateUse when a new entity and corporate records request needs a bounded work scope to produce a scoped intake card for the entity record index. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each indexed record has a known entity, date, status, and authoritative storage location. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three foc...Votes: 0GitHub stars: 2
- Legal Ops Entity Records Source Provenance LedgerUse when a decision about entity and corporate records depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the entity record index. Success means each material claim has a source, version/date, location, and confidence note; each indexed record has a known entity, date, status, and authoritative storage location. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, l...Votes: 0GitHub stars: 2
- Legal Ops Entity Records Threshold Rule CheckUse when a entity and corporate records decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the entity record index 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 indexed record has a known entity, date, status, and authoritative storage location. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Legal Ops Legal Holds Approval Evidence PacketUse when a legal hold and records administration result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the hold acknowledgement ledger 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 custodian and relevant system has a traceable preserve/acknowledge status. Use configured search, fetch, read,...Votes: 0GitHub stars: 2
- Legal Ops Legal Holds Change Impact TraceUse when a version, rule, source, or stakeholder change may affect legal hold and records administration to produce a before/after change record and impact map for the hold acknowledgement ledger. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; every custodian and relevant system has a traceable preserve/acknowledge status. Use configured search, fetch, read, browser, test, and write capabilities only when re...Votes: 0GitHub stars: 2
- Legal Ops Legal Holds Closeout Handoff LedgerUse when a legal hold and records administration work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the hold acknowledgement ledger 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 custodian and relevant system has a traceable preserve/acknowledge status. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2
- Legal Ops Legal Holds Completeness ReconciliationUse when the legal hold and records administration workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the hold acknowledgement ledger 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 custodian and relevant system has a traceable preserve/acknowledge status. Use configured search, fetch, read, browser,...Votes: 0GitHub stars: 2
- Legal Ops Legal Holds Exception Triage QueueUse when the legal hold and records administration workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the hold acknowledgement ledger 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 custodian and relevant system has a traceable preserve/acknowledge status. Use configured search, fetch, read, browser, test, and wr...Votes: 0GitHub stars: 2
- Legal Ops Legal Holds Recovery Readiness DrillUse when the legal hold and records administration workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the hold acknowledgement ledger 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 custodian and relevant system has a traceable preserve/acknowledge status. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Legal Ops Legal Holds Scenario Sensitivity MatrixUse when the legal hold and records administration team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the hold acknowledgement ledger with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; every custodian and relevant system has a traceable preserve/acknowledge status. Use configured search, fetch, read, browser, test, and write ca...Votes: 0GitHub stars: 2
- Legal Ops Legal Holds Scope Intake GateUse when a new legal hold and records administration request needs a bounded work scope to produce a scoped intake card for the hold acknowledgement ledger. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; every custodian and relevant system has a traceable preserve/acknowledge status. 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
- Legal Ops Legal Holds Source Provenance LedgerUse when a decision about legal hold and records administration depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the hold acknowledgement ledger. Success means each material claim has a source, version/date, location, and confidence note; every custodian and relevant system has a traceable preserve/acknowledge status. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evi...Votes: 0GitHub stars: 2
- Legal Ops Legal Holds Threshold Rule CheckUse when a legal hold and records administration decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the hold acknowledgement ledger 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 custodian and relevant system has a traceable preserve/acknowledge status. Use configured search, fetch, read, br...Votes: 0GitHub stars: 2
- Legal Ops Matter Intake Approval Evidence PacketUse when a matter intake result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the matter record 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 intake fields are present or explicitly assigned for follow-up. Use configured search, fetch, read, browser, test, and write capabilities onl...Votes: 0GitHub stars: 2
- Legal Ops Matter Intake Change Impact TraceUse when a version, rule, source, or stakeholder change may affect matter intake to produce a before/after change record and impact map for the matter record. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; all required intake fields are present or explicitly assigned for follow-up. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, li...Votes: 0GitHub stars: 2
- Legal Ops Matter Intake Closeout Handoff LedgerUse when a matter intake work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the matter record 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 intake fields are present or explicitly assigned for follow-up. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and aut...Votes: 0GitHub stars: 2
- Legal Ops Matter Intake Completeness ReconciliationUse when the matter intake workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the matter record 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 intake fields are present or explicitly assigned for follow-up. Use configured search, fetch, read, browser, test, and write capabilities only when re...Votes: 0GitHub stars: 2
- Legal Ops Matter Intake Exception Triage QueueUse when the matter intake workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the matter record 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 intake fields are present or explicitly assigned for follow-up. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and au...Votes: 0GitHub stars: 2