Skip to content
Back to skills

Composition Evaluate

ASecurity

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

  • 211 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 21, 2026
ai-agentsrustapi

Works with

  • api

Security analysis

A100/100

Scanned September 21, 2026

npx -y skills add jmagly/ai-writing-guide --skill composition-evaluate --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Composition Evaluate?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Composition Evaluate
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jmagly-composition-evaluate-aiwg/badge)](https://www.skillsdirectory.com/skills/jmagly-composition-evaluate-aiwg)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
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

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.