Open source · In production

Seller workspace

An open Claude Code workspace template for a marketplace seller: connectors to three marketplaces, seven ready commands - from the weekly report to ABC analysis - and a knowledge base inside the repository itself. One clone, one store.

The pain

Going through sales, unit economics, the funnel, card SEO, ABC analysis, competitors - that is a job for a separate person. A small store has nothing to hire them with.

Now

An open template: one clone per store, keys in the environment, connectors to three marketplaces and seven commands for those questions. Intended so; how far it replaces an analyst I have not measured.

What the business gets

The report, unit economics, the funnel, an SEO audit, ABC and competitors are called by a command instead of being assembled from scratch each time.
The store keys stay with the owner: they live in the environment of their clone, not in someone else’s service.
Critical operations require confirmation and, without it, only show a «before → after» preview.
Improvements go back into the template rather than staying inside one store’s clone.

From source to result

A clone per store
Marketplace keys in the environment
Connectors to three marketplaces
Commands and knowledge base
An answer in chat

Changing a price or stock, or replying to a review, only shows a preview without an explicit confirmation: a live store does not change on a careless phrasing.

How it works

The usage model is one clone per store: keys, logs and caches are not versioned, while improvements come back into the shared template as a separate change.

The phrase «without hiring an analyst» is the purpose of the template and an assessment from store owners’ own words. I have no measurement of how much work it takes off, so for now it is an intent rather than a result.

Who maintains it now

Me. Open source; the store is run by its owner inside their own clone.

Other cases for this step

Internal system · In production

Management finance loop

A finance analyst develops it, not a programmer

The pain: Every change ran into hiring and a queue to the developer: growth depended on whether a person could be found.
Now: The finance analyst extends the system directly; the engineer owns review and the release to production.

Maintained by: a finance analyst
Specialist’s path: one month to margin calculation

43 % of changes are made by a company specialist, not a programmer

The same system pays off across 3 more steps

Internal system · In production

Product portal

A product specialist runs it: 73 % of changes are theirs

The pain: A fix in product data had to be ordered: from the PLM vendor as a paid modification, internally as a ticket to a developer. Either way it meant a queue.
Now: The portal is run by the product specialist - the person who fills in the product cards every day. The engineer owns review and the release to production, not the next card attribute.

Maintained by: a product specialist
Specialist’s path: days to a working portal

73 % of changes are made by the product specialist

The same system pays off across 2 more steps

Open source · In production

Starter application template

Seven applications in a month with one team

The pain: Every new project started with a week of setup, and only an engineer could do it. The queue to that engineer was the real ceiling on speed.
Now: Setup stopped being the bottleneck: the order those three production systems were built in is folded into a single command. In that same month one team launched seven applications.

Launched
Maintained by: an engineer and company specialists
Workspace: skills and commands for daily work

The same system pays off on one more step

GitHub

Own product · In production

Content factory

A video from script to subtitles - without contractors

The pain: Video means a scriptwriter, a motion designer, an editor and someone to lay the text out across platforms. For one author that is a contract per video, or no videos at all.
Now: A workshop in a repository: commands write the script in blocks, overlays and diagrams are built in code, and a local Whisper does the transcription. Filming, editing and publishing stay with the human.

In the workshop
The graphics library
Subtitles

nine videos taken through to publication, two still in progress

Type: Open source
Status: In production
Commands: seven, from the report to ABC analysis
Maintained by: the store owner
Replaced: collecting reports across the accounts by hand

Claude CodeMCPTypeScriptNode.jsMarkdown

GitHub