import-clients
Skill0 starsChanged 10 days agoMITView on GitHub
Create client folders for many brands at once from a CSV file (columns name, brand, site, shopify, meta).
1 other project uses a version of this.
Adopted by
Most recently taken up by
- itinovo-crm/claude-plugintheir own version, first seen Oct 17, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- itinovo-crm/claude-plugin★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- add-clientSkill
- agency-setupSkill
- agency-workspaceSkill
- briefSkill
- client-numbersSkill
- clientsSkill
- connectSkill
- onboardSkill
- rename-clientSkill
- saveSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
If the user has no file yet, show this template and stop:
- Very specific: line 17
Run from the agency folder: node "${CLAUDE_PLUGIN_ROOT}/scripts/clients.mjs" import $ARGUMENTS
≈ “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.
Files
Import clients from a CSV
- If the user has no file yet, show this template and stop:
name,brand,site,shopify,meta Caliego,Caliego,https://caliego.com,caliego.myshopify.com,act_1234567890brandis the Brand name in Analify (defaults toname).shopifyandmetaare optional notes used in the setup checklist. - Run from the agency folder:
node "${CLAUDE_PLUGIN_ROOT}/scripts/clients.mjs" import $ARGUMENTS - Report how many folders were created and list any rows that failed with the reason.
- Give the per-client next steps in one short list: create the Brand in Analify (Agency → Clients), connect Shopify and Meta inside it, then open the client's folder in Claude Code and authenticate its connection in
/mcp. Suggest doing them in batches of about ten, and asking each client for Shopify collaborator access first, because waiting on that is the slowest part.
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
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.

