All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Data Eng Catalog Lineage Source Provenance LedgerUse when a decision about catalog and lineage depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the catalog asset. Success means each material claim has a source, version/date, location, and confidence note; every changed asset has an owner and complete, reviewable upstream/downstream links. 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
- Data Eng Catalog Lineage Threshold Rule CheckUse when a catalog and lineage decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the catalog asset 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 changed asset has an owner and complete, reviewable upstream/downstream links. Use configured search, fetch, read, browser, test, and write capab...Votes: 0GitHub stars: 2
- Data Eng Cost Reliability Approval Evidence PacketUse when a data-platform cost and reliability result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the platform workload 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 optimization preserves workload correctness and declared recovery targets. Use configured search, fetch, read, browser, test,...Votes: 0GitHub stars: 2
- Data Eng Cost Reliability Change Impact TraceUse when a version, rule, source, or stakeholder change may affect data-platform cost and reliability to produce a before/after change record and impact map for the platform workload. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the optimization preserves workload correctness and declared recovery targets. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and auth...Votes: 0GitHub stars: 2
- Data Eng Cost Reliability Closeout Handoff LedgerUse when a data-platform cost and reliability work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the platform workload 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 optimization preserves workload correctness and declared recovery targets. Use configured search, fetch, read, browser, test, and write capabilities...Votes: 0GitHub stars: 2
- Data Eng Cost Reliability Completeness ReconciliationUse when the data-platform cost and reliability workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the platform workload 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 optimization preserves workload correctness and declared recovery targets. Use configured search, fetch, read, browser, test, and writ...Votes: 0GitHub stars: 2
- Data Eng Cost Reliability Exception Triage QueueUse when the data-platform cost and reliability workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the platform workload 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 optimization preserves workload correctness and declared recovery targets. Use configured search, fetch, read, browser, test, and write capabilitie...Votes: 0GitHub stars: 2
- Data Eng Cost Reliability Recovery Readiness DrillUse when the data-platform cost and reliability workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the platform workload 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 optimization preserves workload correctness and declared recovery targets. Use configured search, fetch, read, browser, test, and write ...Votes: 0GitHub stars: 2
- Data Eng Cost Reliability Scenario Sensitivity MatrixUse when the data-platform cost and reliability team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the platform workload with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the optimization preserves workload correctness and declared recovery targets. Use configured search, fetch, read, browser, test, and write capabilities only...Votes: 0GitHub stars: 2
- Data Eng Cost Reliability Scope Intake GateUse when a new data-platform cost and reliability request needs a bounded work scope to produce a scoped intake card for the platform workload. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the optimization preserves workload correctness and declared recovery targets. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused pa...Votes: 0GitHub stars: 2
- Data Eng Cost Reliability Source Provenance LedgerUse when a decision about data-platform cost and reliability depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the platform workload. Success means each material claim has a source, version/date, location, and confidence note; the optimization preserves workload correctness and declared recovery targets. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit re...Votes: 0GitHub stars: 2
- Data Eng Cost Reliability Threshold Rule CheckUse when a data-platform cost and reliability decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the platform workload 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 optimization preserves workload correctness and declared recovery targets. Use configured search, fetch, read, browser, test, an...Votes: 0GitHub stars: 2
- Data Eng Ingestion Approval Evidence PacketUse when a source ingestion result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the partner feed 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; accepted and rejected records reconcile to the producer manifest. Use configured search, fetch, read, browser, test, and write capabilities only when re...Votes: 0GitHub stars: 2
- Data Eng Ingestion Change Impact TraceUse when a version, rule, source, or stakeholder change may affect source ingestion to produce a before/after change record and impact map for the partner feed. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; accepted and rejected records reconcile to the producer manifest. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refin...Votes: 0GitHub stars: 2
- Data Eng Ingestion Closeout Handoff LedgerUse when a source ingestion work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the partner feed 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; accepted and rejected records reconcile to the producer manifest. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. ...Votes: 0GitHub stars: 2
- Data Eng Ingestion Completeness ReconciliationUse when the source ingestion workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the partner feed 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; accepted and rejected records reconcile to the producer manifest. Use configured search, fetch, read, browser, test, and write capabilities only when relevant an...Votes: 0GitHub stars: 2
- Data Eng Ingestion Exception Triage QueueUse when the source ingestion workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the partner feed 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; accepted and rejected records reconcile to the producer manifest. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized....Votes: 0GitHub stars: 2
- Data Eng Ingestion Recovery Readiness DrillUse when the source ingestion workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the partner feed 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; accepted and rejected records reconcile to the producer manifest. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and ...Votes: 0GitHub stars: 2
- Data Eng Ingestion Scenario Sensitivity MatrixUse when the source ingestion team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the partner feed with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; accepted and rejected records reconcile to the producer manifest. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Recor...Votes: 0GitHub stars: 2
- Data Eng Ingestion Scope Intake GateUse when a new source ingestion request needs a bounded work scope to produce a scoped intake card for the partner feed. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; accepted and rejected records reconcile to the producer manifest. 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 approval before exter...Votes: 0GitHub stars: 2
- Data Eng Ingestion Source Provenance LedgerUse when a decision about source ingestion depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the partner feed. Success means each material claim has a source, version/date, location, and confidence note; accepted and rejected records reconcile to the producer manifest. 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
- Data Eng Ingestion Threshold Rule CheckUse when a source ingestion decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the partner feed 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; accepted and rejected records reconcile to the producer manifest. Use configured search, fetch, read, browser, test, and write capabilities only when relev...Votes: 0GitHub stars: 2
- Data Eng Lakehouse Approval Evidence PacketUse when a lakehouse table operations result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the lakehouse table containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; the proposed maintenance preserves the required snapshots and table contract. Use configured search, fetch, read, browser, test, and write ...Votes: 0GitHub stars: 2
- Data Eng Lakehouse Change Impact TraceUse when a version, rule, source, or stakeholder change may affect lakehouse table operations to produce a before/after change record and impact map for the lakehouse table. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the proposed maintenance preserves the required snapshots and table contract. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Rec...Votes: 0GitHub stars: 2
- Data Eng Lakehouse Closeout Handoff LedgerUse when a lakehouse table operations work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the lakehouse table with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; the proposed maintenance preserves the required snapshots and table contract. Use configured search, fetch, read, browser, test, and write capabilities only when ...Votes: 0GitHub stars: 2
- Data Eng Lakehouse Completeness ReconciliationUse when the lakehouse table operations workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the lakehouse table with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; the proposed maintenance preserves the required snapshots and table contract. Use configured search, fetch, read, browser, test, and write capabilit...Votes: 0GitHub stars: 2
- Data Eng Lakehouse Exception Triage QueueUse when the lakehouse table operations workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the lakehouse table with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; the proposed maintenance preserves the required snapshots and table contract. Use configured search, fetch, read, browser, test, and write capabilities only when...Votes: 0GitHub stars: 2
- Data Eng Lakehouse Recovery Readiness DrillUse when the lakehouse table operations workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the lakehouse table with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; the proposed maintenance preserves the required snapshots and table contract. Use configured search, fetch, read, browser, test, and write capabilitie...Votes: 0GitHub stars: 2
- Data Eng Lakehouse Scenario Sensitivity MatrixUse when the lakehouse table operations team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the lakehouse table with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the proposed maintenance preserves the required snapshots and table contract. Use configured search, fetch, read, browser, test, and write capabilities only when relev...Votes: 0GitHub stars: 2
- Data Eng Lakehouse Scope Intake GateUse when a new lakehouse table operations request needs a bounded work scope to produce a scoped intake card for the lakehouse table. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the proposed maintenance preserves the required snapshots and table contract. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, and s...Votes: 0GitHub stars: 2
- Data Eng Lakehouse Source Provenance LedgerUse when a decision about lakehouse table operations depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the lakehouse table. Success means each material claim has a source, version/date, location, and confidence note; the proposed maintenance preserves the required snapshots and table contract. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to...Votes: 0GitHub stars: 2
- Data Eng Lakehouse Threshold Rule CheckUse when a lakehouse table operations decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the lakehouse table showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; the proposed maintenance preserves the required snapshots and table contract. Use configured search, fetch, read, browser, test, and write cap...Votes: 0GitHub stars: 2
- Data Eng Orchestration Approval Evidence PacketUse when a pipeline orchestration result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the scheduled workflow 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 blocked or late run has a causal reason, owner, and next step. Use configured search, fetch, read, browser, test, and write capabilitie...Votes: 0GitHub stars: 2
- Data Eng Orchestration Change Impact TraceUse when a version, rule, source, or stakeholder change may affect pipeline orchestration to produce a before/after change record and impact map for the scheduled workflow. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each blocked or late run has a causal reason, owner, and next step. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidenc...Votes: 0GitHub stars: 2
- Data Eng Orchestration Closeout Handoff LedgerUse when a pipeline orchestration work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the scheduled workflow 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 blocked or late run has a causal reason, owner, and next step. Use configured search, fetch, read, browser, test, and write capabilities only when relevant an...Votes: 0GitHub stars: 2
- Data Eng Orchestration Completeness ReconciliationUse when the pipeline orchestration workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the scheduled workflow 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 blocked or late run has a causal reason, owner, and next step. Use configured search, fetch, read, browser, test, and write capabilities only wh...Votes: 0GitHub stars: 2
- Data Eng Orchestration Exception Triage QueueUse when the pipeline orchestration workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the scheduled workflow 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 blocked or late run has a causal reason, owner, and next step. Use configured search, fetch, read, browser, test, and write capabilities only when relevant a...Votes: 0GitHub stars: 2
- Data Eng Orchestration Recovery Readiness DrillUse when the pipeline orchestration workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the scheduled workflow 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 blocked or late run has a causal reason, owner, and next step. Use configured search, fetch, read, browser, test, and write capabilities only when...Votes: 0GitHub stars: 2
- Data Eng Orchestration Scenario Sensitivity MatrixUse when the pipeline orchestration team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the scheduled workflow with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each blocked or late run has a causal reason, owner, and next step. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and aut...Votes: 0GitHub stars: 2
- Data Eng Orchestration Scope Intake GateUse when a new pipeline orchestration request needs a bounded work scope to produce a scoped intake card for the scheduled workflow. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each blocked or late run has a causal reason, owner, and next step. 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
- Data Eng Orchestration Source Provenance LedgerUse when a decision about pipeline orchestration depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the scheduled workflow. Success means each material claim has a source, version/date, location, and confidence note; each blocked or late run has a causal reason, owner, and next step. 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
- Data Eng Orchestration Threshold Rule CheckUse when a pipeline orchestration decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the scheduled workflow 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 blocked or late run has a causal reason, owner, and next step. Use configured search, fetch, read, browser, test, and write capabilities o...Votes: 0GitHub stars: 2
- Data Eng Privacy Approval Evidence PacketUse when a data privacy governance result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the sensitive dataset 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 sensitive field has a documented purpose, owner, retention rule, and access basis. Use configured search, fetch, read, browser, test, ...Votes: 0GitHub stars: 2
- Data Eng Privacy Change Impact TraceUse when a version, rule, source, or stakeholder change may affect data privacy governance to produce a before/after change record and impact map for the sensitive dataset. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; every sensitive field has a documented purpose, owner, retention rule, and access basis. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and autho...Votes: 0GitHub stars: 2
- Data Eng Privacy Closeout Handoff LedgerUse when a data privacy governance work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the sensitive dataset 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 sensitive field has a documented purpose, owner, retention rule, and access basis. Use configured search, fetch, read, browser, test, and write capabilities ...Votes: 0GitHub stars: 2
- Data Eng Privacy Completeness ReconciliationUse when the data privacy governance workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the sensitive dataset 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 sensitive field has a documented purpose, owner, retention rule, and access basis. Use configured search, fetch, read, browser, test, and write...Votes: 0GitHub stars: 2
- Data Eng Privacy Exception Triage QueueUse when the data privacy governance workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the sensitive dataset 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 sensitive field has a documented purpose, owner, retention rule, and access basis. Use configured search, fetch, read, browser, test, and write capabilities...Votes: 0GitHub stars: 2
- Data Eng Privacy Recovery Readiness DrillUse when the data privacy governance workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the sensitive dataset 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 sensitive field has a documented purpose, owner, retention rule, and access basis. Use configured search, fetch, read, browser, test, and write c...Votes: 0GitHub stars: 2
- Data Eng Privacy Scenario Sensitivity MatrixUse when the data privacy governance team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the sensitive dataset with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; every sensitive field has a documented purpose, owner, retention rule, and access basis. Use configured search, fetch, read, browser, test, and write capabilities only ...Votes: 0GitHub stars: 2
- Data Eng Privacy Scope Intake GateUse when a new data privacy governance request needs a bounded work scope to produce a scoped intake card for the sensitive dataset. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; every sensitive field has a documented purpose, owner, retention rule, and access basis. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused pas...Votes: 0GitHub stars: 2