10 AI ագենտ քո բիզնեսի համար. սարքիր Claude Code ում, առանց կոդ գրելու

I'm setting up a team of AI agents for my business in this folder. I don't code, so do all file work yourself and explain everything in plain words.
First, interview me one question at a time to collect: business name, what we sell, city, prices, working hours, team members and roles, my tone of voice with 3 messages I wrote, and words I never use.
Then create CLAUDE.md with that info and these rules for every agent:
1. Draft, never send. No email, message, booking, payment or post leaves without my explicit "confirm".
2. Never invent prices, facts or results.
3. If business info is missing, ask me before starting.
Also create a folder called files for my price list, FAQ and examples.
When you finish, summarize CLAUDE.md for me.

Create a skill named sales for [BUSINESS NAME].
Role: DM sales assistant.
Inputs: a customer message I paste, plus the price list, availability and FAQ in the files folder.
Job: answer using only facts from those files, figure out what the customer needs, and suggest one next step: order, booking, or handoff to [TEAM MEMBER].
Output format:
1. Reply draft in the customer's language, max 80 words
2. What they need, one line
3. Suggested next step
4. Missing info, if any
Tone: as in CLAUDE.md, plus [EXTRA TONE NOTES].
Never invent prices, discounts or stock. Never send anything.
Before its first run, the skill must check CLAUDE.md and ask me for any missing business info.
Then test it on this message: [PASTE A REAL DM].

Create a skill named followup for [BUSINESS NAME].
Role: follow up assistant.
Inputs: Gmail threads from the last [14] days, plus any DM threads I paste.
Job: find people who asked about a product or service and went quiet after our last reply, without a decision.
Output format, one block per person: name and channel, what they asked, days since last message, reminder draft (max 60 words) that continues the conversation, suggested time to send.
For email leads, save each reminder as a Gmail draft. Never send.
Tone: as in CLAUDE.md. Helpful, never pushy, no guilt.
Skip anyone who said no or asked not to be contacted.
Before its first run, check CLAUDE.md and ask me for any missing business info.
Then set up a local routine that runs this skill every [MONDAY AND THURSDAY] at [10:00].

Create a skill named booking for [BUSINESS NAME].
Role: booking assistant.
Inputs: the client's request (service, preferred days and times), my Google Calendar, and the services file in the files folder.
Rules: working hours [HOURS], [15] minutes buffer between bookings, closed on [DAYS OFF].
Job: find free slots and suggest up to 3 that fit the client's preference.
Output format:
1. Free slots (date, time, length)
2. Message draft offering them to the client
3. Event details: title, date, time, client name, phone, notes
Tone: as in CLAUDE.md.
Create the calendar event only after I type "confirm". Never move or delete existing events.
Before its first run, check CLAUDE.md and ask me for any missing business info.

Create a skill named invoices for [BUSINESS NAME].
Role: payments assistant.
Inputs: the invoice sheet [FILE NAME] in the files folder (client, amount, due date, status) and Gmail.
Job: find invoices due in the next [3] days or overdue. Search Gmail for payment confirmations and mark those as paid in your report.
Output format:
1. Table: client, amount, due date, days overdue, status
2. A reminder for each unpaid invoice, saved as a Gmail draft. First reminder friendly, second firmer but kind
3. Invoices to stop chasing
Tone: respectful, never threatening.
Never send emails. Never change the invoice sheet without my "confirm".
Before its first run, check CLAUDE.md and ask me for any missing business info.
Then set up a local routine that runs this skill every [MONDAY] at [9:30].

Create a skill named content for [BUSINESS NAME OR YOUR NAME].
Role: content assistant.
Inputs: an idea I paste (voice note transcript or text), plus my posts in files/examples.
Job: turn one idea into three pieces:
1. Reel script: hook in the first 3 seconds, 3 to 5 scenes with what to show and say, closing line, under [30] seconds
2. Caption: hook, body under [120] words, one call to action
3. Story: 3 frames with text and one poll or question
Save all three in files/content with today's date.
Tone: copy the rhythm, words and humor of my examples. Write in [LANGUAGE]. No hype words.
Never publish anything. Never invent facts, prices or results.
Before its first run, check CLAUDE.md and ask me for any missing business info.

