All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Energy Ops Demand Response Change Impact TraceUse when a version, rule, source, or stakeholder change may affect demand response readiness to produce a before/after change record and impact map for the demand-response readiness checklist. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; all assumed controllable load has an owner and a safe non-participation path. Use configured search, fetch, read, browser, test, and write capabilities only when relevant ...Votes: 0GitHub stars: 2
- Energy Ops Demand Response Closeout Handoff LedgerUse when a demand response readiness work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the demand-response readiness 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; all assumed controllable load has an owner and a safe non-participation path. Use configured search, fetch, read, browser, test, and write capa...Votes: 0GitHub stars: 2
- Energy Ops Demand Response Completeness ReconciliationUse when the demand response readiness workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the demand-response readiness 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; all assumed controllable load has an owner and a safe non-participation path. Use configured search, fetch, read, browser, test, ...Votes: 0GitHub stars: 2
- Energy Ops Demand Response Exception Triage QueueUse when the demand response readiness workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the demand-response readiness 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; all assumed controllable load has an owner and a safe non-participation path. Use configured search, fetch, read, browser, test, and write cap...Votes: 0GitHub stars: 2
- Energy Ops Demand Response Recovery Readiness DrillUse when the demand response readiness workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the demand-response readiness 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; all assumed controllable load has an owner and a safe non-participation path. Use configured search, fetch, read, browser, test, an...Votes: 0GitHub stars: 2
- Energy Ops Demand Response Scenario Sensitivity MatrixUse when the demand response readiness team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the demand-response readiness checklist with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; all assumed controllable load has an owner and a safe non-participation path. Use configured search, fetch, read, browser, test, and write capabilit...Votes: 0GitHub stars: 2
- Energy Ops Demand Response Scope Intake GateUse when a new demand response readiness request needs a bounded work scope to produce a scoped intake card for the demand-response readiness checklist. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; all assumed controllable load has an owner and a safe non-participation path. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three fo...Votes: 0GitHub stars: 2
- Energy Ops Demand Response Source Provenance LedgerUse when a decision about demand response readiness depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the demand-response readiness checklist. Success means each material claim has a source, version/date, location, and confidence note; all assumed controllable load has an owner and a safe non-participation path. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, ...Votes: 0GitHub stars: 2
- Energy Ops Demand Response Threshold Rule CheckUse when a demand response readiness decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the demand-response readiness 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; all assumed controllable load has an owner and a safe non-participation path. Use configured search, fetch, read, browser, ...Votes: 0GitHub stars: 2
- Energy Ops Efficiency Approval Evidence PacketUse when a facility energy-efficiency project tracking result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the efficiency measure register 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; savings claims are tied to a defined baseline and uncertainty is reported. Use configured search, fetch, read,...Votes: 0GitHub stars: 2
- Energy Ops Efficiency Change Impact TraceUse when a version, rule, source, or stakeholder change may affect facility energy-efficiency project tracking to produce a before/after change record and impact map for the efficiency measure register. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; savings claims are tied to a defined baseline and uncertainty is reported. Use configured search, fetch, read, browser, test, and write capabilities only when re...Votes: 0GitHub stars: 2
- Energy Ops Efficiency Closeout Handoff LedgerUse when a facility energy-efficiency project tracking work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the efficiency measure register 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; savings claims are tied to a defined baseline and uncertainty is reported. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2
- Energy Ops Efficiency Completeness ReconciliationUse when the facility energy-efficiency project tracking workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the efficiency measure register 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; savings claims are tied to a defined baseline and uncertainty is reported. Use configured search, fetch, read, browser,...Votes: 0GitHub stars: 2
- Energy Ops Efficiency Exception Triage QueueUse when the facility energy-efficiency project tracking workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the efficiency measure register 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; savings claims are tied to a defined baseline and uncertainty is reported. Use configured search, fetch, read, browser, test, and wr...Votes: 0GitHub stars: 2
- Energy Ops Efficiency Recovery Readiness DrillUse when the facility energy-efficiency project tracking workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the efficiency measure register 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; savings claims are tied to a defined baseline and uncertainty is reported. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Energy Ops Efficiency Scenario Sensitivity MatrixUse when the facility energy-efficiency project tracking team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the efficiency measure register with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; savings claims are tied to a defined baseline and uncertainty is reported. Use configured search, fetch, read, browser, test, and write ca...Votes: 0GitHub stars: 2
- Energy Ops Efficiency Scope Intake GateUse when a new facility energy-efficiency project tracking request needs a bounded work scope to produce a scoped intake card for the efficiency measure register. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; savings claims are tied to a defined baseline and uncertainty is reported. 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
- Energy Ops Efficiency Source Provenance LedgerUse when a decision about facility energy-efficiency project tracking depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the efficiency measure register. Success means each material claim has a source, version/date, location, and confidence note; savings claims are tied to a defined baseline and uncertainty is reported. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evi...Votes: 0GitHub stars: 2
- Energy Ops Efficiency Threshold Rule CheckUse when a facility energy-efficiency project tracking decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the efficiency measure register 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; savings claims are tied to a defined baseline and uncertainty is reported. Use configured search, fetch, read, br...Votes: 0GitHub stars: 2
- Energy Ops Energy Reporting Approval Evidence PacketUse when a energy and emissions reporting evidence result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the energy reporting evidence ledger 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 reported value traces to a source, period, unit, and factor version. Use configured search, fetch, read,...Votes: 0GitHub stars: 2
- Energy Ops Energy Reporting Change Impact TraceUse when a version, rule, source, or stakeholder change may affect energy and emissions reporting evidence to produce a before/after change record and impact map for the energy reporting evidence ledger. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each reported value traces to a source, period, unit, and factor version. Use configured search, fetch, read, browser, test, and write capabilities only when re...Votes: 0GitHub stars: 2
- Energy Ops Energy Reporting Closeout Handoff LedgerUse when a energy and emissions reporting evidence work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the energy reporting evidence ledger 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 reported value traces to a source, period, unit, and factor version. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2
- Energy Ops Energy Reporting Completeness ReconciliationUse when the energy and emissions reporting evidence workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the energy reporting evidence ledger 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 reported value traces to a source, period, unit, and factor version. Use configured search, fetch, read, browser,...Votes: 0GitHub stars: 2
- Energy Ops Energy Reporting Exception Triage QueueUse when the energy and emissions reporting evidence workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the energy reporting evidence ledger 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 reported value traces to a source, period, unit, and factor version. Use configured search, fetch, read, browser, test, and wr...Votes: 0GitHub stars: 2
- Energy Ops Energy Reporting Recovery Readiness DrillUse when the energy and emissions reporting evidence workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the energy reporting evidence ledger 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 reported value traces to a source, period, unit, and factor version. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Energy Ops Energy Reporting Scenario Sensitivity MatrixUse when the energy and emissions reporting evidence team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the energy reporting evidence ledger with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each reported value traces to a source, period, unit, and factor version. Use configured search, fetch, read, browser, test, and write ca...Votes: 0GitHub stars: 2
- Energy Ops Energy Reporting Scope Intake GateUse when a new energy and emissions reporting evidence request needs a bounded work scope to produce a scoped intake card for the energy reporting evidence ledger. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each reported value traces to a source, period, unit, and factor version. 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
- Energy Ops Energy Reporting Source Provenance LedgerUse when a decision about energy and emissions reporting evidence depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the energy reporting evidence ledger. Success means each material claim has a source, version/date, location, and confidence note; each reported value traces to a source, period, unit, and factor version. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evi...Votes: 0GitHub stars: 2
- Energy Ops Energy Reporting Threshold Rule CheckUse when a energy and emissions reporting evidence decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the energy reporting evidence ledger 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 reported value traces to a source, period, unit, and factor version. Use configured search, fetch, read, br...Votes: 0GitHub stars: 2
- Energy Ops Load Forecast Approval Evidence PacketUse when a facility energy load forecasting result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the load forecast review packet containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; forecast drivers are explicit and a scenario is not presented as a guaranteed demand level. Use configured search, fetch,...Votes: 0GitHub stars: 2
- Energy Ops Load Forecast Change Impact TraceUse when a version, rule, source, or stakeholder change may affect facility energy load forecasting to produce a before/after change record and impact map for the load forecast review packet. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; forecast drivers are explicit and a scenario is not presented as a guaranteed demand level. Use configured search, fetch, read, browser, test, and write capabilities only w...Votes: 0GitHub stars: 2
- Energy Ops Load Forecast Closeout Handoff LedgerUse when a facility energy load forecasting work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the load forecast review packet with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; forecast drivers are explicit and a scenario is not presented as a guaranteed demand level. Use configured search, fetch, read, browser, test, a...Votes: 0GitHub stars: 2
- Energy Ops Load Forecast Completeness ReconciliationUse when the facility energy load forecasting workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the load forecast review packet with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; forecast drivers are explicit and a scenario is not presented as a guaranteed demand level. Use configured search, fetch, read, br...Votes: 0GitHub stars: 2
- Energy Ops Load Forecast Exception Triage QueueUse when the facility energy load forecasting workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the load forecast review packet with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; forecast drivers are explicit and a scenario is not presented as a guaranteed demand level. Use configured search, fetch, read, browser, test, ...Votes: 0GitHub stars: 2
- Energy Ops Load Forecast Recovery Readiness DrillUse when the facility energy load forecasting workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the load forecast review packet with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; forecast drivers are explicit and a scenario is not presented as a guaranteed demand level. Use configured search, fetch, read, brow...Votes: 0GitHub stars: 2
- Energy Ops Load Forecast Scenario Sensitivity MatrixUse when the facility energy load forecasting team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the load forecast review packet with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; forecast drivers are explicit and a scenario is not presented as a guaranteed demand level. Use configured search, fetch, read, browser, test, and wr...Votes: 0GitHub stars: 2
- Energy Ops Load Forecast Scope Intake GateUse when a new facility energy load forecasting request needs a bounded work scope to produce a scoped intake card for the load forecast review packet. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; forecast drivers are explicit and a scenario is not presented as a guaranteed demand level. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinemen...Votes: 0GitHub stars: 2
- Energy Ops Load Forecast Source Provenance LedgerUse when a decision about facility energy load forecasting depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the load forecast review packet. Success means each material claim has a source, version/date, location, and confidence note; forecast drivers are explicit and a scenario is not presented as a guaranteed demand level. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Reco...Votes: 0GitHub stars: 2
- Energy Ops Load Forecast Threshold Rule CheckUse when a facility energy load forecasting decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the load forecast review packet showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; forecast drivers are explicit and a scenario is not presented as a guaranteed demand level. Use configured search, fetch, re...Votes: 0GitHub stars: 2
- Energy Ops Onsite Generation Approval Evidence PacketUse when a onsite generation and interconnection planning result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the onsite generation readiness packet containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; each dependency has a named owner and no connection or commissioning approval is inferred. Use confi...Votes: 0GitHub stars: 2
- Energy Ops Onsite Generation Change Impact TraceUse when a version, rule, source, or stakeholder change may affect onsite generation and interconnection planning to produce a before/after change record and impact map for the onsite generation readiness packet. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each dependency has a named owner and no connection or commissioning approval is inferred. Use configured search, fetch, read, browser, test, and write...Votes: 0GitHub stars: 2
- Energy Ops Onsite Generation Closeout Handoff LedgerUse when a onsite generation and interconnection planning work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the onsite generation readiness packet with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; each dependency has a named owner and no connection or commissioning approval is inferred. Use configured search, fetch, re...Votes: 0GitHub stars: 2
- Energy Ops Onsite Generation Completeness ReconciliationUse when the onsite generation and interconnection planning workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the onsite generation readiness packet with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; each dependency has a named owner and no connection or commissioning approval is inferred. Use configured sea...Votes: 0GitHub stars: 2
- Energy Ops Onsite Generation Exception Triage QueueUse when the onsite generation and interconnection planning workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the onsite generation readiness packet with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; each dependency has a named owner and no connection or commissioning approval is inferred. Use configured search, fetch, r...Votes: 0GitHub stars: 2
- Energy Ops Onsite Generation Recovery Readiness DrillUse when the onsite generation and interconnection planning workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the onsite generation readiness packet with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; each dependency has a named owner and no connection or commissioning approval is inferred. Use configured searc...Votes: 0GitHub stars: 2
- Energy Ops Onsite Generation Scenario Sensitivity MatrixUse when the onsite generation and interconnection planning team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the onsite generation readiness packet with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each dependency has a named owner and no connection or commissioning approval is inferred. Use configured search, fetch, read, b...Votes: 0GitHub stars: 2
- Energy Ops Onsite Generation Scope Intake GateUse when a new onsite generation and interconnection planning request needs a bounded work scope to produce a scoped intake card for the onsite generation readiness packet. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each dependency has a named owner and no connection or commissioning approval is inferred. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evide...Votes: 0GitHub stars: 2
- Energy Ops Onsite Generation Source Provenance LedgerUse when a decision about onsite generation and interconnection planning depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the onsite generation readiness packet. Success means each material claim has a source, version/date, location, and confidence note; each dependency has a named owner and no connection or commissioning approval is inferred. Use configured search, fetch, read, browser, test, and write capabilities only when relevant ...Votes: 0GitHub stars: 2
- Energy Ops Onsite Generation Threshold Rule CheckUse when a onsite generation and interconnection planning decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the onsite generation readiness packet showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; each dependency has a named owner and no connection or commissioning approval is inferred. Use configur...Votes: 0GitHub stars: 2
- Energy Ops Procurement Approval Evidence PacketUse when a energy supply procurement result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the energy request-for-proposal comparison 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; offers are normalized to comparable terms and no bid is accepted or negotiated by the agent. Use configured search, f...Votes: 0GitHub stars: 2