CHATBOTS

Weekly digest of unanswered ReadMe questions to Slack

On a schedule, reviews the week's logged docs questions, clusters the ones ReadMe couldn't answer well.

CategoryChatbots
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionRead logged questions and scores from PostgresPostgreSQLPostgres
  • LogicFilter to poorly answered questions
  • ActionCluster gaps and rank against ReadMe pagesOpenAI
  • OutputPost ranked doc-gap digest to SlackSlack

What it does

Produces a weekly "what our docs are missing" report. It reads the logged questions your /docs bot handled, finds the ones where ReadMe coverage was weak, clusters them into themes, and posts a ranked digest to Slack listing the top documentation gaps with example questions and suggested pages to write or improve.

When to use it

When individual gap tickets are too noisy and you want a single prioritized view each week of where your ReadMe knowledge base is failing readers. Gives docs leads a standing agenda for planning.

How it works

  1. 1A weekly schedule trigger fires the workflow.
  2. 2The flow reads logged questions and their retrieval scores from Postgres.
  3. 3A logic step filters to low-confidence (poorly answered) questions.
  4. 4OpenAI clusters them into themes and ranks the biggest gaps against current ReadMe pages.
  5. 5A formatted digest with examples and suggested pages is posted to the docs Slack channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PostgresAny Postgres URL — query, write, migrate.
  2. 2
    Connect ReadMeAPI docs, changelog, auth.
  3. 3
    Connect OpenAIModels, embeddings, files.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.