Explore skills
Showing 50791–50820 of 77079 skills
Use when the agent message-to-tool correlation workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the correlation 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 cited action maps to the correct call and no result is attributed to a neighboring turn. 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 message-to-tool correlation workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the correlation 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 cited action maps to the correct call and no result is attributed to a neighboring turn. 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 message-to-tool correlation workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the correlation 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 cited action maps to the correct call and no result is attributed to a neighboring turn. 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 message-to-tool correlation team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the correlation map with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each cited action maps to the correct call and no result is attributed to a neighboring turn. 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 message-to-tool correlation request needs a bounded work scope to produce a scoped intake card for the correlation map. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each cited action maps to the correct call and no result is attributed to a neighboring turn. 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 message-to-tool correlation depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the correlation map. Success means each material claim has a source, version/date, location, and confidence note; each cited action maps to the correct call and no result is attributed to a neighboring turn. 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 message-to-tool correlation decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the correlation 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; each cited action maps to the correct call and no result is attributed to a neighboring turn. 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 run outcome classification result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the outcome taxonomy and sample audit 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; classes are mutually understandable and separate model output from verified task completion. 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 run outcome classification to produce a before/after change record and impact map for the outcome taxonomy and sample audit. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; classes are mutually understandable and separate model output from verified task completion. 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 run outcome classification work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the outcome taxonomy and sample audit 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; classes are mutually understandable and separate model output from verified task completion. 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 run outcome classification workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the outcome taxonomy and sample audit 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; classes are mutually understandable and separate model output from verified task completion. 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 run outcome classification workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the outcome taxonomy and sample audit 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; classes are mutually understandable and separate model output from verified task completion. 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 run outcome classification workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the outcome taxonomy and sample audit 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; classes are mutually understandable and separate model output from verified task completion. 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 run outcome classification team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the outcome taxonomy and sample audit with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; classes are mutually understandable and separate model output from verified task completion. 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 run outcome classification request needs a bounded work scope to produce a scoped intake card for the outcome taxonomy and sample audit. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; classes are mutually understandable and separate model output from verified task completion. 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 run outcome classification depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the outcome taxonomy and sample audit. Success means each material claim has a source, version/date, location, and confidence note; classes are mutually understandable and separate model output from verified task completion. 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 run outcome classification decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the outcome taxonomy and sample audit 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; classes are mutually understandable and separate model output from verified task completion. 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 trace replay fixtures result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the minimized replay fixture 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 fixture reproduces the declared failure without replaying external side effects or private content. 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 trace replay fixtures to produce a before/after change record and impact map for the minimized replay fixture. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; the fixture reproduces the declared failure without replaying external side effects or private content. 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 trace replay fixtures work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the minimized replay fixture 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 fixture reproduces the declared failure without replaying external side effects or private content. 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 trace replay fixtures workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the minimized replay fixture 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 fixture reproduces the declared failure without replaying external side effects or private content. 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 trace replay fixtures workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the minimized replay fixture 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 fixture reproduces the declared failure without replaying external side effects or private content. 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 CodeCodexDoHyun468/claw-hwp
Stars: 223Claude CodeCodexBuild PFC 5.0 asphalt-mixture specimens with explicit aggregate objects, a declared homogenized-mastic or fine-particle abstraction, residual air voids, measured gradation conversion, contact-pair assignment, compaction, equilibrium, and mass-volume closure; use before Marshall, rutting, creep, or strength tests.
Echo-aloha/asphalt-codex-skills-5
Stars: 26Claude CodeCodexSelect, probe, calibrate, and audit the Burger viscoelastic contact model for PFC 5.0 asphalt-mixture cases, including Maxwell-Kelvin parameter roles, units, temperature/rate dependence, PFC5 cmat assignment, timestep checks, creep/recovery validation, and PFC5-only syntax boundary checks.
Echo-aloha/asphalt-codex-skills-5
Stars: 26Claude CodeCodexAdapt and audit a PFC 5.0 asphalt Marshall stability/flow simulation using the external fistPkg26 dc.fis two-head controller as a starting skeleton; use for curved-head geometry, PFC5 wall/contact kinematics, load-deformation histories, peak stability, edition-specific flow processing, and validation against laboratory data.
Echo-aloha/asphalt-codex-skills-5
Stars: 26Claude CodeCodexDesign, implement, and audit PFC3D 5.0 asphalt wheel-tracking and intersection-rutting simulations using RVE-to-strip-to-full-size scaling, PFC5-compatible vector reaction control, Burger-calibrated contacts, vertical-horizontal coupled loads, rut/shear histories, edition-specific metrics, and explicit surrogate validation.
Echo-aloha/asphalt-codex-skills-5
Stars: 26Claude CodeCodexGovern Asphalt-Codex-Skills-5 as a PFC 5.0-only asphalt-mixture package, enforcing version purity, external fistPkg boundaries, portable assets, validation, and release hygiene.
Echo-aloha/asphalt-codex-skills-5
Stars: 26Claude CodeCodexPost-process exported PFC 5.0 asphalt DEM data with vedo for particle, force-chain, crack, displacement, velocity, slice, figure, and animation workflows.
Echo-aloha/asphalt-codex-skills-5
Stars: 26Claude CodeCodexInstrument and post-process PFC 5.0 asphalt damage studies using bond-break hits, clustered AE events, macro energy density, source fields, stage summaries, and auditable CSV outputs.
Echo-aloha/asphalt-codex-skills-5
Stars: 26Claude CodeCodex