All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Aas Data Cdc Checkpoint Source Provenance LedgerUse when a decision about change-data-capture checkpoint recovery depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the CDC checkpoint continuity map. Success means each material claim has a source, version/date, location, and confidence note; 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 auth...Votes: 0GitHub stars: 2
- Aas Data Cdc Checkpoint Threshold Rule CheckUse when a change-data-capture checkpoint recovery decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the CDC checkpoint continuity map showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; restart resumes from a known boundary and duplicate events are handled by the declared policy. Use configured searc...Votes: 0GitHub stars: 2
- Aas Data Cursor Sync Approval Evidence PacketUse when a paginated API cursor synchronization result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the cursor synchronization test 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; retries neither skip nor duplicate fixture records under the declared ordering guarantees. Use configured sear...Votes: 0GitHub stars: 2
- Aas Data Cursor Sync Change Impact TraceUse when a version, rule, source, or stakeholder change may affect paginated API cursor synchronization to produce a before/after change record and impact map for the cursor synchronization test record. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; retries neither skip nor duplicate fixture records under the declared ordering guarantees. Use configured search, fetch, read, browser, test, and write capabilit...Votes: 0GitHub stars: 2
- Aas Data Cursor Sync Closeout Handoff LedgerUse when a paginated API cursor synchronization work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the cursor synchronization test 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; retries neither skip nor duplicate fixture records under the declared ordering guarantees. Use configured search, fetch, read, browse...Votes: 0GitHub stars: 2
- Aas Data Cursor Sync Completeness ReconciliationUse when the paginated API cursor synchronization workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the cursor synchronization test 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; retries neither skip nor duplicate fixture records under the declared ordering guarantees. Use configured search, fetch...Votes: 0GitHub stars: 2
- Aas Data Cursor Sync Exception Triage QueueUse when the paginated API cursor synchronization workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the cursor synchronization test 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; retries neither skip nor duplicate fixture records under the declared ordering guarantees. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2
- Aas Data Cursor Sync Recovery Readiness DrillUse when the paginated API cursor synchronization workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the cursor synchronization test 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; retries neither skip nor duplicate fixture records under the declared ordering guarantees. Use configured search, fetch, ...Votes: 0GitHub stars: 2
- Aas Data Cursor Sync Scenario Sensitivity MatrixUse when the paginated API cursor synchronization team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the cursor synchronization test record with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; retries neither skip nor duplicate fixture records under the declared ordering guarantees. Use configured search, fetch, read, browser, te...Votes: 0GitHub stars: 2
- Aas Data Cursor Sync Scope Intake GateUse when a new paginated API cursor synchronization request needs a bounded work scope to produce a scoped intake card for the cursor synchronization test record. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; retries neither skip nor duplicate fixture records under the declared ordering guarantees. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit...Votes: 0GitHub stars: 2
- Aas Data Cursor Sync Source Provenance LedgerUse when a decision about paginated API cursor synchronization depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the cursor synchronization test record. Success means each material claim has a source, version/date, location, and confidence note; retries neither skip nor duplicate fixture records under the declared ordering guarantees. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and author...Votes: 0GitHub stars: 2
- Aas Data Cursor Sync Threshold Rule CheckUse when a paginated API cursor synchronization decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the cursor synchronization test 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; retries neither skip nor duplicate fixture records under the declared ordering guarantees. Use configured search,...Votes: 0GitHub stars: 2
- Aas Data Freshness Contract Approval Evidence PacketUse when a data freshness contract definition result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the freshness service contract 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 freshness threshold is measurable and a stale state is visible to consumers. Use configured search, fetch, read, bro...Votes: 0GitHub stars: 2
- Aas Data Freshness Contract Change Impact TraceUse when a version, rule, source, or stakeholder change may affect data freshness contract definition to produce a before/after change record and impact map for the freshness service contract. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the freshness threshold is measurable and a stale state is visible to consumers. Use configured search, fetch, read, browser, test, and write capabilities only when releva...Votes: 0GitHub stars: 2
- Aas Data Freshness Contract Closeout Handoff LedgerUse when a data freshness contract definition work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the freshness service contract 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 freshness threshold is measurable and a stale state is visible to consumers. Use configured search, fetch, read, browser, test, and write c...Votes: 0GitHub stars: 2
- Aas Data Freshness Contract Completeness ReconciliationUse when the data freshness contract definition workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the freshness service contract 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 freshness threshold is measurable and a stale state is visible to consumers. Use configured search, fetch, read, browser, tes...Votes: 0GitHub stars: 2
- Aas Data Freshness Contract Exception Triage QueueUse when the data freshness contract definition workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the freshness service contract 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 freshness threshold is measurable and a stale state is visible to consumers. Use configured search, fetch, read, browser, test, and write ...Votes: 0GitHub stars: 2
- Aas Data Freshness Contract Recovery Readiness DrillUse when the data freshness contract definition workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the freshness service contract 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 freshness threshold is measurable and a stale state is visible to consumers. Use configured search, fetch, read, browser, test,...Votes: 0GitHub stars: 2
- Aas Data Freshness Contract Scenario Sensitivity MatrixUse when the data freshness contract definition team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the freshness service contract with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the freshness threshold is measurable and a stale state is visible to consumers. Use configured search, fetch, read, browser, test, and write capabi...Votes: 0GitHub stars: 2
- Aas Data Freshness Contract Scope Intake GateUse when a new data freshness contract definition request needs a bounded work scope to produce a scoped intake card for the freshness service contract. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the freshness threshold is measurable and a stale state is visible to consumers. 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
- Aas Data Freshness Contract Source Provenance LedgerUse when a decision about data freshness contract definition depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the freshness service contract. Success means each material claim has a source, version/date, location, and confidence note; the freshness threshold is measurable and a stale state is visible to consumers. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidenc...Votes: 0GitHub stars: 2
- Aas Data Freshness Contract Threshold Rule CheckUse when a data freshness contract definition decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the freshness service contract 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 freshness threshold is measurable and a stale state is visible to consumers. Use configured search, fetch, read, browse...Votes: 0GitHub stars: 2
- Aas Data Result Masking Approval Evidence PacketUse when a data query result masking result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the result-field minimization check 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; only purpose-necessary fields are exposed and restricted values are masked in test output. Use configured search, fetch, rea...Votes: 0GitHub stars: 2
- Aas Data Result Masking Change Impact TraceUse when a version, rule, source, or stakeholder change may affect data query result masking to produce a before/after change record and impact map for the result-field minimization check. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; only purpose-necessary fields are exposed and restricted values are masked in test output. Use configured search, fetch, read, browser, test, and write capabilities only when ...Votes: 0GitHub stars: 2
- Aas Data Result Masking Closeout Handoff LedgerUse when a data query result masking work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the result-field minimization check 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; only purpose-necessary fields are exposed and restricted values are masked in test output. Use configured search, fetch, read, browser, test, and w...Votes: 0GitHub stars: 2
- Aas Data Result Masking Completeness ReconciliationUse when the data query result masking workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the result-field minimization check 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; only purpose-necessary fields are exposed and restricted values are masked in test output. Use configured search, fetch, read, browse...Votes: 0GitHub stars: 2
- Aas Data Result Masking Exception Triage QueueUse when the data query result masking workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the result-field minimization check 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; only purpose-necessary fields are exposed and restricted values are masked in test output. Use configured search, fetch, read, browser, test, and ...Votes: 0GitHub stars: 2
- Aas Data Result Masking Recovery Readiness DrillUse when the data query result masking workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the result-field minimization check 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; only purpose-necessary fields are exposed and restricted values are masked in test output. Use configured search, fetch, read, browser,...Votes: 0GitHub stars: 2
- Aas Data Result Masking Scenario Sensitivity MatrixUse when the data query result masking team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the result-field minimization check with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; only purpose-necessary fields are exposed and restricted values are masked in test output. Use configured search, fetch, read, browser, test, and write ...Votes: 0GitHub stars: 2
- Aas Data Result Masking Scope Intake GateUse when a new data query result masking request needs a bounded work scope to produce a scoped intake card for the result-field minimization check. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; only purpose-necessary fields are exposed and restricted values are masked in test output. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to...Votes: 0GitHub stars: 2
- Aas Data Result Masking Source Provenance LedgerUse when a decision about data query result masking depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the result-field minimization check. Success means each material claim has a source, version/date, location, and confidence note; only purpose-necessary fields are exposed and restricted values are masked in test output. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record e...Votes: 0GitHub stars: 2
- Aas Data Result Masking Threshold Rule CheckUse when a data query result masking decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the result-field minimization check 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; only purpose-necessary fields are exposed and restricted values are masked in test output. Use configured search, fetch, read, ...Votes: 0GitHub stars: 2
- Aas Data Retrieval Holdout Approval Evidence PacketUse when a retrieval evaluation holdout design result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the retrieval holdout provenance 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; holdout examples remain separate from tuning and relevance labels have provenance. Use configured search, fetc...Votes: 0GitHub stars: 2
- Aas Data Retrieval Holdout Change Impact TraceUse when a version, rule, source, or stakeholder change may affect retrieval evaluation holdout design to produce a before/after change record and impact map for the retrieval holdout provenance packet. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; holdout examples remain separate from tuning and relevance labels have provenance. Use configured search, fetch, read, browser, test, and write capabilities only...Votes: 0GitHub stars: 2
- Aas Data Retrieval Holdout Closeout Handoff LedgerUse when a retrieval evaluation holdout design work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the retrieval holdout provenance 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; holdout examples remain separate from tuning and relevance labels have provenance. Use configured search, fetch, read, browser, test,...Votes: 0GitHub stars: 2
- Aas Data Retrieval Holdout Completeness ReconciliationUse when the retrieval evaluation holdout design workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the retrieval holdout provenance 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; holdout examples remain separate from tuning and relevance labels have provenance. Use configured search, fetch, read, ...Votes: 0GitHub stars: 2
- Aas Data Retrieval Holdout Exception Triage QueueUse when the retrieval evaluation holdout design workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the retrieval holdout provenance 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; holdout examples remain separate from tuning and relevance labels have provenance. Use configured search, fetch, read, browser, test...Votes: 0GitHub stars: 2
- Aas Data Retrieval Holdout Recovery Readiness DrillUse when the retrieval evaluation holdout design workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the retrieval holdout provenance 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; holdout examples remain separate from tuning and relevance labels have provenance. Use configured search, fetch, read, br...Votes: 0GitHub stars: 2
- Aas Data Retrieval Holdout Scenario Sensitivity MatrixUse when the retrieval evaluation holdout design team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the retrieval holdout provenance packet with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; holdout examples remain separate from tuning and relevance labels have provenance. Use configured search, fetch, read, browser, test, and ...Votes: 0GitHub stars: 2
- Aas Data Retrieval Holdout Scope Intake GateUse when a new retrieval evaluation holdout design request needs a bounded work scope to produce a scoped intake card for the retrieval holdout provenance packet. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; holdout examples remain separate from tuning and relevance labels have provenance. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinem...Votes: 0GitHub stars: 2
- Aas Data Retrieval Holdout Source Provenance LedgerUse when a decision about retrieval evaluation holdout design depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the retrieval holdout provenance packet. Success means each material claim has a source, version/date, location, and confidence note; holdout examples remain separate from tuning and relevance labels have provenance. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Re...Votes: 0GitHub stars: 2
- Aas Data Retrieval Holdout Threshold Rule CheckUse when a retrieval evaluation holdout design decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the retrieval holdout provenance 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; holdout examples remain separate from tuning and relevance labels have provenance. Use configured search, fetch, ...Votes: 0GitHub stars: 2
- Data Eng Catalog Lineage Approval Evidence PacketUse when a catalog and lineage result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the catalog asset 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 changed asset has an owner and complete, reviewable upstream/downstream links. Use configured search, fetch, read, browser, test, and write ca...Votes: 0GitHub stars: 2
- Data Eng Catalog Lineage Change Impact TraceUse when a version, rule, source, or stakeholder change may affect catalog and lineage to produce a before/after change record and impact map for the catalog asset. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; 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. Recor...Votes: 0GitHub stars: 2
- Data Eng Catalog Lineage Closeout Handoff LedgerUse when a catalog and lineage work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the catalog asset 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 changed asset has an owner and complete, reviewable upstream/downstream links. Use configured search, fetch, read, browser, test, and write capabilities only when re...Votes: 0GitHub stars: 2
- Data Eng Catalog Lineage Completeness ReconciliationUse when the catalog and lineage workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the catalog asset 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 changed asset has an owner and complete, reviewable upstream/downstream links. Use configured search, fetch, read, browser, test, and write capabilitie...Votes: 0GitHub stars: 2
- Data Eng Catalog Lineage Exception Triage QueueUse when the catalog and lineage workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the catalog asset 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 changed asset has an owner and complete, reviewable upstream/downstream links. Use configured search, fetch, read, browser, test, and write capabilities only when r...Votes: 0GitHub stars: 2
- Data Eng Catalog Lineage Recovery Readiness DrillUse when the catalog and lineage workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the catalog asset 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 changed asset has an owner and complete, reviewable upstream/downstream links. Use configured search, fetch, read, browser, test, and write capabilities ...Votes: 0GitHub stars: 2
- Data Eng Catalog Lineage Scenario Sensitivity MatrixUse when the catalog and lineage team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the catalog asset with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; every changed asset has an owner and complete, reviewable upstream/downstream links. Use configured search, fetch, read, browser, test, and write capabilities only when relevan...Votes: 0GitHub stars: 2
- Data Eng Catalog Lineage Scope Intake GateUse when a new catalog and lineage request needs a bounded work scope to produce a scoped intake card for the catalog asset. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; 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 three focused passes, and see...Votes: 0GitHub stars: 2