How to Use Hootsuite Board Stream Checklist from Board Inventory (No Invented Engagement)
How to run Hootsuite Board Stream Checklist from Board Inventory (No Invented Engagement) on PromptDig from a locked inventory without inventing evidence.
You pasted a messy Hootsuite inventory and need a clean deliverable without invented numbers. This PromptDig prompt turns only what you already listed into a structured map or checklist.
What this prompt does
It locks your inventory, version, workspace label, and domain fields, then builds a ledger plus a table that refuses fake metrics. Missing cells stay NOT IN INPUTS instead of guessing.
Use it when you already have real stubs from Hootsuite and want a teachable map for this job, not a generic template swap.
How to fill the brackets
- Paste your Inventory with concrete nouns only.
- Lock Version to what you actually run.
- Quote Workspace and SpecNames when known; otherwise UNKNOWN.
- Fill the three domain fields shown in the prompt.
- List Banned words and Never invent rules.
Example shape
The included example_input uses Harbor Quay and River Ops labels so you can see how two inventory rows become a checklist without inventing metrics. Swap those labels for your own before you run it.
Why the honesty rules matter
Teams lose trust when a model invents cook times, engagement rates, citation counts, battery health, latency, rem scales, RDA percent, or run durations. This prompt quotes Banned and Never hits, then cuts them.
Step by step run
Copy the prompt into ChatGPT, Claude, or Gemini. Replace every bracket with your locked values. Keep Cap style limits if you add any later. Run once, then check the honesty ledger against your paste.
If the model invents a metric, quote the Banned or Never line that forbids it and re-run. Prefer a second short pass that only reorders rows over asking for a longer rewrite.
When to skip this prompt
Skip it if you do not have a real inventory yet. Skip it if you need legal, clinical, or financial advice. Skip it if you want marketing copy with testimonials. This job is a compiler for pasted stubs, not a research agent that browses the web for missing facts.
Quality checklist before you trust the output
Confirm SpecNames match your source. Confirm Version matches what you run. Confirm every numeric claim appears in Inputs. Confirm the refuse list names the invent risks you care about. Confirm Format matches what your wiki expects.
Save the accepted map next to the export that produced the inventory. That pair is the audit trail your team can re-open next week without guessing.
Worked walkthrough
Start with a short inventory you already trust. Paste only the rows you can defend in a meeting. Lock the version string to the build you actually open today. If a domain field is blank, write UNKNOWN rather than inventing a filler value.
Run the prompt once. Read the honesty ledger first. If a noun in the ledger is not in your paste, stop and fix the Inputs. Then read the map or checklist table. Every row should quote a SpecName or Inventory label you locked. Empty cells should say NOT IN INPUTS.
Do a refuse pass next. If the model invents a metric the title forbids, quote the Never line and re-run with a harder Cap. Keep the second pass short: reorder, cut, and label gaps. Do not ask for a longer essay.
Common failure modes
Teams fail this job when they paste marketing copy instead of an inventory. The prompt is a compiler, not a research agent. Another failure is unlocking Version so the model invents a newer release. Lock the version. A third failure is treating example_output as live data. The example is a shape only. Replace Harbor Quay style labels with your own nouns before you ship the map to a wiki.
If your teammates need a screen recording, show them the Inputs block and the refuse list, not a polished screenshot of invented numbers. The audit trail is the paste plus the accepted map.
Keeping the map honest over time
Save the accepted map beside the export that produced the inventory. When the source system changes, re-export and re-run rather than editing invented cells by hand. Prefer a weekly inventory refresh over a one-time perfect document. If legal, clinical, or financial advice is requested, stop. This prompt does not give that advice.
When you publish the map internally, link back to the PromptDig page so the next person can re-run with the same brackets. That habit keeps the deliverable reproducible.
Try it on PromptDig
Open Hootsuite Board Stream Checklist from Board Inventory (No Invented Engagement) on PromptDig, replace every bracket, and run it on ChatGPT, Claude, or Gemini.
Want more job shaped prompts? Browse more prompts.
Have a workflow worth sharing? Share a prompt.