harness-model-protocol

Map internal message objects to provider-specific wire formats for LLM interactions.

5|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/Dowwie/agent_framework_study --skill harness-model-protocol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-model-protocol
Source: https://github.com/Dowwie/agent_framework_study/tree/main/.claude/skills/harness-model-protocol
Command: npx skills add https://github.com/Dowwie/agent_framework_study --skill harness-model-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Harness-Model Protocol Skill analyzes the interface layer between agent harnesses and LLMs, focusing on wire formats, message encoding, and protocol semantics to ensure reliable tool usage and provider interoperability.

Core Features & Use Cases

  • Map wire-format variants across providers (OpenAI/Anthropic/Gemini) and identify translation points.
  • Evaluate streaming, tool_call encoding, and multi-provider abstraction strategies to guide robust integration.
  • Use Case: When integrating a new LLM provider, generate a compatibility assessment and a translation blueprint for internal message formats.

Quick Start

Use harness-model-protocol to inspect how internal messages become provider-native requests and how streaming tool calls are parsed.

Frequently Asked Questions about harness-model-protocol

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I map internal message objects to provider-specific wire formats for LLM integration?

Map internal message objects to provider-specific wire formats by identifying translation points and applying explicit mapping rules. This ensures internal messages become provider-native requests correctly across different LLMs.

What's the best way to parse streaming tool calls across multi-provider LLM integrations?

Parse streaming tool calls by applying streaming parsing logic to evaluate multi-provider abstraction strategies. This guides robust integration by decoding how streaming tool call encoding works across different LLM providers.

How do message roles like system, user, assistant, and tool work in LLM wire protocols?

Message roles in LLM wire protocols work through clear role handling across system, user, assistant, and tool messages. Translating these roles correctly ensures proper protocol semantics and reliable tool usage in agent harnesses.

How do I generate a compatibility assessment for integrating a new LLM provider?

Generate a compatibility assessment for a new LLM provider by evaluating wire-format variants across OpenAI, Anthropic, and Gemini. This produces a translation blueprint for internal message formats to ensure interoperability.

Does this approach support OpenAI, Anthropic, and Gemini wire formats?

Yes, this approach supports mapping wire-format variants across OpenAI, Anthropic, and Gemini providers. It identifies translation points to ensure correct parsing and execution of tool calls and streaming interactions.