weigh
SolidWeighted-trajectory selection: sample N candidate trajectories for one task, attach deterministic signals to each, then weight + select among them with a pure, version-controlled scorer we own (score-trajectories.mjs) rather than a model black box. The Workflow tool's judge-panel / adversarial-verify patterns PROPOSE the trajectories; this skill owns the weight function that PICKS among them (frozen DEFAULT_WEIGHTS: consistency:30 evalPass:20 auditPass:15 cost:10 judge:25, sum 100; judge:0 → fully deterministic). disable-model-invocation because the sampling step spawns N agents and burns tokens — manual-invoke only. TRIGGER when: /weigh invoked, or asked to "sample N approaches and pick the best", "weigh these trajectories", "best-of-n this task", "score candidate outputs", "self-consistency vote over samples", "ensemble these answers".
Install
Quality Score: 86/100
Skill Content
Details
- Author
- mifunedev
- Repository
- mifunedev/openharness
- Created
- 5 months ago
- Last Updated
- today
- Language
- TypeScript
- License
- Apache-2.0
Similar Skills
Semantically similar based on skill content — not just same category
decision-matrix
Use when choosing between options or prioritizing — "decide", "choose between", "which should I pick", "compare options", "trade-off", "which library/framework/database/vendor", "build vs buy", "best option for", "prioritize", "rank these", "RICE/WSJF". A quantitative weighted-decision engine: scores options against weighted criteria with multiple methods (weighted-sum, Pugh, TOPSIS/AHP, RICE/WSJF/ICE/Kano), runs sensitivity analysis, flags when methods disagree, applies hard-constraint vetoes, aggregates multiple scorers, and records a numbered DEC decision. Fire this for ANY non-trivial multi-option choice or prioritization, even a mid-task internal fork — the math is deterministic and the decision is recorded. Not for qualitative-only trade-off framing (use decision-mapping) or stochastic rollout search (use recursive-decision-ledger).
trajectory
Discover, run, interpret, and iteratively tune a project's existing agent trajectory evaluation capability. Use when the user asks to evaluate agent trajectories, compare effect and cost across runs, find trajectory smells or the next trajectory problem, or identify optimizations for a known trajectory issue. Operate project-owned trajectory evidence and canonical entrypoints; do not invent missing evidence, verdicts, or a parallel evaluation framework.
dynamic-workflow-patterns
Pattern taxonomy, agent role combinations, model routing, unit-of-work sizing, and resilience discipline for Claude Code dynamic workflows. ALWAYS load this skill before authoring or running any Workflow tool script, and ALWAYS load it when the user mentions "workflow" or "ultracode" in any form -- or when the task calls for multi-agent orchestration such as fan-out, tournaments, adversarial verification, triage at scale, ranking large lists, deep verification of claims, or root-cause hunting; do not hand-roll a workflow from memory when this skill applies.