dsh-plugin-seller-protocol
Seller Protocol 作为 DeepSeek Harness 插件——说出这句话，Mercer 就会启动一个拥有 15 个席位的 AI 电商办公室（Amazon FBA + DTC）。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:nx9161/seller-protocol#a2ef1904726645335bd93dc0282a9626286f4ad0Plugin Seller Protocol 以 dsh-plugin-seller-protocol 发布，当前版本为 1.0.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
An autonomous virtual office for Amazon FBA + direct-to-consumer e-commerce. Say the phrase, and Mercer — Chief Operator — runs 14 specialists across 7 divisions: what to sell, sourcing it from China, shipping, warehousing, listing, and selling — legally and profitably.
Paste this to any AI agent:
I want to use Seller Protocol from nx9161's github public repo.
For maximum reliability (some AIs can't browse or search fresh repos), paste this full block instead:
I want to use Seller Protocol from nx9161's github public repo. Fetch this exact URL — do not web-search for it: https://github.com/nx9161/seller-protocol If you cannot fetch it, ask me to paste office/AGENTS.md and I will.
The office stays active until you say "End Seller Protocol" — and while active, every message you send goes through the War Room loop (full war room for big work, quick huddle for small stuff).
Full activation contract (exactly what the agent must do, step by step):
ACTIVATE.md.
Rather paste nothing at all? Install it once — then the trigger phrase works from the first message of every new session. In the Harness plugin screen, enter the GitHub address:
nx9161/seller-protocol
or via CLI:
dsh plugin --profile web add github:nx9161/seller-protocol
# local clone also works:
dsh plugin --profile web add /path/to/seller-protocol
Then open a new session. The plugin injects the activation contract on session start, so you can say the phrase immediately — no fetching, no pasting.
The npm package name dsh-plugin-seller-protocol is reserved for a
future publish; the GitHub address installs today. The plugin is
zero-build and zero-dependency, so github: installs just work.
The entire pipeline from product idea to money in the bank, as agent profiles: product research, China sourcing and factory QC, freight and forwarder selection, warehousing, Amazon FBA operations, listings and PPC, Shopify and web storefronts, outstanding UI, international trade law, and finance. Mercer handles everything and reports to you.
Sister project: War Room Protocol — the same operating model for software, led by Sloane.
The Chief. Mercer takes your request, dispatches specialists, runs the War Room, and reports status, numbers, and decisions needed. The business, handled.
The seats — 15 roles, 7 divisions.
| Division | Seats |
|---|---|
| Sourcing & Supply Chain | China Sourcing Expert, Vendor Picker (China ground agent) |
| Logistics & Warehousing | Shipping Expert, Warehouse Expert |
| Marketplaces | Amazon FBA Specialist, Amazon Services Expert, Product Suggester |
| Digital Storefront | Website Expert, Shopify Expert, UI Designer |
| Legal & Finance | International Trade Lawyer, Finance & Tax Counsel |
| Intelligence | Prompt Writer, Knowledge Wizard |
| Leadership | Mercer (Chief Operator) |
Three seats can block: the Vendor Picker (failed QC), the Trade Lawyer (compliance), and Finance Counsel (tax/financial compliance). Blocks stand until cleared or the owner accepts the risk in writing.
Playbooks (office/playbooks/) — repeatable procedures, each run as
one subagent per step: intake, war-room, launch-product,
fix-listing, skill-hunt.
The War Room — runs before any product launch, inventory buy, or freight booking:
The money rule (house rule #1): no money moves without your explicit approval — inventory, freight, ads, contracts. Every buy ships with Finance Counsel's landed-cost model.
Memory (memory/) — the office's working memory: product pipeline,
vetted vendors, forwarder and 3PL panels, landed-cost models, per-SKU
P&L, compliance notes. See Privacy
— vendor names, rates, and margins live here.
Skill Hunt — when the office lacks a capability, the Knowledge
Wizard finds existing skills across the whole internet (GitHub, Hugging
Face, registries), vets them, installs them to office/skills/, and
wires up every tool they need. See office/playbooks/skill-hunt.md.
Since this is open source, a new user needs a few minutes of setup before their AI agent can run the office. Two paths:
git — only if you want the local-integration path below.Paste the activation phrase from above into
any AI agent. It fetches this repo, loads the office bundle
(office/AGENTS.md), becomes Mercer, and confirms activation. Nothing
to install.
git clone https://github.com/nx9161/seller-protocol && cd seller-protocoloffice/AGENTS.md into your own project root — it's the
complete bundle (persona + roster + protocols + memory schema).memory/INDEX.md first
(Memory Operations Protocol, repo-root AGENTS.md), so it starts
every session with full context: vendors, forwarders, P&L.gh auth login.
The office uses GitHub Issues as its task board and pull requests
for every change; gh lets your agent file issues and open PRs.| Capability | Why |
|---|---|
| File read/write in the repo clone | Staff files, playbooks, memory, logs |
| Subagent spawning | One agent per role per War Room phase |
| Internet access | Knowledge Wizard research + Skill Hunt |
git + gh CLI (recommended) | Issues as task board, PR workflow |
├── ACTIVATE.md # trigger-phrase activation contract
├── AGENTS.md # repo operating manual (memory protocol)
├── office/
│ ├── AGENTS.md # full agent bundle: persona + roster + protocols
│ ├── HOUSE_RULES.md # binding rules (money rule is #1)
│ ├── PLAN.md # founding plan
│ ├── README.md # office handbook
│ ├── staff/ # 15 employee profiles (one file per role)
│ ├── playbooks/ # intake, war-room, launch-product, fix-listing, skill-hunt
│ ├── skills/ # Wizard-installed skills (registry in README)
│ ├── scripts/ # automation (repo validation)
│ └── log/ # decisions.md + per-run journals
├── memory/ # working memory: pipeline, vendors, logistics, finance, legal
└── .github/ # issue/PR templates, CODEOWNERS, CI
CI runs office/scripts/validate_repo.py on every push and PR —
required files, reference integrity, hygiene.
The office records everything: product decisions, vendor names and
quotes, forwarder rates, landed-cost models, per-SKU P&L, and your
preferences live in memory/ and office/log/. On a public repo
or fork, all of that is public — it reveals what you sell, who you buy
from, what you pay, and what you earn.
What's in this repo's memory right now: templates only — the vendor, forwarder, and P&L files are empty scaffolds waiting for your first product. A clean starting point; keep it that way deliberately:
git filter-repo + force-push) hides it from the repo going
forward, but cannot un-publish what was already fetched.Standing rule, public or private: no secrets, tokens, keys, or credentials in code, commits, issues, or logs — ever.
| Dependency | Required? | Notes |
|---|---|---|
| None | — | This repo is fully self-contained. No external git repos, no packages, no services needed to run the office. |