Skip to content
Development
Skill

/composition-evaluate

Compare FlowGraph composition policies with fixed tasks, requested-versus-realized resources, failure injection, and an evidence claim gate

From plugin
aiwg
211200 skills199 agents26 commands
Install
$ npx -y skills add jmagly/aiwg --skill composition-evaluate --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/composition-evaluate

Context preview

The summary Claude sees to decide when to auto-load this skill.

Compare FlowGraph composition policies with fixed tasks, requested-versus-realized resources, failure injection, and an evidence claim gate

SKILL.md

composition-evaluate.SKILL.md
namespace: aiwg
name: composition-evaluate
platforms: [all]
description: Compare FlowGraph composition policies with fixed tasks, requested-versus-realized resources, failure injection, and an evidence claim gate
triggers:
  - benchmark composition policies
  - compare strict lcm and adaptive cost quality
  - evaluate graph flow against loop dag and durable code
  - test composition failure modes and claim gate

Composition evaluation

Use this skill when a composition policy needs reproducible comparison against a single-pass baseline.

1. Start from `benchmarks/composition-policy-benchmark.v1.json` and preserve fixed tasks, settings, budgets, seeds, metrics, and thresholds. 2. Run `aiwg composition benchmark <manifest.json>`; use `--raw-out` and `--summary-out` to retain both evidence layers. 3. Compare success-conditioned cost and latency, not unconditioned cheap failures. Review speed-of-accuracy and strict-LCM-versus-adaptive deltas. 4. Require an independent or human evaluation path and inspect self-judge bias. 5. Review every failure-injection outcome and recovery receipt. 6. Keep synthetic conformance distinct from provider evidence. Do not open the claim gate without repeated trusted runs, independent evaluation, confidence intervals, and task-family replication.

Composition graphs remain `flow.aiwg.io/v1alpha1` `FlowGraph`; do not introduce a fourth-level DNS API group. Do not request or persist private chain-of-thought.

@implements #2118

Read more
Ships withaiwg

Reusable project context and specialist workflows for the AI tools you already use. Plan software, coordinate specialist reviews, prepare campaigns, investigate incidents, organize research, curate media, and maintain operational knowledge.

Get the whole plugin

Other skills on aiwg.