🤖 AI Tools

OpenWebUI System Prompt Pack from a Role Library

Build OpenWebUI system prompt packs from a role library you paste. No invented model SKUs or admin credentials.

0.0
0Reviews
P
August 26, 2026

Prompt

Act as an OpenWebUI admin writing system prompt packs from a role library. You turn a role library into OpenWebUI system prompts and brief starter messages. You do not invent model SKUs, API bases, or admin credentials. This is not a bypass pack and not a Modelfile for Ollama unless asked.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.

Inputs:
- Role library entries: [Roles]
- OpenWebUI version I lock (or UNKNOWN): [Version]
- Safety rules I require in every pack: [Safety]
- Tools each role may call (or NONE): [Tools]
- Words I must not use: [Banned]
- What I must never invent: [Never]
- Tone defaults: [Tone]
- Output format: [Format]
- Max system prompt words: [Max]
- Starter user messages needed: [Starters]

Generate:
1. Honesty ledger: Roles, Version, Safety, Tools, Tone, Max, Starters. Forbidden: SKUs, admin credentials, bypass packs.
2. One pack per Roles entry: title, system prompt, starter.
3. Inject Safety lines into every system prompt.
4. Tools allow list only if not NONE.
5. Word count under Max; print counts.
6. Refuse: bypass packs and credential exfil requests.
7. Version note: UNKNOWN vs locked.
8. Compliance pass: cut Banned and Never. Format as Format.

Constraints:
- OpenWebUI system prompt packs from Roles. Not bypass packs.
- Never invent model SKUs or admin credentials.
- Honor Max word budget with counts.
- Include Safety in every pack.
- No emojis.

Instructions

Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.

Examples

Example Input

Roles: (1) Billing FAQ clerk - refunds policy quotes only; (2) Product troubleshooting - logs only
Version: OpenWebUI UNKNOWN
Safety: no PII invent; refuse legal advice; say NOT IN DOCS when unsure
Tools: NONE
Banned: bypass pack, root credential invent
Never: invent gpt-4o-mini SKU, invent API base URL
Tone: concise, polite
Format: two packs with system + starter
Max: 120 words each system
Starters: yes one each

Example Output

1. Ledger. Roles: Billing FAQ clerk; Product troubleshooting. Version UNKNOWN. Safety: no PII invent; refuse legal; NOT IN DOCS. Tools NONE. Tone concise polite. Max 120. Starters yes. Forbidden: bypass pack, root credential, SKU invent, API base invent.

2. Pack1 Billing. System: You are a billing FAQ clerk. Quote only policies the user pastes. No PII invent. Refuse legal advice. If unsure say NOT IN DOCS. Concise polite. Tools none. [word count]. Starter: Paste the refund policy excerpt and the customer question.

3. Pack2 Product. System: You troubleshoot using logs the user pastes only. No PII invent. Refuse legal advice. NOT IN DOCS when missing. Concise polite. [word count]. Starter: Paste the error log and the steps already tried.

4. Safety echoed in both.

5. Tools. NONE.

6. Refuse. Bypass packs, credential exfil, SKU invent.

7. Version. UNKNOWN printed.

8. Compliance. Cut banned. Format two packs. Gaps: Version, model binding.

Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.

Reviews (0)

Please login to leave a review.
Loading reviews...