Library — DistroSource

Everything digital. One source.

22 resources

Checklist · Beginner · 10 min
Support macro before it goes live checklist
The checks a new reply macro passes before agents can use it.
- A bad macro is a mistake sent a hundred times. Review each one once, properly.
- ☐ Under ninety words
- ☐ Uses only policy sentences from the snippet library
Items 10ChatGPTClaude
Checklist · Beginner · 10 min
Automation touching customer orders checklist
What an ecommerce automation must satisfy before it can change or message an order.
- Order automations are where a small bug becomes a hundred wrong emails. Verify these before enabling.
- ☐ Trigger is deduplicated on order id
- ☐ Every write is idempotent
Items 10ChatGPTClaude
Checklist · Beginner · 10 min
CRM data before automating on it checklist
The data hygiene an automation needs before it can route, score or nudge from CRM records.
- Automations amplify whatever is in the CRM. Clean first.
- ☐ Emails lower-cased and deduplicated
- ☐ Stage definitions written and applied
Items 10ChatGPTClaude
Checklist · Intermediate · 10 min
Agent tool definition review checklist
What to check before a tool is exposed to an agent, so the description and schema cannot be misread.
- Most agent misbehaviour traces to a tool the model misunderstood. Review every tool against this list before it goes live.
- ☐ The description says when to use the tool and when not
- ☐ The input schema is strict: required fields, types, enums
Items 10ClaudeChatGPT
Checklist · Beginner · 10 min
Process handover checklist
What must exist before a process can be handed to someone new or to an automation.
- A process that lives in one head is not a process. This is the minimum written form.
- ☐ Purpose in one sentence
- ☐ Trigger and frequency
Items 10Any assistant
Checklist · Beginner · 10 min
Scheduled job safety checklist
What a nightly job needs before it is allowed to run unattended.
- A job that misfires at night can destroy data by morning. These items prevent that.
- ☐ Dry run by default; --write to act
- ☐ Idempotent: running twice is safe
Items 10Claude CodeAny assistant
Checklist · Beginner · 10 min
No-code scenario review checklist
A review list for scenarios built by someone else, or by you last quarter.
- Scenarios rot. This list finds the rot before it finds a customer.
- ☐ Every module is named by what it does
- ☐ The trigger's polling interval is deliberate
Items 10MakeZapier
Checklist · Beginner · 10 min
Automation go-live checklist
What to verify before an automation runs unattended.
- Automations that work in a test run fail on the first unexpected input. This list is the unexpected input.
- ☐ Tested with a missing field
- ☐ Tested with a duplicate trigger
Items 10ZapierMake
Checklist · Beginner · 10 min
Before sharing an assistant-produced analysis checklist
The checks between a generated number and a decision.
- A confident wrong number travels fast. Run this before sending.
- ☐ The definition of each metric is written down
- ☐ The query was run by you and the code is saved
Items 10ChatGPTClaude
Checklist · Beginner · 10 min
Assistant-written SEO content before publishing checklist
The checks that keep generated pages from being thin, wrong or duplicated.
- Generated pages are easy to make and easy to make badly. This list is the difference.
- ☐ The page answers the searcher's questions in order
- ☐ It contains something the top results do not
Items 10ChatGPTClaude
Checklist · Beginner · 10 min
Publishing assistant-assisted content checklist
The gate between a generated draft and a published piece.
- Assistants write plausible content. Publishing plausible content damages a publication faster than publishing nothing.
- ☐ Every factual claim traces to a source you opened
- ☐ Quotes are verbatim and attributed
Items 10ChatGPTClaude
Checklist · Beginner · 10 min
Assistant in the support queue checklist
What must be in place before an assistant drafts customer replies.
- Support is where a wrong sentence costs money and trust. Set these before the first draft.
- ☐ Policies exist as exact sentences the assistant can be given
- ☐ Personal data is redacted before any model call
Items 9ChatGPTClaude
Checklist · Beginner · 10 min
Generated product listing before publishing checklist
The checks that keep a generated listing accurate.
- Generated listings read well and lie casually. Facts first.
- ☐ Every specification traces to the spec sheet
- ☐ Dimensions, materials and compatibility are exact
Items 9ChatGPTClaude
Checklist · Beginner · 10 min
Assistant-drafted sales email before sending checklist
What to check on a generated outreach or follow-up.
- Generated sales emails are fluent and generic. This list keeps the one thing that gets replies: a true, specific observation.
- ☐ The observation is true and linked to a source
- ☐ The prospect's name and company are spelled correctly
Items 9ChatGPTClaude
Checklist · Beginner · 10 min
Assistant-written marketing copy before publishing checklist
The checks that keep generated copy honest and on brand.
- Generated copy drifts toward superlatives and invented proof. Publish nothing that fails this list.
- ☐ Every claim has proof you can show
- ☐ No superlative without a source
Items 10ChatGPTClaude
Checklist · Beginner · 10 min
Before repeating a fact from an assistant checklist
The checks between an assistant's answer and your slide.
- Assistants produce confident sentences with or without evidence. This list is how a fact earns its place in your work.
- ☐ The claim has a named source
- ☐ You opened the source
Items 9ClaudeChatGPT
Checklist · Beginner · 10 min
Accepting an assistant's code change checklist
What to check before an assistant-written diff is committed.
- Assistants write plausible code fast. The failure mode is not syntax; it is confident wrongness in the places you did not read.
- ☐ You read every changed line, including tests
- ☐ The tests were run by you or the output was pasted
Items 10Claude CodeCursor
Checklist · Advanced · 10 min
Agent production readiness checklist
What must be true before an agent is allowed to act on real systems.
- An agent is code that decides. This list is the difference between a demo and something you can leave running.
- ☐ The job and the boundary are written down
- ☐ Every side-effect tool is behind approval or a strict allow-list
Items 10ClaudeChatGPT
Checklist · Beginner · 10 min
Assistant use policy for a small team checklist
The rules a small team needs before everyone starts pasting things into assistants.
- Without a short policy, someone will paste a customer list or a contract into a consumer tool. Write the rules once.
- ☐ Which tools are approved and on which plan
- ☐ What must never be pasted: customer personal data, credentials, unreleased financials
Items 8ChatGPTClaude
Checklist · Beginner · 10 min
Before automating a business process checklist
Questions to answer before you build an automation, so you automate the right thing.
- Automating a broken process makes it break faster. Ten minutes on this list saves a rebuild.
- ☐ The process has been done manually at least ten times and is stable
- ☐ Inputs arrive in a consistent shape (or the first step normalises them)
Items 10ChatGPTClaude
Checklist · Beginner · 10 min
Setting up an assistant for daily work checklist
One-time setup so an assistant is useful on day one rather than a novelty.
- Most people abandon assistants because every chat starts from zero. An hour of setup fixes that.
- ☐ Written instructions: your role, audience, tone, output formats
- ☐ Three reference documents uploaded to a project
Items 8ChatGPTClaude
Checklist · Beginner · 10 min
Assistant-drafted email before sending checklist
The checks that keep an assistant-drafted email from embarrassing you.
- Assistants write fluent emails with confident mistakes: wrong names, invented dates, promises you did not make. Run this list before every send.
- ☐ The recipient's name is spelled as they spell it
- ☐ Every date and number came from your input, not the draft
Items 9ChatGPTClaude

Search