メニュー
General content-utility prompts — the writer-persona system prompt, content summarization, and free-form content-to-JSON conversion. Use for the writer system role, condensing content, or coercing content into structured JSON.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
TTS pronunciation configuration. Controls how written text is normalized to natural spoken English before being passed to the Speaches/Kokoro TTS engine. Two DB-configurable app_settings keys let operators add or override pronunciation rules without code changes.
Image-direction prompts for the content pipeline. Generate featured-image prompts, build stock image search queries, run the image-director reasoning that picks which sections get visuals (image_gen vs pexels, style, and prompt/query for each) plus one featured hero image, and caption rendered images with vision-derived alt text.
Generate a native, community-appropriate Reddit value-post from a published blog post
Blog drafting & revision prompts. Turn a topic + research context into a publication-ready markdown article, then refine it against reviewer feedback. Includes the writer system prompt, the draft request, the anti-fabrication initial-draft prompt, an SEO-metadata helper, and the iterative-refinement prompt. Use during the content-generation stage of the pipeline.
Video director — given a post body + podcast script + target duration, produces a JSON shot list (ordered shots with per-shot source plugin, prompt/query, and duration) for the post's video. Enforces the no-AI-humans + stylized-not-photoreal policies. Used by the generate_video_shot_list pipeline stage. Operator brand is templated via {site_name}.
Classify a published post into brand content-types (multi-label). Populates post_content_types via ClassifyContentTypesJob.
| name | utility |
| description | General content-utility prompts — the writer-persona system prompt, content summarization, and free-form content-to-JSON conversion. Use for the writer system role, condensing content, or coercing content into structured JSON. |
| license | Apache-2.0 |
| metadata | {"category":"utility","prompts":[{"key":"system.content_writer","output_format":"markdown","description":"Default writer-persona system prompt — basic but functional; production-quality prompt packs ship as a premium add-on"},{"key":"task.content_summarization","output_format":"text","description":"Summarize content concisely — basic but functional; production-quality prompt packs ship as a premium add-on"},{"key":"task.utility_json_conversion","output_format":"json","description":"Convert free-form content into structured JSON — basic but functional; production-quality prompt packs ship as a premium add-on"},{"key":"task.affiliate_derive_keywords","output_format":"json","description":"Derive a short display name + keyword aliases for an affiliate-catalog product from its long marketing title + description -> {display_text, keywords} JSON. Used by `poindexter affiliate import-csv`."}]} |
General-purpose content prompts the pipeline falls back to when no
premium prompt pack is provisioned. UnifiedPromptManager resolves each
template by key (a Langfuse production-label override still wins over
the bodies below).
Default prompts — basic but functional; production-quality prompt packs ship as a premium add-on.
You are a content writer. Write in a {style} style for {target_audience}.
Domain: {domain}. Tone: {tone}. Target length: ~{target_length} words.
Format output as clean Markdown with proper headings.
Summarize this content concisely: {content}
Convert this content to structured JSON: {content}
You are naming and tagging a product for an affiliate-link catalog.
Given the product title and description below, respond with ONLY a JSON
object: {{"display_text": "<short human name, 2-6 words>", "keywords":
["<alias 1>", "<alias 2>", ...]}}
- display_text: a short, natural name a reader would recognize (not the
full marketing title).
- keywords: 3 to 6 short phrases (1-4 words each) that might plausibly
appear in prose referring to this product - brand names, model numbers,
common nicknames. Avoid generic single words that could describe many
products.
Title: {title}
Description: {description}