All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Stem Lab Bench Safety Threshold Rule CheckUse when a supervised low-voltage lab readiness decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the lab-safety preflight 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; all safety responsibilities are assigned and live energization remains instructor-controlled. Use configured search, fetch, rea...Votes: 0GitHub stars: 2
- Stem Lab Lab Access Approval Evidence PacketUse when a SoC lab tool and station access readiness result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the lab station access 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 learner group has an approved station and access route without sharing credentials. Use configured search, fetch...Votes: 0GitHub stars: 2
- Stem Lab Lab Access Change Impact TraceUse when a version, rule, source, or stakeholder change may affect SoC lab tool and station access readiness to produce a before/after change record and impact map for the lab station access map. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each learner group has an approved station and access route without sharing credentials. Use configured search, fetch, read, browser, test, and write capabilities only ...Votes: 0GitHub stars: 2
- Stem Lab Lab Access Closeout Handoff LedgerUse when a SoC lab tool and station access readiness work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the lab station access 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 learner group has an approved station and access route without sharing credentials. Use configured search, fetch, read, browser, test, ...Votes: 0GitHub stars: 2
- Stem Lab Lab Access Completeness ReconciliationUse when the SoC lab tool and station access readiness workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the lab station access 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 learner group has an approved station and access route without sharing credentials. Use configured search, fetch, read, b...Votes: 0GitHub stars: 2
- Stem Lab Lab Access Exception Triage QueueUse when the SoC lab tool and station access readiness workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the lab station access 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 learner group has an approved station and access route without sharing credentials. Use configured search, fetch, read, browser, test,...Votes: 0GitHub stars: 2
- Stem Lab Lab Access Recovery Readiness DrillUse when the SoC lab tool and station access readiness workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the lab station access 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 learner group has an approved station and access route without sharing credentials. Use configured search, fetch, read, bro...Votes: 0GitHub stars: 2
- Stem Lab Lab Access Scenario Sensitivity MatrixUse when the SoC lab tool and station access readiness team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the lab station access map with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each learner group has an approved station and access route without sharing credentials. Use configured search, fetch, read, browser, test, and w...Votes: 0GitHub stars: 2
- Stem Lab Lab Access Scope Intake GateUse when a new SoC lab tool and station access readiness request needs a bounded work scope to produce a scoped intake card for the lab station access map. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each learner group has an approved station and access route without sharing credentials. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refineme...Votes: 0GitHub stars: 2
- Stem Lab Lab Access Source Provenance LedgerUse when a decision about SoC lab tool and station access readiness depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the lab station access map. Success means each material claim has a source, version/date, location, and confidence note; each learner group has an approved station and access route without sharing credentials. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Rec...Votes: 0GitHub stars: 2
- Stem Lab Lab Access Threshold Rule CheckUse when a SoC lab tool and station access readiness decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the lab station access 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 learner group has an approved station and access route without sharing credentials. Use configured search, fetch, r...Votes: 0GitHub stars: 2
- Stem Lab Lab Objective Approval Evidence PacketUse when a hardware lab objective design result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the measurable lab objective card 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 objective maps to an observable artifact without requiring unapproved hardware changes. Use configured search, fetch,...Votes: 0GitHub stars: 2
- Stem Lab Lab Objective Change Impact TraceUse when a version, rule, source, or stakeholder change may affect hardware lab objective design to produce a before/after change record and impact map for the measurable lab objective card. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each objective maps to an observable artifact without requiring unapproved hardware changes. Use configured search, fetch, read, browser, test, and write capabilities only w...Votes: 0GitHub stars: 2
- Stem Lab Lab Objective Closeout Handoff LedgerUse when a hardware lab objective design work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the measurable lab objective card 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 objective maps to an observable artifact without requiring unapproved hardware changes. Use configured search, fetch, read, browser, test, a...Votes: 0GitHub stars: 2
- Stem Lab Lab Objective Completeness ReconciliationUse when the hardware lab objective design workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the measurable lab objective card 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 objective maps to an observable artifact without requiring unapproved hardware changes. Use configured search, fetch, read, br...Votes: 0GitHub stars: 2
- Stem Lab Lab Objective Exception Triage QueueUse when the hardware lab objective design workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the measurable lab objective card 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 objective maps to an observable artifact without requiring unapproved hardware changes. Use configured search, fetch, read, browser, test, ...Votes: 0GitHub stars: 2
- Stem Lab Lab Objective Recovery Readiness DrillUse when the hardware lab objective design workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the measurable lab objective card 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 objective maps to an observable artifact without requiring unapproved hardware changes. Use configured search, fetch, read, brow...Votes: 0GitHub stars: 2
- Stem Lab Lab Objective Scenario Sensitivity MatrixUse when the hardware lab objective design team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the measurable lab objective card with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each objective maps to an observable artifact without requiring unapproved hardware changes. Use configured search, fetch, read, browser, test, and wr...Votes: 0GitHub stars: 2
- Stem Lab Lab Objective Scope Intake GateUse when a new hardware lab objective design request needs a bounded work scope to produce a scoped intake card for the measurable lab objective card. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each objective maps to an observable artifact without requiring unapproved hardware changes. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinemen...Votes: 0GitHub stars: 2
- Stem Lab Lab Objective Source Provenance LedgerUse when a decision about hardware lab objective design depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the measurable lab objective card. Success means each material claim has a source, version/date, location, and confidence note; each objective maps to an observable artifact without requiring unapproved hardware changes. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Reco...Votes: 0GitHub stars: 2
- Stem Lab Lab Objective Threshold Rule CheckUse when a hardware lab objective design decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the measurable lab objective card 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 objective maps to an observable artifact without requiring unapproved hardware changes. Use configured search, fetch, re...Votes: 0GitHub stars: 2
- Stem Lab Prerequisite Map Approval Evidence PacketUse when a digital-systems prerequisite mapping result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the prerequisite-to-lab 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; every lab has a reachable prerequisite path or an explicitly named preparation activity. Use configured search, fetch, re...Votes: 0GitHub stars: 2
- Stem Lab Prerequisite Map Change Impact TraceUse when a version, rule, source, or stakeholder change may affect digital-systems prerequisite mapping to produce a before/after change record and impact map for the prerequisite-to-lab map. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; every lab has a reachable prerequisite path or an explicitly named preparation activity. Use configured search, fetch, read, browser, test, and write capabilities only when...Votes: 0GitHub stars: 2
- Stem Lab Prerequisite Map Closeout Handoff LedgerUse when a digital-systems prerequisite mapping work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the prerequisite-to-lab 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; every lab has a reachable prerequisite path or an explicitly named preparation activity. Use configured search, fetch, read, browser, test, and ...Votes: 0GitHub stars: 2
- Stem Lab Prerequisite Map Completeness ReconciliationUse when the digital-systems prerequisite mapping workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the prerequisite-to-lab 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; every lab has a reachable prerequisite path or an explicitly named preparation activity. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2
- Stem Lab Prerequisite Map Exception Triage QueueUse when the digital-systems prerequisite mapping workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the prerequisite-to-lab 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; every lab has a reachable prerequisite path or an explicitly named preparation activity. Use configured search, fetch, read, browser, test, and...Votes: 0GitHub stars: 2
- Stem Lab Prerequisite Map Recovery Readiness DrillUse when the digital-systems prerequisite mapping workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the prerequisite-to-lab 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; every lab has a reachable prerequisite path or an explicitly named preparation activity. Use configured search, fetch, read, browser...Votes: 0GitHub stars: 2
- Stem Lab Prerequisite Map Scenario Sensitivity MatrixUse when the digital-systems prerequisite mapping team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the prerequisite-to-lab map with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; every lab has a reachable prerequisite path or an explicitly named preparation activity. Use configured search, fetch, read, browser, test, and write...Votes: 0GitHub stars: 2
- Stem Lab Prerequisite Map Scope Intake GateUse when a new digital-systems prerequisite mapping request needs a bounded work scope to produce a scoped intake card for the prerequisite-to-lab map. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; every lab has a reachable prerequisite path or an explicitly named preparation activity. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement t...Votes: 0GitHub stars: 2
- Stem Lab Prerequisite Map Source Provenance LedgerUse when a decision about digital-systems prerequisite mapping depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the prerequisite-to-lab map. Success means each material claim has a source, version/date, location, and confidence note; every lab has a reachable prerequisite path or an explicitly named preparation activity. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record ...Votes: 0GitHub stars: 2
- Stem Lab Prerequisite Map Threshold Rule CheckUse when a digital-systems prerequisite mapping decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the prerequisite-to-lab 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; every lab has a reachable prerequisite path or an explicitly named preparation activity. Use configured search, fetch, read,...Votes: 0GitHub stars: 2
- Stem Lab Simulation Exercise Approval Evidence PacketUse when a digital logic simulation exercise design result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the simulation exercise and check set 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 expected behavior is independently checked and student evidence targets the stated concept. Use configu...Votes: 0GitHub stars: 2
- Stem Lab Simulation Exercise Change Impact TraceUse when a version, rule, source, or stakeholder change may affect digital logic simulation exercise design to produce a before/after change record and impact map for the simulation exercise and check set. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the expected behavior is independently checked and student evidence targets the stated concept. Use configured search, fetch, read, browser, test, and write c...Votes: 0GitHub stars: 2
- Stem Lab Simulation Exercise Closeout Handoff LedgerUse when a digital logic simulation exercise design work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the simulation exercise and check set 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 expected behavior is independently checked and student evidence targets the stated concept. Use configured search, fetch, read...Votes: 0GitHub stars: 2
- Stem Lab Simulation Exercise Completeness ReconciliationUse when the digital logic simulation exercise design workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the simulation exercise and check set 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 expected behavior is independently checked and student evidence targets the stated concept. Use configured searc...Votes: 0GitHub stars: 2
- Stem Lab Simulation Exercise Exception Triage QueueUse when the digital logic simulation exercise design workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the simulation exercise and check set 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 expected behavior is independently checked and student evidence targets the stated concept. Use configured search, fetch, rea...Votes: 0GitHub stars: 2
- Stem Lab Simulation Exercise Recovery Readiness DrillUse when the digital logic simulation exercise design workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the simulation exercise and check set 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 expected behavior is independently checked and student evidence targets the stated concept. Use configured search,...Votes: 0GitHub stars: 2
- Stem Lab Simulation Exercise Scenario Sensitivity MatrixUse when the digital logic simulation exercise design team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the simulation exercise and check set with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the expected behavior is independently checked and student evidence targets the stated concept. Use configured search, fetch, read, bro...Votes: 0GitHub stars: 2
- Stem Lab Simulation Exercise Scope Intake GateUse when a new digital logic simulation exercise design request needs a bounded work scope to produce a scoped intake card for the simulation exercise and check set. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; the expected behavior is independently checked and student evidence targets the stated concept. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidenc...Votes: 0GitHub stars: 2
- Stem Lab Simulation Exercise Source Provenance LedgerUse when a decision about digital logic simulation exercise design depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the simulation exercise and check set. Success means each material claim has a source, version/date, location, and confidence note; the expected behavior is independently checked and student evidence targets the stated concept. Use configured search, fetch, read, browser, test, and write capabilities only when relevant an...Votes: 0GitHub stars: 2
- Stem Lab Simulation Exercise Threshold Rule CheckUse when a digital logic simulation exercise design decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the simulation exercise and check set 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 expected behavior is independently checked and student evidence targets the stated concept. Use configured...Votes: 0GitHub stars: 2
- Stem Lab Team Capstone Approval Evidence PacketUse when a systems-design team capstone evidence result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the team capstone evidence board 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; technical claims map to a saved artifact and individual contributions are not inferred from activity counts. Use co...Votes: 0GitHub stars: 2
- Stem Lab Team Capstone Change Impact TraceUse when a version, rule, source, or stakeholder change may affect systems-design team capstone evidence to produce a before/after change record and impact map for the team capstone evidence board. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; technical claims map to a saved artifact and individual contributions are not inferred from activity counts. Use configured search, fetch, read, browser, test, and wr...Votes: 0GitHub stars: 2
- Stem Lab Team Capstone Closeout Handoff LedgerUse when a systems-design team capstone evidence work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the team capstone evidence board 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; technical claims map to a saved artifact and individual contributions are not inferred from activity counts. Use configured search, fetch,...Votes: 0GitHub stars: 2
- Stem Lab Team Capstone Completeness ReconciliationUse when the systems-design team capstone evidence workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the team capstone evidence board 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; technical claims map to a saved artifact and individual contributions are not inferred from activity counts. Use configured ...Votes: 0GitHub stars: 2
- Stem Lab Team Capstone Exception Triage QueueUse when the systems-design team capstone evidence workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the team capstone evidence board 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; technical claims map to a saved artifact and individual contributions are not inferred from activity counts. Use configured search, fetch...Votes: 0GitHub stars: 2
- Stem Lab Team Capstone Recovery Readiness DrillUse when the systems-design team capstone evidence workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the team capstone evidence board 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; technical claims map to a saved artifact and individual contributions are not inferred from activity counts. Use configured se...Votes: 0GitHub stars: 2
- Stem Lab Team Capstone Scenario Sensitivity MatrixUse when the systems-design team capstone evidence team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the team capstone evidence board with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; technical claims map to a saved artifact and individual contributions are not inferred from activity counts. Use configured search, fetch, read...Votes: 0GitHub stars: 2
- Stem Lab Team Capstone Scope Intake GateUse when a new systems-design team capstone evidence request needs a bounded work scope to produce a scoped intake card for the team capstone evidence board. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; technical claims map to a saved artifact and individual contributions are not inferred from activity counts. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record ev...Votes: 0GitHub stars: 2
- Stem Lab Team Capstone Source Provenance LedgerUse when a decision about systems-design team capstone evidence depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the team capstone evidence board. Success means each material claim has a source, version/date, location, and confidence note; technical claims map to a saved artifact and individual contributions are not inferred from activity counts. Use configured search, fetch, read, browser, test, and write capabilities only when releva...Votes: 0GitHub stars: 2