A complete outbound sales department in one skill. An agent skill from romangojiberryAI/gojiberryai-sales-os.

MITAuto-check passedSales & Support

Install Sales Os

skills CLI
$ npx skills add romangojiberryAI/gojiberryai-sales-os --skill sales-os -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install romangojiberryAI/gojiberryai-sales-os sales-os --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/romangojiberryAI/gojiberryai-sales-os.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/sales-os .claude/skills/sales-os && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
sales-os
GitHub stars
139
Token cost
~2k tokens
SKILL.md length
744 words
Files
16 (incl. references)
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

A complete outbound sales department in one skill. An agent skill from romangojiberryAI/gojiberryai-sales-os.

  • Works in 3 steps: Gojiberry is the source of truth.… → Ship artifacts, not advice. The… → Propose, don't send — until asked.…
  • ANY outbound task — find leads
  • SKILL.md covers Setup — always do this first, Routing, Default outbound chain and Subagent fan-out, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Sales Os is an agent skill from romangojiberryAI/gojiberryai-sales-os. A complete outbound sales department in one skill. Finds buying-intent prospects, filters them against an ICP, researches accounts, enriches contact data, scores likelihood to buy, writes personalised LinkedIn messages, launches campaigns, triages replies, follows up, qualifies meetings, and reports which ICPs/signals/messages convert — all through the GojiberryAI MCP. Use for ANY outbound task — find leads, research a company, write a connection note, check Unibox, score a list, launch a campaign, book a demo…

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 16 other files, including reference files (for example `icp-context.template.md`, `references/copy.md` and `references/enrichment.md`).

It sits in Sales & Support, covering Go-to-market strategy and Cold outreach. It works with LinkedIn and Model Context Protocol. The repository describes itself as: GojiberryAI Sales OS: a full AI outbound team for Grok Bot, powered by the GojiberryAI MCP. The licence is MIT.

When your agent uses it

  • ANY outbound task — find leads
  • Research a company
  • Write a connection note
  • Launch a campaign

Example prompts

  • “/sales-os”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Gojiberry is the source of truth. Contacts, lists, campaigns, intent types, and Unibox threads come from MCP tools. Invented emails, fake…
  2. Ship artifacts, not advice. The deliverable is the list, the score, the message, the next action. "You should personalise more" is…
  3. Propose, don't send — until asked. Default mode never fires a connection request, message, or campaign mutation. Autonomous mode requires…

What it can do on your machine

Read from SKILL.md and the folder at commit 0ee5d22. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Sales Os loads about 2k tokens when it runs, and up to ~7.8k if it reads all its reference files. Until then it costs about 211 tokens; SKILL.md has 744 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~211
When it runs · the whole SKILL.md, loaded when a task matches
~2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~7.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from romangojiberryAI/gojiberryai-sales-os at commit 0ee5d22, republished under its MIT licence (© romangojiberryAI). 744 words, ~1,954 tokens.

