How do I install the Text Generation skill?

Run npx skillmds@latest add video-production-buddy/text-generation in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Text Generation safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Text Generation?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Text Generation free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Text Generation?

video-production-buddy (@video-production-buddy) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Text Generation by video-production-buddy

Name: Text Generation
Author: video-production-buddy

Text Generation

Use when routing standalone ad-hoc text generation to Qwen or MiniMax provider tools, including setup, model choice, cost discipline, output persistence, and the boundary that the agent remains the primary reasoner.

File contents

Text Generation Provider Calls

Use this skill for standalone text-generation provider tools:

qwen_chat
minimax_chat

These tools are optional provider calls for bounded text sub-tasks. They do not replace the coding assistant or become a Python pipeline orchestrator.

Boundary

Video Production Buddy is agent-first. The agent remains the primary reasoner and owner of pipeline decisions, artifacts, validation, and checkpoint writes.

Use text-generation tools only when a specific bounded text job benefits from a billed provider call, such as:

bulk script polishing
translation variants
long-document summarization
style rewrites
structured copy alternatives

Do not auto-wire these tools into pipeline stages. Do not use them to bypass stage director skills, artifact schemas, reviewer skills, checkpoint policy, or human approval gates.

Provider Setup

qwen_chat requires DASHSCOPE_API_KEY and calls Bailian / DashScope's OpenAI-compatible chat-completions endpoint.

minimax_chat requires MINIMAX_API_KEY. The default API base is the China-mainland MiniMax host; use MINIMAX_API_BASE when an overseas host is required.

Both providers are network API tools. Confirm setup through the tool status or provider_menu_summary() before proposing them as available.

Model Choice

Use Qwen when the task needs Qwen's long-context models, strong Chinese and multilingual handling, or Qwen Coder.

Use MiniMax when the task needs MiniMax-M3/M2.7 behavior, MiniMax account routing, or multimodal message support exposed by the provider.

Prefer the lower-cost or faster model for drafts and alternatives. Reserve the highest-quality model for final polish, difficult reasoning, or long-context review.

Output Persistence

When output_path is provided, it must be project-scoped and should point under projects/<project-name>/artifacts/..., projects/<project-name>/assets/..., or projects/<project-name>/renders/... as accepted by the tool.

Persist outputs when the generated text becomes evidence, a draft artifact, or an input to later review. For one-off exploratory calls, returning the text in the ToolResult is enough.

Cost Discipline

Keep prompts narrow and explicit. Include only the source text and constraints needed for the sub-task. Avoid sending secrets, credentials, private keys, personal contact/payment data, or unrelated project files.

Record provider, model, token counts, output path, and cost from the tool result when the call contributes to a production artifact.

---name: text-generationdescription: Use when routing standalone ad-hoc text generation to Qwen or MiniMax provider tools, including setup, model choice, cost discipline, output persistence, and the boundary that the agent remains the primary reasoner.---# Text Generation Provider CallsUse this skill for standalone text-generation provider tools:- `qwen_chat`- `minimax_chat`These tools are optional provider calls for bounded text sub-tasks. They do notreplace the coding assistant or become a Python pipeline orchestrator.## BoundaryVideo Production Buddy is agent-first. The agent remains the primary reasonerand owner of pipeline decisions, artifacts, validation, and checkpoint writes.Use text-generation tools only when a specific bounded text job benefits from abilled provider call, such as:- bulk script polishing- translation variants- long-document summarization- style rewrites- structured copy alternativesDo not auto-wire these tools into pipeline stages. Do not use them to bypassstage director skills, artifact schemas, reviewer skills, checkpoint policy, orhuman approval gates.## Provider Setup`qwen_chat` requires `DASHSCOPE_API_KEY` and calls Bailian / DashScope'sOpenAI-compatible chat-completions endpoint.`minimax_chat` requires `MINIMAX_API_KEY`. The default API base is theChina-mainland MiniMax host; use `MINIMAX_API_BASE` when an overseas host isrequired.Both providers are network API tools. Confirm setup through the tool status or`provider_menu_summary()` before proposing them as available.## Model ChoiceUse Qwen when the task needs Qwen's long-context models, strong Chinese andmultilingual handling, or Qwen Coder.Use MiniMax when the task needs MiniMax-M3/M2.7 behavior, MiniMax accountrouting, or multimodal message support exposed by the provider.Prefer the lower-cost or faster model for drafts and alternatives. Reserve thehighest-quality model for final polish, difficult reasoning, or long-contextreview.## Output PersistenceWhen `output_path` is provided, it must be project-scoped and should point under`projects/<project-name>/artifacts/...`, `projects/<project-name>/assets/...`,or `projects/<project-name>/renders/...` as accepted by the tool.Persist outputs when the generated text becomes evidence, a draft artifact, oran input to later review. For one-off exploratory calls, returning the text inthe `ToolResult` is enough.## Cost DisciplineKeep prompts narrow and explicit. Include only the source text and constraintsneeded for the sub-task. Avoid sending secrets, credentials, private keys,personal contact/payment data, or unrelated project files.Record provider, model, token counts, output path, and cost from the toolresult when the call contributes to a production artifact.

Frequently asked questions