{"id":19875,"plugin_id":"plugins_6aa1544694448191bd62b11d68de420e","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:15:54.970Z","digest":"e92319e21f126fa8f28490407bf896d1ec795b02be52478f06cd5b423132c152","against":null,"payload":{"description":"Compile an Open Bible Images brief, research, entities, composition, and character references into a model-neutral image direction and provider-ready prompt package. Use when preparing or revising an image-generation prompt without changing project facts, including private working drafts and feedback-driven revisions.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":288},{"relative_path":"references/prompt-package.md","size_in_bytes":702}],"name":"obi-prompt-generator","skill_md_contents":"---\nname: obi-prompt-generator\ndescription: Compile an Open Bible Images brief, research, entities, composition, and character references into a model-neutral image direction and provider-ready prompt package. Use when preparing or revising an image-generation prompt without changing project facts, including private working drafts and feedback-driven revisions.\n---\n\n# OBI Prompt Generator\n\nPrompts are disposable delivery formats. The approved composition and character records remain authoritative. Read [references/prompt-package.md](references/prompt-package.md).\n\nWhen a canonical project JSON file is supplied, preserve all other sections, update only `prompt_packages`, increment its artifact revision and the project revision, and append a history/capability-run entry. If revision was triggered by feedback or review, link the prompt revision back to the upstream artifact/finding that required it. If no project file is supplied, label the result `unpersisted`.\n\n## Workflow\n\n1. Load the latest relevant artifacts and determine whether this is a private working draft or formal approved use.\n2. Identify the target provider, model, aspect ratio, generation mode, and reference-image capabilities. If no provider is named, default the user-facing prompt to Nano Banana Pro while retaining a model-neutral master direction.\n3. Check whether the requested change is actually a prompt problem. If research, entity, character, or composition data is wrong or unresolved, return the earliest required capability instead of hiding the problem in prompt wording.\n4. Build a model-neutral master direction faithful to the current composition and character records.\n5. Translate it into concise provider-ready instructions, normally 150–400 words and ordered by visual importance. Apply the Research & Create prompt standards: observational documentary realism, natural light, ordinary regionally plausible people, material and environmental realism, practical wear, believable scale, and natural spatial relationships.\n6. Map each reference image to its intended control and prevent unintended transfer of style, clothing, pose, or identity.\n7. Include historically important exclusions and known model failure risks without overwhelming the positive direction.\n8. For feedback-driven revisions, change only prompt instructions affected by the approved upstream revision and preserve unrelated successful instructions.\n9. For a private draft, a working or draft composition may produce a `working_private_draft` prompt with provisional choices preserved. For formal OBI use or costly batch generation, require an approved composition and return an `approved_provider_prompt`. List only material blockers.\n10. If the user explicitly requested an image revision and the prompt is ready, return disposition `needs_generation`; otherwise stop with the updated prompt.\n\n## Boundaries\n\n- Do not introduce new biblical, historical, entity, or composition facts.\n- Do not convert uncertainty into certainty.\n- Do not promise exact compliance from a generative model.\n- Do not use fake inscriptions, halos, fantasy conventions, or anachronisms unless explicitly approved.\n- Do not generate or accept an image unless requested.\n- Do not substitute cinematic spectacle, glamour, uniform beige dirtiness, or a long generic negative list for specific historical direction.\n- Do not patch an upstream factual problem with downstream prompt tricks.\n\nCompletion means the prompt is traceable to its project artifacts and clearly labeled either `working_private_draft` or `approved_provider_prompt`.\n\n## User-facing response\n\nReturn the usable prompt first. Add only essential settings, reference instructions, and up to three risks or decisions. If an upstream issue blocks a trustworthy prompt, state the single earliest action needed, such as **Research this**, **Update character**, or **Revise composition**. Do not repeat the entire project brief or explain every translation choice.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}