Download SKILL.mdSave it as .claude/skills/sales-os/SKILL.md (or your agent's skills folder). This skill also uses 15 other files; get the full folder from GitHub.
name
sales-os
description
A complete outbound sales department in one skill. Finds buying-intent prospects, filters them against an ICP, researches accounts, enriches contact data, scores likelihood to buy, writes personalised LinkedIn messages, launches campaigns, triages replies, follows up, qualifies meetings, and reports which ICPs/signals/messages convert — all through the GojiberryAI MCP. Use for ANY outbound task — find leads, research a company, write a connection note, check Unibox, score a list, launch a campaign, book a demo, report pipeline — whenever the user mentions sales, outbound, SDR, GTM, LinkedIn, prospects, ICP, intent, enrichment, campaigns, replies, follow-up, demos, pipeline, or Gojiberry. Route via the table inside; fan out the 13 specialist agents for multi-step work. Not for inbound support, legal contracts, or engineering.
license
MIT
metadata.author
GojiberryAI
metadata.version
1.0

GojiberryAI Sales OS

One skill, thirteen specialists, the full surface a working outbound team touches. Powered by the GojiberryAI MCP.

Three rules hold across every module:

  1. Gojiberry is the source of truth. Contacts, lists, campaigns, intent types, and Unibox threads come from MCP tools. Invented emails, fake reply quotes, and phantom sends are defects.
  2. Ship artifacts, not advice. The deliverable is the list, the score, the message, the next action. "You should personalise more" is worthless; the rewritten note is the deliverable.
  3. Propose, don't send — until asked. Default mode never fires a connection request, message, or campaign mutation. Autonomous mode requires an explicit user instruction and a score threshold.

Setup — always do this first

Read icp-context.md if it exists (working directory, .grok/, .claude/, or .agents/). It holds the product, ICP, disqualifiers, proof, voice, and send policy. If absent: proceed, say the output is un-contextualised, and offer to generate the file from icp-context.template.md.

Confirm MCP. If GojiberryAI tools are available, call UserExternalController_getMe (or the equivalent "who am I" tool) once per session before mutating anything. If MCP is missing, you may research and draft only. Say so.

Identify the task type, then open ONLY the module file(s) needed. Do not load all references.

Routing

The user wants to...ModuleSpawn
Who to target, ICP, markets, "why these people"references/icp.mdhead-of-sales
Find buying intent, competitor engagement, hiring, social signalsreferences/signals.mdsignal-hunter
Filter / disqualify a listreferences/icp.mdicp-analyst
Research a company or person, find the anglereferences/research.mdaccount-researcher
Emails, phones, missing fieldsreferences/enrichment.mdlead-enricher
Rank likelihood to buyreferences/scoring.mdintent-scorer
LinkedIn notes, follow-up copyreferences/copy.md + references/slop-patterns.mdlinkedin-copywriter
Campaigns, lists, sendsreferences/outreach.mdoutreach-operator
Read replies, who is interestedreferences/replies.mdreply-agent
Keep warm threads alivereferences/follow-up.mdfollow-up-agent
Qualify before calendarreferences/qualification.mdmeeting-qualifier
What convertsreferences/pipeline.mdpipeline-analyst
Run the whole motionreferences/routing.mdsales-manager

MCP tool map: references/mcp.md. Load it whenever you are about to call a Gojiberry tool and are unsure which one.

Multi-part requests load multiple modules in the handoff order below. Carry evidence forward.

Default outbound chain

Signal Hunter
  → ICP Analyst
    → Account Researcher
      → Lead Enricher
        → Intent Scorer
          → LinkedIn Copywriter
            → Outreach Operator   (approval gate)
              → Reply Agent
                → Follow-up Agent
                  → Meeting Qualifier

Head of Sales sets the target before the chain. Sales Manager owns the chain. Pipeline Analyst reports after there is volume.

Subagent fan-out

When subagents are available, parallelize. This is the difference between a 15-minute list and a 2-hour one.

Find + filter — spawn signal-hunter and have icp-analyst wait on its output; do not contact in this pass.

Research a batch — one account-researcher per account (cap 8 in parallel). You synthesise angles; never let a researcher write the outreach message.

Copy a batch — one linkedin-copywriter per cluster of similar angles (not one per lead unless the batch is ≤5). You run the de-slop pass on the merged set.

Unibox triage — reply-agent classifies; follow-up-agent and meeting-qualifier only receive the threads that match their job.

Rules for fan-out: give each subagent its exact reference slice, MCP tool names, and output schema; launch in one turn; never let a subagent send. If subagents are unavailable, walk the chain sequentially — the sequence is deliberate.

Show full SKILL.md (249 more words)Show less

Shared output standards

Lists are tables, not prose:

# [List] — [signal / ICP] — [date]
Source: Gojiberry MCP | Mode: propose | Count: N

| Name | Title | Company | Signal | ICP (Y/N + why) | Intent 0-100 | Angle | Next action |

Messages lead with the copy, reasoning after. One recommended note first, then a sharper test contrast.

Reports follow this skeleton:

# [Deliverable] — [subject]
[date] · Mode: propose|autonomous · Basis: [MCP / public web / user]

## The one thing
## Scorecard / Findings
## Do these first
## What's already working
## What I couldn't determine

Write reports to files (outbound-[subject]-[date].md) when the host can write files. These are documents people forward.

Honesty spine — applies to every module

  • All scores are heuristics unless the number came from Gojiberry intent data. Say which.
  • Never invent contact data. If enrichment returns nothing, write [NEED: email] and keep moving. A plausible fake email is how you burn a domain and a relationship.
  • Never invent company news. If you cannot verify a hiring round, a post, or a competitor mention, drop that angle.
  • Never claim a send you did not perform. "Drafted" and "queued" and "sent" are different words. Use the right one.
  • Do not anchor on ICP claims the user supplies if MCP data contradicts them. Form an independent read, then compare.
  • Say when the problem isn't outbound. If the offer is weak or the ICP is a fantasy, more messages will not fix it.
  • Respect platform and legal limits. LinkedIn connection notes stay short. No scraping credentials. No purchased lists dumped in blindly — run ICP + intent first.

Module directory

references/
├── routing.md        Sales Manager playbook + chain
├── icp.md            Head of Sales + ICP Analyst
├── signals.md        Signal Hunter
├── research.md       Account Researcher
├── enrichment.md     Lead Enricher
├── scoring.md        Intent Scorer
├── copy.md           LinkedIn Copywriter
├── slop-patterns.md  AI-tell catalogue — run on all prose
├── outreach.md       Outreach Operator
├── replies.md        Reply Agent
├── follow-up.md      Follow-up Agent
├── qualification.md  Meeting Qualifier
├── pipeline.md       Pipeline Analyst
└── mcp.md            GojiberryAI MCP tool map

Chaining

  • "Find me 25 SaaS founders hiring SDRs" → signals → icp → research → enrich → score → copy. Stop. Show the pack.
  • "Launch this" → outreach, only after the pack exists and the user approved.
  • "Check replies" → replies → follow-up and/or qualification.
  • "What's working" → pipeline, then head-of-sales if targeting should change.

When chaining, carry evidence forward.

© romangojiberryAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 15 other files (references) in skills/sales-os of romangojiberryAI/gojiberryai-sales-os.

  • SKILL.md
  • icp-context.template.md
  • references/copy.md
  • references/enrichment.md
  • references/follow-up.md
  • references/icp.md
  • references/mcp.md
  • references/outreach.md
  • references/pipeline.md
  • references/qualification.md
  • references/replies.md
  • references/research.md
  • references/routing.md
  • references/scoring.md
  • references/signals.md
  • references/slop-patterns.md

Open the folder on GitHubat commit 0ee5d22

Compare with similar skills

Sales Os next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Sales Os compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Sales Os this skillromangojiberryAI/gojiberryai-sales-os139—~2kAutomated safety check: PassMIT
Omentir Linkedin Outreachsickn33/agentic-awesome-skills47k1 repos~1.4kAutomated safety check: PassMIT
Prd V09 Cold Outreach Tieredmattgierhart/PRD-driven-context-engineering180—~2.5kAutomated safety check: PassMIT
LinkedIn MCP Usage Rulesstickerdaniel/linkedin-mcp-server3.8k—~651Automated safety check: PassApache-2.0
Social Sellingtech-leads-club/agent-skills7k—~4.9kAutomated safety check: PassCustom licence
Cold Email Outreachgooseworks-ai/goose-skills1.2k1 repos~3.4kAutomated safety check: NotesMIT

Similar skills

  • Omentir Linkedin Outreach

    sickn33/agentic-awesome-skills

    Run LinkedIn prospecting and outreach through the Omentir MCP server: find people, score fit, draft messages, and check campaigns.

    47k GitHub starsUsed in 1 repo~1.4k tokens
    Sales & SupportAuto-check passed
  • Prd V09 Cold Outreach Tiered

    mattgierhart/PRD-driven-context-engineering

    Build Tier 1/2/3 cold outreach sequences differentiated by personalization depth and research signal strength during PRD v0.9 Go-to-Market.

    180 GitHub stars~2.5k tokensUpdated 1 mo ago
    Sales & SupportAuto-check passed
  • LinkedIn MCP Usage Rules

    stickerdaniel/linkedin-mcp-server

    Rules for using the bundled LinkedIn MCP server for profile, company, job, post, feed and inbox work, with explicit authorization required for messages and connection requests.

    3.8k GitHub stars~651 tokensUpdated yesterday
    Sales & SupportAuto-check passed
  • Social Selling

    tech-leads-club/agent-skills

    When the user wants to sell through social media, optimize LinkedIn for sales, build DM sequences, or convert content engagement into pipeline.

    7k GitHub stars~4.9k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Cold Email Outreach

    gooseworks-ai/goose-skills

    End-to-end cold email outreach orchestration. An agent skill from gooseworks-ai/goose-skills.

    1.2k GitHub starsUsed in 1 repo~3.4k tokens
    Sales & SupportAuto-check: notes
  • Vibe Prospecting

    hashgraph-online/awesome-codex-plugins

    Find company & contact data. An agent skill from hashgraph-online/awesome-codex-plugins.

    1.3k GitHub starsUsed in 1 repo~2.8k tokens
    Sales & SupportAuto-check passed

Categories

Questions about Sales Os

What does Sales Os do?

A complete outbound sales department in one skill. An agent skill from romangojiberryAI/gojiberryai-sales-os. Sales Os is an agent skill from romangojiberryAI/gojiberryai-sales-os. A complete outbound sales department in one skill.

When should I use Sales Os?

Sales Os fits situations like: ANY outbound task — find leads; research a company; write a connection note; launch a campaign.

How do I install Sales Os in Claude Code?

Run `npx skills add romangojiberryAI/gojiberryai-sales-os --skill sales-os -a claude-code`. Or copy the skill folder (skills/sales-os in romangojiberryAI/gojiberryai-sales-os) into .claude/skills/sales-os in your project. Claude Code loads it when a task matches its description.

How do I install Sales Os in Codex?

Run `npx skills add romangojiberryAI/gojiberryai-sales-os --skill sales-os -a codex`. Or copy the skill folder (skills/sales-os in romangojiberryAI/gojiberryai-sales-os) into .agents/skills/sales-os in your project. Codex loads it when a task matches its description.

Can I use Sales Os in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add romangojiberryAI/gojiberryai-sales-os --skill sales-os -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sales-os, .gemini/skills/sales-os, .github/skills/sales-os and .opencode/skills/sales-os in your project.

What does Sales Os need to run?

SKILL.md names no scripts, command-line tools or credentials: Sales Os is instructions for the agent only.

Does Sales Os access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Sales Os safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Sales Os use?

Sales Os is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Sales Os use?

About 2k tokens (SKILL.md is roughly 7.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.9k tokens, read only when the agent opens those files.

What are the alternatives to Sales Os?

Skills that share tags, products or a category with Sales Os: Omentir Linkedin Outreach (sickn33/agentic-awesome-skills, 47k stars), Prd V09 Cold Outreach Tiered (mattgierhart/PRD-driven-context-engineering, 180 stars), LinkedIn MCP Usage Rules (stickerdaniel/linkedin-mcp-server, 3.8k stars) and Social Selling (tech-leads-club/agent-skills, 7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sales Os?

romangojiberryAI (a GitHub user) maintains it in romangojiberryAI/gojiberryai-sales-os, which has 139 GitHub stars. The repository was last updated on September 1, 2026.

Source: romangojiberryAI/gojiberryai-sales-os on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.