Loading…
Not enough history yet: 3 of 7 days recorded. Until then this list is ordered by the most recent content change.
77104 skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| aas-agent-coordination-artifact-integration-recovery-readiness-drillManoj-11-Dahal/try-SkillsUse when the parallel artifact integration workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the integration staging plan 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 output is reviewed against the same baseline and conflicts remain visible. 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-artifact-integration-scenario-sensitivity-matrixManoj-11-Dahal/try-SkillsUse when the parallel artifact integration team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the integration staging plan with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each output is reviewed against the same baseline and conflicts remain visible. 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-artifact-integration-scope-intake-gateManoj-11-Dahal/try-SkillsUse when a new parallel artifact integration request needs a bounded work scope to produce a scoped intake card for the integration staging plan. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each output is reviewed against the same baseline and conflicts remain visible. 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-artifact-integration-source-provenance-ledgerManoj-11-Dahal/try-SkillsUse when a decision about parallel artifact integration depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the integration staging plan. Success means each material claim has a source, version/date, location, and confidence note; each output is reviewed against the same baseline and conflicts remain visible. 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-artifact-integration-threshold-rule-checkManoj-11-Dahal/try-SkillsUse when a parallel artifact integration decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the integration staging plan 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 output is reviewed against the same baseline and conflicts remain visible. 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-cancel-propagation-approval-evidence-packetManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-cancel-propagation-change-impact-traceManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-cancel-propagation-closeout-handoff-ledgerManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-cancel-propagation-completeness-reconciliationManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-cancel-propagation-exception-triage-queueManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-cancel-propagation-recovery-readiness-drillManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-cancel-propagation-scenario-sensitivity-matrixManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-cancel-propagation-scope-intake-gateManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-cancel-propagation-source-provenance-ledgerManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-cancel-propagation-threshold-rule-checkManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-checkpoint-resume-approval-evidence-packetManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-checkpoint-resume-change-impact-traceManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-checkpoint-resume-closeout-handoff-ledgerManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-checkpoint-resume-completeness-reconciliationManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-checkpoint-resume-exception-triage-queueManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-checkpoint-resume-recovery-readiness-drillManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-checkpoint-resume-scenario-sensitivity-matrixManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-checkpoint-resume-scope-intake-gateManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-checkpoint-resume-source-provenance-ledgerManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-checkpoint-resume-threshold-rule-checkManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-context-handoff-approval-evidence-packetManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-context-handoff-change-impact-traceManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-context-handoff-closeout-handoff-ledgerManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-context-handoff-completeness-reconciliationManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-context-handoff-exception-triage-queueManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |