Verified:GitHub

authoring-extractors

Create custom error extractors for vibe-validate from raw tool outputs.

3|Updated Oct 16, 2025

Search Tags:#validation #tool-integration #plugin-development #extractors #error-extraction #log-parsing #custom-extractor

Ready to run

npx skills add https://github.com/jdutton/vibe-validate --skill authoring-extractors

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: authoring-extractors
Source: https://github.com/jdutton/vibe-validate/tree/main/docs/skills/authoring-extractors
Command: npx skills add https://github.com/jdutton/vibe-validate --skill authoring-extractors

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When validation fails but extraction is missing or garbled, this skill guides how to author custom extractors that transform raw tool outputs into structured error lists. It covers built-in extractors, the plugin system, and the workflow for creating and wiring new extractors with vv create-extractor and the vibe-validate configuration.

Core Features & Use Cases

Provide custom detect() and extract() implementations to translate tool output into a stable, structured error model.
Leverage the plugin system to author, test, and share extractors for new languages, build tools, and proprietary workflows.
Use scaffolding, testing fixtures, and config wiring to integrate extractors into vibe-validate workflows across teams and projects.

Quick Start

Run vv create-extractor <tool> to scaffold a new extractor and register it with vibe-validate.

Frequently Asked Questions about authoring-extractors

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

FAQPage Schema

How do I parse custom tool output into structured errors when validation fails?▼

Authoring custom error extractors lets you implement detect() and extract() hooks to reliably transform raw tool outputs into structured errors. This solves missing or garbled validation results when wiring support for new tools, languages, or build systems into your workflow.

How do I scaffold a new extractor for vibe-validate?▼

To scaffold a new extractor for vibe-validate, run the command vv create-extractor <tool>. This generates the required custom detect() and extract() implementations and registers the plugin in the vibe-validate configuration so teams can reuse and share it.

What is an error extractor plugin and when do I need one?▼

An error extractor plugin translates raw tool outputs into a stable, structured error model during validation. You need one when validation reports failures but extraction is missing or garbled, or when wiring support for new tools, languages, or build systems.

Can I use custom extractors with new build systems and languages?▼

Yes, custom extractors support new languages, build tools, and proprietary workflows. By leveraging the plugin system, you can author, test with fixtures, and share extractors to integrate tool outputs into vibe-validate workflows across teams and projects.

Why does my validation report failures but error extraction is garbled?▼

Error extraction is garbled when the built-in extractors cannot parse the raw tool output format. You must author a custom extractor with specific detect() and extract() implementations to reliably transform the tool output into structured errors.

Do I need to manually register a custom extractor in configuration files?▼

Registration depends on your scaffolding workflow. Using vv create-extractor automatically scaffolds and registers the extractor in the vibe-validate config, while manually authored plugins require explicit configuration wiring to ensure reuse across projects.