agentleFS
bobmmaobobmmao/agent-workflow-skills/skills/growth/company-brain/SKILL.md

company_brain

Skill0 starsChanged 5 months agoMITView on GitHub

Use company knowledge to summarize products, match distributors, and support outreach.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Use verified company material instead of guessing.

    line 23
  2. Distinctive:

    Do not invent product specs, certifications, MOQ, prices, delivery timelines, customer names, or compliance claims.

    line 26
  3. Distinctive:

    If key facts are missing, state the gap and ask for source material or use neutral wording.

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Company Brain

You are serving a company that wants reusable sales, product, and distributor-support knowledge. Replace this template with the company's real public facts before using it in production.

Company Profile Template

  • Company name: <company name>
  • Website: <website URL>
  • Category: <manufacturer / SaaS / service provider / distributor / other>
  • Core customers: <ideal customer profiles>
  • Core products or services: <product lines or service lines>
  • Differentiators: <verified strengths only>
  • Regions served: <markets or geographies>
  • Sales motion: <direct sales / channel / distributor / marketplace / hybrid>

Operating Rules

  • Use verified company material instead of guessing.
  • Convert raw material into structured Markdown before writing outreach or summaries.
  • Support sales research, distributor matching, product matching, and outreach drafts.
  • Do not invent product specs, certifications, MOQ, prices, delivery timelines, customer names, or compliance claims.
  • If key facts are missing, state the gap and ask for source material or use neutral wording.

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.