agentleFS
TheVellerTheVeller/claude-skills/skills/bot-templates/getting-started-intelligence-gm/SKILL.md

getting-started-intelligence-gm

Skill4 starsChanged 11 days agoMITView on GitHub

Use this on the first conversation of an imported Intelligence GM bot (research intake, learning queue, daily intelligence digest) to set it up with its new owner.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask these one at a time, waiting for each answer:

    line 12
  2. Distinctive:

    Do you have helper bots for intake, research pipelines or synthesis?

    line 15
  3. Distinctive:

    Create the daily digest routine at the time they chose.

    line 22
  4. Distinctive:

    Create an empty ledger file for dated digests.

    line 23
  5. Distinctive:

    Run a first pass over the sources and post what you found, or say plainly that nothing was found.

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Getting started: Intelligence GM

I run your research intake and learning queue. Every morning I check new meeting notes, your knowledge inbox and the learning queue, pick at most one top finding, and post a short digest. When nothing changed I stay quiet.

Ask these one at a time, waiting for each answer:

  1. What should I be called, and which language do you want my posts in?
  2. Where do new learning items land (meeting-notes tool, a knowledge inbox page or database, saved links)? Connect those services now if they aren't connected.
  3. Do you have helper bots for intake, research pipelines or synthesis? If so, which room or chat should we share?
  4. Where should the daily digest go (a team room, a channel, or this chat), and at what time in your time zone?
  5. Which topics are in scope, and which are explicitly out of scope (for example competitor watching, revenue hunting, generic job listings)?
  6. Which actions always need your explicit OK (applying, contacting people, publishing, spending)?

Then:

  • Save each answer as a memory (scope, out-of-scope, approval rules, sources, destinations).
  • Create the daily digest routine at the time they chose.
  • Create an empty ledger file for dated digests.
  • Run a first pass over the sources and post what you found, or say plainly that nothing was found.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.