Showing 50791–50820 of 77205 skills
Plan and validate PFC 5.0 asphalt fluid, pore-pressure, buoyancy, seepage, and PFC-FLAC coupling contracts while keeping version-specific commands and licensed coupling assets external.
Echo-aloha/asphalt-codex-skills-5
Design and audit PFC 5.0 asphalt dynamic loading and stress-wave studies with damping, timestep, rate, dispersion, source direction, boundary reflection, histories, and wheel-load handoff checks.
Echo-aloha/asphalt-codex-skills-5
Author and audit PFC 5.0 FISH for asphalt cases, including def/end functions, globals and locals, callbacks, numbered histories, object traversal, command blocks, IO, and stop logic.
Echo-aloha/asphalt-codex-skills-5
Prepare and validate portable CAD, polyline, node-element, clump, and boundary geometry contracts for PFC 5.0 asphalt models without bundling opaque legacy executables.
Echo-aloha/asphalt-codex-skills-5
Design and audit PFC 5.0 wall servo, loading-rate control, equilibrium checks, micro-to-macro calibration, two-target local solves, DOE campaigns, and independent confirmation for asphalt models.
Echo-aloha/asphalt-codex-skills-5
Plan, audit, and post-process PFC 5.0 asphalt calibration tests, including compression, diametral loading, direct tension, creep-recovery, test geometry, histories, peak metrics, stiffness, and fistPkg handoff.
Echo-aloha/asphalt-codex-skills-5
Author a work order for a boringoperator lane (terra build or sol review) with proper context loading, per James's professional-process directive
boringmarketer/kimi-first
Productionization loop for any product repo — classify the lane (rail / surface / activation), fix the proof column, ONE review pass, scripted path to production, done = live with a receipt. Use whenever a feature is being built for a real customer; use instead of ad-hoc review rounds.
boringmarketer/kimi-first
Control local apps through Computer Use. Use for tasks that require reading or operating app UI by clicking, typing, scrolling, dragging, pressing keys, or setting values.
xinetzone/SpecWeave
Use this skill for TRAE brand identity and official product knowledge questions, including: who you are, what TRAE is, product differences, TraeCode / TraeWork / TraeCode CLI / TraeCode Plugin entry points, supported capabilities, MCP, Skills, official documentation, and official product links. Do not use it for ordinary coding questions or repository-specific implementation work.
xinetzone/SpecWeave
用于代码安全扫描,或用户要求对 MR/PR、commit、分支、代码差异或未提交变更执行安全审查、漏洞扫描或安全审计时使用。只报告可证实可利用且由本次变更引入的风险。不得用于通用代码审查、普通编码、功能实现或修复请求,也不得用于运行时故障排查。
xinetzone/SpecWeave
Use when a version, rule, source, or stakeholder change may affect parallel artifact integration to produce a before/after change record and impact map for the integration staging plan. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; 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.
Manoj-11-Dahal/try-Skills
Use 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.
Manoj-11-Dahal/try-Skills
Use 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.
Manoj-11-Dahal/try-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
Use 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
Use 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
Use 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
Use 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
Use 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
Use 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
Use 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
Use 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
Use 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
Use 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
Use 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
Use 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
Use 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
Use 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
Use 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