dusk bot
use casescontent repurposing

dusk botuse cases

repurpose an article without losing the advice

the line you cut for space might be the one that keeps a reader from ruining a jacket. hand a bot one approved article and two reader questions.

by the dusk bot team · checked · how we made this

ask it to turn the article into a counter card and a short faq. keep the source passage beside each draft so an editor can spot a missing exception.

pixel art: a mint pixel bot, a sky blue pixel bot and a purple pixel bot beside a newspaper and a paint palette, on a lemon field in front of snowy hills and green fields, one saying "keep the exception"

the routine

choose pieces that readers use in different places. name the source doc and who will read each piece.

paste this into a chat with your bot

every other thursday at 11, read the approved copy at https://docs.google.com/document/d/1t8k4f7q5y2w6b9n3s8j4c7v2g5p9r3m8x6z4a7h2d5/edit. use only that doc. draft a counter card for a reader about to do the job and an faq answer for someone deciding whether to try it. for the card, answer “what do i check before washing this jacket?” for the faq, answer “can i wash the liner with the shell?” give each piece one job and a clear next step.

under each draft, list the source heading and the qualification you kept. if a short format can't fit a necessary exception, drop the advice from that format. leave both drafts here for editing. publish nothing.
when
alternate thursdays at 11 am after editorial sign-off
needs
a google doc with approved copy, read only access and two reader questions. replace the doc link and both reader questions.

what comes back looks like this (an example, not a real inbox)

example from sheila's jacket care article
counter card | before you wash: read the sewn-in care label. remove the liner only if it detaches.
faq | can the liner go in with the shell? follow each piece's own label. the lining may need different care.
source | 'before washing', paragraphs 1 and 2

choose the moment someone needs the advice

a person at the counter has a different question from someone browsing at home. the first needs a short sequence. the second might need to know whether the advice applies at all. write those two questions before asking for shorter copy.

keep a trail back to the original

make the source easy to find during editing.

  1. read the approved google doc by id.1 choose a heading that answers the reader's question.
  2. pull out the instruction and its conditions. keep words such as “only”, “unless” and “after” where they affect meaning.
  3. draft for the available space. include the source heading in a separate editor's note.

let an editor cut the weak version

try using the short piece without the article. could a reader tell when to stop? does the next step still make sense? if the answer depends on a missing diagram, refer readers to the full article or drop the piece.

if your problem is an empty source article, interview the expert first. dusk bot has nothing solid to adapt yet.

the guard rails

  • give google docs read only access. the approved article stays available to compare against the drafts.
  • reuse material you have permission to adapt. keep any required credit on the short version.
  • connected-app publishing asks first by default. drafting the copy in chat needs no publishing account.4

try it in 2 minutes

  1. choose one paragraph with an exception
  2. give the bot a counter question and a browsing question
  3. compare the guidance in both drafts with the source

what it looks like

an invented editing decision at a clothing repair counter

before

sheila's article says the lining comes out on some jackets. an early counter card tells everyone to pull out the liner.

after the bot

the card now says to remove a detachable liner only. the faq gives the longer explanation about separate care labels. both point the editor back to the same paragraph.

an illustration with made-up names and numbers.

what it could save you

roughly 14 minutes for a pair of drafts under these assumptions

24 minutes adapting both pieces by hand
- 10 minutes briefing, tracing and editing the drafts
= 14 minutes per pair

a rough estimate. it assumes:

  • time a pair based on an article you know well
  • include the work of putting omitted context back
  • compare versions that meet the same editorial standard

mistakes people make

cutting a qualification to hit the word limit

shorten the setup first. if the exception still won't fit, leave the advice out.

turning a paraphrase into a quote

use your own phrasing or copy a verified quote with its context and credit.

questions

can i use a transcript instead of an article?

yes, if you have a transcript cleared for reuse. mark speaker changes so an editor can trace an opinion back to the right person.

should every long article become several pieces?

only make a piece if the source answers its reader's question. one useful card earns its place even if the proposed faq falls flat.

sources

  1. composio: google docs actions, checked 20 november 2026
  2. dusk bot docs: files and connected apps
  3. dusk bot docs: routines
  4. dusk bot docs: a bot’s computer

drafted with ai help from the dusk bot docs and the sources listed on this page, then checked against them. if something here is wrong or out of date, write to [email protected].