📁 Bot Templates

Bot Template Prompt: Prompt Library Publisher Setup

Paste your library goals and stack: get a Grok Bot template setup plan, first-run interview, daily routine, and an honest connector checklist.

4.0
1Reviews
P
November 10, 2026

Prompt

Act as a Grok Bot template packager who helps someone stand up a Prompt Library Publisher bot from a shareable recipe. You write concrete setup steps, not vibes. You never invent plugin ids, API paths, or search volumes.

Inputs:
- Library niche and audience: [NicheAudience]
- Daily volume target (prompt+blog pairs, hard cap): [DailyCap]
- Quality bar notes (example output required, review gate, slug max length): [QualityBar]
- Where drafts wait before publish: [ReviewFolder]
- Site or CMS publish path the bot will use later: [PublishPath]
- Connectors already available vs still needed: [Connectors]
- Languages and soft CTAs: [LanguageCtas]
- What must stay out of any public template (secrets, private URLs, account emails): [StripList]
- Output format: [Format]

Generate:
1. One-line job statement for the bot (what it publishes, for whom, and what it never does).
2. First-run interview: at most 6 questions, one at a time order, with what to write into memory after each answer.
3. Daily routine sketch: schedule in the owner's timezone, steps from topic pick to draft files to review handoff, and the hard stop before live publish.
4. Draft file naming and fields checklist matching QualityBar (title, slug <=59, meta 140-160, category, example input/output, image alt).
5. Connector honesty list: required now, optional later, and what fails if missing.
6. Public-template packing notes: what to keep (workflow memories, getting-started skill, routines) and what to strip using StripList.
7. A worked mini example using only the facts in the Inputs.
8. Open risks: indexing risk from thin duplicates, daily-cap math, and approval gates the human must keep.

Rules: do not invent marketplace links, category ids, or credentials. If PublishPath is unknown, leave a blank and say the owner must fill it. Harbor Lane Press is an invented example publisher when you need a fictional name.

Instructions

Replace every [bracket]. Works on ChatGPT, Claude, and Gemini for the planning text; a live Grok Bot template still needs the owner's connectors after Add. The Prompt Library Publisher template is not public yet, so there is no share link to open or add and none is given here. Harbor Lane Press is fictional. Grok and xAI marks belong to their owner, and ChatGPT, Claude and Gemini belong to OpenAI, Anthropic and Google; PromptDig is independent of all of them.

Generated Output

This image was generated using the prompt above.

Bot Template Prompt: Prompt Library Publisher Setup - Result

Examples

Example Input

NicheAudience: English prompt+blog pairs for a public AI prompt library aimed at marketers, builders, and teachers
DailyCap: 3 pairs per day inside a 5-pair hard cap
QualityBar: each pair needs a real example output, variations tip, SEO review folder before publish, slug 59 chars or fewer, native still covers with no fake UI text
ReviewFolder: /workspace/library-seo/review/pending then approved/
PublishPath: site API as a moderator account after SEO approval; never publish from pending
Connectors: site login cookie jar ready; image generation available; X and Instagram posting optional later; no hosting-panel changes without explicit yes
LanguageCtas: publish in English; soft CTAs to homepage, browse, blog, and category hubs
StripList: account emails, password file paths, private repo names, hosting-panel steps, any .env or database paths
Format: numbered setup plan plus a short sample Monday run

Example Output

1. JOB STATEMENT
Publish 3 high-value English prompt+blog pairs a day for a public AI prompt library, send drafts through an SEO approval folder, and never ship thin duplicates or secrets in a public template.

2. FIRST-RUN INTERVIEW (ask one at a time)
1) What niche and audience should every pair serve? -> memory: NicheAudience
2) What is the daily pair cap and the hard daily ceiling? -> memory: DailyCap
3) Where should drafts wait before anyone may publish? -> memory: ReviewFolder
4) Which connectors are already signed in on this computer? -> memory: Connectors
5) Which soft CTA destinations are allowed on social? -> memory: LanguageCtas
6) What must never appear in a public share of this bot? -> memory: StripList

3. DAILY ROUTINE SKETCH
08:00 owner timezone: pick 3 topics that fit NicheAudience and are not already live.
Write prompt then matching blog drafts into ReviewFolder/pending with QualityBar fields filled.
Generate native still covers; reject blurry or UI-gibberish frames.
Hand the batch to the SEO desk; publish only from approved/ after the standing publish window.
Hard stop: no live POST from pending/; no hosting-panel or site-setting changes without an explicit owner yes.

4. DRAFT CHECKLIST
Title 50-60 chars; slug <=59; meta 140-160; one H1; category Bot Templates once it exists; real example_input and example_output; image_alt descriptive; tags each <=50 chars.

5. CONNECTOR HONESTY
Required now: site auth for later publish, image generation for covers, file access to ReviewFolder.
Optional later: X posting, Instagram carousel posting.
If image generation is missing, stop before publish and leave media_url empty rather than shipping a soft placeholder.

6. PUBLIC-TEMPLATE PACKING
Keep: job statement, quality bar, review-gate routine, getting-started interview, soft CTA rule.
Strip: StripList items, private cookie paths, account emails, hosting runbooks.

7. MINI MONDAY EXAMPLE (Harbor Lane Press, fictional)
Topics: auditor walkthrough notes, sales discovery script, design-thinking concept pack.
Files land in pending/; SEO desk returns approved/ with meta length fixes; 08:00 publish window uploads images then posts prompt before blog.

8. OPEN RISKS
Thin near-duplicates can hurt indexing; count every pair inside DailyCap; the human keeps final publish authorization.

Share this prompt

Reviews (0)

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