New Agents Start Here

Train agents the way you train people. Point them at one front door. Then add your GCT — who you serve, how you position, how you operate. Do not rebuild the wheel.

You do not onboard a new hire by dumping last week’s Slack into their head. You point them at the welcome page, then they learn how you do things. Agents need the same treatment. If you skip it, the fifth Claude, the new Cursor chat, the Grok Bot, and the intern’s ChatGPT all invent a different company.

What problem this solves

Companies are spinning up agents faster than they can brief them. One person runs Cursor, Claude, ChatGPT, and Grok. A team of ten does the same. None of those runtimes share a brain unless you give them one.

This page is the on-ramp. It is for operators who already have more than one agent, or who are about to. The value is simple: the next agent starts useful on minute one, and it does not undo the last one.

Train them like humans

A new teammate gets a welcome URL, a roster, and the house rules. Then they add judgment. A new agent gets a start-here file, a roster, and the house rules. Then they add GCT — your goal, your content, your targeting.

Do not paste the client list into ChatGPT custom instructions, Claude memory, and a Cursor rule, then update all three when someone churns. That is how rows disappear and dead accounts keep getting tickets. Vendor memory is a cache. The record is a file your team owns.

What goes in START HERE

Keep it short enough to scan. A smart person should not feel talked down to. An agent should not have to guess.

Humans on our team still start at /new-team-member/. Agents start here. Same company. Two doors on purpose, because a welcome essay written for people is the wrong shape for a model that can clone a repo.

Three statuses. That is the whole client list.

You need a database, not a vibe. We use three values. You can copy the words. You cannot copy our private names onto the open web, and you should not publish yours either.

Unpaid this month is not Not Active. Missing from this month’s money tab is not a delete. Never delete a row. The flag switches. Humans comment. Agents write the file. If the roster says Not Active, the agent stops before it “helps.”

The spreadsheet your bookkeeper loves is the money view. It is not the client list. Filter the roster when you need who is paying.

Take the published skills. Add your GCT.

You do not need a new agentic framework. You need a front door, then the skills a team already keeps current, then the thin layer that is actually yours.

Our marketing skills live in public: skill packs, the source on github.com/dennisyu/local-service-spotlight-skills, the operating map at The System, and the install path at AI agent implementation. A skill is how. A routine is when. Point your agent at those URLs instead of asking it to invent Dollar a Day, the SEO Tree, or article guidelines again.

Then say the sentence that makes it yours:

Load Dennis’s published skills. Combine them with our positioning, the clients we serve, and how we operate — our GCT. Do not rebuild the framework. Keep it current from the source.

That is the whole bargain. The framework is a moving target because a team is paid to keep updating it. Your GCT is the part no skill pack can know until you write it down.

Stop agents from colliding

Two agents once built the same memory system in the same hour in the same folder. The fix is boring and it works: before real work, claim the task in a shared live-state file. If a claim is fresh, coordinate or pick different work. Read-only questions do not need a claim.

After every substantive organization job, write one private internal note in the team runtime. That note is the internal job receipt. Publish a public meta-article only when the run is public-safe, reusable proof and can link to its parent definitive article. Do not make the human click Push for the internal note; the agent finishes the git plumbing.

Feed this URL to any agent

Copy the box. Point Claude, Cursor, Grok, ChatGPT, or a vendor bot at it. Then add two private files they cannot get from the open web: your START HERE, and your roster.

You are joining a company that already has agents. Before any client or site work:

1. Read https://blitzmetrics.com/new-agents-start-here/
2. Read our private START HERE (who we are, where files live, how we operate).
3. Read our client roster. Status is only Active Client, Special Project, or Not Active. If Not Active, stop. Never delete a row. The money spreadsheet is not the roster.
4. Load published skills from https://localservicespotlight.com/skill-packs/ and https://github.com/dennisyu/local-service-spotlight-skills. Do not invent a second marketing framework.
5. Combine those skills with OUR GCT: who we serve, how we position, how we operate.
6. Claim your task on the shared live-state file so two agents do not build the same thing.
7. After a substantive job, write the private internal note. Publish a public meta-article only when the run is public-safe, reusable proof; link it to the parent definitive article. Do not hand the human a paste.

Vendor memory is a cache. The files we own are the record.

If the agent can clone your private repo, that repo is the front door. If it cannot, this public page plus the two private files in the project is enough to start. A filtered Drive or project copy is a distribution mirror, not a second source to edit. Do not wait for a perfect knowledge graph before the fifth agent ships something.

If you are joining us, human or agent

Do not treat this page as the job application. It is the operating manual after you are in. Recruiting posts should send people to two different doors:

One of the jobs a new pair will ship is interactive video: educate, entertain, train, and qualify in one sitting. We already taught the method in create your own interactive video and how to use interactive video in a funnel. The product is a choose-your-own-adventure in Tolstoy. Agents can inventory clips and wire branches. A young adult still owns the show: what the next question should feel like, and whether the path qualifies or just entertains.

Where this sits

Shared memory across vendors is Give your AI team one shared brain. The public-safe capsule is Dennis agent context. Doing the work instead of handing a paste is if you can do it, you should. This page is the missing onboarding step: what the new agent reads first.

Lookup for every named concept: canonical directory. How we write: article guidelines.