All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Data Eng Privacy Source Provenance LedgerUse when a decision about data privacy governance depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the sensitive dataset. Success means each material claim has a source, version/date, location, and confidence note; 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 ref...Votes: 0GitHub stars: 2
- Data Eng Privacy Threshold Rule CheckUse when a data privacy governance decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the sensitive dataset 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 sensitive field has a documented purpose, owner, retention rule, and access basis. Use configured search, fetch, read, browser, test, and...Votes: 0GitHub stars: 2
- Data Eng Quality Approval Evidence PacketUse when a data quality operations result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the quality rule 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 rule detects the intended defect without silently masking valid variation. Use configured search, fetch, read, browser, test, and write capab...Votes: 0GitHub stars: 2
- Data Eng Quality Change Impact TraceUse when a version, rule, source, or stakeholder change may affect data quality operations to produce a before/after change record and impact map for the quality rule. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the rule detects the intended defect without silently masking valid variation. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record e...Votes: 0GitHub stars: 2
- Data Eng Quality Closeout Handoff LedgerUse when a data quality operations work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the quality rule 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 rule detects the intended defect without silently masking valid variation. Use configured search, fetch, read, browser, test, and write capabilities only when relev...Votes: 0GitHub stars: 2
- Data Eng Quality Completeness ReconciliationUse when the data quality operations workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the quality rule 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 rule detects the intended defect without silently masking valid variation. Use configured search, fetch, read, browser, test, and write capabilities o...Votes: 0GitHub stars: 2
- Data Eng Quality Exception Triage QueueUse when the data quality operations workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the quality rule 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 rule detects the intended defect without silently masking valid variation. Use configured search, fetch, read, browser, test, and write capabilities only when rele...Votes: 0GitHub stars: 2
- Data Eng Quality Recovery Readiness DrillUse when the data quality operations workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the quality rule 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 rule detects the intended defect without silently masking valid variation. Use configured search, fetch, read, browser, test, and write capabilities onl...Votes: 0GitHub stars: 2
- Data Eng Quality Scenario Sensitivity MatrixUse when the data quality operations team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the quality rule with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the rule detects the intended defect without silently masking valid variation. Use configured search, fetch, read, browser, test, and write capabilities only when relevant a...Votes: 0GitHub stars: 2
- Data Eng Quality Scope Intake GateUse when a new data quality operations request needs a bounded work scope to produce a scoped intake card for the quality rule. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the rule detects the intended defect without silently masking valid variation. 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 a...Votes: 0GitHub stars: 2
- Data Eng Quality Source Provenance LedgerUse when a decision about data quality operations depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the quality rule. Success means each material claim has a source, version/date, location, and confidence note; the rule detects the intended defect without silently masking valid variation. 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
- Data Eng Quality Threshold Rule CheckUse when a data quality operations decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the quality rule 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 rule detects the intended defect without silently masking valid variation. Use configured search, fetch, read, browser, test, and write capabili...Votes: 0GitHub stars: 2
- Data Eng Streaming Approval Evidence PacketUse when a stream processing result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the streaming job 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; replayed inputs are idempotent and the declared event-time window is complete. Use configured search, fetch, read, browser, test, and write capabiliti...Votes: 0GitHub stars: 2
- Data Eng Streaming Change Impact TraceUse when a version, rule, source, or stakeholder change may affect stream processing to produce a before/after change record and impact map for the streaming job. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; replayed inputs are idempotent and the declared event-time window is complete. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record eviden...Votes: 0GitHub stars: 2
- Data Eng Streaming Closeout Handoff LedgerUse when a stream processing work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the streaming job 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; replayed inputs are idempotent and the declared event-time window is complete. Use configured search, fetch, read, browser, test, and write capabilities only when relevant a...Votes: 0GitHub stars: 2
- Data Eng Streaming Completeness ReconciliationUse when the stream processing workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the streaming job 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; replayed inputs are idempotent and the declared event-time window is complete. Use configured search, fetch, read, browser, test, and write capabilities only w...Votes: 0GitHub stars: 2
- Data Eng Streaming Exception Triage QueueUse when the stream processing workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the streaming job 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; replayed inputs are idempotent and the declared event-time window is complete. Use configured search, fetch, read, browser, test, and write capabilities only when relevant ...Votes: 0GitHub stars: 2
- Data Eng Streaming Recovery Readiness DrillUse when the stream processing workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the streaming job 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; replayed inputs are idempotent and the declared event-time window is complete. Use configured search, fetch, read, browser, test, and write capabilities only whe...Votes: 0GitHub stars: 2
- Data Eng Streaming Scenario Sensitivity MatrixUse when the stream processing team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the streaming job with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; replayed inputs are idempotent and the declared event-time window is complete. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and au...Votes: 0GitHub stars: 2
- Data Eng Streaming Scope Intake GateUse when a new stream processing request needs a bounded work scope to produce a scoped intake card for the streaming job. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; replayed inputs are idempotent and the declared event-time window is complete. 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 approv...Votes: 0GitHub stars: 2
- Data Eng Streaming Source Provenance LedgerUse when a decision about stream processing depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the streaming job. Success means each material claim has a source, version/date, location, and confidence note; replayed inputs are idempotent and the declared event-time window is complete. 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
- Data Eng Streaming Threshold Rule CheckUse when a stream processing decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the streaming job 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; replayed inputs are idempotent and the declared event-time window is complete. Use configured search, fetch, read, browser, test, and write capabilities ...Votes: 0GitHub stars: 2
- Data Eng Transformation Approval Evidence PacketUse when a data transformation result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the transformation model 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; output invariants pass and any changed rows are attributable to a rule. Use configured search, fetch, read, browser, test, and write capabili...Votes: 0GitHub stars: 2
- Data Eng Transformation Change Impact TraceUse when a version, rule, source, or stakeholder change may affect data transformation to produce a before/after change record and impact map for the transformation model. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; output invariants pass and any changed rows are attributable to a rule. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evid...Votes: 0GitHub stars: 2
- Data Eng Transformation Closeout Handoff LedgerUse when a data transformation work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the transformation model 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; output invariants pass and any changed rows are attributable to a rule. Use configured search, fetch, read, browser, test, and write capabilities only when relevant...Votes: 0GitHub stars: 2
- Data Eng Transformation Completeness ReconciliationUse when the data transformation workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the transformation model 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; output invariants pass and any changed rows are attributable to a rule. Use configured search, fetch, read, browser, test, and write capabilities only...Votes: 0GitHub stars: 2
- Data Eng Transformation Exception Triage QueueUse when the data transformation workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the transformation model 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; output invariants pass and any changed rows are attributable to a rule. Use configured search, fetch, read, browser, test, and write capabilities only when relevan...Votes: 0GitHub stars: 2
- Data Eng Transformation Recovery Readiness DrillUse when the data transformation workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the transformation model 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; output invariants pass and any changed rows are attributable to a rule. Use configured search, fetch, read, browser, test, and write capabilities only w...Votes: 0GitHub stars: 2
- Data Eng Transformation Scenario Sensitivity MatrixUse when the data transformation team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the transformation model with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; output invariants pass and any changed rows are attributable to a rule. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and ...Votes: 0GitHub stars: 2
- Data Eng Transformation Scope Intake GateUse when a new data transformation request needs a bounded work scope to produce a scoped intake card for the transformation model. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; output invariants pass and any changed rows are attributable to a rule. 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 appr...Votes: 0GitHub stars: 2
- Data Eng Transformation Source Provenance LedgerUse when a decision about data transformation depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the transformation model. Success means each material claim has a source, version/date, location, and confidence note; output invariants pass and any changed rows are attributable to a rule. 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
- Data Eng Transformation Threshold Rule CheckUse when a data transformation decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the transformation model 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; output invariants pass and any changed rows are attributable to a rule. Use configured search, fetch, read, browser, test, and write capabilitie...Votes: 0GitHub stars: 2
- Data Eng Warehouse Approval Evidence PacketUse when a warehouse serving result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the warehouse 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 change meets the agreed latency/cost target without changing result semantics. Use configured search, fetch, read, browser, test, and write c...Votes: 0GitHub stars: 2
- Data Eng Warehouse Change Impact TraceUse when a version, rule, source, or stakeholder change may affect warehouse serving to produce a before/after change record and impact map for the warehouse workload. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the change meets the agreed latency/cost target without changing result semantics. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Reco...Votes: 0GitHub stars: 2
- Data Eng Warehouse Closeout Handoff LedgerUse when a warehouse serving work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the warehouse 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 change meets the agreed latency/cost target without changing result semantics. Use configured search, fetch, read, browser, test, and write capabilities only when r...Votes: 0GitHub stars: 2
- Data Eng Warehouse Completeness ReconciliationUse when the warehouse serving workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the warehouse 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 change meets the agreed latency/cost target without changing result semantics. Use configured search, fetch, read, browser, test, and write capabiliti...Votes: 0GitHub stars: 2
- Data Eng Warehouse Exception Triage QueueUse when the warehouse serving workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the warehouse 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 change meets the agreed latency/cost target without changing result semantics. Use configured search, fetch, read, browser, test, and write capabilities only when ...Votes: 0GitHub stars: 2
- Data Eng Warehouse Recovery Readiness DrillUse when the warehouse serving workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the warehouse 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 change meets the agreed latency/cost target without changing result semantics. Use configured search, fetch, read, browser, test, and write capabilities...Votes: 0GitHub stars: 2
- Data Eng Warehouse Scenario Sensitivity MatrixUse when the warehouse serving team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the warehouse workload with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the change meets the agreed latency/cost target without changing result semantics. Use configured search, fetch, read, browser, test, and write capabilities only when releva...Votes: 0GitHub stars: 2
- Data Eng Warehouse Scope Intake GateUse when a new warehouse serving request needs a bounded work scope to produce a scoped intake card for the warehouse workload. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the change meets the agreed latency/cost target without changing result semantics. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, and se...Votes: 0GitHub stars: 2
- Data Eng Warehouse Source Provenance LedgerUse when a decision about warehouse serving depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the warehouse workload. Success means each material claim has a source, version/date, location, and confidence note; the change meets the agreed latency/cost target without changing result semantics. 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 Warehouse Threshold Rule CheckUse when a warehouse serving decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the warehouse 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 change meets the agreed latency/cost target without changing result semantics. Use configured search, fetch, read, browser, test, and write capa...Votes: 0GitHub stars: 2
- Data Engineering Data Pipeline Capability Surface MapUse when the actual capability boundary of Data pipeline engineering needs to be distinguished from assumptions. Produce a capability map for Data pipeline engineering 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 source contract, transformation sequence,...Votes: 0GitHub stars: 2
- Data Engineering Data Pipeline Change Impact AssessmentUse when a proposed Data pipeline engineering version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for Data pipeline engineering 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 source contract, transformation sequenc...Votes: 0GitHub stars: 2
- Data Engineering Data Pipeline Failure Triage RecordUse when a reproducible Data pipeline engineering symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for Data pipeline engineering 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 source contract, transformation sequence, checkpoint identity, and freshness ...Votes: 0GitHub stars: 2
- Data Engineering Data Pipeline Input Output ContractUse when the accepted inputs or produced outputs for Data pipeline engineering need a checkable boundary. Produce an input/output contract for Data pipeline engineering 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 source contract, transformation sequence, checkpoint identity, and fr...Votes: 0GitHub stars: 2
- Data Engineering Data Pipeline Integration Parity TraceUse when Data pipeline engineering exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for Data pipeline engineering 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 source contract, transformation sequence, checkpoint identity, and freshness boundary....Votes: 0GitHub stars: 2
- Data Engineering Data Pipeline Performance EnvelopeUse when Data pipeline engineering must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for Data pipeline engineering 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 source contract, transformation sequence, checkpoint identi...Votes: 0GitHub stars: 2
- Data Engineering Data Pipeline Permission Boundary ReviewUse when Data pipeline engineering may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for Data pipeline engineering 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 source contract, transformation sequence, checkp...Votes: 0GitHub stars: 2
- Data Engineering Data Pipeline Release Handoff RecordUse when a Data pipeline engineering review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for Data pipeline engineering 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 source contract, transformation sequence,...Votes: 0GitHub stars: 2