Set up a workspace

An agent reads this skill with get_skill and the name set-up-workspace. It is also the MCP prompt set-up-workspace, and part of the Claude Code plugin.

What follows is the skill as the agent reads it.

Work down this list. get_started says which steps are already done: skip those. Some steps need a person in a browser. Say which, give the link, and carry on with what you can do.

1. See where things stand

Call get_started. Read missing. Tell the person in a few lines what is done and what is left.

2. HubSpot (a person)

If HubSpot is not connected, a person must connect it: Settings in Signalbox. You cannot. Stop here until it is done.

Once connected, call get_hubspot_status. If the forms or reps have never been read, call sync_hubspot (Publish level) and check the status again after a minute.

3. The website

Call list_sites. If the site is missing, ask for its address and call add_site (Publish level). The answer holds the tag: one line to put in the head of every page that has a form. Give it to the person. If the site sends a Content-Security-Policy header, point them to the install guide.

4. Reps and calendars (each rep)

Call list_reps. A rep with no connected calendar gets no leads. For each one who should, call send_calendar_link (Publish level). The rep gets an email and connects their own calendar. You never see the link.

Tell the person who has been sent a link. Do not wait for the reps: carry on.

5. A queue

If leads will be shared between reps, call save_queue (Build level) with a name and its members (rep ids from list_reps). The defaults suit most teams: the rep with the fewest leads for their weight goes next, counted when picked, reset monthly.

6. A meeting type and working hours

If the flow will show a calendar, call save_meeting_type (Build level): a name and a length in minutes are enough.

Call get_working_hours. If the hours or the time zone are wrong for the team, ask, then set_working_hours (Publish level).

Once a rep has connected, preview_free_times shows the times a visitor would be offered. Use it to check the hours make sense.

7. A flow

Follow the build-a-flow skill (get_skill with build-a-flow).

8. Go live

When the person has agreed to the flow:

1. publish_flow.
2. set_form_flow for the form, and set_form_routing on.
3. Ask the person to submit the form once on the real page.
4. If you may read leads, list_leads then get_lead shows the lead and the path it took. If not, give them the link to Leads.

Finish

Tell the person what is set up, what is waiting on someone else (HubSpot, a rep’s calendar, the tag on the site), and where to look: the links from the tools.