agentleFS
cobusgreylingcobusgreyling/grok-bot-templates/skills/research-accounts/SKILL.md

research-accounts

Skill14 starsChanged 3 months agoMITView on GitHub

Paste this into Grok Bot after a successful run: Save the process we just used as a skill called “Research Accounts”. A useful skill states the six fields from Skills and routines. A list of accounts must be scored against an ICP and recent intent, with contacts and draft outreach, stopping at a review list. Every score has a source. Skipped accounts are listed with why. Drafts are clearly labeled DRAFT. No message is sent. A review list: account, score,…

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Every score has a source. Skipped accounts are listed with why.

    line 30
  2. Distinctive:

    Do not send email, InMail, or enroll anyone in a sequence.

    line 40

≈ “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

Research Accounts

Paste this into Grok Bot after a successful run:

Save the process we just used as a skill called “Research Accounts”.

A useful skill states the six fields from Skills and routines.

1. When to use it

A list of accounts must be scored against an ICP and recent intent, with contacts and draft outreach, stopping at a review list.

2. Required inputs and access

  • CRM view, spreadsheet, or pasted account list
  • ICP definition (ask once if missing, then save)
  • Style examples for outreach if the owner attached them

3. Sequence of work

  1. Confirm the account list and ICP. Do not expand the list silently.
  2. Research each account from current sources. Skip anyone already in an active sequence if that field exists.
  3. Score against ICP and recent intent with evidence links.
  4. Identify up to three relevant contacts per account.
  5. Draft email and LinkedIn outreach in the attached style. Do not send.

4. How to validate the result

Every score has a source. Skipped accounts are listed with why. Drafts are clearly labeled DRAFT. No message is sent.

5. What to return

A review list: account, score, evidence, contacts, drafts, skips.

6. What requires approval

Do not send email, InMail, or enroll anyone in a sequence. Do not create CRM records unless the owner names that action later.

Type / in the composer to reference a saved skill. If it does not appear, open Settings → Plugins → Yours and enable it for this Bot.

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.