All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Built Env Facilities Threshold Rule CheckUse when a facility operations decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the facility service review showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; work-order status and asset identity reconcile without changing live control settings. Use configured search, fetch, read, browser, test, and...Votes: 0GitHub stars: 2
- Built Env Field Quality Approval Evidence PacketUse when a field quality evidence result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the field observation 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; every observation has traceable location and revision without claiming certification. Use configured search, fetch, read, browser, t...Votes: 0GitHub stars: 2
- Built Env Field Quality Change Impact TraceUse when a version, rule, source, or stakeholder change may affect field quality evidence to produce a before/after change record and impact map for the field observation register. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; every observation has traceable location and revision without claiming certification. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and ...Votes: 0GitHub stars: 2
- Built Env Field Quality Closeout Handoff LedgerUse when a field quality evidence work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the field observation 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; every observation has traceable location and revision without claiming certification. Use configured search, fetch, read, browser, test, and write capabili...Votes: 0GitHub stars: 2
- Built Env Field Quality Completeness ReconciliationUse when the field quality evidence workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the field observation 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; every observation has traceable location and revision without claiming certification. Use configured search, fetch, read, browser, test, and ...Votes: 0GitHub stars: 2
- Built Env Field Quality Exception Triage QueueUse when the field quality evidence workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the field observation 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; every observation has traceable location and revision without claiming certification. Use configured search, fetch, read, browser, test, and write capabil...Votes: 0GitHub stars: 2
- Built Env Field Quality Recovery Readiness DrillUse when the field quality evidence workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the field observation 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; every observation has traceable location and revision without claiming certification. Use configured search, fetch, read, browser, test, and wr...Votes: 0GitHub stars: 2
- Built Env Field Quality Scenario Sensitivity MatrixUse when the field quality evidence team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the field observation register with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; every observation has traceable location and revision without claiming certification. Use configured search, fetch, read, browser, test, and write capabilities ...Votes: 0GitHub stars: 2
- Built Env Field Quality Scope Intake GateUse when a new field quality evidence request needs a bounded work scope to produce a scoped intake card for the field observation register. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; every observation has traceable location and revision without claiming certification. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focuse...Votes: 0GitHub stars: 2
- Built Env Field Quality Source Provenance LedgerUse when a decision about field quality evidence depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the field observation register. Success means each material claim has a source, version/date, location, and confidence note; every observation has traceable location and revision without claiming certification. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limi...Votes: 0GitHub stars: 2
- Built Env Field Quality Threshold Rule CheckUse when a field quality evidence decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the field observation 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; every observation has traceable location and revision without claiming certification. Use configured search, fetch, read, browser, test...Votes: 0GitHub stars: 2
- Built Env Permits Approval Evidence PacketUse when a permit and submittal tracking result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the permit submittal tracker 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 requirement has a current owner and status tied to the correct revision. Use configured search, fetch, read, browser, tes...Votes: 0GitHub stars: 2
- Built Env Permits Change Impact TraceUse when a version, rule, source, or stakeholder change may affect permit and submittal tracking to produce a before/after change record and impact map for the permit submittal tracker. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; every requirement has a current owner and status tied to the correct revision. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and au...Votes: 0GitHub stars: 2
- Built Env Permits Closeout Handoff LedgerUse when a permit and submittal tracking work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the permit submittal tracker 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 requirement has a current owner and status tied to the correct revision. Use configured search, fetch, read, browser, test, and write capabiliti...Votes: 0GitHub stars: 2
- Built Env Permits Completeness ReconciliationUse when the permit and submittal tracking workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the permit submittal tracker 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 requirement has a current owner and status tied to the correct revision. Use configured search, fetch, read, browser, test, and wr...Votes: 0GitHub stars: 2
- Built Env Permits Exception Triage QueueUse when the permit and submittal tracking workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the permit submittal tracker 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 requirement has a current owner and status tied to the correct revision. Use configured search, fetch, read, browser, test, and write capabilit...Votes: 0GitHub stars: 2
- Built Env Permits Recovery Readiness DrillUse when the permit and submittal tracking workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the permit submittal tracker 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 requirement has a current owner and status tied to the correct revision. Use configured search, fetch, read, browser, test, and writ...Votes: 0GitHub stars: 2
- Built Env Permits Scenario Sensitivity MatrixUse when the permit and submittal tracking team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the permit submittal tracker with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; every requirement has a current owner and status tied to the correct revision. Use configured search, fetch, read, browser, test, and write capabilities on...Votes: 0GitHub stars: 2
- Built Env Permits Scope Intake GateUse when a new permit and submittal tracking request needs a bounded work scope to produce a scoped intake card for the permit submittal tracker. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; every requirement has a current owner and status tied to the correct revision. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused ...Votes: 0GitHub stars: 2
- Built Env Permits Source Provenance LedgerUse when a decision about permit and submittal tracking depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the permit submittal tracker. Success means each material claim has a source, version/date, location, and confidence note; every requirement has a current owner and status tied to the correct revision. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit ...Votes: 0GitHub stars: 2
- Built Env Permits Threshold Rule CheckUse when a permit and submittal tracking decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the permit submittal tracker 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 requirement has a current owner and status tied to the correct revision. Use configured search, fetch, read, browser, test, ...Votes: 0GitHub stars: 2
- Built Env Safety Docs Approval Evidence PacketUse when a site safety documentation result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the safety action 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; open hazards are assigned to qualified personnel and no automated closeout is asserted. Use configured search, fetch, read, browser, ...Votes: 0GitHub stars: 2
- Built Env Safety Docs Change Impact TraceUse when a version, rule, source, or stakeholder change may affect site safety documentation to produce a before/after change record and impact map for the safety action register. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; open hazards are assigned to qualified personnel and no automated closeout is asserted. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and...Votes: 0GitHub stars: 2
- Built Env Safety Docs Closeout Handoff LedgerUse when a site safety documentation work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the safety action 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; open hazards are assigned to qualified personnel and no automated closeout is asserted. Use configured search, fetch, read, browser, test, and write capabil...Votes: 0GitHub stars: 2
- Built Env Safety Docs Completeness ReconciliationUse when the site safety documentation workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the safety action 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; open hazards are assigned to qualified personnel and no automated closeout is asserted. Use configured search, fetch, read, browser, test, and...Votes: 0GitHub stars: 2
- Built Env Safety Docs Exception Triage QueueUse when the site safety documentation workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the safety action 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; open hazards are assigned to qualified personnel and no automated closeout is asserted. Use configured search, fetch, read, browser, test, and write capabi...Votes: 0GitHub stars: 2
- Built Env Safety Docs Recovery Readiness DrillUse when the site safety documentation workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the safety action 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; open hazards are assigned to qualified personnel and no automated closeout is asserted. Use configured search, fetch, read, browser, test, and w...Votes: 0GitHub stars: 2
- Built Env Safety Docs Scenario Sensitivity MatrixUse when the site safety documentation team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the safety action register with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; open hazards are assigned to qualified personnel and no automated closeout is asserted. Use configured search, fetch, read, browser, test, and write capabilities...Votes: 0GitHub stars: 2
- Built Env Safety Docs Scope Intake GateUse when a new site safety documentation request needs a bounded work scope to produce a scoped intake card for the safety action register. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; open hazards are assigned to qualified personnel and no automated closeout is asserted. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focus...Votes: 0GitHub stars: 2
- Built Env Safety Docs Source Provenance LedgerUse when a decision about site safety documentation depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the safety action register. Success means each material claim has a source, version/date, location, and confidence note; open hazards are assigned to qualified personnel and no automated closeout is asserted. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, lim...Votes: 0GitHub stars: 2
- Built Env Safety Docs Threshold Rule CheckUse when a site safety documentation decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the safety action 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; open hazards are assigned to qualified personnel and no automated closeout is asserted. Use configured search, fetch, read, browser, tes...Votes: 0GitHub stars: 2
- Built Env Schedule Approval Evidence PacketUse when a schedule and constraint planning result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the lookahead constraint log 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 near-term activity has a verified prerequisite status or named blocker. Use configured search, fetch, read, browser, te...Votes: 0GitHub stars: 2
- Built Env Schedule Change Impact TraceUse when a version, rule, source, or stakeholder change may affect schedule and constraint planning to produce a before/after change record and impact map for the lookahead constraint log. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each near-term activity has a verified prerequisite status or named blocker. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and a...Votes: 0GitHub stars: 2
- Built Env Schedule Closeout Handoff LedgerUse when a schedule and constraint planning work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the lookahead constraint log 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 near-term activity has a verified prerequisite status or named blocker. Use configured search, fetch, read, browser, test, and write capabilit...Votes: 0GitHub stars: 2
- Built Env Schedule Completeness ReconciliationUse when the schedule and constraint planning workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the lookahead constraint log 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 near-term activity has a verified prerequisite status or named blocker. Use configured search, fetch, read, browser, test, and w...Votes: 0GitHub stars: 2
- Built Env Schedule Exception Triage QueueUse when the schedule and constraint planning workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the lookahead constraint log 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 near-term activity has a verified prerequisite status or named blocker. Use configured search, fetch, read, browser, test, and write capabili...Votes: 0GitHub stars: 2
- Built Env Schedule Recovery Readiness DrillUse when the schedule and constraint planning workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the lookahead constraint log 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 near-term activity has a verified prerequisite status or named blocker. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2
- Built Env Schedule Scenario Sensitivity MatrixUse when the schedule and constraint planning team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the lookahead constraint log with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each near-term activity has a verified prerequisite status or named blocker. Use configured search, fetch, read, browser, test, and write capabilities o...Votes: 0GitHub stars: 2
- Built Env Schedule Scope Intake GateUse when a new schedule and constraint planning request needs a bounded work scope to produce a scoped intake card for the lookahead constraint log. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each near-term activity has a verified prerequisite status or named blocker. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused...Votes: 0GitHub stars: 2
- Built Env Schedule Source Provenance LedgerUse when a decision about schedule and constraint planning depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the lookahead constraint log. Success means each material claim has a source, version/date, location, and confidence note; each near-term activity has a verified prerequisite status or named blocker. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit...Votes: 0GitHub stars: 2
- Built Env Schedule Threshold Rule CheckUse when a schedule and constraint planning decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the lookahead constraint log 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 near-term activity has a verified prerequisite status or named blocker. Use configured search, fetch, read, browser, test,...Votes: 0GitHub stars: 2
- Built Env Site Approval Evidence PacketUse when a site due diligence result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the site review record containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; each constraint is sourced and unresolved items have a qualified reviewer. Use configured search, fetch, read, browser, test, and write capabili...Votes: 0GitHub stars: 2
- Built Env Site Change Impact TraceUse when a version, rule, source, or stakeholder change may affect site due diligence to produce a before/after change record and impact map for the site review record. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each constraint is sourced and unresolved items have a qualified reviewer. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evid...Votes: 0GitHub stars: 2
- Built Env Site Closeout Handoff LedgerUse when a site due diligence work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the site review record with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; each constraint is sourced and unresolved items have a qualified reviewer. Use configured search, fetch, read, browser, test, and write capabilities only when relevant...Votes: 0GitHub stars: 2
- Built Env Site Completeness ReconciliationUse when the site due diligence workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the site review record with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; each constraint is sourced and unresolved items have a qualified reviewer. Use configured search, fetch, read, browser, test, and write capabilities only...Votes: 0GitHub stars: 2
- Built Env Site Exception Triage QueueUse when the site due diligence workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the site review record with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; each constraint is sourced and unresolved items have a qualified reviewer. Use configured search, fetch, read, browser, test, and write capabilities only when relevan...Votes: 0GitHub stars: 2
- Built Env Site Recovery Readiness DrillUse when the site due diligence workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the site review record with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; each constraint is sourced and unresolved items have a qualified reviewer. Use configured search, fetch, read, browser, test, and write capabilities only w...Votes: 0GitHub stars: 2
- Built Env Site Scenario Sensitivity MatrixUse when the site due diligence team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the site review record with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each constraint is sourced and unresolved items have a qualified reviewer. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and ...Votes: 0GitHub stars: 2
- Built Env Site Scope Intake GateUse when a new site due diligence request needs a bounded work scope to produce a scoped intake card for the site review record. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each constraint is sourced and unresolved items have a qualified reviewer. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, and seek appr...Votes: 0GitHub stars: 2
- Built Env Site Source Provenance LedgerUse when a decision about site due diligence depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the site review record. Success means each material claim has a source, version/date, location, and confidence note; each constraint is sourced and unresolved items have a qualified reviewer. 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