All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Edge Fleet Ota Recovery Closeout Handoff LedgerUse when a edge update recovery readiness work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the update recovery drill 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 staged device returns to a known test state without contacting live fleet endpoints. Use configured search, fetch, read, browser, test, and w...Votes: 0GitHub stars: 2
- Edge Fleet Ota Recovery Completeness ReconciliationUse when the edge update recovery readiness workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the update recovery drill 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 staged device returns to a known test state without contacting live fleet endpoints. Use configured search, fetch, read, browse...Votes: 0GitHub stars: 2
- Edge Fleet Ota Recovery Exception Triage QueueUse when the edge update recovery readiness workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the update recovery drill 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 staged device returns to a known test state without contacting live fleet endpoints. Use configured search, fetch, read, browser, test, and ...Votes: 0GitHub stars: 2
- Edge Fleet Ota Recovery Recovery Readiness DrillUse when the edge update recovery readiness workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the update recovery drill 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 staged device returns to a known test state without contacting live fleet endpoints. Use configured search, fetch, read, browser,...Votes: 0GitHub stars: 2
- Edge Fleet Ota Recovery Scenario Sensitivity MatrixUse when the edge update recovery readiness team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the update recovery drill record with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the staged device returns to a known test state without contacting live fleet endpoints. Use configured search, fetch, read, browser, test, and write ...Votes: 0GitHub stars: 2
- Edge Fleet Ota Recovery Scope Intake GateUse when a new edge update recovery readiness request needs a bounded work scope to produce a scoped intake card for the update recovery drill record. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the staged device returns to a known test state without contacting live fleet endpoints. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to...Votes: 0GitHub stars: 2
- Edge Fleet Ota Recovery Source Provenance LedgerUse when a decision about edge update recovery readiness depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the update recovery drill record. Success means each material claim has a source, version/date, location, and confidence note; the staged device returns to a known test state without contacting live fleet endpoints. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record e...Votes: 0GitHub stars: 2
- Edge Fleet Ota Recovery Threshold Rule CheckUse when a edge update recovery readiness decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the update recovery drill 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; the staged device returns to a known test state without contacting live fleet endpoints. Use configured search, fetch, read, ...Votes: 0GitHub stars: 2
- Edge Fleet Sensor Calibration Approval Evidence PacketUse when a edge sensor calibration provenance result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the sensor calibration lineage 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; a reading can be tied to sensor and calibration state or is marked unsuitable for comparison. Use configured sear...Votes: 0GitHub stars: 2
- Edge Fleet Sensor Calibration Change Impact TraceUse when a version, rule, source, or stakeholder change may affect edge sensor calibration provenance to produce a before/after change record and impact map for the sensor calibration lineage record. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; a reading can be tied to sensor and calibration state or is marked unsuitable for comparison. Use configured search, fetch, read, browser, test, and write capabilit...Votes: 0GitHub stars: 2
- Edge Fleet Sensor Calibration Closeout Handoff LedgerUse when a edge sensor calibration provenance work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the sensor calibration lineage 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; a reading can be tied to sensor and calibration state or is marked unsuitable for comparison. Use configured search, fetch, read, browse...Votes: 0GitHub stars: 2
- Edge Fleet Sensor Calibration Completeness ReconciliationUse when the edge sensor calibration provenance workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the sensor calibration lineage 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; a reading can be tied to sensor and calibration state or is marked unsuitable for comparison. Use configured search, fetch...Votes: 0GitHub stars: 2
- Edge Fleet Sensor Calibration Exception Triage QueueUse when the edge sensor calibration provenance workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the sensor calibration lineage 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; a reading can be tied to sensor and calibration state or is marked unsuitable for comparison. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2
- Edge Fleet Sensor Calibration Recovery Readiness DrillUse when the edge sensor calibration provenance workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the sensor calibration lineage 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; a reading can be tied to sensor and calibration state or is marked unsuitable for comparison. Use configured search, fetch, ...Votes: 0GitHub stars: 2
- Edge Fleet Sensor Calibration Scenario Sensitivity MatrixUse when the edge sensor calibration provenance team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the sensor calibration lineage record with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; a reading can be tied to sensor and calibration state or is marked unsuitable for comparison. Use configured search, fetch, read, browser, te...Votes: 0GitHub stars: 2
- Edge Fleet Sensor Calibration Scope Intake GateUse when a new edge sensor calibration provenance request needs a bounded work scope to produce a scoped intake card for the sensor calibration lineage record. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; a reading can be tied to sensor and calibration state or is marked unsuitable for comparison. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit...Votes: 0GitHub stars: 2
- Edge Fleet Sensor Calibration Source Provenance LedgerUse when a decision about edge sensor calibration provenance depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the sensor calibration lineage record. Success means each material claim has a source, version/date, location, and confidence note; a reading can be tied to sensor and calibration state or is marked unsuitable for comparison. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and author...Votes: 0GitHub stars: 2
- Edge Fleet Sensor Calibration Threshold Rule CheckUse when a edge sensor calibration provenance decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the sensor calibration lineage 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; a reading can be tied to sensor and calibration state or is marked unsuitable for comparison. Use configured search,...Votes: 0GitHub stars: 2
- Edge Fleet Telemetry Minimization Approval Evidence PacketUse when a edge telemetry minimization result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the telemetry field and retention map containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; each field has a documented purpose and unnecessary precision or retention is removed from draft. Use configured search,...Votes: 0GitHub stars: 2
- Edge Fleet Telemetry Minimization Change Impact TraceUse when a version, rule, source, or stakeholder change may affect edge telemetry minimization to produce a before/after change record and impact map for the telemetry field and retention map. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each field has a documented purpose and unnecessary precision or retention is removed from draft. Use configured search, fetch, read, browser, test, and write capabilities...Votes: 0GitHub stars: 2
- Edge Fleet Telemetry Minimization Closeout Handoff LedgerUse when a edge telemetry minimization work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the telemetry field and retention map with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; each field has a documented purpose and unnecessary precision or retention is removed from draft. Use configured search, fetch, read, browser, ...Votes: 0GitHub stars: 2
- Edge Fleet Telemetry Minimization Completeness ReconciliationUse when the edge telemetry minimization workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the telemetry field and retention map with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; each field has a documented purpose and unnecessary precision or retention is removed from draft. Use configured search, fetch, r...Votes: 0GitHub stars: 2
- Edge Fleet Telemetry Minimization Exception Triage QueueUse when the edge telemetry minimization workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the telemetry field and retention map with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; each field has a documented purpose and unnecessary precision or retention is removed from draft. Use configured search, fetch, read, browser,...Votes: 0GitHub stars: 2
- Edge Fleet Telemetry Minimization Recovery Readiness DrillUse when the edge telemetry minimization workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the telemetry field and retention map with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; each field has a documented purpose and unnecessary precision or retention is removed from draft. Use configured search, fetch, rea...Votes: 0GitHub stars: 2
- Edge Fleet Telemetry Minimization Scenario Sensitivity MatrixUse when the edge telemetry minimization team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the telemetry field and retention map with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each field has a documented purpose and unnecessary precision or retention is removed from draft. Use configured search, fetch, read, browser, test,...Votes: 0GitHub stars: 2
- Edge Fleet Telemetry Minimization Scope Intake GateUse when a new edge telemetry minimization request needs a bounded work scope to produce a scoped intake card for the telemetry field and retention map. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each field has a documented purpose and unnecessary precision or retention is removed from draft. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit re...Votes: 0GitHub stars: 2
- Edge Fleet Telemetry Minimization Source Provenance LedgerUse when a decision about edge telemetry minimization depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the telemetry field and retention map. Success means each material claim has a source, version/date, location, and confidence note; each field has a documented purpose and unnecessary precision or retention is removed from draft. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorize...Votes: 0GitHub stars: 2
- Edge Fleet Telemetry Minimization Threshold Rule CheckUse when a edge telemetry minimization decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the telemetry field and retention 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; each field has a documented purpose and unnecessary precision or retention is removed from draft. Use configured search, fe...Votes: 0GitHub stars: 2
- Edge Model Export ValidationUse when a task involves checking that an exported AI model preserves behavior in its edge runtime to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform production, financial, devi...Votes: 0GitHub stars: 2
- Edge Model Version Rollout ReviewUse when a task involves reviewing a staged update of an AI model across edge devices to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform production, financial, device-control, d...Votes: 0GitHub stars: 2
- Edge Site Compute Capacity BudgetUse when a task involves estimating compute and memory capacity for an edge site workload to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform production, financial, device-contro...Votes: 0GitHub stars: 2
- Edge Site To Cloud Bandwidth BudgetUse when a task involves budgeting network use for video, telemetry, model, and administrative traffic to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform production, financial, ...Votes: 0GitHub stars: 2
- Embedded Wifi Low Power DiagnosticsUse when a task involves collecting structured evidence for Wi-Fi sleep-current or wake failures in an embedded device to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform product...Votes: 0GitHub stars: 2
- Emc Precompliance CheckUse when a task involves screening a PCB design for likely electromagnetic-compatibility risks before formal testing to identify the intended outcome, relevant inputs, platform or version, sensitive data, and permission boundary before acting. Use current primary documentation for version-sensitive behavior, produce a reviewable artifact, and verify it against stated criteria. Trigger for planning, implementation, evaluation, or troubleshooting in this focused domain; do not install or run th...Votes: 0GitHub stars: 2
- Finite Element Model VerificationUse when a task involves verifying finite-element implementation and model setup before interpreting a result to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform production, fina...Votes: 0GitHub stars: 2
- Finite Volume Flux Balance ReviewUse when a task involves reviewing flux assembly and conservation in a finite-volume discretization to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform production, financial, har...Votes: 0GitHub stars: 2
- Formal Property Coverage PlanningUse when a task involves planning properties and proof coverage for a hardware block to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform production, financial, hardware-control, ...Votes: 0GitHub stars: 2
- Fpga Prototype Io Constraint ReviewUse when a task involves reviewing FPGA pin assignments and electrical constraints for an SoC prototype to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform production, financial,...Votes: 0GitHub stars: 2
- Hardware Software Interface Contract ReviewUse when a task involves aligning firmware assumptions with a hardware peripheral interface to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform production, financial, hardware-co...Votes: 0GitHub stars: 2
- Iot Alert Noise And Escalation AuditUse when a task involves auditing alert volume, deduplication, severity, and escalation in an IoT operations workflow to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform producti...Votes: 0GitHub stars: 2
- Iot Camera Fleet Credential Rotation PlanUse when a task involves planning credential rotation for a managed camera fleet to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform production, financial, device-control, deploy...Votes: 0GitHub stars: 2
- Iot Camera Storage And Retention BudgetUse when a task involves estimating storage for authorized camera streams and event clips to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform production, financial, device-contro...Votes: 0GitHub stars: 2
- Iot Device Certificate Lifecycle ReviewUse when a task involves reviewing certificate enrollment, renewal, revocation, and expiry handling for IoT devices to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform production...Votes: 0GitHub stars: 2
- Iot Device Firmware Rollout Canary PlanUse when a task involves planning a staged firmware update for a heterogeneous IoT fleet to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform production, financial, device-control...Votes: 0GitHub stars: 2
- Iot Device Inventory And Identity AuditUse when a task involves auditing device identity, ownership, and lifecycle records in an IoT fleet to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform production, financial, dev...Votes: 0GitHub stars: 2
- Iot Edge Cloud Failover Test PlanUse when a task involves planning failure tests for edge-to-cloud service dependencies to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform production, financial, device-control, ...Votes: 0GitHub stars: 2
- Iot Gateway Device Onboarding RunbookUse when a task involves planning safe onboarding for sensors or cameras through an IoT gateway to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform production, financial, device-...Votes: 0GitHub stars: 2
- Iot Offline Buffering Replay Integrity ReviewUse when a task involves checking how edge devices buffer and replay events after connectivity loss to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform production, financial, dev...Votes: 0GitHub stars: 2
- Iot Sensor Calibration Drift ReviewUse when a task involves checking whether an IoT sensor's calibration remains valid over field deployment to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform production, financia...Votes: 0GitHub stars: 2
- Iot Telemetry Retention Minimization ReviewUse when a task involves reviewing whether IoT telemetry collection and retention are proportionate to a stated purpose to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform produc...Votes: 0GitHub stars: 2