agentleFS
scalyax-aiscalyax-ai/claude-plugin-performance-marketing-agency/skills/onboard/SKILL.md

onboard

Skill0 starsChanged 9 days agoMITView on GitHub

Onboard a performance marketing agency onto Analify in Claude Code — agency name, every client's website, one folder and one Analify connection per client, then connecting each client's Shopify, Meta, TikTok, Google Ads and Snapchat accounts in Analify. Start here.

168 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use soak-test, team-live-ops and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • lilangMaxSkill

    soak-test

    Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.

    Also in 9 projects that use this

  • lilangMaxSkill

    team-live-ops

    Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.

    Also in 9 projects that use this

  • HK-hubSkill

    teach-impeccable

    One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.

    Also in 19 projects that use this

  • CoralGameSkill

    project-stage-detect

    Automatically analyze project state, detect stage, identify gaps, and recommend next steps based on existing artifacts.

    Also in 15 projects that use this

  • CoralGameSkill

    team-level

    Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation.

    Also in 11 projects that use this

  • +5 more from lilangMax
  • +2 more from CoralGame

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 156 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If $ARGUMENTS is empty, ask: "What's your agency called?" Then run: node "${CLAUDE_PLUGIN_ROOT}/scripts/clients.mjs" init --name "<agency …

    line 14
  2. Distinctive:

    Ask: "Paste your clients' website addresses, one per line (or the path to a CSV with columns name,brand,site,shopify,meta)."

    line 19
  3. Very specific:

    Run node "${CLAUDE_PLUGIN_ROOT}/scripts/clients.mjs" open to open Analify's Agency → Clients page (no Analify account yet: open signup).

    line 25
  4. Distinctive:

    Never create Analify accounts, enter passwords or click anything in Analify for the user: they do the connecting in their browser.

    line 37

“Common” is measured: kept by at least 6 in 10 of the 156 edited versions of this file we could read. “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

Onboard the agency

Walk the agency through this one step at a time. Short messages, plain words, one question at a time. Run every script from the folder the user is in (it becomes the agency folder).

Step 1 — The agency

If $ARGUMENTS is empty, ask: "What's your agency called?" Then run: node "${CLAUDE_PLUGIN_ROOT}/scripts/clients.mjs" init --name "<agency name>" Tell them this folder now holds all their clients, one folder each. Then ask them to turn on auto-update once, so new versions of this plugin reach them on their own: /plugin → Marketplaces → scalyax → Enable auto-update (a plugin can't switch this on itself; an organization owner can switch it on for the whole team, see the README).

Step 2 — The clients

Ask: "Paste your clients' website addresses, one per line (or the path to a CSV with columns name,brand,site,shopify,meta)."

  • Websites: node "${CLAUDE_PLUGIN_ROOT}/scripts/clients.mjs" add-sites <url> <url> ...
  • CSV: node "${CLAUDE_PLUGIN_ROOT}/scripts/clients.mjs" import <file.csv> Show the list of clients created. Two websites with the same name (nour.com and nour.ae) become two clients ("Nour" and "Nour AE"). Ask if any name is wrong; fix it with node "${CLAUDE_PLUGIN_ROOT}/scripts/clients.mjs" rename "<current name or website>" "<right name>", adding --brand "<Analify brand name>" if the brand is named differently in Analify. Renaming keeps the client's connection and sign-in.

Step 3 — Connect each client's accounts in Analify

Run node "${CLAUDE_PLUGIN_ROOT}/scripts/clients.mjs" open to open Analify's Agency → Clients page (no Analify account yet: open signup). Then tell them, for each client:

  1. Open or add the client's brand in Analify. Agency is in beta; if the agency view isn't on their account, they can use brands their Analify account already belongs to, or ask Analify to switch Agency on.
  2. In that brand, connect what the client runs: Shopify, Meta Ads, TikTok Ads, Google Ads (beta), Snapchat Ads, Google Analytics (beta), and couriers such as Bosta.
  3. Shopify asks the store to install the Analify app, so ask each client for Shopify collaborator access first; that wait is usually the slowest part. Suggest batches of about ten clients.

Step 4 — Connect Claude to each client

For each client: open Claude Code in that client's folder (terminal: cd "Clients/<Name>" && claude; desktop app: open the folder as a new session) and run /analify-agency:connect. It signs in to that client's brand and reads what's connected, so the plugin works with exactly what each client has.

Step 5 — Check progress

node "${CLAUDE_PLUGIN_ROOT}/scripts/clients.mjs" status — show who is ready and, for the rest, the one next thing each needs. Remind them they can run /analify-agency:clients any time.

Never create Analify accounts, enter passwords or click anything in Analify for the user: they do the connecting in their browser.

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.