Explore skills
Showing 56671–56700 of 72688 skills
Use when a delegated task cancellation propagation result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the cancellation propagation check 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; all cancellable work reaches a known terminal state and pending side effects are surfaced. 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 approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when a delegated task cancellation propagation work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the cancellation propagation check 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 cancellable work reaches a known terminal state and pending side effects are surfaced. 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 approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when the delegated task cancellation propagation workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the cancellation propagation check 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 cancellable work reaches a known terminal state and pending side effects are surfaced. 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 approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when the delegated task cancellation propagation workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the cancellation propagation check 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 cancellable work reaches a known terminal state and pending side effects are surfaced. 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 approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when the delegated task cancellation propagation team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the cancellation propagation check with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; all cancellable work reaches a known terminal state and pending side effects are surfaced. 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 approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when a decision about delegated task cancellation propagation depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the cancellation propagation check. Success means each material claim has a source, version/date, location, and confidence note; all cancellable work reaches a known terminal state and pending side effects are surfaced. 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 approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when a multi-agent checkpoint and resume result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the resume checkpoint manifest 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; resumption does not repeat completed side effects or lose unresolved decisions. 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 approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when the multi-agent checkpoint and resume workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the resume checkpoint manifest 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; resumption does not repeat completed side effects or lose unresolved decisions. 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 approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when the multi-agent checkpoint and resume workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the resume checkpoint manifest 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; resumption does not repeat completed side effects or lose unresolved decisions. 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 approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when the multi-agent checkpoint and resume team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the resume checkpoint manifest with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; resumption does not repeat completed side effects or lose unresolved decisions. 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 approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when a decision about multi-agent checkpoint and resume depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the resume checkpoint manifest. Success means each material claim has a source, version/date, location, and confidence note; resumption does not repeat completed side effects or lose unresolved decisions. 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 approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when the delegated context handoff workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the minimal context handoff 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; the receiver can continue without hidden assumptions or unnecessary private data. 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 approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when the delegated context handoff team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the minimal context handoff packet with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; the receiver can continue without hidden assumptions or unnecessary private data. 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 approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when the agent task dependency graphs workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the task dependency graph 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; no task starts before its prerequisites and every output has a receiving owner. 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 approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when the agent task dependency graphs team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the task dependency graph with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; no task starts before its prerequisites and every output has a receiving owner. 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 approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when a multi-reviewer disagreement adjudication result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the reviewer disagreement 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; disagreement is resolved by evidence or routed to an owner rather than averaged away. 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 approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when a multi-reviewer disagreement adjudication work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the reviewer disagreement 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; disagreement is resolved by evidence or routed to an owner rather than averaged away. 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 approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when the multi-reviewer disagreement adjudication workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the reviewer disagreement 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; disagreement is resolved by evidence or routed to an owner rather than averaged away. 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 approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when the multi-reviewer disagreement adjudication workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the reviewer disagreement 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; disagreement is resolved by evidence or routed to an owner rather than averaged away. 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 approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when the multi-reviewer disagreement adjudication workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the reviewer disagreement 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; disagreement is resolved by evidence or routed to an owner rather than averaged away. 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 approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when the multi-reviewer disagreement adjudication team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the reviewer disagreement ledger with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; disagreement is resolved by evidence or routed to an owner rather than averaged away. 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 approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when a decision about multi-reviewer disagreement adjudication depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the reviewer disagreement ledger. Success means each material claim has a source, version/date, location, and confidence note; disagreement is resolved by evidence or routed to an owner rather than averaged away. 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 approval before external or irreversible actions.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when an authorized implementation needs repeatable steps and a visible change boundary for Human-governed agent improvement: evaluator integrity for conflicting evidence. Produce a bounded build or configuration runbook with scope, versions, decisions, and evidence for this task-specific gate: Report regressions and evaluator conflicts separately; do not hide a loss in one held-out case behind an aggregate score. Success means the prepared result is reproducible, reviewable, and within the approved scope. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when a solution needs a coherent structure before implementation or production for Human-governed agent improvement: evaluator integrity for conflicting evidence. Produce a staged design blueprint with scope, versions, decisions, and evidence for this task-specific gate: Report regressions and evaluator conflicts separately; do not hide a loss in one held-out case behind an aggregate score. Success means interfaces, dependencies, constraints, and review points are testable before build. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when an unexpected result needs diagnosis without widening risk or losing evidence for Human-governed agent improvement: evaluator integrity for conflicting evidence. Produce a failure-triage record and reversible recovery plan with scope, versions, decisions, and evidence for this task-specific gate: Report regressions and evaluator conflicts separately; do not hide a loss in one held-out case behind an aggregate score. Success means the failure is bounded by observations, one testable hypothesis, and a safe next step. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when several tools, designs, methods, or workflows could satisfy the same need for Human-governed agent improvement: evaluator integrity for conflicting evidence. Produce an evidence-backed option-comparison matrix with scope, versions, decisions, and evidence for this task-specific gate: Report regressions and evaluator conflicts separately; do not hide a loss in one held-out case behind an aggregate score. Success means options are compared on user-approved criteria with uncertainty and trade-offs shown. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when a request must be converted into testable constraints and an owned decision for Human-governed agent improvement: evaluator integrity for conflicting evidence. Produce a reviewable requirements and decision brief with scope, versions, decisions, and evidence for this task-specific gate: Report regressions and evaluator conflicts separately; do not hide a loss in one held-out case behind an aggregate score. Success means requirements have priorities, evidence, owners, and measurable acceptance conditions. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when the work needs a verified goal, authorized boundary, and starting state for Human-governed agent improvement: evaluator integrity for conflicting evidence. Produce a scope-and-baseline record with scope, versions, decisions, and evidence for this task-specific gate: Report regressions and evaluator conflicts separately; do not hide a loss in one held-out case behind an aggregate score. Success means the owner, constraints, baseline, and acceptance signal are explicit. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when the workflow could affect people, systems, confidential data, intellectual property, or physical outcomes for Human-governed agent improvement: evaluator integrity for conflicting evidence. Produce a scoped risk-and-control review with scope, versions, decisions, and evidence for this task-specific gate: Report regressions and evaluator conflicts separately; do not hide a loss in one held-out case behind an aggregate score. Success means the review names relevant hazards, permissions, controls, evidence gaps, and approval owners. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodexUse when a decision depends on current, source-grounded information for Human-governed agent improvement: evaluator integrity for conflicting evidence. Produce a source-and-claim ledger with scope, versions, decisions, and evidence for this task-specific gate: Report regressions and evaluator conflicts separately; do not hide a loss in one held-out case behind an aggregate score. Success means material claims are linked to current primary sources with dates and limitations. Use permissioned inputs, preserve a baseline, check current primary guidance, and stop when evidence, authority, rights, or safe recovery is unclear.
Manoj-11-Dahal/try-Skills
Stars: 3Claude CodeCodex