Hire an AI community question and update writer

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• Every thread unanswered after two days, with who could answer it
• The week's themes with quotes and the questions asked most
• Members who reached a level, checked against who was thanked recently
• One moment designed when a milestone is near
• The weekly note drafted with one core idea at the top
• A four-week trend in members, first posts and unanswered threads

How it does the job well

• Start from the user's task and the content, then the layout. Decoration comes last.
• Design every state: empty, loading, error, long text and mobile.
• Keep one visual system. Reuse spacing, type and colour tokens instead of one-off values.
• Check text contrast (at least 4.5:1 for body text) and keyboard focus as you go.

Mistakes it avoids

• Thanking the same five people.
• A weekly note that is a list of links.
• Planning a peak for every week.
• Quoting a member outside the community without asking.
• Designing only the happy path at desktop width.
• Copying a reference's logo, text or claims instead of learning from its structure.

What a good result looks like

An example, not your task: You run a community for customers, members or learners and the launch energy has faded.

• This week in one line. Members joined, active, first posts, unanswered threads and recognitions proposed.
• Answers owed. Every thread unanswered after two days, with its age and who could answer it.
• Themes. The week's themes with member quotes, and the questions asked most often.
• Recognitions. Members who reached a level, checked against who was thanked in the last four weeks.
• The moment. When a milestone is near, the one peak to build and what stays simple.
• The weekly note. A draft with one core idea at the top, ready for you to post.

How the work is checked

• Every unanswered thread is listed with its age.
• Every recognition matches a level in the plan and the member was not thanked in the last four weeks for the same thing.
• Quotes carry a handle only where the person approves.
• The weekly note has one core idea at the top.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

A second opinion

Before it hands back, your AI reviews the draft the way Chip Heath and Mary Kay Ash would. This is a way of reviewing the work. It does not mean they wrote or endorse it.

Capabilities

• Build the plan once. The channels, the onboarding path, the events and the recognition levels anyone can reach, approved by you and reviewed each quarter.
• Read the week. Adds the week's numbers, finds the themes with quotes and lists every thread unanswered after two days.
• Pick the recognitions. Members who reached a level this week, with anyone thanked in the last four weeks for the same level held back. A new level can be recognised sooner.
• Design the moment when one is near. For a first, a launch or a milestone in the next month, the one peak to build and what stays simple.
• Draft the weekly note. One core idea at the top, the answers owed, the recognitions and the moment, in your voice.
• Log and hand back. Updates the weeks and recognised files, then stops for your yes.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id weekly-community-keeper only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/weekly-community-keeper/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• The week's posts and replies, exported from your own community, with handles, channels and reply counts
• Members joined, active, first-time posters and left, for the week (advised)
• Your brand brain and what the community is for (advised)
• Launches, milestones and events in the next month (advised)
• The community plan, once it exists

Helpful context (optional)

• A list of members who are also customers at risk, so their threads are never the unanswered ones
• Your event calendar for the next quarter

Tools and access

• Claude Code: It can keep the plan, weeks and recognised files between weeks and run every Friday.
• Your community tool: Export the week's posts with handles, channels and reply counts. Most forums and chat servers can.
• Claude, ChatGPT or Gemini: Any chat AI works. Nothing needs to run and no file access is needed.
• Any good chat AI: Turning goals and a budget into levels and praise lines is text work any strong chat AI does well.
• A shared spreadsheet: A visible tracker lets people see their own progress toward each level.
• Any good chat AI: A chat AI can read a CSV and group comments into themes.
• Google Sheets or Excel: Use them to clean and export your survey results first.
• Claude, ChatGPT or Gemini: Choosing a peak and writing the plan is text work. No files, web access or paid tools needed.
• A shared task list: The owners and dates in the plan go straight into a list the team can tick off.

Functions and deliverables

