agent-contracts-routing-tuning

Étoiles12

Forks0

Mis à jour17 janvier 2026 à 10:31

Tune routing with TriggerCondition priorities, LLM hints, context_builder, and traceable decisions.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

yatarousan0227

yatarousan0227/agent-contracts

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

4 fichiers

SKILL.md

readonly

name	agent-contracts-routing-tuning
description	Tune routing with TriggerCondition priorities, LLM hints, context_builder, and traceable decisions.
metadata	{"short-description":"Routing design and debugging"}

agent-contracts Routing Tuning

Use this skill when you are designing or debugging routing behavior (rule matches vs LLM selection).

Routing Model (what to optimize)

Rule filtering via TriggerCondition (when / when_not, priority)
Candidate selection (top matches + ties)
Optional LLM decision among candidates (with llm_hint)
Fallbacks and terminal states (response.response_type)

Practical Tuning Steps

Make rule-based selection deterministic first (LLM off).
Use priorities to express business rules (100+ = critical, 50-99 = main, 1-49 = fallback).
Add llm_hint only where ambiguity remains after rules.
Use context_builder only when needed; keep default minimal slices.
Debug with decide_with_trace() and inspect matched rules.

Guardrails

Prefer rules for safety/constraints; use LLM for ambiguous intent.
Keep candidate sets small and explainable.
Treat response.response_type terminal values as part of routing design.

References (load only when needed)

docs/core_concepts.md (Traceable Routing / Context Builder)
examples/02_routing_explain.py
docs/skills/official/agent-contracts-routing-tuning/references/debug_playbook.md

Plus depuis ce dépôt

même dépôt

agent-contracts-app-builder

yatarousan0227/agent-contracts

Build a production-minded AI agent using agent-contracts (contracts, slices, validation, graph, runtime, CLI tooling).

2026-01-1712

agent-contracts-backend-runtime

yatarousan0227/agent-contracts

Build an API-oriented agent using AgentRuntime/StreamingRuntime with predictable request/response slices and session support.

2026-01-1712

agent-contracts-contracts-ci

yatarousan0227/agent-contracts

Make contract-driven agents safe to change with strict validation, architecture docs, and contract diffs in CI.

2026-01-1712

agent-contracts-interactive-flow

yatarousan0227/agent-contracts

Build question/answer style agents using InteractiveNode, explicit routing, and workflow slices.

2026-01-1712

agent-contracts-tool-use-rag

yatarousan0227/agent-contracts

Implement tool-using or retrieval-style nodes with services, dependency injection, and safe LLM context building.

2026-01-1712

name	agent-contracts-routing-tuning
description	Tune routing with TriggerCondition priorities, LLM hints, context_builder, and traceable decisions.
metadata	{"short-description":"Routing design and debugging"}

agent-contracts Routing Tuning

Use this skill when you are designing or debugging routing behavior (rule matches vs LLM selection).

Routing Model (what to optimize)

Rule filtering via TriggerCondition (when / when_not, priority)
Candidate selection (top matches + ties)
Optional LLM decision among candidates (with llm_hint)
Fallbacks and terminal states (response.response_type)

Practical Tuning Steps

Make rule-based selection deterministic first (LLM off).
Use priorities to express business rules (100+ = critical, 50-99 = main, 1-49 = fallback).
Add llm_hint only where ambiguity remains after rules.
Use context_builder only when needed; keep default minimal slices.
Debug with decide_with_trace() and inspect matched rules.

Guardrails

Prefer rules for safety/constraints; use LLM for ambiguous intent.
Keep candidate sets small and explainable.
Treat response.response_type terminal values as part of routing design.

References (load only when needed)

docs/core_concepts.md (Traceable Routing / Context Builder)
examples/02_routing_explain.py
docs/skills/official/agent-contracts-routing-tuning/references/debug_playbook.md