add-prompt-enhancement-guide

Author and deploy per-ecosystem prompt-enhancement system prompts for the orchestrator's prompt-analysis service.

7.2k|734|Updated Oct 11, 2022
One-click install
npx skills add https://github.com/civitai/civitai --skill add-prompt-enhancement-guide
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: add-prompt-enhancement-guide
Source: https://github.com/civitai/civitai/tree/main/.claude/skills/add-prompt-enhancement-guide
Command: npx skills add https://github.com/civitai/civitai --skill add-prompt-enhancement-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Onboarding a new image or video generation ecosystem (e.g. a new Flux variant or Wan video version) requires writing a tuned system prompt for the prompt-analysis service, and doing it ad hoc produces guides that drift from the model's real behavior or saturate the analyzer with repetitive recommendations.

Core Features & Use Cases

  • Guide authoring workflow: Researches the ecosystem from a model card or spec, maps findings to a fixed guide template, and enforces measured tone rules (no absence-check guidelines, no emphatic capability claims, no out-of-payload conditions).
  • Measurement and audit tooling: measure.mjs A/B-tests a candidate guide against the live one using topic-saturation metrics, and audit.mjs statically screens every live guide for known defect patterns.
  • Safe deployment: manage.mjs registers, updates, exports, and rolls back guides on the orchestrator's /v1/manager/prompt-analysis endpoints with write gating, readback polling, and sample preservation.
  • Use Case: When a new video model like MiniMax H3 ships, provide its ecosystem key and HuggingFace model card, and the skill drafts a guide consistent with sibling ecosystems, measures it against the live baseline, and deploys it with few-shot samples.

Quick Start

Ask the assistant to add a prompt-enhancement guide for a new ecosystem, providing the ecosystem key from basemodel.constants.ts and a link to the model card or prompting documentation.

Frequently Asked Questions about add-prompt-enhancement-guide

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

FAQPage Schema
How do I add a prompt-enhancement guide for a new model ecosystem?▼

Provide the ecosystem key from packages/civitai-shared/src/basemodel.constants.ts (lowercased) plus a reference URL or model description. The skill researches the model, drafts a guide following the standard template, asks for your sign-off, then deploys it with manage.mjs put.

How do I test a prompt-analysis guide before deploying it?▼

Run measure.mjs with --ecosystem and --candidate to A/B the draft against the live guide on a shared prompt corpus. Use --runs 6 for deployment decisions, since the metric has a measured noise floor of plus or minus one saturated topic.

Which ecosystems are out of scope for prompt-enhancement guides?▼

3D and audio modalities are explicitly out of scope: tripo, hunyuan3d, polygen, and ace stay on the built-in default. The guide template only describes image and video prompting concepts like subject, lighting, camera, and composition.

Why does the ecosystem key differ from the engine name?▼

The key is the AIR ecosystem value lowercased, derived from getRootEcosystem, so child ecosystems like Pony or Illustrious resolve to their parent sdxl. Guides filed under an engine name or a child ecosystem are never read by the prompt-analysis service.

Why did my guide deploy seem to fail right after a successful write?▼

Orchestrator writes take up to a minute to propagate, so immediate readbacks report both false failures and false successes. The put and set-samples commands poll the readback for 30 seconds; re-check with status before rewriting.

What are few-shot samples and when should I add them?▼

Samples are prompt/assistantResponse triples replayed as conversation turns on every request for that ecosystem. Add them for judgement calls prose cannot state, such as handling already-good prompts, and keep them to two or three since they consume context on every call.