• Community question and update writer: Review community posts and unanswered threads. Get a weekly note, people to thank and repeated questions, all as drafts to review.
  • Every thread unanswered after two days, with who could answer it
  • The week's themes with quotes and the questions asked most
  • Members who reached a level, checked against who was thanked recently
  • One moment designed when a milestone is near
  • The weekly note drafted with one core idea at the top
  • A four-week trend in members, first posts and unanswered threads
• Developer community builder: Share who you want to reach and staff time. Get advice on platforms, channels, welcome steps, and events.
  • A platform pick with reasons and a runner-up
  • A channel map with a one-line purpose for each channel
  • A welcome message and a new-member path
  • Rules and a plan for handling problems
  • A 90-day calendar of prompts and events
  Source: sickn33.
• Recognition plan designer: Plan a team recognition and reward program where anyone who reaches a goal level wins, with prizes people want and a public moment.
  • A review of who wins now and why that matters
  • Levels and goals that anyone can reach on their own
  • Prizes, public moments and praise lines for each level
  • A budget check and a pay fairness check
• Feedback theme finder: Share customer ratings and comments to get score summaries, counted themes, quotes, and recommended actions.
  • A scorecard with NPS and CSAT and how many responses sit behind each
  • Themes with counts and exact quotes
  • Detractor and promoter comments looked at separately
  • Trends against the earlier period, if you gave one
  • Actions tied to specific themes
  Source: Burhan Sebin.
• Event key moment designer: Plan an event people remember. Get the one peak worth building, the expected step to break and a plan with owners, dates and costs.
  • The one peak to build, with the reason it was picked
  • The expected step you will break, and what happens instead
  • One lift, one proof of progress or insight, and one link to others or to your purpose
  • A plain, cheap version of every other step
  • Who does what, by when, at what cost, and any basics to fix first
• Internal update writer: Write an internal update from your facts: a team update, newsletter, FAQ answer or status report, in a clear format your readers can scan fast.
  • A finished update in the right format
  • Key points up front
  • Plans and problems clearly separated
  • A tone suited to the audience
  Source: Anthropic.
• Brand profile builder: Share your website. Get a reusable profile covering your products, customers, voice and approved claims, with sources.
  • A folder of eight plain files, from a start file for your AI to a claims list and a change log
  • A tag on every fact, and every claim marked approved, pending or banned
  • A two-sentence diagnosis of your biggest gap, and a list of what's missing and who can answer it
  • A short slice for your next step, if you name one
• Chip Heath: Clarify a message, change plan or difficult choice using Chip Heath’s public methods. Find the core, make it concrete and widen the options.
  • Your problem worked on the way Chip Heath would: their questions, their method, their push-back
  • The answer or the work, in Chip Heath's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step
• Mary Kay Ash: Plan recognition or feedback using Mary Kay Ash’s recorded approach. Consider the other person, set fair goals and make the message clear.
  • Your problem worked on the way Mary Kay Ash would: their questions, their method, their push-back
  • The answer or the work, in Mary Kay Ash's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step

Tasks you can use it for

• You run a community for customers, members or learners and the launch energy has faded.
• Threads go unanswered and you only notice when a member leaves.
• Your weekly note has become a list of links nobody reads.

Limits to check before starting

• You need to reply to comments on your own social posts: reply by hand, or ask your AI for a draft of each reply.
• You have a one-off launch and no ongoing member posts: write the launch note yourself with your AI.
• You want to answer one support question: paste that thread into your AI and ask for a reply.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Start a chat with the agent. In Claude Code, add it as a skill or save it in .claude/agents, then ask it to run the week.
• Export the week's posts from your community tool. Put them in one folder, or attach them in the chat.
• On the first run, describe who the members are and what the community is for. Approve the plan and the recognition levels.
• Read the answers owed first and get them answered. Then approve the recognitions and the note.
• Post the note yourself. Run it again next Friday.
• To run it every Friday, set up a weekly scheduled run in Claude Code. Or start it by hand each Friday after you export the posts.
• No export yet? Say so. It builds the plan first and reads the posts the week you have them.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/weekly-community-keeper for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.