Explore skills
Showing 50701–50730 of 77104 skills
Use when a version, rule, source, or stakeholder change may affect delegated task cancellation propagation to produce a before/after change record and impact map for the cancellation propagation check. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; 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 has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the cancellation propagation check with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; all 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 new delegated task cancellation propagation request needs a bounded work scope to produce a scoped intake card for the cancellation propagation check. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are 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 a delegated task cancellation propagation decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the cancellation propagation check showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; all 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 version, rule, source, or stakeholder change may affect multi-agent checkpoint and resume to produce a before/after change record and impact map for the resume checkpoint manifest. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; 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 multi-agent checkpoint and resume work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the resume checkpoint manifest 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; 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 has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the resume checkpoint manifest 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; 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 new multi-agent checkpoint and resume request needs a bounded work scope to produce a scoped intake card for the resume checkpoint manifest. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; 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 multi-agent checkpoint and resume decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the resume checkpoint manifest 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; 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 delegated context handoff result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the minimal context handoff packet containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; 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 a version, rule, source, or stakeholder change may affect delegated context handoff to produce a before/after change record and impact map for the minimal context handoff packet. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; 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 a delegated context handoff work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the minimal context handoff packet with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; 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 workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the minimal context handoff packet with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; 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 workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the minimal context handoff packet with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; 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 a new delegated context handoff request needs a bounded work scope to produce a scoped intake card for the minimal context handoff packet. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; 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 a decision about delegated context handoff depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the minimal context handoff packet. Success means each material claim has a source, version/date, location, and confidence note; 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 a delegated context handoff decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the minimal context handoff packet showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; 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 a agent task dependency graphs result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the task dependency graph 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; 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 version, rule, source, or stakeholder change may affect agent task dependency graphs to produce a before/after change record and impact map for the task dependency graph. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; 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 agent task dependency graphs work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the task dependency graph 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; 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 workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the task dependency graph 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; 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 workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the task dependency graph 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; 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 new agent task dependency graphs request needs a bounded work scope to produce a scoped intake card for the task dependency graph. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; 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 decision about agent task dependency graphs depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the task dependency graph. Success means each material claim has a source, version/date, location, and confidence note; 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 agent task dependency graphs decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the task dependency graph 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; 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 version, rule, source, or stakeholder change may affect multi-reviewer disagreement adjudication to produce a before/after change record and impact map for the reviewer disagreement ledger. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; 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 new multi-reviewer disagreement adjudication request needs a bounded work scope to produce a scoped intake card for the reviewer disagreement ledger. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are 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 a multi-reviewer disagreement adjudication decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the reviewer disagreement 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; 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 parallel worker file leases result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the file-ownership lease 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; no two workers edit the same protected path concurrently without explicit coordination. 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 version, rule, source, or stakeholder change may affect parallel worker file leases to produce a before/after change record and impact map for the file-ownership lease map. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; no two workers edit the same protected path concurrently without explicit coordination. 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 CodeCodex