Community Builder

An example pack

What you take home

These are the files from one coaching session. The community is invented. The coach and the files are real: a tester played the lead of a quiet AI network in a logistics company, and the coach wrote what you see here.

README.md

How to start

What is in the pack and how to load it into your AI. Read this first.

Made by the AI Community Builder on 2026-11-18. These files hold what you found out about your community during the coaching session, what you decided, and the method behind it, so your own AI can keep coaching you for as long as you like.

What's in it

About your community

  • community-profile.md: what kind of community it is, its name, size and sponsors, and a private note about you as the lead.
  • community-pyramid.md: each Community Pyramid block, its state and the evidence behind it, plus the 12 claims you answered at the start.
  • plan.md: what you learned and what you'll do, block by block, with ideas for the months ahead. Suggestions, not a schedule.
  • coaching-summary.md: what you learned, what you decided and what you set aside.
  • open-questions.md: what you still know only from your own view, and ways to find out.
  • evidence-log.md: what you found, from which kind of source and when. Summaries only.
  • exercise-cards/: the exercise cards from the coaching session, activities to run with your community.
  • sponsor-summary.md: a short version to share with your sponsor.

The method

  • method/community-pyramid.md: the six blocks, what each means and its warning signs.
  • method/expertise.md: the author's judgements on building AI communities.
  • method/exercise-library.md and method/exercise-cards/: every exercise card.
  • method/reality-checks/: every reality check, with steps.

The coach

  • skills/community-coach/SKILL.md: turns your own AI into a coach for this community. It listens first, uses the pyramid to work out where a challenge lies, and asks to be connected to your meeting notes and documents so it can follow the community as it changes.

Load it into your own AI

ChatGPT:

  1. Open ChatGPT and create a new project (or a custom GPT).
  2. Add the files from the pack to the project. If your plan limits the number of files, start with the main files and method/community-pyramid.md.
  3. Open the project instructions and paste in everything below the first heading of SKILL.md.
  4. Start a chat inside the project and tell it what is on your mind.

Gemini:

  1. Open Gemini and create a new Gem.
  2. Paste everything below the first heading of SKILL.md into the Gem's instructions.
  3. Add the other files from the pack as the Gem's knowledge.
  4. Save the Gem and start a chat with it.

Claude:

  1. Open Claude and create a new project.
  2. Add the files from the pack to the project knowledge, including the method/ folder.
  3. Paste everything below the first heading of SKILL.md into the project instructions, or add the skills/community-coach folder as a skill if your plan allows it.
  4. Start a chat inside the project.

Microsoft Copilot:

  1. In Microsoft 365 Copilot, create a new agent.
  2. Paste everything below the first heading of SKILL.md into the agent's instructions.
  3. Add the other files as the agent's knowledge, uploaded or from a OneDrive or SharePoint folder only you can see.
  4. Save the agent and start a chat with it. Creating agents depends on your organisation's Copilot licence and settings.

An AI on your own computer:

  1. Put the folder where your tool reads documents.
  2. Use the text of SKILL.md as its instructions.

The menus in these tools change from time to time, so the names may differ slightly.

Connect it to where your community works

Your coach will suggest this itself. It doesn't need copies of your files, only access to read them where they already are. Connect only what you are allowed to share with your AI tool.

ChatGPT:

  1. Open your project and choose Add sources (in some versions, Add files).
  2. Choose Google Drive, approve access, and pick the folder or files with your community's memos and transcripts.
  3. For SharePoint or Teams, open the + menu in a chat inside the project and pick the app from the list of apps (earlier called connectors). Sign in with your work account.
  4. On a work plan, your administrator may need to switch these apps on first.

Gemini:

  1. Open your Gem for editing and scroll to Knowledge.
  2. Choose Add files, then Drive, and pick the documents. Gemini reads the latest version of a Drive file each time.
  3. If Drive isn't offered, connect Google Workspace in Gemini's settings. With a work account, your administrator may need to allow it.
  4. A Gem reads Google Drive only. For material in Teams or SharePoint, save or export it to Drive, or add it to the conversation.

Claude:

  1. Open Customize, then Connectors, and connect Google Drive or Microsoft 365. Sign in when asked.
  2. For Google Drive documents: open your project, press + in the Files section, choose Drive and pick the documents. This works in a private project, not in a shared one.
  3. For Microsoft 365 (SharePoint, OneDrive, Teams, Outlook): once it is connected, ask in a chat inside the project, for example "Read the latest memo in our community folder".
  4. On a Team or Enterprise plan, the owner of your Claude organisation and a Microsoft administrator have to switch the Microsoft 365 connector on first.

Microsoft Copilot:

  1. Open your agent for editing and go to Knowledge.
  2. Add the SharePoint site, folder or files, or the OneDrive files, where the community's documents are. Paste a link or use the file picker.
  3. Add Teams chats and meetings. Pick the community's own chats and meetings, not everything you have access to, so the agent stays on the community.
  4. The agent sees only what you can see yourself. Teams and SharePoint sources need a Microsoft 365 Copilot licence, and other systems need a connector your administrator sets up.

Miro, Howspace, Slack and other platforms:

  1. Look in your AI tool's list of apps or connectors. Some platforms have one.
  2. If yours doesn't, export the board or the workspace summary as a PDF or text file into a folder your AI is connected to, or add it to the conversation.

These steps were checked in November 2026. The menus change and depend on your plan and your organisation's settings, so if something looks different, ask your coach or your IT support where the setting is now.

Things you can say to it

  • "Something's been bothering me about the community. Can I think out loud?"
  • "Our last meetup felt flat. Help me work out why."
  • "I've got a meetup next week. What could we focus on?"
  • "Things are quiet with the holidays. What, if anything, is worth doing now?"
  • "Which block of the pyramid do you think this is about?"
  • "Help me prepare an update for our sponsor."
  • "I'd like to answer the community snapshot claims again and see what's changed."
  • "What could I connect you to, so you can follow what happens in the community?"
  • "Here is the transcript from yesterday's meetup. What do you notice?"

Keeping it current

Your coach is meant to stay with you as the community changes, not to repeat what was true on the day of the coaching session. It will ask where your community works and suggest that you connect it to those places: your meeting transcripts and memos, your documents, and platforms such as Teams, Google Drive, SharePoint, Miro or Howspace. It doesn't need copies of the files, only access to read them where they are. What can be connected depends on the AI tool you use and on your organisation's settings. Where a connection isn't possible, add the material to the conversation instead.

The coach runs in your own AI environment, so it works with the names and details in your material as they are.

When something new happens, your coach can suggest the exact lines to add to evidence-log.md, plan.md or open-questions.md. Paste them in, so the next conversation starts from where you are.

The pack is based on what you shared during the coaching session. Where the evidence is thin, the files say so. Treat those parts as assumptions to test.

Your pack would be about your community.

Start with the community snapshot. It is free and takes about ten minutes.

Take the free community snapshot