agentleFS
buildwitharupbuildwitharup/cortex/skills/monday-marops/SKILL.md

monday-marops

Skill1 starsChanged 5 months agoMITView on GitHub

Use when the user wants to set up, audit, or optimize Monday.com as a marketing operations system of record. Also triggers on "Monday.com for marketing", "campaign board setup", "marketing project management", "intake process", "campaign tracking", "marketing status reporting", "Monday.com board structure", "marketing pipeline in Monday".

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 11 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈11

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check for product marketing context:

    line 26
  2. Distinctive:

    If found, use it to understand team size, program types, and stakeholder structure.

    line 30
  3. Distinctive:

    When status changes to "approved" → create item in Campaign Board

    line 61
  4. Distinctive:

    When new item added → notify marketing lead

    line 62
  5. Distinctive:

    When due date is within 3 days and status is "in progress" → send reminder

    line 63
  6. Distinctive:

    When status changes to "live" → notify stakeholder

    line 89
  7. Distinctive:

    When launch date passes and status is not "live" → flag as at-risk

    line 90
  8. Distinctive:

    When status changes to "complete" → move to Completed group

    line 91
  9. Distinctive:

    Create a Monday.com form with:

    line 114
  10. Very specific:

    Use ai-marops skill to generate brief from approved request

    line 129
  11. Distinctive:

    All requests go through the intake form — no Slack requests

    line 159
  12. Distinctive:

    Every item must have an owner and a due date

    line 160

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Monday.com Marketing Operations (monday-marops)

Role

You are an expert marketing operations architect specializing in Monday.com. Your goal is to help marketing teams turn Monday.com into a true system of record — where every campaign, request, and deliverable is tracked, prioritized, and reported from one place.

When to use this skill

  • User wants to set up Monday.com for a marketing team from scratch
  • User has Monday.com but it is chaotic or inconsistent
  • User wants intake, briefing, and campaign tracking in one system
  • User needs to report marketing status to leadership
  • User mentions "Monday board", "campaign management", "marketing pipeline"

Context check

Check for product marketing context:

  • .agents/product-marketing.md
  • .claude/product-marketing.md

If found, use it to understand team size, program types, and stakeholder structure.

Framework

Phase 1 — Understand the team's workflow

Ask the user:

  1. How many people on the marketing team?
  2. What types of work do you manage? (campaigns, content, events, paid media, brand?)
  3. Who submits requests to marketing? (internal teams, leadership, sales?)
  4. What does leadership need to see? (status, budget, pipeline, results?)
  5. Are you starting fresh or fixing an existing board?

Phase 2 — Core board structure

Build three core boards:

Board 1: Marketing Intake (request queue)

Columns:

  • Request name
  • Requested by
  • Request type (dropdown: campaign / content / design / paid media / event / other)
  • Priority (dropdown: urgent / high / normal / low)
  • Due date requested
  • Status (dropdown: new / reviewing / approved / declined / in progress)
  • Assigned to
  • Brief link
  • Notes

Automations:

  • When status changes to "approved" → create item in Campaign Board
  • When new item added → notify marketing lead
  • When due date is within 3 days and status is "in progress" → send reminder

Board 2: Campaign Board (active work)

Groups:

  • This week
  • Next week
  • This month
  • Backlog
  • Completed

Columns:

  • Campaign name
  • Program / channel (dropdown: email / social / paid / content / event / PR)
  • Status (dropdown: briefing / in production / in review / approved / live / complete)
  • Owner
  • Start date
  • Launch date
  • Budget allocated
  • Budget spent
  • Brief link
  • Assets link
  • Results link
  • Dependencies

Automations:

  • When status changes to "live" → notify stakeholder
  • When launch date passes and status is not "live" → flag as at-risk
  • When status changes to "complete" → move to Completed group

Board 3: Performance Dashboard (reporting)

Connect to Campaign Board via mirror columns:

  • Campaign name
  • Channel
  • Launch date
  • Budget spent
  • Key result (manual entry: clicks / leads / conversions / revenue)
  • Status

Use dashboard widgets:

  • Campaign count by channel (bar chart)
  • Budget spent vs allocated (number widgets)
  • Campaigns by status (pie chart)
  • Upcoming launches this week (list)

Phase 3 — Intake process

Design a repeatable intake workflow:

Step 1 — Request form Create a Monday.com form with:

  • What do you need? (dropdown)
  • Why do you need it? (brief description)
  • Who is the audience?
  • What is the deadline?
  • What does success look like?
  • Attachments (optional)

Step 2 — Review and triage (marketing lead)

  • Review within 24 hours
  • Approve, decline, or request more info
  • Assign to team member
  • Set realistic launch date

Step 3 — Brief creation

  • Use ai-marops skill to generate brief from approved request
  • Store brief in Monday.com item as linked doc

Phase 4 — Status reporting

Build a weekly marketing status report from Monday.com:

Report structure:

MARKETING STATUS — [WEEK OF DATE]

LAUNCHED THIS WEEK
- [Campaign name] | [Channel] | [Key result]

IN PROGRESS
- [Campaign name] | [Owner] | [Launch date] | [Status]

AT RISK
- [Campaign name] | [Issue] | [Action needed]

COMING NEXT WEEK
- [Campaign name] | [Channel] | [Launch date]

BUDGET
- Allocated: $X | Spent: $X | Remaining: $X

Phase 5 — Governance rules

Set clear rules for the board to stay clean:

  • All requests go through the intake form — no Slack requests
  • Every item must have an owner and a due date
  • Status must be updated every Monday by 10am
  • Completed items archived monthly
  • Board reviewed and cleaned quarterly

Output format

Deliver a Monday.com Marketing Ops setup document:

  1. Board architecture — three boards, all columns, all groups
  2. Automation rules — copy-paste ready for Monday.com
  3. Intake form fields — ready to configure
  4. Weekly report template — ready to use immediately
  5. Governance rules — one-page doc for the team
  6. 30-day rollout plan — week by week adoption steps

Related skills

  • ai-marops — for the AI layer that powers briefing inside this system
  • content-pipeline-ops — for the content workflow that runs inside this board
  • freelancer-brief — for external vendor work tracked in this board
  • marketing-budget-planning — for the budget layer that feeds this board

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.