weigh

Solid

Weighted-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".

AI & Automation 38 stars 3 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 86/100

Stars 20%
53
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# weigh — weighted-trajectory selection Run `sample → attach signals → weight → select` over one task. The model side *proposes* candidate trajectories (this is the Workflow tool's substrate — its judge-panel / adversarial-verify sampling); the **harness owns the weight function that picks among them**: `scripts/score-trajectories.mjs`, a pure, zero-dep, frozen-weights scorer. See `references/workflow-shape.md` for the seam and `references/scoring.md` for the weighting contract. **Core principle: the model proposes, the scorer disposes.** Selection is a deterministic, version-controlled, reconstructable weighted sum — not a vibe. > `disable-model-invocation: true` suppresses **auto**-invocation only — the model > never fires `/weigh` on its own (it spawns N agents and burns tokens). A > user-typed `/weigh` runs the full procedure below, including the Step-2 sampling > fan-out. `allowed-tools` includes **`Agent`** because Step 2 spawns the N > sampling agents — without it the sampling step cannot run. ## Result tag Announce exactly one human result tag at the end of the run: ``` RESULT: SELECTED | NO-SELECTION | DRY-RUN ``` | Tag | Meaning | |-----|---------| | `SELECTED` | The scorer ran and returned a `selected` id (or top-K for `synthesis`). | | `NO-SELECTION` | Every trajectory broke the hard floor — the scorer returned `{ selected: null, reason: "NO-SELECTION", floorViolations }`. Report the floor that killed them; do not promote a failure. | | `DRY-RUN` | `--dry-r...

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

AI & Automation Listed

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).

0 Updated today
RubyEyedReaper
AI & Automation Listed

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.

4 Updated today
compforge
AI & Automation Listed

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.

6 Updated 5 days ago
alex-feel