All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Geo Ops Geoparquet Source Provenance LedgerUse when a decision about GeoParquet packaging and partition review depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the geospatial package validation report. Success means each material claim has a source, version/date, location, and confidence note; package metadata and representative spatial queries are reproducible in the declared target environment. Use configured search, fetch, read, browser, test, and write capabilities only whe...Votes: 0GitHub stars: 2
- Geo Ops Geoparquet Threshold Rule CheckUse when a GeoParquet packaging and partition review decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the geospatial package validation report 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; package metadata and representative spatial queries are reproducible in the declared target environment. U...Votes: 0GitHub stars: 2
- Geo Ops Hosted Layer Approval Evidence PacketUse when a hosted-layer publication preflight result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the hosted layer release checklist 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 draft is read-only until an owner confirms sharing scope and every public field passes review. Use configured se...Votes: 0GitHub stars: 2
- Geo Ops Hosted Layer Change Impact TraceUse when a version, rule, source, or stakeholder change may affect hosted-layer publication preflight to produce a before/after change record and impact map for the hosted layer release checklist. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the draft is read-only until an owner confirms sharing scope and every public field passes review. Use configured search, fetch, read, browser, test, and write capabil...Votes: 0GitHub stars: 2
- Geo Ops Hosted Layer Closeout Handoff LedgerUse when a hosted-layer publication preflight work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the hosted layer release checklist 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 draft is read-only until an owner confirms sharing scope and every public field passes review. Use configured search, fetch, read, brow...Votes: 0GitHub stars: 2
- Geo Ops Hosted Layer Completeness ReconciliationUse when the hosted-layer publication preflight workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the hosted layer release checklist 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 draft is read-only until an owner confirms sharing scope and every public field passes review. Use configured search, fet...Votes: 0GitHub stars: 2
- Geo Ops Hosted Layer Exception Triage QueueUse when the hosted-layer publication preflight workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the hosted layer release checklist 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 draft is read-only until an owner confirms sharing scope and every public field passes review. Use configured search, fetch, read, bro...Votes: 0GitHub stars: 2
- Geo Ops Hosted Layer Recovery Readiness DrillUse when the hosted-layer publication preflight workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the hosted layer release checklist 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 draft is read-only until an owner confirms sharing scope and every public field passes review. Use configured search, fetch...Votes: 0GitHub stars: 2
- Geo Ops Hosted Layer Scenario Sensitivity MatrixUse when the hosted-layer publication preflight team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the hosted layer release checklist with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the draft is read-only until an owner confirms sharing scope and every public field passes review. Use configured search, fetch, read, browser, ...Votes: 0GitHub stars: 2
- Geo Ops Hosted Layer Scope Intake GateUse when a new hosted-layer publication preflight request needs a bounded work scope to produce a scoped intake card for the hosted layer release checklist. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the draft is read-only until an owner confirms sharing scope and every public field passes review. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, lim...Votes: 0GitHub stars: 2
- Geo Ops Hosted Layer Source Provenance LedgerUse when a decision about hosted-layer publication preflight depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the hosted layer release checklist. Success means each material claim has a source, version/date, location, and confidence note; the draft is read-only until an owner confirms sharing scope and every public field passes review. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and auth...Votes: 0GitHub stars: 2
- Geo Ops Hosted Layer Threshold Rule CheckUse when a hosted-layer publication preflight decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the hosted layer release checklist 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 draft is read-only until an owner confirms sharing scope and every public field passes review. Use configured searc...Votes: 0GitHub stars: 2
- Geo Ops Imagery Quality Approval Evidence PacketUse when a satellite imagery quality and mask review result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the imagery QA evidence 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; mask behavior is validated on sampled areas and remaining artifacts are explicitly disclosed. Use configured sear...Votes: 0GitHub stars: 2
- Geo Ops Imagery Quality Change Impact TraceUse when a version, rule, source, or stakeholder change may affect satellite imagery quality and mask review to produce a before/after change record and impact map for the imagery QA evidence packet. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; mask behavior is validated on sampled areas and remaining artifacts are explicitly disclosed. Use configured search, fetch, read, browser, test, and write capabilit...Votes: 0GitHub stars: 2
- Geo Ops Imagery Quality Closeout Handoff LedgerUse when a satellite imagery quality and mask review work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the imagery QA evidence 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; mask behavior is validated on sampled areas and remaining artifacts are explicitly disclosed. Use configured search, fetch, read, browse...Votes: 0GitHub stars: 2
- Geo Ops Imagery Quality Completeness ReconciliationUse when the satellite imagery quality and mask review workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the imagery QA evidence 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; mask behavior is validated on sampled areas and remaining artifacts are explicitly disclosed. Use configured search, fetch...Votes: 0GitHub stars: 2
- Geo Ops Imagery Quality Exception Triage QueueUse when the satellite imagery quality and mask review workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the imagery QA evidence 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; mask behavior is validated on sampled areas and remaining artifacts are explicitly disclosed. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2
- Geo Ops Imagery Quality Recovery Readiness DrillUse when the satellite imagery quality and mask review workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the imagery QA evidence 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; mask behavior is validated on sampled areas and remaining artifacts are explicitly disclosed. Use configured search, fetch, ...Votes: 0GitHub stars: 2
- Geo Ops Imagery Quality Scenario Sensitivity MatrixUse when the satellite imagery quality and mask review team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the imagery QA evidence packet with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; mask behavior is validated on sampled areas and remaining artifacts are explicitly disclosed. Use configured search, fetch, read, browser, te...Votes: 0GitHub stars: 2
- Geo Ops Imagery Quality Scope Intake GateUse when a new satellite imagery quality and mask review request needs a bounded work scope to produce a scoped intake card for the imagery QA evidence packet. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; mask behavior is validated on sampled areas and remaining artifacts are explicitly disclosed. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit...Votes: 0GitHub stars: 2
- Geo Ops Imagery Quality Source Provenance LedgerUse when a decision about satellite imagery quality and mask review depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the imagery QA evidence packet. Success means each material claim has a source, version/date, location, and confidence note; mask behavior is validated on sampled areas and remaining artifacts are explicitly disclosed. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and author...Votes: 0GitHub stars: 2
- Geo Ops Imagery Quality Threshold Rule CheckUse when a satellite imagery quality and mask review decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the imagery QA evidence 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; mask behavior is validated on sampled areas and remaining artifacts are explicitly disclosed. Use configured search,...Votes: 0GitHub stars: 2
- Geo Ops Map Export Approval Evidence PacketUse when a cartographic map export and accessibility review result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the map export QA checklist 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; map elements communicate units, date, source, uncertainty, and access needs without implying unwarranted prec...Votes: 0GitHub stars: 2
- Geo Ops Map Export Change Impact TraceUse when a version, rule, source, or stakeholder change may affect cartographic map export and accessibility review to produce a before/after change record and impact map for the map export QA checklist. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; map elements communicate units, date, source, uncertainty, and access needs without implying unwarranted precision. Use configured search, fetch, read, browser,...Votes: 0GitHub stars: 2
- Geo Ops Map Export Closeout Handoff LedgerUse when a cartographic map export and accessibility review work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the map export QA checklist 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; map elements communicate units, date, source, uncertainty, and access needs without implying unwarranted precision. Use configured s...Votes: 0GitHub stars: 2
- Geo Ops Map Export Completeness ReconciliationUse when the cartographic map export and accessibility review workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the map export QA checklist 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; map elements communicate units, date, source, uncertainty, and access needs without implying unwarranted precision. Us...Votes: 0GitHub stars: 2
- Geo Ops Map Export Exception Triage QueueUse when the cartographic map export and accessibility review workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the map export QA checklist 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; map elements communicate units, date, source, uncertainty, and access needs without implying unwarranted precision. Use configured ...Votes: 0GitHub stars: 2
- Geo Ops Map Export Recovery Readiness DrillUse when the cartographic map export and accessibility review workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the map export QA checklist 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; map elements communicate units, date, source, uncertainty, and access needs without implying unwarranted precision. Use ...Votes: 0GitHub stars: 2
- Geo Ops Map Export Scenario Sensitivity MatrixUse when the cartographic map export and accessibility review team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the map export QA checklist with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; map elements communicate units, date, source, uncertainty, and access needs without implying unwarranted precision. Use configured search...Votes: 0GitHub stars: 2
- Geo Ops Map Export Scope Intake GateUse when a new cartographic map export and accessibility review request needs a bounded work scope to produce a scoped intake card for the map export QA checklist. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; map elements communicate units, date, source, uncertainty, and access needs without implying unwarranted precision. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authoriz...Votes: 0GitHub stars: 2
- Geo Ops Map Export Source Provenance LedgerUse when a decision about cartographic map export and accessibility review depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the map export QA checklist. Success means each material claim has a source, version/date, location, and confidence note; map elements communicate units, date, source, uncertainty, and access needs without implying unwarranted precision. Use configured search, fetch, read, browser, test, and write capabilities onl...Votes: 0GitHub stars: 2
- Geo Ops Map Export Threshold Rule CheckUse when a cartographic map export and accessibility review decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the map export QA checklist 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; map elements communicate units, date, source, uncertainty, and access needs without implying unwarranted precisi...Votes: 0GitHub stars: 2
- Geo Ops Overlay Analysis Approval Evidence PacketUse when a spatial overlay and join result validation result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the spatial operation reconciliation 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 counts and sampled relationships match the stated predicate and edge cases are recorded. Use config...Votes: 0GitHub stars: 2
- Geo Ops Overlay Analysis Change Impact TraceUse when a version, rule, source, or stakeholder change may affect spatial overlay and join result validation to produce a before/after change record and impact map for the spatial operation reconciliation. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; output counts and sampled relationships match the stated predicate and edge cases are recorded. Use configured search, fetch, read, browser, test, and write ...Votes: 0GitHub stars: 2
- Geo Ops Overlay Analysis Closeout Handoff LedgerUse when a spatial overlay and join result validation work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the spatial operation reconciliation 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 counts and sampled relationships match the stated predicate and edge cases are recorded. Use configured search, fetch, rea...Votes: 0GitHub stars: 2
- Geo Ops Overlay Analysis Completeness ReconciliationUse when the spatial overlay and join result validation workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the spatial operation reconciliation 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 counts and sampled relationships match the stated predicate and edge cases are recorded. Use configured sear...Votes: 0GitHub stars: 2
- Geo Ops Overlay Analysis Exception Triage QueueUse when the spatial overlay and join result validation workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the spatial operation reconciliation 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 counts and sampled relationships match the stated predicate and edge cases are recorded. Use configured search, fetch, re...Votes: 0GitHub stars: 2
- Geo Ops Overlay Analysis Recovery Readiness DrillUse when the spatial overlay and join result validation workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the spatial operation reconciliation 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 counts and sampled relationships match the stated predicate and edge cases are recorded. Use configured search...Votes: 0GitHub stars: 2
- Geo Ops Overlay Analysis Scenario Sensitivity MatrixUse when the spatial overlay and join result validation team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the spatial operation reconciliation with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; output counts and sampled relationships match the stated predicate and edge cases are recorded. Use configured search, fetch, read, br...Votes: 0GitHub stars: 2
- Geo Ops Overlay Analysis Scope Intake GateUse when a new spatial overlay and join result validation request needs a bounded work scope to produce a scoped intake card for the spatial operation reconciliation. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; output counts and sampled relationships match the stated predicate and edge cases are recorded. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record eviden...Votes: 0GitHub stars: 2
- Geo Ops Overlay Analysis Source Provenance LedgerUse when a decision about spatial overlay and join result validation depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the spatial operation reconciliation. Success means each material claim has a source, version/date, location, and confidence note; output counts and sampled relationships match the stated predicate and edge cases are recorded. Use configured search, fetch, read, browser, test, and write capabilities only when relevant a...Votes: 0GitHub stars: 2
- Geo Ops Overlay Analysis Threshold Rule CheckUse when a spatial overlay and join result validation decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the spatial operation reconciliation 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 counts and sampled relationships match the stated predicate and edge cases are recorded. Use configure...Votes: 0GitHub stars: 2
- Geo Ops Pipeline Repro Approval Evidence PacketUse when a geospatial pipeline reproducibility and output checks result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the geospatial pipeline run record containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; the result can be reproduced from the recorded inputs and declared differences are reviewed. Use ...Votes: 0GitHub stars: 2
- Geo Ops Pipeline Repro Change Impact TraceUse when a version, rule, source, or stakeholder change may affect geospatial pipeline reproducibility and output checks to produce a before/after change record and impact map for the geospatial pipeline run record. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the result can be reproduced from the recorded inputs and declared differences are reviewed. Use configured search, fetch, read, browser, test, and ...Votes: 0GitHub stars: 2
- Geo Ops Pipeline Repro Closeout Handoff LedgerUse when a geospatial pipeline reproducibility and output checks work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the geospatial pipeline run record with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; the result can be reproduced from the recorded inputs and declared differences are reviewed. Use configured search, fetc...Votes: 0GitHub stars: 2
- Geo Ops Pipeline Repro Completeness ReconciliationUse when the geospatial pipeline reproducibility and output checks workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the geospatial pipeline run record with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; the result can be reproduced from the recorded inputs and declared differences are reviewed. Use configure...Votes: 0GitHub stars: 2
- Geo Ops Pipeline Repro Exception Triage QueueUse when the geospatial pipeline reproducibility and output checks workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the geospatial pipeline run record with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; the result can be reproduced from the recorded inputs and declared differences are reviewed. Use configured search, fet...Votes: 0GitHub stars: 2
- Geo Ops Pipeline Repro Recovery Readiness DrillUse when the geospatial pipeline reproducibility and output checks workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the geospatial pipeline run record with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; the result can be reproduced from the recorded inputs and declared differences are reviewed. Use configured ...Votes: 0GitHub stars: 2
- Geo Ops Pipeline Repro Scenario Sensitivity MatrixUse when the geospatial pipeline reproducibility and output checks team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the geospatial pipeline run record with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the result can be reproduced from the recorded inputs and declared differences are reviewed. Use configured search, fetch, re...Votes: 0GitHub stars: 2
- Geo Ops Pipeline Repro Scope Intake GateUse when a new geospatial pipeline reproducibility and output checks request needs a bounded work scope to produce a scoped intake card for the geospatial pipeline run record. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the result can be reproduced from the recorded inputs and declared differences are reviewed. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record ...Votes: 0GitHub stars: 2