القائمة
Produce a weekly agency status — traffic-light health per project, the week's top three priorities, blocked items with owners, and a Slack/WhatsApp-ready morning briefing.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Draft a clean client approval request, set a 48h SLA with a 72h escalation, and track revision rounds so the third billable revision never slips through unbilled.
Generate a client proposal from scope, budget and past project references. Draws from scope/outcome example pairs when provided.
Build a line-item client quote with payment terms and a revision policy, run an internal margin check, and warn when gross margin drops below 40 percent before you send it.
Turn a month of campaign data into a confident client report — executive summary, what worked, what didn't, next month's plan and a clean channel/KPI table with deltas.
Run a fast, blame-free project retrospective — what worked, what didn't, root causes and three concrete changes — and append a structured entry to LESSONS.md.
Turn a rough client request into a structured project brief with phases, tasks, owners, deadlines and risks. Ready to paste into Asana, ClickUp or Notion.
| name | agency-status |
| version | 1.0.0 |
| description | Produce a weekly agency status — traffic-light health per project, the week's top three priorities, blocked items with owners, and a Slack/WhatsApp-ready morning briefing. |
| author | MarcoZorn |
| license | MIT |
| tags | ["agency","workflow","operations","management"] |
| compatible | claude-code, codex-cli, cursor, gemini-cli, openclaw |
English: "status update", "team briefing", "weekly update", "what's happening", "Monday briefing", "agency status".
Italiano: "stato agenzia", "briefing team", "aggiornamento settimanale", "riunione lunedì", "come stiamo".
Gives an agency owner or PM a single, honest read of the whole studio in thirty seconds: every active project on a traffic light, the three things that actually matter this week, what is blocked and who unblocks it, and a briefing message ready to drop in Slack or WhatsApp on Monday morning. It replaces the vague "how's everything going" with a picture you can act on.
If the user dumps everything unstructured, sort it yourself. If a project has no clear owner or next step, that absence is itself a finding — surface it.
If a BRAND.md file exists in this skill's folder (.claude/skills/agency-status/BRAND.md) or in .claude/brand/BRAND.md (global fallback), read it before generating output and apply its tone, terminology, and examples to all text you produce. A skill-local BRAND.md overrides the global one; if neither exists, use a clean, professional default voice.
Assign each project a status and one line explaining it:
Be honest. A status report that is all green is a status report nobody trusts. If everything really is green, say why in a sentence so it reads as earned, not lazy.
The three things that, if they happen, make the week a win — usually the intersection of nearest deadline, biggest client, and thinnest slack. Not a task list. Three. Each phrased as an outcome with an owner.
For every 🟡 and 🔴, name the single next action and who does it. A blocker without a named owner and a concrete next step is not tracked, it is just worrying. "Waiting on client" is not an action; "Sara calls the client today to get the logo files" is.
A short, energising, copy-paste block for the team channel. Lead with the one thing that matters most this week, list the traffic lights compactly, call out the blockers with their owners, and close with a single clear focus. Warm and direct, not corporate. This is the message the team actually reads.
AGENCY STATUS — week of [date]
PROJECT STATUS
🟢 [Project] — [one line: why it's on track]
🟡 [Project] — [one line: what to watch]
🔴 [Project] — [one line: what's blocking it]
TOP 3 PRIORITIES THIS WEEK
1. [Outcome] — [owner]
2. [Outcome] — [owner]
3. [Outcome] — [owner]
BLOCKED
• [Project] — blocked on [X]. Next: [action] — [owner], by [when].
MORNING BRIEFING (Slack / WhatsApp)
☀️ Morning team — week of [date]
Big one this week: [the single most important thing].
Status:
🟢 [Project] 🟢 [Project] 🟡 [Project] 🔴 [Project]
Blocked:
• [Project]: [owner] → [next action] today.
Focus: [one clear line]. Let's go.
Per una lettura settimanale dell'agenzia: "stato agenzia", "briefing team", "aggiornamento settimanale", "come stiamo". Da a un titolare o PM una lettura onesta di tutto lo studio in trenta secondi.
Ogni progetto attivo su un semaforo, le tre cose che contano davvero questa settimana, cosa è bloccato e chi lo sblocca, e un messaggio di briefing pronto da incollare in Slack o WhatsApp lunedì mattina. Sostituisce il vago "come va tutto" con un quadro su cui agire.
Se l'utente butta tutto disordinato, ordinalo tu. Se un progetto non ha owner o next step chiaro, quell'assenza è già un risultato: segnalala.
Se esiste un file BRAND.md nella cartella di questa skill (.claude/skills/agency-status/BRAND.md) o in .claude/brand/BRAND.md (fallback globale), leggilo prima di generare l'output e applica tono, terminologia ed esempi a tutto il testo che produci. Il BRAND.md locale ha la precedenza su quello globale.
STATO AGENZIA — settimana del [data]
STATO PROGETTI
🟢 [Progetto] — [una riga: perché è on track]
🟡 [Progetto] — [una riga: cosa tenere d'occhio]
🔴 [Progetto] — [una riga: cosa lo blocca]
TOP 3 PRIORITÀ DELLA SETTIMANA
1. [Risultato] — [owner]
2. [Risultato] — [owner]
3. [Risultato] — [owner]
BLOCCATI
• [Progetto] — bloccato su [X]. Prossima: [azione] — [owner], entro [quando].
BRIEFING DEL MATTINO (Slack / WhatsApp)
☀️ Buongiorno team — settimana del [data]
La grande di questa settimana: [la cosa più importante].
Stato:
🟢 [Progetto] 🟢 [Progetto] 🟡 [Progetto] 🔴 [Progetto]
Bloccati:
• [Progetto]: [owner] → [prossima azione] oggi.
Focus: [una riga chiara]. Andiamo.