All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Ml Data Ops Drift Monitoring Source Provenance LedgerUse when a decision about tabular model input-drift monitoring depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the drift-monitor definition. Success means each material claim has a source, version/date, location, and confidence note; alerts distinguish data-contract breaks from population movement and have an owner. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evid...Votes: 0GitHub stars: 2
- Ml Data Ops Drift Monitoring Threshold Rule CheckUse when a tabular model input-drift monitoring decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the drift-monitor definition 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; alerts distinguish data-contract breaks from population movement and have an owner. Use configured search, fetch, read, bro...Votes: 0GitHub stars: 2
- Ml Data Ops Experiment Reproduction Approval Evidence PacketUse when a model experiment reproduction result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the experiment reproduction packet 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 run can be reproduced within declared tolerance or every variance is recorded. Use configured search, fetch, read, br...Votes: 0GitHub stars: 2
- Ml Data Ops Experiment Reproduction Change Impact TraceUse when a version, rule, source, or stakeholder change may affect model experiment reproduction to produce a before/after change record and impact map for the experiment reproduction packet. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the run can be reproduced within declared tolerance or every variance is recorded. Use configured search, fetch, read, browser, test, and write capabilities only when relev...Votes: 0GitHub stars: 2
- Ml Data Ops Experiment Reproduction Closeout Handoff LedgerUse when a model experiment reproduction work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the experiment reproduction packet 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 run can be reproduced within declared tolerance or every variance is recorded. Use configured search, fetch, read, browser, test, and write ...Votes: 0GitHub stars: 2
- Ml Data Ops Experiment Reproduction Completeness ReconciliationUse when the model experiment reproduction workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the experiment reproduction packet 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 run can be reproduced within declared tolerance or every variance is recorded. Use configured search, fetch, read, browser, te...Votes: 0GitHub stars: 2
- Ml Data Ops Experiment Reproduction Exception Triage QueueUse when the model experiment reproduction workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the experiment reproduction packet 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 run can be reproduced within declared tolerance or every variance is recorded. Use configured search, fetch, read, browser, test, and write...Votes: 0GitHub stars: 2
- Ml Data Ops Experiment Reproduction Recovery Readiness DrillUse when the model experiment reproduction workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the experiment reproduction packet 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 run can be reproduced within declared tolerance or every variance is recorded. Use configured search, fetch, read, browser, test...Votes: 0GitHub stars: 2
- Ml Data Ops Experiment Reproduction Scenario Sensitivity MatrixUse when the model experiment reproduction team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the experiment reproduction packet with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the run can be reproduced within declared tolerance or every variance is recorded. Use configured search, fetch, read, browser, test, and write capab...Votes: 0GitHub stars: 2
- Ml Data Ops Experiment Reproduction Scope Intake GateUse when a new model experiment reproduction request needs a bounded work scope to produce a scoped intake card for the experiment reproduction packet. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the run can be reproduced within declared tolerance or every variance is recorded. 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
- Ml Data Ops Experiment Reproduction Source Provenance LedgerUse when a decision about model experiment reproduction depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the experiment reproduction packet. Success means each material claim has a source, version/date, location, and confidence note; the run can be reproduced within declared tolerance or every variance is recorded. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record eviden...Votes: 0GitHub stars: 2
- Ml Data Ops Experiment Reproduction Threshold Rule CheckUse when a model experiment reproduction decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the experiment reproduction packet 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 run can be reproduced within declared tolerance or every variance is recorded. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2
- Ml Data Ops Metric Uncertainty Approval Evidence PacketUse when a model metric uncertainty reporting result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the metric uncertainty worksheet 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; uncertainty and small-sample limits accompany every reported point estimate. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2
- Ml Data Ops Metric Uncertainty Change Impact TraceUse when a version, rule, source, or stakeholder change may affect model metric uncertainty reporting to produce a before/after change record and impact map for the metric uncertainty worksheet. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; uncertainty and small-sample limits accompany every reported point estimate. Use configured search, fetch, read, browser, test, and write capabilities only when relevant...Votes: 0GitHub stars: 2
- Ml Data Ops Metric Uncertainty Closeout Handoff LedgerUse when a model metric uncertainty reporting work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the metric uncertainty worksheet 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; uncertainty and small-sample limits accompany every reported point estimate. Use configured search, fetch, read, browser, test, and write cap...Votes: 0GitHub stars: 2
- Ml Data Ops Metric Uncertainty Completeness ReconciliationUse when the model metric uncertainty reporting workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the metric uncertainty worksheet 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; uncertainty and small-sample limits accompany every reported point estimate. Use configured search, fetch, read, browser, test,...Votes: 0GitHub stars: 2
- Ml Data Ops Metric Uncertainty Exception Triage QueueUse when the model metric uncertainty reporting workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the metric uncertainty worksheet 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; uncertainty and small-sample limits accompany every reported point estimate. Use configured search, fetch, read, browser, test, and write ca...Votes: 0GitHub stars: 2
- Ml Data Ops Metric Uncertainty Recovery Readiness DrillUse when the model metric uncertainty reporting workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the metric uncertainty worksheet 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; uncertainty and small-sample limits accompany every reported point estimate. Use configured search, fetch, read, browser, test, a...Votes: 0GitHub stars: 2
- Ml Data Ops Metric Uncertainty Scenario Sensitivity MatrixUse when the model metric uncertainty reporting team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the metric uncertainty worksheet with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; uncertainty and small-sample limits accompany every reported point estimate. Use configured search, fetch, read, browser, test, and write capabili...Votes: 0GitHub stars: 2
- Ml Data Ops Metric Uncertainty Scope Intake GateUse when a new model metric uncertainty reporting request needs a bounded work scope to produce a scoped intake card for the metric uncertainty worksheet. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; uncertainty and small-sample limits accompany every reported point estimate. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three f...Votes: 0GitHub stars: 2
- Ml Data Ops Metric Uncertainty Source Provenance LedgerUse when a decision about model metric uncertainty reporting depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the metric uncertainty worksheet. Success means each material claim has a source, version/date, location, and confidence note; uncertainty and small-sample limits accompany every reported point estimate. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence,...Votes: 0GitHub stars: 2
- Ml Data Ops Metric Uncertainty Threshold Rule CheckUse when a model metric uncertainty reporting decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the metric uncertainty worksheet 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; uncertainty and small-sample limits accompany every reported point estimate. Use configured search, fetch, read, browser,...Votes: 0GitHub stars: 2
- Ml Data Ops Subgroup Coverage Approval Evidence PacketUse when a subgroup evaluation coverage result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the subgroup coverage matrix 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; unsupported or too-small groups are marked unknown rather than inferred. Use configured search, fetch, read, browser, test, and ...Votes: 0GitHub stars: 2
- Ml Data Ops Subgroup Coverage Change Impact TraceUse when a version, rule, source, or stakeholder change may affect subgroup evaluation coverage to produce a before/after change record and impact map for the subgroup coverage matrix. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; unsupported or too-small groups are marked unknown rather than inferred. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorize...Votes: 0GitHub stars: 2
- Ml Data Ops Subgroup Coverage Closeout Handoff LedgerUse when a subgroup evaluation coverage work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the subgroup coverage matrix 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; unsupported or too-small groups are marked unknown rather than inferred. Use configured search, fetch, read, browser, test, and write capabilities only...Votes: 0GitHub stars: 2
- Ml Data Ops Subgroup Coverage Completeness ReconciliationUse when the subgroup evaluation coverage workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the subgroup coverage matrix 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; unsupported or too-small groups are marked unknown rather than inferred. Use configured search, fetch, read, browser, test, and write cap...Votes: 0GitHub stars: 2
- Ml Data Ops Subgroup Coverage Exception Triage QueueUse when the subgroup evaluation coverage workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the subgroup coverage matrix 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; unsupported or too-small groups are marked unknown rather than inferred. Use configured search, fetch, read, browser, test, and write capabilities onl...Votes: 0GitHub stars: 2
- Ml Data Ops Subgroup Coverage Recovery Readiness DrillUse when the subgroup evaluation coverage workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the subgroup coverage matrix 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; unsupported or too-small groups are marked unknown rather than inferred. Use configured search, fetch, read, browser, test, and write capab...Votes: 0GitHub stars: 2
- Ml Data Ops Subgroup Coverage Scenario Sensitivity MatrixUse when the subgroup evaluation coverage team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the subgroup coverage matrix with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; unsupported or too-small groups are marked unknown rather than inferred. Use configured search, fetch, read, browser, test, and write capabilities only when...Votes: 0GitHub stars: 2
- Ml Data Ops Subgroup Coverage Scope Intake GateUse when a new subgroup evaluation coverage request needs a bounded work scope to produce a scoped intake card for the subgroup coverage matrix. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; unsupported or too-small groups are marked unknown rather than inferred. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes,...Votes: 0GitHub stars: 2
- Ml Data Ops Subgroup Coverage Source Provenance LedgerUse when a decision about subgroup evaluation coverage depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the subgroup coverage matrix. Success means each material claim has a source, version/date, location, and confidence note; unsupported or too-small groups are marked unknown rather than inferred. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinem...Votes: 0GitHub stars: 2
- Ml Data Ops Subgroup Coverage Threshold Rule CheckUse when a subgroup evaluation coverage decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the subgroup coverage matrix 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; unsupported or too-small groups are marked unknown rather than inferred. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2
- Plotly Capability Surface MapUse when the actual capability boundary of Plotly visualization needs to be distinguished from assumptions. Produce a capability map for Plotly visualization covering the requested behavior, verified support, exclusions, and unknowns. Success means each in-scope capability is tied to local configuration, a version-matched authoritative reference, or an observed non-production result, and all unknowns remain explicit. The review is bounded to figure data identity, trace configuration, accessib...Votes: 0GitHub stars: 2
- Plotly Change Impact AssessmentUse when a proposed Plotly visualization version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Plotly visualization with baseline, affected dependencies, validation needs, and recovery boundary. Success means affected dependencies and compatibility assumptions are evidenced, unknown consumers are named as unknown, and no migration or rollout is implied. The review is bounded to figure data identity, trace configuration, access...Votes: 0GitHub stars: 2
- Plotly Failure Triage RecordUse when a reproducible Plotly visualization symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Plotly visualization with symptom, environment, evidence, hypothesis, and next safe check. Success means the diagnosis distinguishes observation from inference, each proposed check is reversible and scoped, and unresolved causes remain open. The review is bounded to figure data identity, trace configuration, accessibility, renderer, and export fidelity...Votes: 0GitHub stars: 2
- Plotly Input Output ContractUse when the accepted inputs or produced outputs for Plotly visualization need a checkable boundary. Produce an input/output contract for Plotly visualization with types, required fields, exclusions, and representative approved fixtures. Success means the contract names its source and version, boundary cases are visible, and no private or unapproved payload is needed to explain the result. The review is bounded to figure data identity, trace configuration, accessibility, renderer, and export ...Votes: 0GitHub stars: 2
- Plotly Integration Parity TraceUse when Plotly visualization exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Plotly visualization showing source, transformation, destination, and observed result. Success means each material field or state transition has a traceable mapping and observed mismatches are separated from assumptions. The review is bounded to figure data identity, trace configuration, accessibility, renderer, and export fidelity. Use onl...Votes: 0GitHub stars: 2
- Plotly Performance EnvelopeUse when Plotly visualization must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Plotly visualization with test conditions, baseline, observed range, and limitations. Success means conditions and measurements are reproducible, the comparison uses the stated budget, and limitations or resource costs are visible. The review is bounded to figure data identity, trace configuration, accessibility, renderer, a...Votes: 0GitHub stars: 2
- Plotly Permission Boundary ReviewUse when Plotly visualization may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Plotly visualization showing identity, requested capability, data scope, and approval gate. Success means every sensitive capability has a named authorization boundary, unnecessary data and privileges are called out, and no action is treated as approved by implication. The review is bounded to figure data identity, trace configuration, accessibility, ...Votes: 0GitHub stars: 2
- Plotly Release Handoff RecordUse when a Plotly visualization review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Plotly visualization with version, evidence, open issues, approval state, and safe next step. Success means the receiver can distinguish verified facts, proposals, approvals, and unknowns, and no publication, deployment, write, or contact is claimed unless independently confirmed. The review is bounded to figure data identity, trace configuration, accessib...Votes: 0GitHub stars: 2
- Plotly Reproducibility Fixture PlanUse when a Plotly visualization result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for Plotly visualization defining fixture identity, environment, expected observations, and cleanup boundary. Success means another reviewer can identify the fixture and environment, distinguish expected from observed behavior, and repeat the check without an unapproved external effect. The review is bounded to figure data identity, t...Votes: 0GitHub stars: 2
- Plotly Version CompatibilityUse when a Plotly visualization integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for Plotly visualization with exact versions, supported combinations, and open questions. Success means the tested version tuple is explicit, each compatibility claim has a dated source or local result, and unsupported combinations are not presented as working. The review is bounded to figure data identity, trace configuration, acc...Votes: 0GitHub stars: 2
- Aas Data Cdc Checkpoint Approval Evidence PacketUse when a change-data-capture checkpoint recovery result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the CDC checkpoint continuity 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; restart resumes from a known boundary and duplicate events are handled by the declared policy. Use configured se...Votes: 0GitHub stars: 2
- Aas Data Cdc Checkpoint Change Impact TraceUse when a version, rule, source, or stakeholder change may affect change-data-capture checkpoint recovery to produce a before/after change record and impact map for the CDC checkpoint continuity map. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; restart resumes from a known boundary and duplicate events are handled by the declared policy. Use configured search, fetch, read, browser, test, and write capabil...Votes: 0GitHub stars: 2
- Aas Data Cdc Checkpoint Closeout Handoff LedgerUse when a change-data-capture checkpoint recovery work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the CDC checkpoint continuity 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; restart resumes from a known boundary and duplicate events are handled by the declared policy. Use configured search, fetch, read, brow...Votes: 0GitHub stars: 2
- Aas Data Cdc Checkpoint Completeness ReconciliationUse when the change-data-capture checkpoint recovery workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the CDC checkpoint continuity 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; restart resumes from a known boundary and duplicate events are handled by the declared policy. Use configured search, fet...Votes: 0GitHub stars: 2
- Aas Data Cdc Checkpoint Exception Triage QueueUse when the change-data-capture checkpoint recovery workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the CDC checkpoint continuity 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; restart resumes from a known boundary and duplicate events are handled by the declared policy. Use configured search, fetch, read, bro...Votes: 0GitHub stars: 2
- Aas Data Cdc Checkpoint Recovery Readiness DrillUse when the change-data-capture checkpoint recovery workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the CDC checkpoint continuity 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; restart resumes from a known boundary and duplicate events are handled by the declared policy. Use configured search, fetch...Votes: 0GitHub stars: 2
- Aas Data Cdc Checkpoint Scenario Sensitivity MatrixUse when the change-data-capture checkpoint recovery team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the CDC checkpoint continuity map with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; restart resumes from a known boundary and duplicate events are handled by the declared policy. Use configured search, fetch, read, browser, ...Votes: 0GitHub stars: 2
- Aas Data Cdc Checkpoint Scope Intake GateUse when a new change-data-capture checkpoint recovery request needs a bounded work scope to produce a scoped intake card for the CDC checkpoint continuity map. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; restart resumes from a known boundary and duplicate events are handled by the declared policy. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, lim...Votes: 0GitHub stars: 2