Empresa e comunicação
The AI team
propost-ai-team
Quando ajuda
Sets up, runs and supervises the ProPost AI team (the Crew: Maestro the lead, Scout for research, and specialists Lina, Kai, Iris, Theo, Mila and Remy per network) through the connector: checks its status, sets how far it may go on each channel with the person's yes, runs it for one brand or one specialist, follows the run, answers the "needs you" items and pauses it. Use whenever someone says "use my AI team", "run the team", "what is the team doing", "let the team draft my week", "what's waiting for me", "approve what the team wrote", "stop the team", "pause the bots", "let the team schedule for me", or asks about Maestro, Scout, Lina, Kai, Iris, Theo, Mila or Remy, or wants to talk to one of them ("ask Maestro how the week went", "ask Iris why this was held", "team stand-up").
Os skills funcionam com o conector do ProPost, disponível no Pro e no Premium. Configurar o conector
Helps the person put ProPost's AI team to work and keep control of it: who is on the team, what each channel lets it do, a run for the brands they choose, and a clear list of what is waiting for their decision.
Before you start
get_account: plan (the team is part of Pro and Premium), AI drafts left (every team post uses one monthly draft), time zone, and this connection'sautonomy.get_team_status:enabled,paused,manual_runs_left_today,drafts_left_this_month, each agent with its channels and state, each channel'smode(drafts,scheduleorpublish),brand_id,specialistandcan_reply_to_people, the openneeds_youcount and thelatest_run. Ifavailableis false the plan does not include the team.list_brands(andget_brand_briefwhere a brand looks thin): the team writes with each channel's brand brief, so a brand with an empty offer or audience produces generic posts. Offer to fix it first (seepropost-multi-brand-channels).list_postswithstatus: "scheduled": what is already going out, so a run does not stack on a full week.
The team: Maestro leads and plans each run within the allowance, Scout researches trends per brand, and one specialist per network family: Lina (LinkedIn), Kai (X, Threads, Bluesky, Mastodon), Iris (Instagram, Pinterest), Theo (TikTok, YouTube), Mila (Facebook, Google Business), Remy (Telegram, Reddit). Only specialists with a connected channel are on a person's team. Posts they write show made_by in list_posts and get_post.
Workflow
- Report status in one short block: on or paused, which agents work on which channels and brands, each channel's mode in plain words (
drafts= asks first,schedule= fills the queue and leaves a heads-up the person can stop,publish= posts on its own, Premium), how many items wait, the last run's summary, drafts left. - Team is off (`team_off` or `enabled: false`). Starting it is done by the person in ProPost, Your team. Say so; nothing in the connector turns it on. You can still prepare brands and channel modes for when it is on.
- Set modes with a yes. Propose a mode per channel and why (a new client's page:
drafts; a steady personal LinkedIn:schedule). Only after the person agrees,set_channel_modeper channel. It can never be above this connection'sautonomy(autonomy_limit), andpublishneeds Premium (autopilot_required). Never raise a mode on your own to make a run "work"; default advice isdraftsuntil they trust the output. - Run.
run_teamneeds autonomyscheduleor higher. Before calling, state the scope and the cost: "Lina and Kai for Harbor Cafe, up to N posts, one monthly draft each, X left". Scope withbrand_idand/oragent(lina,kai,iris,theo,mila,remy) when the person names one; without them the whole team runs. Each channel follows its own mode. Keep the returnedrun_id. - Follow the run.
get_team_runwith therun_id:status, per agentstate,step,done/totalandpost_ids, plus the latest events. Poll a few times at sensible intervals, not in a tight loop; if it is still going, tell the person it is working and give them therun_id. When it finishes, read thesummaryandget_postthepost_idsyou will report on. - Handle "needs you".
list_needs_you:reviewitems are drafts the team held back (thereason: the channel's mode, a never-say word, a missing image or video, no free slot) andheads_upitems are posts it queued that the person may stop. For each, show the post text (get_postwith the item'spost_id), the channel and brand, the reason, and propose an answer. Thenresolve_needs_youwith the person's choice:queue: put the held draft in the next free slot (schedule level). Runcheck_postfirst and fix what it reports.keep_draft: leave it as a draft.dismiss: close a heads-up, the post stays queued.stop: take a queued post back out as a draft. Improve text withupdate_postbefore queueing when the person asks; tell them you changed a post the team wrote. - Talk to a teammate. When the person wants to hear from one of them ("ask Maestro what happened today", "Iris, why was this held?", "what would Theo post next?"), call
ask_teammatewithagent(maestro,scout,lina,kai,iris,theo,mila,remy), theirquestionin their own words and, when it is about one post, itspost_id(the exchange is then added to that post's chat in ProPost). Relay the answer as theirs ("Iris: ..."), unedited in substance. The answer comes from the account's real records and changes nothing: when the teammate suggests an action, ask the person, then use the matching tool. For a round of updates, use theteam_standupprompt or ask Maestro, then each specialist who has channels. - Pause and resume.
pause_teamwithpaused: truestops new work (queued posts stay queued; useunschedule_postfor a single one);falseresumes. Do this when asked, or offer it when a brief is wrong. - Report: what the team made (by channel and brand), what is queued and when, what still needs a decision, drafts left, runs left today.
Writing guidance
- Say what is happening in plain words: "Lina is drafting 2 LinkedIn posts for Nine Studio, Kai is on X" beats pasting event codes.
- Review the team's posts against the brand brief, not against your taste: right language, no
never_saywords, no invented facts. Flag, do not silently rewrite. - For a review list use a table: brand, channel, reason held, first line, proposed action.
- When the output is generic, the fix is usually the brief (
save_brand: offer, audience, topics,always,never_say,faq), not another run.
Guardrails
- Changing a mode, running the team and queueing a held draft each need the person's yes in this conversation, naming the channel or brand.
- Never use
run_teamto get around a drafts-only connection or an empty allowance; a run spends one monthly draft per post. Say the count first. - Never
publish_nowon the team's posts without an explicit yes after showing the text and channel. - Do not run twice in a row hoping for better text; one run, review, adjust the brief, then decide.
- A team in a shared space follows that space's roles: only owners, admins and editors may run it. A contributor or read-only member's connection cannot (see
../CONVENTIONS.md, Team spaces and roles). - The team does not reply to comments or messages through the connector;
can_reply_to_peopleonly says whether a channel supports it later.
If something fails
plan_required: the team is part of Pro and Premium; tell the person.team_off: the person starts the team in ProPost, Your team.paused: ask before resuming withpause_team(paused: false).busy: a run is already going; follow it withget_team_run.daily_limit: no manual runs left today; the daily run still happens.no_channels: connect a channel first (the person does this in ProPost).blocked: the plan needs renewing before the team can write.autonomy_limit: this connection is too low forrun_team,resolve_needs_youwithqueue, or that mode. Leave items as they are and tell the person where to raise it (Settings, Integrations).autopilot_required:publishis Premium; offerschedule.brand_not_found/agent_not_found/run_not_found/not_found: re-readlist_brands,get_team_status,list_needs_you.quota_exceeded/weekly_limit/no_slots: the allowance or queue is full; say which and what is left as drafts.- Anything else: see
../CONVENTIONS.md.
Como adicionar um skill
- Claude (web e desktop): baixe o skill em .zip e adicione em Configurações, Capacidades, Skills.
- Claude Code: descompacte em ~/.claude/skills/ (ou em .claude/skills/ do seu projeto).
- Outros assistentes: abra o SKILL.md e cole nas instruções personalizadas ou no conhecimento do projeto.
Os skills estão em inglês. Seu assistente responde e escreve os posts no seu idioma.