All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Built Env Site Threshold Rule CheckUse when a site due diligence decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the site review 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; each constraint is sourced and unresolved items have a qualified reviewer. Use configured search, fetch, read, browser, test, and write capabilitie...Votes: 0GitHub stars: 2
- Adc Dynamic Performance ReviewUse when a task involves reviewing dynamic ADC metrics derived from a sampled waveform 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
- Adc Static Linearity Metric AuditUse when a task involves auditing static converter linearity metrics from code-transition data 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...Votes: 0GitHub stars: 2
- Analog Comparator Regeneration ReviewUse when a task involves reviewing a dynamic comparator for regeneration speed, offset, and kickback 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, ha...Votes: 0GitHub stars: 2
- Analog Ic Topology TradeoffUse when a task involves choosing an analog IC topology from explicit performance and process requirements 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, financi...Votes: 0GitHub stars: 2
- Analog Layout Matching ReviewUse when a task involves reviewing layout choices that affect matching and common-mode rejection 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, hardwa...Votes: 0GitHub stars: 2
- Analog Ldo Load Transient ReviewUse when a task involves evaluating an LDO response to load steps and operating limits 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
- Analog Noise Budget ReviewUse when a task involves reviewing input-referred noise contributions in an analog signal chain 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, hardwar...Votes: 0GitHub stars: 2
- Analog Opamp Loop Stability ReviewUse when a task involves reviewing loop stability and compensation for an analog amplifier 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-con...Votes: 0GitHub stars: 2
- Analog Pll Loop Dynamics ReviewUse when a task involves reviewing a phase-locked loop's acquisition and tracking behavior 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-con...Votes: 0GitHub stars: 2
- Analog Pvt Corner CoverageUse when a task involves planning process, voltage, temperature, and mismatch coverage for an analog design 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, financ...Votes: 0GitHub stars: 2
- Analog Transistor Bias ReviewUse when a task involves reviewing a transistor-level bias plan for an analog 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, d...Votes: 0GitHub stars: 2
- Arm Cortex Expert Capability Surface MapUse when the actual capability boundary of ARM Cortex-M firmware workflows needs to be distinguished from assumptions. Produce a capability map for ARM Cortex-M firmware workflows covering the requested behavior, verified support, exclusions, and unknowns. Success means each in-scope capability is tied to local configuration, a version-matched authoritative reference, or an observed non-production result, and all unknowns remain explicit. The review is bounded to board and silicon revision, p...Votes: 0GitHub stars: 2
- Arm Cortex Expert Change Impact AssessmentUse when a proposed ARM Cortex-M firmware workflows version, setting, schema, model, or integration change may affect existing consumers. Produce a change-impact record for ARM Cortex-M firmware workflows with baseline, affected dependencies, validation needs, and recovery boundary. Success means affected dependencies and compatibility assumptions are evidenced, unknown consumers are named as unknown, and no migration or rollout is implied. The review is bounded to board and silicon revision,...Votes: 0GitHub stars: 2
- Arm Cortex Expert Failure Triage RecordUse when a reproducible ARM Cortex-M firmware workflows symptom needs bounded diagnosis before any corrective change. Produce a failure-triage record for ARM Cortex-M firmware workflows with symptom, environment, evidence, hypothesis, and next safe check. Success means the diagnosis distinguishes observation from inference, each proposed check is reversible and scoped, and unresolved causes remain open. The review is bounded to board and silicon revision, peripheral assumptions, interrupt bou...Votes: 0GitHub stars: 2
- Arm Cortex Expert Input Output ContractUse when the accepted inputs or produced outputs for ARM Cortex-M firmware workflows need a checkable boundary. Produce an input/output contract for ARM Cortex-M firmware workflows with types, required fields, exclusions, and representative approved fixtures. Success means the contract names its source and version, boundary cases are visible, and no private or unapproved payload is needed to explain the result. The review is bounded to board and silicon revision, peripheral assumptions, inter...Votes: 0GitHub stars: 2
- Arm Cortex Expert Integration Parity TraceUse when ARM Cortex-M firmware workflows exchanges state or data with another component and the handoff needs to be verified. Produce an integration-parity trace for ARM Cortex-M firmware workflows showing source, transformation, destination, and observed result. Success means each material field or state transition has a traceable mapping and observed mismatches are separated from assumptions. The review is bounded to board and silicon revision, peripheral assumptions, interrupt boundary, an...Votes: 0GitHub stars: 2
- Arm Cortex Expert Performance EnvelopeUse when ARM Cortex-M firmware workflows must be assessed against a user- or owner-defined latency, memory, throughput, size, or cost budget. Produce a performance-envelope note for ARM Cortex-M firmware workflows with test conditions, baseline, observed range, and limitations. Success means conditions and measurements are reproducible, the comparison uses the stated budget, and limitations or resource costs are visible. The review is bounded to board and silicon revision, peripheral assumpti...Votes: 0GitHub stars: 2
- Arm Cortex Expert Permission Boundary ReviewUse when ARM Cortex-M firmware workflows may read, write, transmit, publish, spend, or administer data or resources. Produce a permission-boundary map for ARM Cortex-M firmware workflows showing identity, requested capability, data scope, and approval gate. Success means every sensitive capability has a named authorization boundary, unnecessary data and privileges are called out, and no action is treated as approved by implication. The review is bounded to board and silicon revision, peripher...Votes: 0GitHub stars: 2
- Arm Cortex Expert Release Handoff RecordUse when a ARM Cortex-M firmware workflows review is ready to be handed to a maintainer or accountable operator. Produce a release-handoff record for ARM Cortex-M firmware workflows with version, evidence, open issues, approval state, and safe next step. Success means the receiver can distinguish verified facts, proposals, approvals, and unknowns, and no publication, deployment, write, or contact is claimed unless independently confirmed. The review is bounded to board and silicon revision, p...Votes: 0GitHub stars: 2
- Arm Cortex Expert Reproducibility Fixture PlanUse when a ARM Cortex-M firmware workflows result must be independently repeated or compared without relying on an uncontrolled live action. Produce a reproducibility plan for ARM Cortex-M firmware workflows defining fixture identity, environment, expected observations, and cleanup boundary. Success means another reviewer can identify the fixture and environment, distinguish expected from observed behavior, and repeat the check without an unapproved external effect. The review is bounded to b...Votes: 0GitHub stars: 2
- Arm Cortex Expert Version CompatibilityUse when a ARM Cortex-M firmware workflows integration or upgrade depends on compatible runtime, client, service, or artifact versions. Produce a version-compatibility record for ARM Cortex-M firmware workflows with exact versions, supported combinations, and open questions. Success means the tested version tuple is explicit, each compatibility claim has a dated source or local result, and unsupported combinations are not presented as working. The review is bounded to board and silicon revisi...Votes: 0GitHub stars: 2
- Bom Component SourcingUse when a task involves preparing a component bill of materials and sourcing plan for an electronics prototype or production run 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 inst...Votes: 0GitHub stars: 2
- Clock Domain Crossing Verification PlanUse when a task involves planning CDC analysis for signals moving between asynchronous or unrelated clocks 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, financi...Votes: 0GitHub stars: 2
- Clock Tree Synthesis Readiness ReviewUse when a task involves checking whether a digital design is ready for clock-tree implementation 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, hardw...Votes: 0GitHub stars: 2
- Constellation Revisit Performance AnalysisUse when a task involves evaluating revisit and coverage claims for a satellite constellation 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-...Votes: 0GitHub stars: 2
- Cubesat Deployable Mechanism Trade ReviewUse when a task involves comparing deployable structures or antennas for a CubeSat mission 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-con...Votes: 0GitHub stars: 2
- Cuda Environment ReproducibilityUse when a task involves capturing a reproducible CUDA development environment across toolkit, driver, libraries, compiler, and hardware to identify the research or operational question, target population or system, relevant version, sensitive data, and approval boundary before acting. Use current primary sources, produce a traceable artifact, and verify it against explicit criteria. Trigger for planning, analysis, review, or troubleshooting in this focused domain; do not execute external wri...Votes: 0GitHub stars: 2
- Edge Fleet Decommissioning Approval Evidence PacketUse when a edge-device decommissioning evidence result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the device retirement 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; retired status is not claimed until access, data, and custody evidence reconcile. Use configured search, fetch, read,...Votes: 0GitHub stars: 2
- Edge Fleet Decommissioning Change Impact TraceUse when a version, rule, source, or stakeholder change may affect edge-device decommissioning evidence to produce a before/after change record and impact map for the device retirement checklist. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; retired status is not claimed until access, data, and custody evidence reconcile. Use configured search, fetch, read, browser, test, and write capabilities only when re...Votes: 0GitHub stars: 2
- Edge Fleet Decommissioning Closeout Handoff LedgerUse when a edge-device decommissioning evidence work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the device retirement 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; retired status is not claimed until access, data, and custody evidence reconcile. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2
- Edge Fleet Decommissioning Completeness ReconciliationUse when the edge-device decommissioning evidence workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the device retirement 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; retired status is not claimed until access, data, and custody evidence reconcile. Use configured search, fetch, read, browser,...Votes: 0GitHub stars: 2
- Edge Fleet Decommissioning Exception Triage QueueUse when the edge-device decommissioning evidence workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the device retirement 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; retired status is not claimed until access, data, and custody evidence reconcile. Use configured search, fetch, read, browser, test, and wr...Votes: 0GitHub stars: 2
- Edge Fleet Decommissioning Recovery Readiness DrillUse when the edge-device decommissioning evidence workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the device retirement 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; retired status is not claimed until access, data, and custody evidence reconcile. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Edge Fleet Decommissioning Scenario Sensitivity MatrixUse when the edge-device decommissioning evidence team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the device retirement checklist with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; retired status is not claimed until access, data, and custody evidence reconcile. Use configured search, fetch, read, browser, test, and write ca...Votes: 0GitHub stars: 2
- Edge Fleet Decommissioning Scope Intake GateUse when a new edge-device decommissioning evidence request needs a bounded work scope to produce a scoped intake card for the device retirement checklist. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; retired status is not claimed until access, data, and custody evidence reconcile. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to t...Votes: 0GitHub stars: 2
- Edge Fleet Decommissioning Source Provenance LedgerUse when a decision about edge-device decommissioning evidence depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the device retirement checklist. Success means each material claim has a source, version/date, location, and confidence note; retired status is not claimed until access, data, and custody evidence reconcile. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evi...Votes: 0GitHub stars: 2
- Edge Fleet Decommissioning Threshold Rule CheckUse when a edge-device decommissioning evidence decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the device retirement 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; retired status is not claimed until access, data, and custody evidence reconcile. Use configured search, fetch, read, br...Votes: 0GitHub stars: 2
- Edge Fleet Firmware Cohort Approval Evidence PacketUse when a firmware cohort planning result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the firmware cohort evidence plan 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 proposed cohort excludes incompatible hardware and remains a plan until approved. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2
- Edge Fleet Firmware Cohort Change Impact TraceUse when a version, rule, source, or stakeholder change may affect firmware cohort planning to produce a before/after change record and impact map for the firmware cohort evidence plan. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the proposed cohort excludes incompatible hardware and remains a plan until approved. Use configured search, fetch, read, browser, test, and write capabilities only when relevant...Votes: 0GitHub stars: 2
- Edge Fleet Firmware Cohort Closeout Handoff LedgerUse when a firmware cohort planning work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the firmware cohort evidence plan 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 proposed cohort excludes incompatible hardware and remains a plan until approved. Use configured search, fetch, read, browser, test, and write cap...Votes: 0GitHub stars: 2
- Edge Fleet Firmware Cohort Completeness ReconciliationUse when the firmware cohort planning workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the firmware cohort evidence plan 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 proposed cohort excludes incompatible hardware and remains a plan until approved. Use configured search, fetch, read, browser, test,...Votes: 0GitHub stars: 2
- Edge Fleet Firmware Cohort Exception Triage QueueUse when the firmware cohort planning workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the firmware cohort evidence plan 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 proposed cohort excludes incompatible hardware and remains a plan until approved. Use configured search, fetch, read, browser, test, and write ca...Votes: 0GitHub stars: 2
- Edge Fleet Firmware Cohort Recovery Readiness DrillUse when the firmware cohort planning workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the firmware cohort evidence plan 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 proposed cohort excludes incompatible hardware and remains a plan until approved. Use configured search, fetch, read, browser, test, a...Votes: 0GitHub stars: 2
- Edge Fleet Firmware Cohort Scenario Sensitivity MatrixUse when the firmware cohort planning team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the firmware cohort evidence plan with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the proposed cohort excludes incompatible hardware and remains a plan until approved. Use configured search, fetch, read, browser, test, and write capabili...Votes: 0GitHub stars: 2
- Edge Fleet Firmware Cohort Scope Intake GateUse when a new firmware cohort planning request needs a bounded work scope to produce a scoped intake card for the firmware cohort evidence plan. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the proposed cohort excludes incompatible hardware and remains a plan until approved. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three f...Votes: 0GitHub stars: 2
- Edge Fleet Firmware Cohort Source Provenance LedgerUse when a decision about firmware cohort planning depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the firmware cohort evidence plan. Success means each material claim has a source, version/date, location, and confidence note; the proposed cohort excludes incompatible hardware and remains a plan until approved. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence,...Votes: 0GitHub stars: 2
- Edge Fleet Firmware Cohort Threshold Rule CheckUse when a firmware cohort planning decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the firmware cohort evidence plan 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 proposed cohort excludes incompatible hardware and remains a plan until approved. Use configured search, fetch, read, browser,...Votes: 0GitHub stars: 2
- Edge Fleet Fleet Alerts Approval Evidence PacketUse when a edge fleet alert aggregation result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the fleet alert quality review 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; repeated symptoms group without hiding distinct device failures and an operator owns each escalation. Use configured search, f...Votes: 0GitHub stars: 2
- Edge Fleet Fleet Alerts Change Impact TraceUse when a version, rule, source, or stakeholder change may affect edge fleet alert aggregation to produce a before/after change record and impact map for the fleet alert quality review. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; repeated symptoms group without hiding distinct device failures and an operator owns each escalation. Use configured search, fetch, read, browser, test, and write capabilities o...Votes: 0GitHub stars: 2