Conf Pipeline Orchestration

The multi-agent communication and orchestration discipline for a staged pipeline whose stages each carry calibrated uncertainty. Agents talk through files with defined schemas and status fields (never free text); the orchestrator passes input paths plus an explicit output path plus a return contract, verifies each artifact's confidence before advancing a stage gate, holds and integrates worker outputs rather than passing them through, freezes its protected control logic against a checksum, maintains a diversity floor, hardens the fragile handoffs not the resilient hubs, and names the substitut

200 stars 25 forksAI, LLMs & Agents Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add lyndonkl/claude

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add lyndonkl/claude --skill conf-pipeline-orchestration
Manual install
git clone --depth 1 https://github.com/lyndonkl/claude.git /tmp/claude
mkdir -p ~/.claude/skills
cp -r /tmp/claude/skills/conf-pipeline-orchestration ~/.claude/skills/conf-pipeline-orchestration

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Conference Pipeline Orchestration

This skill is the operating discipline for an orchestrator that runs a staged pipeline of specialist agents — for a conference scheduler that is ingest → cluster → elicit → schedule, but the discipline is general. Its single organizing idea is **explicit uncertainty management at every layer**: each stage produces *calibrated confidence, not commitments*, and the orchestrator's whole job is to move that uncertainty forward honestly, integrate it, decide when it is small enough to act on, and refuse to let its own safety machinery be optimized away.

The discipline is drawn from how collectives of interacting agents actually fail. The leverage is not in the loudest stage; it is in the **shape of the communication** between stages and in a few **feedback loops on safety-critical asymmetries**. So the rules below are mostly about the *edges* of the pipeline (how stages talk) and about a small set of *invariants* (what the orchestrator must never let drift), not about making any single stage cleverer.

## Common Patterns

### Pattern 1: Confidence propagates — every stage emits it, the next stage reads it
Read the full skill on GitHub

Details

Skill name
conf-pipeline-orchestration
Path
skills/conf-pipeline-orchestration/SKILL.md
Repo updated
1 September 2026

FAQ

What does the Conf Pipeline Orchestration skill do?

The multi-agent communication and orchestration discipline for a staged pipeline whose stages each carry calibrated uncertainty. Agents talk through files with defined schemas and status fields (never free text); the orchestrator passes input paths plus an explicit output path plus a return contract, verifies each artifact's confidence before advancing a stage gate, holds and integrates worker outputs rather than passing them through, freezes its protected control logic against a checksum, maintains a diversity floor, hardens the fragile handoffs not the resilient hubs, and names the substitut

How do I install the Conf Pipeline Orchestration skill?

Claude Code plugin: /plugin marketplace add lyndonkl/claude. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Conf Pipeline Orchestration popular?

It lives in lyndonkl/claude, which has 200 GitHub stars and 25 forks.

Related skills

Abstraction Concrete Examples

200

lyndonkl/claude

Builds structured abstraction ladders that translate high-level principles into concrete, actionable examples across 3-5 levels. Bridges communication gaps, reveals hidden assumptions, and tests whether abstract ideas work in practice. Use when explaining concepts at different expertise levels, moving between abstract principles and concrete implementation, identifying edge cases by testing ideas against scenarios, designing layered documentation, decomposing complex problems into actionable steps, or bridging strategy-execution gaps.

Testing & QA25

Academic Letter Architect

200

lyndonkl/claude

Guides the creation of evidence-based academic recommendation letters, reference letters, and award nominations that combine concrete examples, meaningful comparisons, and genuine enthusiasm. Use when writing recommendation letters for students, postdocs, or colleagues, or when user mentions recommendation letter, reference, nomination, letter of support, endorsement, or needs help with strong advocacy and comparative statements.

Research & Science25

Adr Architecture

200

lyndonkl/claude

Documents significant architectural and technical decisions with full context, alternatives considered, trade-offs analyzed, and consequences understood. Creates a decision trail that helps teams understand why decisions were made. Use when choosing between technology options, making infrastructure decisions, establishing standards, migrating systems, or when user mentions ADR, architecture decision, technical decision record, or decision documentation.

Software Development25

Context Engineering

213

TerminalSkills/skills

Audits and reorganises what an AI coding agent carries in its context window: instruction files, path-scoped rules, skills, subagents, hooks and the running conversation. Use when someone says "the agent ignores our CLAUDE.md", "set this repo up for Claude Code / Codex / Cursor", "my AGENTS.md is too long", "quality drops in long sessions", "it keeps inventing APIs", "what should go in a skill versus the rules file", or asks how to hand work to a subagent. Grounded in the documented loading behaviour of Claude Code, with the equivalents for Codex, Gemini CLI and Cursor.

AI, LLMs & Agents34

Comet Ml

213

TerminalSkills/skills

Comet ML is a platform for tracking machine learning experiments, managing registered models, and comparing runs. Use when logging experiments, hyperparameters and metrics, registering model versions, or comparing training runs; LLM tracing goes through Comet's Opik. Helps developers log experiments, compare model versions, and build reproducible ML pipelines with automatic code/data versioning.

AI, LLMs & Agents34

Context7

213

TerminalSkills/skills

Context7 fetches current, version-specific documentation and code examples for software libraries and hands them to an AI coding agent, so generated code matches the library version in use instead of stale training data. Use when someone says "use context7", "get the latest docs for this library", "look up the current API", "the agent keeps using a deprecated method", "set up Context7 in Claude Code or Cursor", or asks how to call a framework whose API changed recently. Covers the ctx7 CLI, the MCP server and its two tools, library IDs and version pinning, API keys and rate limits, and the RES

AI, LLMs & Agents34

Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.