All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Energy Ops Procurement Change Impact TraceUse when a version, rule, source, or stakeholder change may affect energy supply procurement to produce a before/after change record and impact map for the energy request-for-proposal comparison. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; offers are normalized to comparable terms and no bid is accepted or negotiated by the agent. Use configured search, fetch, read, browser, test, and write capabilities o...Votes: 0GitHub stars: 2
- Energy Ops Procurement Closeout Handoff LedgerUse when a energy supply procurement work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the energy request-for-proposal comparison 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; offers are normalized to comparable terms and no bid is accepted or negotiated by the agent. Use configured search, fetch, read, browser, te...Votes: 0GitHub stars: 2
- Energy Ops Procurement Completeness ReconciliationUse when the energy supply procurement workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the energy request-for-proposal comparison 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; offers are normalized to comparable terms and no bid is accepted or negotiated by the agent. Use configured search, fetch, rea...Votes: 0GitHub stars: 2
- Energy Ops Procurement Exception Triage QueueUse when the energy supply procurement workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the energy request-for-proposal comparison 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; offers are normalized to comparable terms and no bid is accepted or negotiated by the agent. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Energy Ops Procurement Recovery Readiness DrillUse when the energy supply procurement workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the energy request-for-proposal comparison 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; offers are normalized to comparable terms and no bid is accepted or negotiated by the agent. Use configured search, fetch, read,...Votes: 0GitHub stars: 2
- Energy Ops Procurement Scenario Sensitivity MatrixUse when the energy supply procurement team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the energy request-for-proposal comparison with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; offers are normalized to comparable terms and no bid is accepted or negotiated by the agent. Use configured search, fetch, read, browser, test, a...Votes: 0GitHub stars: 2
- Energy Ops Procurement Scope Intake GateUse when a new energy supply procurement request needs a bounded work scope to produce a scoped intake card for the energy request-for-proposal comparison. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; offers are normalized to comparable terms and no bid is accepted or negotiated by the agent. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refi...Votes: 0GitHub stars: 2
- Energy Ops Procurement Source Provenance LedgerUse when a decision about energy supply procurement depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the energy request-for-proposal comparison. Success means each material claim has a source, version/date, location, and confidence note; offers are normalized to comparable terms and no bid is accepted or negotiated by the agent. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized....Votes: 0GitHub stars: 2
- Energy Ops Procurement Threshold Rule CheckUse when a energy supply procurement decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the energy request-for-proposal comparison 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; offers are normalized to comparable terms and no bid is accepted or negotiated by the agent. Use configured search, fetc...Votes: 0GitHub stars: 2
- Energy Ops Renewable Contract Approval Evidence PacketUse when a renewable power-purchase agreement review result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the renewable contract comparison brief 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 modeled case states source dates and contract or legal conclusions are left to qualified reviewers...Votes: 0GitHub stars: 2
- Energy Ops Renewable Contract Change Impact TraceUse when a version, rule, source, or stakeholder change may affect renewable power-purchase agreement review to produce a before/after change record and impact map for the renewable contract comparison brief. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; every modeled case states source dates and contract or legal conclusions are left to qualified reviewers. Use configured search, fetch, read, browser, test...Votes: 0GitHub stars: 2
- Energy Ops Renewable Contract Closeout Handoff LedgerUse when a renewable power-purchase agreement review work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the renewable contract comparison brief 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 modeled case states source dates and contract or legal conclusions are left to qualified reviewers. Use configured search...Votes: 0GitHub stars: 2
- Energy Ops Renewable Contract Completeness ReconciliationUse when the renewable power-purchase agreement review workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the renewable contract comparison brief 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 modeled case states source dates and contract or legal conclusions are left to qualified reviewers. Use con...Votes: 0GitHub stars: 2
- Energy Ops Renewable Contract Exception Triage QueueUse when the renewable power-purchase agreement review workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the renewable contract comparison brief 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 modeled case states source dates and contract or legal conclusions are left to qualified reviewers. Use configured searc...Votes: 0GitHub stars: 2
- Energy Ops Renewable Contract Recovery Readiness DrillUse when the renewable power-purchase agreement review workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the renewable contract comparison brief 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 modeled case states source dates and contract or legal conclusions are left to qualified reviewers. Use confi...Votes: 0GitHub stars: 2
- Energy Ops Renewable Contract Scenario Sensitivity MatrixUse when the renewable power-purchase agreement review team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the renewable contract comparison brief with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; every modeled case states source dates and contract or legal conclusions are left to qualified reviewers. Use configured search, fet...Votes: 0GitHub stars: 2
- Energy Ops Renewable Contract Scope Intake GateUse when a new renewable power-purchase agreement review request needs a bounded work scope to produce a scoped intake card for the renewable contract comparison brief. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; every modeled case states source dates and contract or legal conclusions are left to qualified reviewers. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. R...Votes: 0GitHub stars: 2
- Energy Ops Renewable Contract Source Provenance LedgerUse when a decision about renewable power-purchase agreement review depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the renewable contract comparison brief. Success means each material claim has a source, version/date, location, and confidence note; every modeled case states source dates and contract or legal conclusions are left to qualified reviewers. Use configured search, fetch, read, browser, test, and write capabilities only whe...Votes: 0GitHub stars: 2
- Energy Ops Renewable Contract Threshold Rule CheckUse when a renewable power-purchase agreement review decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the renewable contract comparison brief 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 modeled case states source dates and contract or legal conclusions are left to qualified reviewers. U...Votes: 0GitHub stars: 2
- Energy Ops Storage Approval Evidence PacketUse when a energy storage project evaluation result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the storage scenario worksheet 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; performance assumptions remain within cited evidence and live dispatch is outside scope. Use configured search, fetch, re...Votes: 0GitHub stars: 2
- Energy Ops Storage Change Impact TraceUse when a version, rule, source, or stakeholder change may affect energy storage project evaluation to produce a before/after change record and impact map for the storage scenario worksheet. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; performance assumptions remain within cited evidence and live dispatch is outside scope. Use configured search, fetch, read, browser, test, and write capabilities only when...Votes: 0GitHub stars: 2
- Energy Ops Storage Closeout Handoff LedgerUse when a energy storage project evaluation work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the storage scenario worksheet 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; performance assumptions remain within cited evidence and live dispatch is outside scope. Use configured search, fetch, read, browser, test, and ...Votes: 0GitHub stars: 2
- Energy Ops Storage Completeness ReconciliationUse when the energy storage project evaluation workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the storage scenario worksheet 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; performance assumptions remain within cited evidence and live dispatch is outside scope. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2
- Energy Ops Storage Exception Triage QueueUse when the energy storage project evaluation workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the storage scenario worksheet 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; performance assumptions remain within cited evidence and live dispatch is outside scope. Use configured search, fetch, read, browser, test, and...Votes: 0GitHub stars: 2
- Energy Ops Storage Recovery Readiness DrillUse when the energy storage project evaluation workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the storage scenario worksheet 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; performance assumptions remain within cited evidence and live dispatch is outside scope. Use configured search, fetch, read, browser...Votes: 0GitHub stars: 2
- Energy Ops Storage Scenario Sensitivity MatrixUse when the energy storage project evaluation team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the storage scenario worksheet with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; performance assumptions remain within cited evidence and live dispatch is outside scope. Use configured search, fetch, read, browser, test, and write...Votes: 0GitHub stars: 2
- Energy Ops Storage Scope Intake GateUse when a new energy storage project evaluation request needs a bounded work scope to produce a scoped intake card for the storage scenario worksheet. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; performance assumptions remain within cited evidence and live dispatch is outside scope. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement t...Votes: 0GitHub stars: 2
- Energy Ops Storage Source Provenance LedgerUse when a decision about energy storage project evaluation depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the storage scenario worksheet. Success means each material claim has a source, version/date, location, and confidence note; performance assumptions remain within cited evidence and live dispatch is outside scope. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record ...Votes: 0GitHub stars: 2
- Energy Ops Storage Threshold Rule CheckUse when a energy storage project evaluation decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the storage scenario worksheet 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; performance assumptions remain within cited evidence and live dispatch is outside scope. Use configured search, fetch, read,...Votes: 0GitHub stars: 2
- Energy Ops Utility Bill Approval Evidence PacketUse when a utility bill and tariff analysis result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the utility-bill variance worksheet 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; units and periods reconcile to source documents and proposed tariff changes remain review-only. Use configured search...Votes: 0GitHub stars: 2
- Energy Ops Utility Bill Change Impact TraceUse when a version, rule, source, or stakeholder change may affect utility bill and tariff analysis to produce a before/after change record and impact map for the utility-bill variance worksheet. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; units and periods reconcile to source documents and proposed tariff changes remain review-only. Use configured search, fetch, read, browser, test, and write capabilitie...Votes: 0GitHub stars: 2
- Energy Ops Utility Bill Closeout Handoff LedgerUse when a utility bill and tariff analysis work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the utility-bill variance worksheet 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; units and periods reconcile to source documents and proposed tariff changes remain review-only. Use configured search, fetch, read, browser,...Votes: 0GitHub stars: 2
- Energy Ops Utility Bill Completeness ReconciliationUse when the utility bill and tariff analysis workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the utility-bill variance worksheet 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; units and periods reconcile to source documents and proposed tariff changes remain review-only. Use configured search, fetch, ...Votes: 0GitHub stars: 2
- Energy Ops Utility Bill Exception Triage QueueUse when the utility bill and tariff analysis workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the utility-bill variance worksheet 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; units and periods reconcile to source documents and proposed tariff changes remain review-only. Use configured search, fetch, read, browser...Votes: 0GitHub stars: 2
- Energy Ops Utility Bill Recovery Readiness DrillUse when the utility bill and tariff analysis workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the utility-bill variance worksheet 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; units and periods reconcile to source documents and proposed tariff changes remain review-only. Use configured search, fetch, re...Votes: 0GitHub stars: 2
- Energy Ops Utility Bill Scenario Sensitivity MatrixUse when the utility bill and tariff analysis team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the utility-bill variance worksheet with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; units and periods reconcile to source documents and proposed tariff changes remain review-only. Use configured search, fetch, read, browser, test...Votes: 0GitHub stars: 2
- Energy Ops Utility Bill Scope Intake GateUse when a new utility bill and tariff analysis request needs a bounded work scope to produce a scoped intake card for the utility-bill variance worksheet. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; units and periods reconcile to source documents and proposed tariff changes remain review-only. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit r...Votes: 0GitHub stars: 2
- Energy Ops Utility Bill Source Provenance LedgerUse when a decision about utility bill and tariff analysis depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the utility-bill variance worksheet. Success means each material claim has a source, version/date, location, and confidence note; units and periods reconcile to source documents and proposed tariff changes remain review-only. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authoriz...Votes: 0GitHub stars: 2
- Energy Ops Utility Bill Threshold Rule CheckUse when a utility bill and tariff analysis decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the utility-bill variance worksheet 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; units and periods reconcile to source documents and proposed tariff changes remain review-only. Use configured search, f...Votes: 0GitHub stars: 2
- Energy Ops Utility Reliability Approval Evidence PacketUse when a utility reliability and outage coordination result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the outage coordination status sheet 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; unverified restoration times are labeled and only the utility or site operator confirms operational statu...Votes: 0GitHub stars: 2
- Energy Ops Utility Reliability Change Impact TraceUse when a version, rule, source, or stakeholder change may affect utility reliability and outage coordination to produce a before/after change record and impact map for the outage coordination status sheet. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; unverified restoration times are labeled and only the utility or site operator confirms operational status. Use configured search, fetch, read, browser, tes...Votes: 0GitHub stars: 2
- Energy Ops Utility Reliability Closeout Handoff LedgerUse when a utility reliability and outage coordination work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the outage coordination status sheet 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; unverified restoration times are labeled and only the utility or site operator confirms operational status. Use configured searc...Votes: 0GitHub stars: 2
- Energy Ops Utility Reliability Completeness ReconciliationUse when the utility reliability and outage coordination workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the outage coordination status sheet 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; unverified restoration times are labeled and only the utility or site operator confirms operational status. Use co...Votes: 0GitHub stars: 2
- Energy Ops Utility Reliability Exception Triage QueueUse when the utility reliability and outage coordination workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the outage coordination status sheet 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; unverified restoration times are labeled and only the utility or site operator confirms operational status. Use configured sear...Votes: 0GitHub stars: 2
- Energy Ops Utility Reliability Recovery Readiness DrillUse when the utility reliability and outage coordination workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the outage coordination status sheet 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; unverified restoration times are labeled and only the utility or site operator confirms operational status. Use conf...Votes: 0GitHub stars: 2
- Energy Ops Utility Reliability Scenario Sensitivity MatrixUse when the utility reliability and outage coordination team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the outage coordination status sheet with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; unverified restoration times are labeled and only the utility or site operator confirms operational status. Use configured search, fe...Votes: 0GitHub stars: 2
- Energy Ops Utility Reliability Scope Intake GateUse when a new utility reliability and outage coordination request needs a bounded work scope to produce a scoped intake card for the outage coordination status sheet. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; unverified restoration times are labeled and only the utility or site operator confirms operational status. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. ...Votes: 0GitHub stars: 2
- Energy Ops Utility Reliability Source Provenance LedgerUse when a decision about utility reliability and outage coordination depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the outage coordination status sheet. Success means each material claim has a source, version/date, location, and confidence note; unverified restoration times are labeled and only the utility or site operator confirms operational status. Use configured search, fetch, read, browser, test, and write capabilities only wh...Votes: 0GitHub stars: 2
- Energy Ops Utility Reliability Threshold Rule CheckUse when a utility reliability and outage coordination decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the outage coordination status sheet 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; unverified restoration times are labeled and only the utility or site operator confirms operational status. ...Votes: 0GitHub stars: 2
- Finite Difference Grid ConvergenceUse when a task involves testing a finite-difference solution as spatial resolution changes to define the target, lifecycle stage, controlling artifact, authoritative evidence, version or operating conditions, sensitivity, and approval boundary before applying the method. Separate observed facts from assumptions and model output. Verify the result with appropriate independent checks, preserve provenance, and report uncertainty and limitations. Do not perform production, financial, hardware-co...Votes: 0GitHub stars: 2