Recently active skills
Trending is calculated from star growth this site has recorded itself. No history is estimated or back-filled.
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-context-handoff-recovery-readiness-drillManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-context-handoff-scenario-sensitivity-matrixManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-context-handoff-scope-intake-gateManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-context-handoff-source-provenance-ledgerManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-context-handoff-threshold-rule-checkManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-dependency-graph-approval-evidence-packetManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-dependency-graph-change-impact-traceManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-dependency-graph-closeout-handoff-ledgerManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-dependency-graph-completeness-reconciliationManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-dependency-graph-exception-triage-queueManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-dependency-graph-recovery-readiness-drillManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-dependency-graph-scenario-sensitivity-matrixManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-dependency-graph-scope-intake-gateManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-dependency-graph-source-provenance-ledgerManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-dependency-graph-threshold-rule-checkManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-review-adjudication-approval-evidence-packetManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-review-adjudication-change-impact-traceManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-review-adjudication-closeout-handoff-ledgerManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-review-adjudication-completeness-reconciliationManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-review-adjudication-exception-triage-queueManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-review-adjudication-recovery-readiness-drillManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-review-adjudication-scenario-sensitivity-matrixManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-review-adjudication-scope-intake-gateManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-review-adjudication-source-provenance-ledgerManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-review-adjudication-threshold-rule-checkManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-work-lease-approval-evidence-packetManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-work-lease-change-impact-traceManoj-11-Dahal/try-SkillsUse 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-work-lease-closeout-handoff-ledgerManoj-11-Dahal/try-SkillsUse when a parallel worker file leases work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the file-ownership lease 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; 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-work-lease-completeness-reconciliationManoj-11-Dahal/try-SkillsUse when the parallel worker file leases workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the file-ownership lease 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; 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |
| aas-agent-coordination-work-lease-exception-triage-queueManoj-11-Dahal/try-SkillsUse when the parallel worker file leases workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the file-ownership lease 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; 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. | Stars: 3 | Updated | Claude CodeCodex | Verified | Install |