The Daily Brief

What it does

Every community manager’s morning starts with the same job: open the forum and find out what happened overnight. The Daily Brief does that read for you. Point it at your community and it reviews the last day of activity, checks it against yesterday’s brief, and hands you one short page that tells you where to spend your time.

It reads the forum and nothing else, and it only suggests. It never posts, replies, messages members or changes settings. Every draft it writes is labeled for your approval, and every finding links back to the thread it came from, so you can check its work.

Marius Ciortea built it from one question: what would you ask an intern to tell you every morning? He walks through it, and runs it live on a beekeeping community, in Episode 003.

What you get each morning

1. Top signal. The single most important thing to notice today, why it matters, and the move to make. If nothing is on fire, it says so.
2. What’s changed. Meaningful developments since your last brief: new discussions, notable replies, resolutions, shifts in mood or urgency.
3. Needs attention. Threads that need a response, an escalation, a follow-up or a moderation review, each marked high, medium or low.
4. Recurring patterns. Questions arriving again in different words, with the evidence and the artifact that would answer them once, such as an FAQ entry or a canonical answer.
5. Coach’s note. One decisive recommendation for where your energy goes today, often as a plan for the first twenty minutes.
6. Suggested actions. Up to three actions in priority order, each with a draft or artifact ready for you to edit and use.

The first run is a baseline covering the past 24 hours. Run it every day in the same place and it gets sharper, because it compares each morning against the last.

Install it in Claude

Skills work on every Claude plan, including Free.

1. Turn on code execution. On Free, Pro or Max, go to Settings › Capabilities and turn on Code execution and file creation. On Team or Enterprise, an owner turns on skills for the organization first.
2. Download the Claude version from this page. Don’t unzip it.
3. Upload it. In Claude, go to Customize › Skills, select +, choose Create skill, then Upload a skill, and choose the zip.
4. Run it. Start a new chat and ask for your brief (see Run your first brief below). Claude picks up the skill on its own when you ask for it.

Prefer to let Claude do it? Start a chat, paste in the skill’s SKILL.md, and ask Claude to set it up as a skill for you. That’s how Chris installed it on the episode.

If your community needs a login. Claude’s own browser runs in the cloud and can’t sign in to private communities. On paid plans, Claude in Chrome lets Claude read the community through your own Chrome browser, where you’re already signed in. Only give it permission on sites you trust.

Install it in ChatGPT

How you install it depends on your ChatGPT plan.

ChatGPT Business, Enterprise, Healthcare or Edu. Skills are built in, subject to your workspace settings.

1. Download the ChatGPT version from this page.
2. In ChatGPT, open Plugins, go to the Skills tab, choose Create, then Upload from your computer, and choose the zip. ChatGPT scans uploaded skills before they’re available.
3. Ask for your brief in any chat. ChatGPT uses the skill when it fits the request.

ChatGPT Free, Plus or Pro. Skills aren’t available on personal plans yet, so use a project instead. It works the same way in practice.

1. Download the ChatGPT version and unzip it. Inside is one file, SKILL.md.
2. In ChatGPT, create a new project called Daily Brief.
3. Add SKILL.md to the project’s files.
4. In the project’s instructions, write: When I ask for my daily brief, follow SKILL.md exactly.
5. Run every brief as a new chat inside that project, so it can compare each morning with the last.

If your community needs a login. On paid plans, ChatGPT’s cloud browser can sign in to a community you belong to. ChatGPT asks for your username and password in a secure form that the model never sees, and the sign-in carries over to later briefs.

Run your first brief

Copy this, swap in your community, and send it:

Run my daily brief for [your community’s URL]. Review the last 24 hours in [your timezone]. This is my first brief, so treat it as a baseline.

Then read the coach’s note first. If you want to know why something made the list, scroll back up to the section that flagged it.

Make it yours

The version here is a starting point. Each of the six sections is its own prompt, so you can rewrite any of them for the questions only your community asks.

• Define urgency for your community. Tell it what counts as high, medium and low where you work.
• Point it at your documentation. With your help center or knowledge base in reach, suggested replies can point members to answers that already exist.
• Add your voice. Have it draft in your own voice, or call a voice skill of your own, and still edit before you post.
• Route questions to experts. Marius’s own version builds a directory of who in the company knows what, then suggests the right person for each question.
• Connect more context. With MCP access to your platform and CRM, the brief can add who a member is and which account they belong to.

Whatever you change, keep your judgment in the loop. The brief is right often enough that accepting it becomes a habit. Every draft is a suggestion until you decide it isn’t.

Share what you build

Treat the Daily Brief like an open-source project: fork it, change it, and send us what works. We’ll feature the best versions on the show. Get in touch at communityassistant.ai/join.

Created by Marius Ciortea, Chief Community Officer at Higher Logic, with CommunityAssistant.ai. Marius built this as a practitioner speaking for himself, not for his employer. Shared under CC BY-NC 4.0.