skills.rest
AllenZhou
AllenZhouCOMMUNITY
Explore all skills by this author →
GitHub

feedback-extractor

Route legacy feedback extraction tasks to the content-agent shim.

Updated Aug 23, 2026
Search Tags:#workflow#migration#deprecation#pipelines#feedback-extraction#shim#content-agent
One-click install
npx skills add https://github.com/AllenZhou/MIRISE --skill feedback-extractor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feedback-extractor
Source: https://github.com/AllenZhou/MIRISE/tree/main/agents/uae-docs-pipeline/skills/feedback-extractor
Command: npx skills add https://github.com/AllenZhou/MIRISE --skill feedback-extractor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically routes legacy feedback-extraction tasks to the content-agent shim to preserve workflows during migration.

Core Features & Use Cases

  • Redirects feedback extraction tasks to the content-agent to maintain compatibility in existing pipelines.
  • Preserves interfaces and prompts while centralizing logic in content-agent.

Quick Start

Route feedback extraction tasks through this shim to the content-agent.

Frequently Asked Questions about feedback-extractor

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

FAQPage Schema
How do I redirect legacy feedback extraction tasks during a workflow migration?▼

Redirect legacy feedback extraction tasks by routing them through a shim to the content-agent, which preserves existing pipelines and maintains workflow continuity during migration.

What is a shim and how does it handle feedback extraction deprecation?▼

A shim delegates feedback extraction tasks to the content-agent, preserving existing interfaces and prompts while centralizing logic to handle deprecation without breaking tooling.

Do I need additional dependencies to route feedback extraction to the content-agent?▼

No additional dependencies are required to route feedback extraction to the content-agent, as the shim uses existing project context and delegates directly to the content-agent interfaces.

Can I maintain existing pipeline compatibility when migrating feedback extraction logic?▼

Yes, you can maintain pipeline compatibility by using a shim that redirects feedback extraction tasks to the content-agent, preserving interfaces and prompts while centralizing the logic.

What's the best way to centralize feedback extraction logic without breaking existing tooling?▼

The best way to centralize logic without breaking tooling is implementing a shim that redirects feedback extraction tasks to the content-agent, preserving existing interfaces and prompts.

Why does my feedback extraction pipeline need a shim for content-agent migration?▼

Your feedback extraction pipeline needs a shim to maintain compatibility during migration, ensuring existing tooling and pipelines continue functioning by delegating tasks to the content-agent.

Related Skills

Explore More Software Engineering Skills→
hohai99hohai99

system-context-extractor

Extracts architectural, business, and operational context from systems into dependency maps and graphs.

Community
Basic
vrcmsvrcms
1

santa-method

Validate AI-generated outputs through dual-agent adversarial review against objective rubrics.

Community
Advanced
1Mangesh11Mangesh1
3

api-versioning

Plan API versioning strategies for RESTful endpoints with migration steps.

Community
Advanced
leogallegoleogallego
1

compose-slot-api-pattern

Refactors Jetpack Compose components to replace primitive parameters with slot-based @Composable () -> Unit content delegates.

Community
Intermediate