image-batch-runner
Run fact-grounded image generation batches for short-form video production, especially persona images, first-frame candidates, and light consistency edits. Use this when persona and concept inputs already exist and you need local image assets, prompt records, and reusable model-call metadata. This skill should stay anchored to benchmark-backed persona locks and should save both raw provider responses and normalized local asset manifests.
What this skill does
# Image Batch Runner ## Use When - Persona, concept, or shot inputs already exist and the next step is a hosted image generation, edit, upload, or poll run. - The output must include local image files plus request, response, attempt, and manifest records for later QA or video rendering. ## Do Not Use When - The task belongs to ideation, QA, or another released skill listed in the handoff section. - Required inputs are missing and guessing would change the result. - Creative classification, model/reference policy, or storyboard logic is still unresolved. Use `image-generation` first. ## Execution Boundary - This runner validates and executes normalized requests. It must not make creative strategy, task-classification, or reference-policy decisions. - Default model is `image-gpt-image-2-text`; edits default to `image-gpt-image-2-edit`. - Default creative format is `short_form_vertical` with `aspectRatio: "9:16"`, `quality: "medium"`, `resolution: "1k"`, and async execution (`enableSyncMode: false`). - For Instagram Meta Ads, set `creativeFormat: "instagram_meta_ads"` or an explicit `aspectRatio: "3:4"` in the normalized request, not only in prompt wording. - Switch model, ratio, quality, resolution, or sync mode only when the user asks or the upstream brief explicitly marks a draft or provider constraint. ## Source And Path - Ground every request in a benchmark-backed persona lock, concept or shot need, visual constraints, `assetPurpose`, and `sourceBasis`. - Use source files from the active project/client folder first. Do not treat one client directory as the default for all image work. - Store internal request, response, and polling state under `.postplus` when it is not the user-facing handoff; keep final images and manifests in the active asset folder. If no asset folder exists, choose one explicit workspace path. ## Request Boundary - Hosted media requests require a capability request JSON with explicit `capability`, `operation`, `operationId`, and normalized `input`. - Required request fields: `assetId`, `runId`, `localAssetDir`, `prompt`, `assetPurpose`, and `sourceBasis`. - Use canonical fields only; do not accept `jobId` or `localOutputDir` as image request fallbacks. Upload or reference local source files explicitly before requesting edits. ## Review And Handoff - Before submission, verify persona grounding, asset purpose, source basis, local output path, and what must stay fixed versus vary. - After generation, check realism, benchmark fit, repeatability across videos, copied-creator risk, and ad-like drift. - If processing is still pending, return the manifest/request paths and the status command to poll. ## Stop Conditions - Stop when required user intent, source evidence, or owned input artifacts are missing and guessing would change the result. - If an owned CLI or script command fails, report the exact error and stop. Do not bypass the failure with metadata-only answers, readiness probing, local payload rewrites, fallback providers, or unpublished tools. ## Public Command Boundary - Choose the smallest matching command or workflow from the user input and run it directly. - Readiness diagnostics: `postplus doctor --skill image-batch-runner`. - If an owned CLI or script command fails, report the exact error and stop. Do not bypass the failure with metadata-only answers, readiness probing, local payload rewrites, fallback providers, or unpublished tools. - Use `postplus media schema --json` only when constructing or repairing an unknown request shape. - Hosted media capability: `postplus media capability --request <hosted-capability-request.json> --output <result.json>`. - Use the capability request shape required by the selected workflow; do not call provider APIs directly. - If the CLI returns a quote-confirmation challenge, run `postplus quote confirm --json --challenge-file <challenge.json>` and retry with the returned token.
Related in Image & Video
watch
IncludedWatch a video (URL or local path). Downloads with yt-dlp, extracts auto-scaled frames with ffmpeg, pulls the transcript from captions (or Whisper API fallback), and hands the result to Claude so it can answer questions about what's in the video.
physical-ai-defect-image-generation
IncludedUse when the user wants to orchestrate defect image generation, run associated setup, or handle outputs on OSMO. The Day 0 path handles cold-start with USD-to-ROI, image-edit augmentation, and AnomalyGen to create initial PCBA datasets. The Day 1 path performs inference and labeling on real images. This skill helps with first-time asset setup, creation of finetuning checkpoints, and configuring deployment. Trigger keywords: defect image generation, dig workflow, dig pipeline, defect image detection workflow, aoi pipeline, aoi anomalygen, usd2roi anomalygen, day 0 pcba, day 1 pcba, day 1 real-photo alignment, day 1 manual roi, metal surface anomaly, glass defect, anomalygen finetune, setup_pcb, setup_metal, setup_glass, setup_pretrained, dig setup, dig datasets, dig pretrained checkpoint, dig image-edit endpoint.
accelint-react-best-practices
IncludedReact performance optimization and best practices. ALWAYS use this skill when working with any React code - writing components, hooks, JSX; refactoring; optimizing re-renders, memoization, state management; reviewing for performance; fixing hydration mismatches; debugging infinite re-renders, stale closures, input focus loss, animations restarting; preventing remounting; implementing transitions, lazy initialization, effect dependencies. Even simple React tasks benefit from these patterns. Covers React 19+ (useEffectEvent, Activity, ref props). Triggers - useEffect, useState, useMemo, useCallback, memo, inline components, nested components, components inside components, re-render, performance, hydration, SSR, Next.js, useDeferredValue, combined hooks.
elevenlabs-agents
IncludedBuild conversational AI voice agents with ElevenLabs Platform using React, JavaScript, React Native, or Swift SDKs. Configure agents, tools (client/server/MCP), RAG knowledge bases, multi-voice, and Scribe real-time STT. Use when: building voice chat interfaces, implementing AI phone agents with Twilio, configuring agent workflows or tools, adding RAG knowledge bases, testing with CLI "agents as code", or troubleshooting deprecated @11labs packages, Android audio cutoff, CSP violations, dynamic variables, or WebRTC config. Keywords: ElevenLabs Agents, ElevenLabs voice agents, AI voice agents, conversational AI, @elevenlabs/react, @elevenlabs/client, @elevenlabs/react-native, @elevenlabs/elevenlabs-js, @elevenlabs/agents-cli, elevenlabs SDK, voice AI, TTS, text-to-speech, ASR, speech recognition, turn-taking model, WebRTC voice, WebSocket voice, ElevenLabs conversation, agent system prompt, agent tools, agent knowledge base, RAG voice agents, multi-voice agents, pronunciation dictionary, voice speed control, elevenlabs scribe, @11labs deprecated, Android audio cutoff, CSP violation elevenlabs, dynamic variables elevenlabs, case-sensitive tool names, webhook authentication
humanizer
IncludedHumanize AI-generated text by detecting and removing patterns typical of LLM output. Rewrites text to sound natural, specific, and human. Uses 28 pattern detectors, 560+ AI vocabulary terms across 3 tiers, and statistical analysis (burstiness, type-token ratio, readability) for comprehensive detection. Use when asked to humanize text, de-AI writing, make content sound more natural/human, review writing for AI patterns, score text for AI detection, or improve AI-generated drafts. Covers content, language, style, communication, and filler categories.
generating-mermaid-diagrams
IncludedSalesforce architecture diagrams using Mermaid with ASCII fallback. Use this skill when generating text-based diagrams for Salesforce architecture, OAuth flows, ERDs, integration sequences, or Agentforce structure. TRIGGER when: user says "diagram", "visualize", "ERD", or asks for sequence diagrams, flowcharts, class diagrams, or architecture visualizations in Mermaid. DO NOT TRIGGER when: user wants PNG/SVG image output (use generating-visual-diagrams), or asks about non-Salesforce systems.