| name | summit-get-started |
| description | First-run onboarding skill for anyone setting up the Summit Home Renovations skill pack for their own business. Use this skill whenever the user says "get started", "set up my brain", "onboard me", "I just cloned the repo", "help me set this up for my business", or anything about initializing the Zapier Tables Brain that the other Summit skills depend on. This skill interviews the user with a short set of business questions, then writes the answers into the Your Brain table in Zapier Tables so the morning-triage and quote-generator skills have the context they need to run.
|
Summit — Get Started
This is the first skill to run if you (or someone you shared the repo with) have never used the Summit skill pack before. The morning triage and quote generator both depend on a populated Your Brain table in Zapier Tables. If that table is empty, they either fall back to weak defaults or refuse to run. This skill fixes that in one sitting.
What it does, in order: interview the user, confirm the answers, then write one row per answer into the Your Brain table.
When to run
- First time using the skill pack for a new business
- After cloning the repo into a fresh ClickUp + Zapier workspace
- When the user says the triage or quote output "doesn't sound like them"
- Any time the user wants to reset or rebuild the Brain from scratch
If the table already has rows for this project, confirm with the user before adding more — offer to append, replace, or cancel.
Step 1 — Check whether a Brain already exists
Before asking any questions, look up the Your Brain table and see if there are records for this project.
Tool: zapier_tables_find_records
- Table:
Your Brain
- Filter:
type = "memory" (leave project open for now)
If records come back:
- Ask the user what business/project name they're setting up.
- If rows already exist under that project name, say so plainly and offer three choices: append new rows, replace the existing ones, or cancel.
- Do not delete anything without an explicit "yes, replace" from the user.
If no records come back, move on.
Step 2 — Ask for the project name
One question, kept simple:
"What should I call this business in the Brain? I'll use it as the project tag on every row so the skills only read the rows that belong to you. Example: Summit Home Renovations."
Lock that answer in as PROJECT_NAME and use it for every row you write later.
Step 3 — Run the interview
Ask these questions in order. Use the AskUserQuestion tool where there's a clean multiple-choice, and free text otherwise. Do not batch them all into one giant wall of text — ask, wait, ask the next one. People answer better when they can focus on one thing.
The goal is to end up with the ten core Brain records listed in brain/sample-data.md. The questions below map one-to-one to those ten records.
3.1 — Who we are
"In one or two sentences, who is this business? Name, location, size of the team, how long you've been at it, anything that makes you distinct."
3.2 — What we do and don't do
"What kind of work do you take on? Just as important: what do you not do? And what's your typical project budget range?"
If the answer is vague, push once: "Any specific project types you refuse on sight? Roofing? Commercial? Jobs under some dollar amount?"
3.3 — How you talk to clients
"How do you talk to clients? Formal or casual? Any words you use or avoid? Does one person sign every proposal, or does it vary?"
3.4 — Standard proposal intro
"When you send a quote, is there a standard opening paragraph you use — or that you would use if you had one written down? If not, I can draft one based on your answers so far and you can edit it."
If they say "draft one," write a two-sentence intro in their voice and show it for approval before saving.
3.5 — Any pricing or scope rules
"Are there rules that apply to every job? Things like contingency on older homes, minimum project size, what you mark up, what you pass through at cost?"
3.6 — Payment terms
"What's your standard payment schedule? Deposit percentage, milestones, final payment — whatever you normally tell clients."
3.7 — Scheduling or staffing constraints
"Any scheduling constraints I should know about? Subcontractors that are booked out? A busy season? Equipment or crew bottlenecks?"
3.8 — Discounts or promotions
"Do you offer any discounts — early booking, repeat client, referral, seasonal?"
3.9 — Margin / markup rules
"Without getting into exact numbers if you don't want to, roughly how do you mark things up? Labor, materials, subs. And is anything passed through at cost?"
3.10 — Disqualifiers
"What are the red flags that make you say 'not for us' immediately? Jobs you'll always decline, regardless of the dollar amount."
Step 4 — Summarize and confirm
Show the user a clean list of all ten answers, numbered, in a single response. Ask:
"Here's what I heard. I'm about to write these as ten rows into your Your Brain table under the project name [PROJECT_NAME]. Anything you want me to fix, combine, or drop before I save?"
Wait for confirmation. If the user wants edits, apply them and re-show. Loop until they say save.
Step 5 — Write rows to the Brain
For each confirmed answer, create one record in the Your Brain table. Use this mapping:
| # | Record name | type |
|---|
| 1 | Who We Are | memory |
| 2 | What We Do | memory |
| 3 | How We Talk to Clients | memory |
| 4 | Our standard proposal intro | memory |
| 5 | Pricing Rules | rule |
| 6 | Payment Terms | rule |
| 7 | Scheduling Constraints | schedule |
| 8 | Discounts and Promotions | rule |
| 9 | Margin Rules | rule |
| 10 | Disqualifiers | rule |
Tool: zapier_tables_create_record
For each row:
table: "Your Brain"
fields:
name: [record name from table above]
type: [type from table above]
project: [PROJECT_NAME from Step 2]
content: [the user's answer, cleaned up into plain prose but kept in their voice]
Write them one at a time so a failure on row 6 doesn't leave row 7–10 in a weird state. After each successful write, note it in a running tally so you can report at the end.
If any write fails, stop, tell the user which row failed and why, and ask whether to retry or skip.
Step 6 — Final report
When all rows are in, give a short confirmation:
✅ Brain initialized for [PROJECT_NAME]
Wrote 10 records to the Your Brain table:
1. Who We Are
2. What We Do
3. How We Talk to Clients
4. Our standard proposal intro
5. Pricing Rules
6. Payment Terms
7. Scheduling Constraints
8. Discounts and Promotions
9. Margin Rules
10. Disqualifiers
You're ready to run:
• summit-morning-triage — daily lead triage from your inbox
• summit-quote-generator — auto-quote new leads in ClickUp
You can edit any of these rows directly in Zapier Tables anytime. The skills will pick up changes on the next run.
Edge cases
- User doesn't have Zapier Tables connected. Stop at Step 1. Tell them to connect the Zapier MCP, and offer to hand them a filled-out markdown doc with all ten answers that they can paste in manually once they're set up.
- User only wants to fill in some of the ten. Fine. Skip the ones they don't have answers for and only write the rows they confirmed. Note in the final report which categories were skipped so they can come back to them later.
- User wants to add custom categories beyond the ten. Great sign. Let them add as many extra rows as they want — same
type/project tagging, free-form name and content. The downstream skills read by type + project, not by name, so new rows just get picked up automatically.
- User has multiple businesses. Re-run this skill with a different
PROJECT_NAME. Same table, different project tag. The skills filter on project, so the two businesses won't bleed into each other.
