content-expert

Name: content-expert
Availability: InStock
Author: Allen

Redirect deprecated content-expert calls to the content-agent writing workflow.

Updated Aug 27, 2026

Search Tags:#writing #integration #deprecated #workflows #redirect #shim #content-agent

Ready to run

npx skills add https://github.com/AllenZhou/MIRISE --skill content-expert

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: content-expert
Source: https://github.com/AllenZhou/MIRISE/tree/main/agents/uae-docs-pipeline/skills/content-expert
Command: npx skills add https://github.com/AllenZhou/MIRISE --skill content-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill acts as a redirect shim, guiding users from the deprecated content-expert to the unified content-agent writing workflow.

Core Features & Use Cases

Redirects legacy calls to content-agent to preserve workflow continuity.
Serves as a transition guide for teams migrating to content-agent's writing modes.
Use Case: A developer or writer who previously invoked content-expert can seamlessly switch to content-agent without code changes.

Quick Start

Read the content-agent SKILL.md and use its section 1 writing mode for all writing tasks.

Frequently Asked Questions about content-expert

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

FAQPage Schema

How do I migrate deprecated writing workflows to a unified agent?▼

A redirect shim maps deprecated content-expert calls to the unified content-agent writing workflow, ensuring workflow continuity. You simply read the content-agent SKILL.md and use its section 1 writing mode for all writing tasks.

What is a redirect shim and how does it work for deprecated integrations?▼

A redirect shim is a transition layer that maps deprecated integrations to a canonical source. It points legacy calls to the content-agent SKILL.md, ensuring continuity of writing tasks without code changes.

Do I need to change my code to switch from a legacy writing agent?▼

No, you do not need to change your code to switch from a legacy writing agent. The redirect shim seamlessly maps deprecated content-expert calls to the content-agent writing workflow, preserving integration requirements automatically.

What is the best way to handle deprecated content agent transitions?▼

The best way to handle deprecated content agent transitions is to apply a redirect shim that points directly to the unified content-agent SKILL.md, serving as a transition guide for teams migrating writing modes.

Why does my legacy content writing workflow need a redirect?▼

Your legacy content writing workflow needs a redirect to ensure seamless mapping to the unified content-agent. This preserves workflow continuity and satisfies integration requirements by pointing to the canonical SKILL.md source.