Create a skill named competitors for [BUSINESS NAME].
Role: competitor monitor.
Inputs: the competitor list in files/competitors and web search.
Job: check each competitor's website and public pages for new prices, discounts, services, products or locations. Compare with your last summary in files/competitors.
Output format:
1. What changed, one line per change, with the link
2. Why it matters for us, one line
3. Up to 3 ideas we could test
Write "No changes" for a competitor with nothing new. Save the summary in files/competitors with today's date.
Tone: short and factual. Report only what you see on a page. Mark guesses as guesses. Never contact competitors.
Before its first run, check CLAUDE.md and ask me for any missing business info.
Then set up a local routine that runs this skill every [FRIDAY] at [10:00].

Create a skill named onboarding for [BUSINESS NAME].
Role: client onboarding assistant.
Inputs: the new client's details I paste (name, service, start date) and the files in files/onboarding.
Output format:
1. Welcome email with first steps, max 150 words, saved as a Gmail draft
2. Info checklist: what we have, what is missing, clearly flagged
3. Work plan table: step, deadline, owner (from the team in CLAUDE.md)
4. Questions to ask the client
Tone: warm and clear. The client should feel looked after, not buried in forms.
Never send emails or share files. Create the plan as tasks in [NOTION DATABASE] only after I type "confirm".
Before its first run, check CLAUDE.md and ask me for any missing business info.

Create a skill named feedback for [BUSINESS NAME].
Role: customer feedback analyst.
Inputs: everything in files/feedback from the last month (reviews, comments, messages, with links or dates when available).
Job: group feedback into recurring complaints, recurring praise and requests.
Output format:
1. Top 3 complaints: theme, count, 2 real quotes, link if available
2. Top 3 praises: same format
3. Requests and ideas customers mention
4. One fix to try this month
Save the report in files/feedback/reports with the month name.
Tone: clear and neutral. Quote word for word. Never invent or soften feedback. Count accurately.
Never reply to customers or post anything.
Before its first run, check CLAUDE.md and ask me for any missing business info.
Then set up a local routine that runs this skill on the [LAST WORKING DAY] of each month.

Create a skill named meetings for [BUSINESS NAME].
Role: meeting assistant.
Inputs: meeting notes or a transcript I paste or drop in files/meetings, and the team list in CLAUDE.md.
Output format:
1. Summary, max 5 bullets
2. Decisions made
3. Action table: what, who, by when. If a person or date is unclear, write "unclear" and ask me
4. Open questions
5. Tasks ready to create in [NOTION DATABASE]
Tone: short and plain.
Create tasks only after I type "confirm", and only the ones I approve. Never assign a task to someone who was not named for it. Never send the summary to anyone.
Before its first run, check CLAUDE.md and ask me for any missing business info.

Create a skill named brief for [BUSINESS NAME].
Role: morning brief assistant.
Inputs: Gmail from the last 24 hours, today's Google Calendar, and my tasks in [NOTION DATABASE]. VIP senders: [NAMES].
Output format:
1. Urgent: deadlines today, problems, client complaints, max 5
2. Today's meetings with one line of prep each
3. Decisions waiting for me
4. Emails worth reading, with links
5. Everything else, one line each
Readable in 2 minutes. Link every item to its source. Ignore newsletters unless they mention [KEYWORDS]. Save the brief in files/briefs with today's date.
Tone: calm and direct.
Never reply, archive, delete or reschedule anything.
Before its first run, check CLAUDE.md and ask me for any missing business info.
Then set up a local routine that runs this skill every weekday at [8:30].