All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Edge Fleet Fleet Alerts Closeout Handoff LedgerUse when a edge fleet alert aggregation work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the fleet alert quality review 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; repeated symptoms group without hiding distinct device failures and an operator owns each escalation. Use configured search, fetch, read, browser, te...Votes: 0GitHub stars: 2
- Edge Fleet Fleet Alerts Completeness ReconciliationUse when the edge fleet alert aggregation workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the fleet alert quality review 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; repeated symptoms group without hiding distinct device failures and an operator owns each escalation. Use configured search, fetch, rea...Votes: 0GitHub stars: 2
- Edge Fleet Fleet Alerts Exception Triage QueueUse when the edge fleet alert aggregation workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the fleet alert quality review 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; repeated symptoms group without hiding distinct device failures and an operator owns each escalation. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Edge Fleet Fleet Alerts Recovery Readiness DrillUse when the edge fleet alert aggregation workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the fleet alert quality review 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; repeated symptoms group without hiding distinct device failures and an operator owns each escalation. Use configured search, fetch, read,...Votes: 0GitHub stars: 2
- Edge Fleet Fleet Alerts Scenario Sensitivity MatrixUse when the edge fleet alert aggregation team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the fleet alert quality review with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; repeated symptoms group without hiding distinct device failures and an operator owns each escalation. Use configured search, fetch, read, browser, test, a...Votes: 0GitHub stars: 2
- Edge Fleet Fleet Alerts Scope Intake GateUse when a new edge fleet alert aggregation request needs a bounded work scope to produce a scoped intake card for the fleet alert quality review. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; repeated symptoms group without hiding distinct device failures and an operator owns each escalation. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refi...Votes: 0GitHub stars: 2
- Edge Fleet Fleet Alerts Source Provenance LedgerUse when a decision about edge fleet alert aggregation depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the fleet alert quality review. Success means each material claim has a source, version/date, location, and confidence note; repeated symptoms group without hiding distinct device failures and an operator owns each escalation. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized....Votes: 0GitHub stars: 2
- Edge Fleet Fleet Alerts Threshold Rule CheckUse when a edge fleet alert aggregation decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the fleet alert quality review 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; repeated symptoms group without hiding distinct device failures and an operator owns each escalation. Use configured search, fetc...Votes: 0GitHub stars: 2
- Edge Fleet Gateway Translation Approval Evidence PacketUse when a edge gateway protocol translation result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the protocol mapping 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; representative messages preserve value meaning and conversion exceptions are visible. Use configured search, fetch, read, ...Votes: 0GitHub stars: 2
- Edge Fleet Gateway Translation Change Impact TraceUse when a version, rule, source, or stakeholder change may affect edge gateway protocol translation to produce a before/after change record and impact map for the protocol mapping contract. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; representative messages preserve value meaning and conversion exceptions are visible. Use configured search, fetch, read, browser, test, and write capabilities only when rel...Votes: 0GitHub stars: 2
- Edge Fleet Gateway Translation Closeout Handoff LedgerUse when a edge gateway protocol translation work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the protocol mapping 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; representative messages preserve value meaning and conversion exceptions are visible. Use configured search, fetch, read, browser, test, and writ...Votes: 0GitHub stars: 2
- Edge Fleet Gateway Translation Completeness ReconciliationUse when the edge gateway protocol translation workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the protocol mapping 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; representative messages preserve value meaning and conversion exceptions are visible. Use configured search, fetch, read, browser, ...Votes: 0GitHub stars: 2
- Edge Fleet Gateway Translation Exception Triage QueueUse when the edge gateway protocol translation workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the protocol mapping 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; representative messages preserve value meaning and conversion exceptions are visible. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2
- Edge Fleet Gateway Translation Recovery Readiness DrillUse when the edge gateway protocol translation workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the protocol mapping 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; representative messages preserve value meaning and conversion exceptions are visible. Use configured search, fetch, read, browser, te...Votes: 0GitHub stars: 2
- Edge Fleet Gateway Translation Scenario Sensitivity MatrixUse when the edge gateway protocol translation team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the protocol mapping contract with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; representative messages preserve value meaning and conversion exceptions are visible. Use configured search, fetch, read, browser, test, and write cap...Votes: 0GitHub stars: 2
- Edge Fleet Gateway Translation Scope Intake GateUse when a new edge gateway protocol translation request needs a bounded work scope to produce a scoped intake card for the protocol mapping contract. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; representative messages preserve value meaning and conversion exceptions are visible. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to th...Votes: 0GitHub stars: 2
- Edge Fleet Gateway Translation Source Provenance LedgerUse when a decision about edge gateway protocol translation depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the protocol mapping contract. Success means each material claim has a source, version/date, location, and confidence note; representative messages preserve value meaning and conversion exceptions are visible. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evid...Votes: 0GitHub stars: 2
- Edge Fleet Gateway Translation Threshold Rule CheckUse when a edge gateway protocol translation decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the protocol mapping 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; representative messages preserve value meaning and conversion exceptions are visible. Use configured search, fetch, read, bro...Votes: 0GitHub stars: 2
- Edge Fleet Identity Onboarding Approval Evidence PacketUse when a edge-device identity onboarding result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the device identity enrollment 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; each enrolled device maps to an owner and least-privilege identity without exposing secrets. Use configured searc...Votes: 0GitHub stars: 2
- Edge Fleet Identity Onboarding Change Impact TraceUse when a version, rule, source, or stakeholder change may affect edge-device identity onboarding to produce a before/after change record and impact map for the device identity enrollment checklist. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each enrolled device maps to an owner and least-privilege identity without exposing secrets. Use configured search, fetch, read, browser, test, and write capabiliti...Votes: 0GitHub stars: 2
- Edge Fleet Identity Onboarding Closeout Handoff LedgerUse when a edge-device identity onboarding work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the device identity enrollment 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; each enrolled device maps to an owner and least-privilege identity without exposing secrets. Use configured search, fetch, read, browser...Votes: 0GitHub stars: 2
- Edge Fleet Identity Onboarding Completeness ReconciliationUse when the edge-device identity onboarding workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the device identity enrollment 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; each enrolled device maps to an owner and least-privilege identity without exposing secrets. Use configured search, fetch,...Votes: 0GitHub stars: 2
- Edge Fleet Identity Onboarding Exception Triage QueueUse when the edge-device identity onboarding workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the device identity enrollment 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; each enrolled device maps to an owner and least-privilege identity without exposing secrets. Use configured search, fetch, read, browse...Votes: 0GitHub stars: 2
- Edge Fleet Identity Onboarding Recovery Readiness DrillUse when the edge-device identity onboarding workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the device identity enrollment 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; each enrolled device maps to an owner and least-privilege identity without exposing secrets. Use configured search, fetch, r...Votes: 0GitHub stars: 2
- Edge Fleet Identity Onboarding Scenario Sensitivity MatrixUse when the edge-device identity onboarding team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the device identity enrollment checklist with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each enrolled device maps to an owner and least-privilege identity without exposing secrets. Use configured search, fetch, read, browser, tes...Votes: 0GitHub stars: 2
- Edge Fleet Identity Onboarding Scope Intake GateUse when a new edge-device identity onboarding request needs a bounded work scope to produce a scoped intake card for the device identity enrollment checklist. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each enrolled device maps to an owner and least-privilege identity without exposing secrets. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit ...Votes: 0GitHub stars: 2
- Edge Fleet Identity Onboarding Source Provenance LedgerUse when a decision about edge-device identity onboarding depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the device identity enrollment checklist. Success means each material claim has a source, version/date, location, and confidence note; each enrolled device maps to an owner and least-privilege identity without exposing secrets. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authori...Votes: 0GitHub stars: 2
- Edge Fleet Identity Onboarding Threshold Rule CheckUse when a edge-device identity onboarding decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the device identity enrollment 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; each enrolled device maps to an owner and least-privilege identity without exposing secrets. Use configured search, ...Votes: 0GitHub stars: 2
- Edge Fleet Low Power Regression Approval Evidence PacketUse when a edge low-power behavior regression result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the low-power behavior test matrix 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; tests compare equivalent conditions and do not change deployed power controls. Use configured search, fetch, read, b...Votes: 0GitHub stars: 2
- Edge Fleet Low Power Regression Change Impact TraceUse when a version, rule, source, or stakeholder change may affect edge low-power behavior regression to produce a before/after change record and impact map for the low-power behavior test matrix. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; tests compare equivalent conditions and do not change deployed power controls. Use configured search, fetch, read, browser, test, and write capabilities only when rele...Votes: 0GitHub stars: 2
- Edge Fleet Low Power Regression Closeout Handoff LedgerUse when a edge low-power behavior regression work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the low-power behavior test matrix 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; tests compare equivalent conditions and do not change deployed power controls. Use configured search, fetch, read, browser, test, and write...Votes: 0GitHub stars: 2
- Edge Fleet Low Power Regression Completeness ReconciliationUse when the edge low-power behavior regression workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the low-power behavior test matrix 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; tests compare equivalent conditions and do not change deployed power controls. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Edge Fleet Low Power Regression Exception Triage QueueUse when the edge low-power behavior regression workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the low-power behavior test matrix 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; tests compare equivalent conditions and do not change deployed power controls. Use configured search, fetch, read, browser, test, and writ...Votes: 0GitHub stars: 2
- Edge Fleet Low Power Regression Recovery Readiness DrillUse when the edge low-power behavior regression workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the low-power behavior test matrix 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; tests compare equivalent conditions and do not change deployed power controls. Use configured search, fetch, read, browser, tes...Votes: 0GitHub stars: 2
- Edge Fleet Low Power Regression Scenario Sensitivity MatrixUse when the edge low-power behavior regression team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the low-power behavior test matrix with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; tests compare equivalent conditions and do not change deployed power controls. Use configured search, fetch, read, browser, test, and write capa...Votes: 0GitHub stars: 2
- Edge Fleet Low Power Regression Scope Intake GateUse when a new edge low-power behavior regression request needs a bounded work scope to produce a scoped intake card for the low-power behavior test matrix. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; tests compare equivalent conditions and do not change deployed power controls. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to thr...Votes: 0GitHub stars: 2
- Edge Fleet Low Power Regression Source Provenance LedgerUse when a decision about edge low-power behavior regression depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the low-power behavior test matrix. Success means each material claim has a source, version/date, location, and confidence note; tests compare equivalent conditions and do not change deployed power controls. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evide...Votes: 0GitHub stars: 2
- Edge Fleet Low Power Regression Threshold Rule CheckUse when a edge low-power behavior regression decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the low-power behavior test matrix 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; tests compare equivalent conditions and do not change deployed power controls. Use configured search, fetch, read, brow...Votes: 0GitHub stars: 2
- Edge Fleet Offline Replay Approval Evidence PacketUse when a intermittent-connectivity replay integrity result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the offline replay 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; reconnect replay preserves event identity and surfaces conflicts instead of silently overwriting. Use configured...Votes: 0GitHub stars: 2
- Edge Fleet Offline Replay Change Impact TraceUse when a version, rule, source, or stakeholder change may affect intermittent-connectivity replay integrity to produce a before/after change record and impact map for the offline replay test record. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; reconnect replay preserves event identity and surfaces conflicts instead of silently overwriting. Use configured search, fetch, read, browser, test, and write capa...Votes: 0GitHub stars: 2
- Edge Fleet Offline Replay Closeout Handoff LedgerUse when a intermittent-connectivity replay integrity work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the offline replay 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; reconnect replay preserves event identity and surfaces conflicts instead of silently overwriting. Use configured search, fetch, read, b...Votes: 0GitHub stars: 2
- Edge Fleet Offline Replay Completeness ReconciliationUse when the intermittent-connectivity replay integrity workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the offline replay 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; reconnect replay preserves event identity and surfaces conflicts instead of silently overwriting. Use configured search, ...Votes: 0GitHub stars: 2
- Edge Fleet Offline Replay Exception Triage QueueUse when the intermittent-connectivity replay integrity workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the offline replay 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; reconnect replay preserves event identity and surfaces conflicts instead of silently overwriting. Use configured search, fetch, read, ...Votes: 0GitHub stars: 2
- Edge Fleet Offline Replay Recovery Readiness DrillUse when the intermittent-connectivity replay integrity workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the offline replay 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; reconnect replay preserves event identity and surfaces conflicts instead of silently overwriting. Use configured search, fe...Votes: 0GitHub stars: 2
- Edge Fleet Offline Replay Scenario Sensitivity MatrixUse when the intermittent-connectivity replay integrity team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the offline replay test record with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; reconnect replay preserves event identity and surfaces conflicts instead of silently overwriting. Use configured search, fetch, read, browse...Votes: 0GitHub stars: 2
- Edge Fleet Offline Replay Scope Intake GateUse when a new intermittent-connectivity replay integrity request needs a bounded work scope to produce a scoped intake card for the offline replay test record. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; reconnect replay preserves event identity and surfaces conflicts instead of silently overwriting. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, ...Votes: 0GitHub stars: 2
- Edge Fleet Offline Replay Source Provenance LedgerUse when a decision about intermittent-connectivity replay integrity depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the offline replay test record. Success means each material claim has a source, version/date, location, and confidence note; reconnect replay preserves event identity and surfaces conflicts instead of silently overwriting. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and a...Votes: 0GitHub stars: 2
- Edge Fleet Offline Replay Threshold Rule CheckUse when a intermittent-connectivity replay integrity decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the offline replay 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; reconnect replay preserves event identity and surfaces conflicts instead of silently overwriting. Use configured se...Votes: 0GitHub stars: 2
- Edge Fleet Ota Recovery Approval Evidence PacketUse when a edge update recovery readiness result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the update recovery drill 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 staged device returns to a known test state without contacting live fleet endpoints. Use configured search, fetch, rea...Votes: 0GitHub stars: 2
- Edge Fleet Ota Recovery Change Impact TraceUse when a version, rule, source, or stakeholder change may affect edge update recovery readiness to produce a before/after change record and impact map for the update recovery drill record. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; 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 ...Votes: 0GitHub stars: 2