provider-openai-proxy-user-corrections

Extract user corrections into reusable rules for OpenCode proxy workflows.

171|10|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/fmflurry/settings-opencode --skill provider-openai-proxy-user-corrections
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: provider-openai-proxy-user-corrections
Source: https://github.com/fmflurry/settings-opencode/tree/main/.claude/skills/provider-openai-proxy-user-corrections
Command: npx skills add https://github.com/fmflurry/settings-opencode --skill provider-openai-proxy-user-corrections

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translates recurring user feedback into concrete, reusable correction rules that guide OpenCode AI proxy behavior and decisions.

Core Features & Use Cases

  • Extract corrections as concrete rules from user feedback and logs.
  • Apply the rules to current work and nearby decisions to ensure consistency across prompts.
  • Re-validate outputs against updated expectations and capture corrections for future reuse.

Quick Start

Create a correction rule from recent user feedback and apply it to your prompts so future outputs follow the rule.

Frequently Asked Questions about provider-openai-proxy-user-corrections

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

FAQPage Schema
How do I translate user feedback into concrete rules for AI proxy workflows?

To translate user feedback into concrete rules for AI proxy workflows, you extract recurring corrections from logs and feedback. This process converts user input into reusable guidance that shapes proxy behavior and ensures output consistency.

How do I apply user corrections to ongoing AI proxy decisions?

You apply user corrections to ongoing AI proxy decisions by integrating extracted rules into current work and nearby decisions. This ensures that user feedback is systematically enforced across active prompts and outputs during the session.

What is the best way to capture recurring user corrections for future reuse?

The best way to capture recurring user corrections for future reuse is to extract them as concrete, pattern-based rules. By revalidating outputs against updated expectations, you systematically store the guidance to enforce consistency in later AI proxy tasks.

Can I use pattern-based user corrections to revalidate previous outputs?

Yes, you can use pattern-based user corrections to revalidate previous outputs. The mechanism re-validates generated content against newly extracted rules and updated expectations, ensuring prior decisions align with the latest user feedback.

Does the user correction feedback loop work without external dependencies?

Yes, the user correction feedback loop operates without external dependencies. It functions independently to extract correction rules from user feedback, apply them to ongoing proxy work, and capture the guidance for reuse within your environment.