test-opencode-tooling

Classify tool-call failures between OpenCode and afm during automated testing.

324|17|Updated Aug 8, 2025
One-click install
npx skills add https://github.com/scouzi1966/maclocal-api --skill test-opencode-tooling
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-opencode-tooling
Source: https://github.com/scouzi1966/maclocal-api/tree/main/.claude/skills/test-opencode-tooling
Command: npx skills add https://github.com/scouzi1966/maclocal-api --skill test-opencode-tooling

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams diagnose and classify tool-call failures between OpenCode and afm during automated testing, producing a clear diagnostic report without modifying any runtime behavior.

Core Features & Use Cases

  • Automated paired testing runs OpenCode tasks against afm to surface tool-call errors in a reproducible loop.
  • Error classification distinguishes afm translation bugs from model generation errors to guide debugging focus.
  • Diagnostic reporting compiles structured results that highlight root causes and suggest next steps without applying fixes.

Quick Start

Start an OpenCode run against a running afm instance and generate the diagnostic report for your current test prompt.

Frequently Asked Questions about test-opencode-tooling

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

FAQPage Schema
How do I diagnose tool-call failures between OpenCode and afm?

To diagnose tool-call failures, run automated paired testing against a running afm instance to surface errors and compile a structured diagnostic report highlighting root causes without modifying runtime behavior.

What is automated tool-call reliability testing for model onboarding?

Automated tool-call reliability testing runs OpenCode tasks against afm to surface generation or translation errors in a reproducible loop, validating new model integrations and parser updates across prompts.

Do I need a running OpenCode server to classify afm translation bugs?

Yes, you need a running OpenCode server and an active afm instance. The Skill requires a traceable tool-call pipeline to distinguish afm translation bugs from model generation errors.

Can I use diagnostic reporting to fix model generation errors during regression validation?

Diagnostic reporting classifies model generation errors and afm translation bugs to guide debugging focus, but it does not apply fixes. It compiles structured results suggesting next steps without modifying runtime behavior.

Why does my OpenCode tool-call pipeline fail across different prompts during cross-model experiments?

Cross-model reliability experiments often surface tool-call failures due to afm translation bugs or model generation errors. Running automated paired testing identifies and classifies these specific failure points for debugging.