All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Managementlab Vendor And Procurement Review Uncertain Requirements Verification And Acceptance Test PlanUse when a result must be checked against explicit behavior, safety, or quality conditions for Management, planning, and task operations: vendor and procurement review for uncertain requirements. Produce a risk-weighted verification plan with saved evidence with scope, versions, decisions, and evidence for this task-specific gate: Separate confirmed needs from open questions and assign each unresolved requirement an owner and decision date. Success means each critical requirement maps to a re...Votes: 0GitHub stars: 2
- Aas Devrel Api Error Docs Approval Evidence PacketUse when a API error documentation parity result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the error-doc parity 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; documented error behavior matches the published contract or the discrepancy is owned. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2
- Aas Devrel Api Error Docs Change Impact TraceUse when a version, rule, source, or stakeholder change may affect API error documentation parity to produce a before/after change record and impact map for the error-doc parity ledger. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; documented error behavior matches the published contract or the discrepancy is owned. Use configured search, fetch, read, browser, test, and write capabilities only when relevant...Votes: 0GitHub stars: 2
- Aas Devrel Api Error Docs Closeout Handoff LedgerUse when a API error documentation parity work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the error-doc parity 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; documented error behavior matches the published contract or the discrepancy is owned. Use configured search, fetch, read, browser, test, and write cap...Votes: 0GitHub stars: 2
- Aas Devrel Api Error Docs Completeness ReconciliationUse when the API error documentation parity workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the error-doc parity 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; documented error behavior matches the published contract or the discrepancy is owned. Use configured search, fetch, read, browser, test,...Votes: 0GitHub stars: 2
- Aas Devrel Api Error Docs Exception Triage QueueUse when the API error documentation parity workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the error-doc parity 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; documented error behavior matches the published contract or the discrepancy is owned. Use configured search, fetch, read, browser, test, and write ca...Votes: 0GitHub stars: 2
- Aas Devrel Api Error Docs Recovery Readiness DrillUse when the API error documentation parity workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the error-doc parity 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; documented error behavior matches the published contract or the discrepancy is owned. Use configured search, fetch, read, browser, test, a...Votes: 0GitHub stars: 2
- Aas Devrel Api Error Docs Scenario Sensitivity MatrixUse when the API error documentation parity team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the error-doc parity ledger with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; documented error behavior matches the published contract or the discrepancy is owned. Use configured search, fetch, read, browser, test, and write capabili...Votes: 0GitHub stars: 2
- Aas Devrel Api Error Docs Scope Intake GateUse when a new API error documentation parity request needs a bounded work scope to produce a scoped intake card for the error-doc parity ledger. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; documented error behavior matches the published contract or the discrepancy is owned. 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
- Aas Devrel Api Error Docs Source Provenance LedgerUse when a decision about API error documentation parity depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the error-doc parity ledger. Success means each material claim has a source, version/date, location, and confidence note; documented error behavior matches the published contract or the discrepancy is owned. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence,...Votes: 0GitHub stars: 2
- Aas Devrel Api Error Docs Threshold Rule CheckUse when a API error documentation parity decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the error-doc parity 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; documented error behavior matches the published contract or the discrepancy is owned. Use configured search, fetch, read, browser,...Votes: 0GitHub stars: 2
- Aas Devrel Changelog Upgrade Approval Evidence PacketUse when a developer changelog upgrade-path clarity result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the changelog migration 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 breaking item has a clear affected audience and a testable next step. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2
- Aas Devrel Changelog Upgrade Change Impact TraceUse when a version, rule, source, or stakeholder change may affect developer changelog upgrade-path clarity to produce a before/after change record and impact map for the changelog migration map. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; every breaking item has a clear affected audience and a testable next step. Use configured search, fetch, read, browser, test, and write capabilities only when relevant...Votes: 0GitHub stars: 2
- Aas Devrel Changelog Upgrade Closeout Handoff LedgerUse when a developer changelog upgrade-path clarity work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the changelog migration 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 breaking item has a clear affected audience and a testable next step. Use configured search, fetch, read, browser, test, and write cap...Votes: 0GitHub stars: 2
- Aas Devrel Changelog Upgrade Completeness ReconciliationUse when the developer changelog upgrade-path clarity workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the changelog migration 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 breaking item has a clear affected audience and a testable next step. Use configured search, fetch, read, browser, test,...Votes: 0GitHub stars: 2
- Aas Devrel Changelog Upgrade Exception Triage QueueUse when the developer changelog upgrade-path clarity workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the changelog migration 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 breaking item has a clear affected audience and a testable next step. Use configured search, fetch, read, browser, test, and write ca...Votes: 0GitHub stars: 2
- Aas Devrel Changelog Upgrade Recovery Readiness DrillUse when the developer changelog upgrade-path clarity workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the changelog migration 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 breaking item has a clear affected audience and a testable next step. Use configured search, fetch, read, browser, test, a...Votes: 0GitHub stars: 2
- Aas Devrel Changelog Upgrade Scenario Sensitivity MatrixUse when the developer changelog upgrade-path clarity team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the changelog migration map with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; every breaking item has a clear affected audience and a testable next step. Use configured search, fetch, read, browser, test, and write capabili...Votes: 0GitHub stars: 2
- Aas Devrel Changelog Upgrade Scope Intake GateUse when a new developer changelog upgrade-path clarity request needs a bounded work scope to produce a scoped intake card for the changelog migration map. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; every breaking item has a clear affected audience and a testable next step. 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
- Aas Devrel Changelog Upgrade Source Provenance LedgerUse when a decision about developer changelog upgrade-path clarity depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the changelog migration map. Success means each material claim has a source, version/date, location, and confidence note; every breaking item has a clear affected audience and a testable next step. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence,...Votes: 0GitHub stars: 2
- Aas Devrel Changelog Upgrade Threshold Rule CheckUse when a developer changelog upgrade-path clarity decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the changelog migration 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 breaking item has a clear affected audience and a testable next step. Use configured search, fetch, read, browser,...Votes: 0GitHub stars: 2
- Aas Devrel Community Triage Approval Evidence PacketUse when a open-source developer issue triage result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the maintainer issue triage queue 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; security-sensitive reports are routed privately and ordinary items receive a bounded next step. Use configured search...Votes: 0GitHub stars: 2
- Aas Devrel Community Triage Change Impact TraceUse when a version, rule, source, or stakeholder change may affect open-source developer issue triage to produce a before/after change record and impact map for the maintainer issue triage queue. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; security-sensitive reports are routed privately and ordinary items receive a bounded next step. Use configured search, fetch, read, browser, test, and write capabilitie...Votes: 0GitHub stars: 2
- Aas Devrel Community Triage Closeout Handoff LedgerUse when a open-source developer issue triage work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the maintainer issue triage queue 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; security-sensitive reports are routed privately and ordinary items receive a bounded next step. Use configured search, fetch, read, browser,...Votes: 0GitHub stars: 2
- Aas Devrel Community Triage Completeness ReconciliationUse when the open-source developer issue triage workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the maintainer issue triage queue 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; security-sensitive reports are routed privately and ordinary items receive a bounded next step. Use configured search, fetch, ...Votes: 0GitHub stars: 2
- Aas Devrel Community Triage Exception Triage QueueUse when the open-source developer issue triage workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the maintainer issue triage queue 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; security-sensitive reports are routed privately and ordinary items receive a bounded next step. Use configured search, fetch, read, browser...Votes: 0GitHub stars: 2
- Aas Devrel Community Triage Recovery Readiness DrillUse when the open-source developer issue triage workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the maintainer issue triage queue 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; security-sensitive reports are routed privately and ordinary items receive a bounded next step. Use configured search, fetch, re...Votes: 0GitHub stars: 2
- Aas Devrel Community Triage Scenario Sensitivity MatrixUse when the open-source developer issue triage team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the maintainer issue triage queue with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; security-sensitive reports are routed privately and ordinary items receive a bounded next step. Use configured search, fetch, read, browser, test...Votes: 0GitHub stars: 2
- Aas Devrel Community Triage Scope Intake GateUse when a new open-source developer issue triage request needs a bounded work scope to produce a scoped intake card for the maintainer issue triage queue. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; security-sensitive reports are routed privately and ordinary items receive a bounded next step. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit r...Votes: 0GitHub stars: 2
- Aas Devrel Community Triage Source Provenance LedgerUse when a decision about open-source developer issue triage depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the maintainer issue triage queue. Success means each material claim has a source, version/date, location, and confidence note; security-sensitive reports are routed privately and ordinary items receive a bounded next step. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authoriz...Votes: 0GitHub stars: 2
- Aas Devrel Community Triage Threshold Rule CheckUse when a open-source developer issue triage decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the maintainer issue triage queue 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; security-sensitive reports are routed privately and ordinary items receive a bounded next step. Use configured search, f...Votes: 0GitHub stars: 2
- Aas Devrel Launch Claim Proof Approval Evidence PacketUse when a developer launch claim substantiation result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the developer launch claim matrix 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 public technical claim maps to dated evidence and limitations remain visible. Use configured search, fetch, ...Votes: 0GitHub stars: 2
- Aas Devrel Launch Claim Proof Change Impact TraceUse when a version, rule, source, or stakeholder change may affect developer launch claim substantiation to produce a before/after change record and impact map for the developer launch claim matrix. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; every public technical claim maps to dated evidence and limitations remain visible. Use configured search, fetch, read, browser, test, and write capabilities only wh...Votes: 0GitHub stars: 2
- Aas Devrel Launch Claim Proof Closeout Handoff LedgerUse when a developer launch claim substantiation work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the developer launch claim matrix 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 public technical claim maps to dated evidence and limitations remain visible. Use configured search, fetch, read, browser, test, an...Votes: 0GitHub stars: 2
- Aas Devrel Launch Claim Proof Completeness ReconciliationUse when the developer launch claim substantiation workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the developer launch claim matrix 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 public technical claim maps to dated evidence and limitations remain visible. Use configured search, fetch, read, bro...Votes: 0GitHub stars: 2
- Aas Devrel Launch Claim Proof Exception Triage QueueUse when the developer launch claim substantiation workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the developer launch claim matrix 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 public technical claim maps to dated evidence and limitations remain visible. Use configured search, fetch, read, browser, test, a...Votes: 0GitHub stars: 2
- Aas Devrel Launch Claim Proof Recovery Readiness DrillUse when the developer launch claim substantiation workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the developer launch claim matrix 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 public technical claim maps to dated evidence and limitations remain visible. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2
- Aas Devrel Launch Claim Proof Scenario Sensitivity MatrixUse when the developer launch claim substantiation team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the developer launch claim matrix with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; every public technical claim maps to dated evidence and limitations remain visible. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2
- Aas Devrel Launch Claim Proof Scope Intake GateUse when a new developer launch claim substantiation request needs a bounded work scope to produce a scoped intake card for the developer launch claim matrix. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; every public technical claim maps to dated evidence and limitations remain visible. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement...Votes: 0GitHub stars: 2
- Aas Devrel Launch Claim Proof Source Provenance LedgerUse when a decision about developer launch claim substantiation depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the developer launch claim matrix. Success means each material claim has a source, version/date, location, and confidence note; every public technical claim maps to dated evidence and limitations remain visible. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Recor...Votes: 0GitHub stars: 2
- Aas Devrel Launch Claim Proof Threshold Rule CheckUse when a developer launch claim substantiation decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the developer launch claim matrix 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 public technical claim maps to dated evidence and limitations remain visible. Use configured search, fetch, rea...Votes: 0GitHub stars: 2
- Aas Devrel Quickstart Friction Approval Evidence PacketUse when a developer quickstart friction analysis result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the quickstart friction 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 failure point is tied to a reproducible step or labeled as unverified. Use configured search, fetch, read, browser...Votes: 0GitHub stars: 2
- Aas Devrel Quickstart Friction Change Impact TraceUse when a version, rule, source, or stakeholder change may affect developer quickstart friction analysis to produce a before/after change record and impact map for the quickstart friction map. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each failure point is tied to a reproducible step or labeled as unverified. Use configured search, fetch, read, browser, test, and write capabilities only when relevant a...Votes: 0GitHub stars: 2
- Aas Devrel Quickstart Friction Closeout Handoff LedgerUse when a developer quickstart friction analysis work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the quickstart friction 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 failure point is tied to a reproducible step or labeled as unverified. Use configured search, fetch, read, browser, test, and write capab...Votes: 0GitHub stars: 2
- Aas Devrel Quickstart Friction Completeness ReconciliationUse when the developer quickstart friction analysis workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the quickstart friction 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 failure point is tied to a reproducible step or labeled as unverified. Use configured search, fetch, read, browser, test, a...Votes: 0GitHub stars: 2
- Aas Devrel Quickstart Friction Exception Triage QueueUse when the developer quickstart friction analysis workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the quickstart friction 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 failure point is tied to a reproducible step or labeled as unverified. Use configured search, fetch, read, browser, test, and write capa...Votes: 0GitHub stars: 2
- Aas Devrel Quickstart Friction Recovery Readiness DrillUse when the developer quickstart friction analysis workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the quickstart friction 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 failure point is tied to a reproducible step or labeled as unverified. Use configured search, fetch, read, browser, test, and...Votes: 0GitHub stars: 2
- Aas Devrel Quickstart Friction Scenario Sensitivity MatrixUse when the developer quickstart friction analysis team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the quickstart friction map with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each failure point is tied to a reproducible step or labeled as unverified. Use configured search, fetch, read, browser, test, and write capabiliti...Votes: 0GitHub stars: 2
- Aas Devrel Quickstart Friction Scope Intake GateUse when a new developer quickstart friction analysis request needs a bounded work scope to produce a scoped intake card for the quickstart friction map. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each failure point is tied to a reproducible step or labeled as unverified. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three foc...Votes: 0GitHub stars: 2
- Aas Devrel Quickstart Friction Source Provenance LedgerUse when a decision about developer quickstart friction analysis depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the quickstart friction map. Success means each material claim has a source, version/date, location, and confidence note; each failure point is tied to a reproducible step or labeled as unverified. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, l...Votes: 0GitHub stars: 2