Marker.io MCP Skills

Turn Marker.io website feedback into a triaged backlog, clear patterns, and code fixes — without leaving your AI assistant.

Ready-made workflows for the Marker.io MCP server, for
Claude (Code or Desktop), Cursor, and Windsurf. Built for digital agencies and in-house
teams running Marker.io on client and product websites — where most feedback is content (typos, copy,
images, links) and the rest is functional bugs.

You don't memorize commands. Describe what you want and the matching skill activates. Anything that
changes data shows you the plan first and only acts after you confirm.

Quick start

1. Connect the Marker.io MCP to your assistant — 5-minute setup guide.

2. Install the skills for your tool:

Claude (Code or Desktop) — recommended

cp -r claude/skills/* ~/.claude/skills/      # global (all projects)
# or, for one project only:
cp -r claude/skills/* .claude/skills/

Skills load automatically based on what you ask — nothing else to wire up.

Cursor

cp cursor/rules/*.mdc .cursor/rules/

Cursor applies a rule when it's relevant, or mention it directly: @marker-triage.

Windsurf

cp windsurf/workflows/*.md .windsurf/workflows/

Invoke as a slash command: /marker-triage, /marker-client-report, …

3. Just ask:

"Triage the latest feedback on the Acme Corp project and show me the quick wins."

That's it — marker-triage activates, pulls the backlog, and hands you a categorized dashboard.

The skills

Skill	What it does	Use it when	Data
`marker-triage`	Splits content from bugs, groups by page, prioritizes, dedupes, surfaces quick wins, lists affected users	A backlog piled up and you need to make sense of it fast	Gated writes
`marker-insights`	Aggregates many reports into recurring patterns and per-page hotspots	You want the big picture — what keeps coming back across the site	Read-only
`marker-client-report`	Turns completed work into a polished weekly / monthly client recap	It's time to tell a client what you shipped	Read-only
`marker-bug-to-fix`	Takes one report to its root cause in your repo, to a minimal diff, to a PR	A functional bug needs fixing in code	Gated writes
`marker-sync`	Keeps Marker.io and GitHub / Linear / Jira in step, both ways, with full context	You also run a separate tracker	Gated writes

Read-only skills only look and report. Gated writes skills always show the planned change as a
table and apply it only after you say yes.

Try it — example prompts

Copy, paste, and adapt. You don't need to name the skill — the wording is enough to trigger it.

Make sense of a backlog → marker-triage

"Triage the backlog on the Acme Corp project — split content from functional bugs and list the quick wins."
"Which pages on the Acme site are getting the most feedback this month?"

Find the patterns → marker-insights

"What are the most common content issues across the Acme site this quarter?"
"Is there one root cause behind all these reports?"

Report to the client → marker-client-report

"Write this week's client report for Acme Corp."
"Give me a monthly recap of everything we completed on the Acme site."

Fix a bug → marker-bug-to-fix

"Fix the marker issue about the Request a Demo button not working."
"What's causing this bug? "

Stay in sync → marker-sync

"Pull this week's new marker issues into Linear and flag any already closed on one side."

What you get — feedback, triaged

From a single prompt, marker-triage reads the backlog and hands back a decision-ready dashboard:

# Acme Corp — feedback triage
24 reports · last 14 days · acme-corp.com

Content 19 · Functional 5 — most of the backlog is copy, images, and links.

## By page
| Page | Reports | Top theme |
| --- | --- | --- |
| /pricing | 8 | wrong plan details |
| /solutions | 6 | typos |
| /about | 5 | outdated numbers |

## Quick wins (2-minute fixes)
- /pricing — "Essentials" plan shows "/year", should be "/month".
- /solutions — typo in the intro paragraph.

## Worth a look
- /pricing — the "Request a Demo" button throws an error (functional).

Every skill produces a focused artifact like this — a brief, a client report, a diff, or a synced ticket.

Good to know

Describe, don't dictate. Skills resolve the project from a name and ask if more than one matches —
you never hand-copy IDs.
Nothing changes without a yes. Status, priority, type, and comment edits are proposed as a table
first; you approve before anything is written.
Marker-first. Everything runs on the Marker.io MCP. marker-sync is the only skill that reaches
into an external tracker, and only when you have one.

How it's built (for contributors)

Each skill has one canonical body in shared/skills/. scripts/build.mjs wraps it in the right
frontmatter for each client and regenerates claude/, cursor/, and windsurf/. The common operating
contract lives once in shared/snippets/operating-rules.md and is injected into every skill.

node scripts/build.mjs

The generated folders are committed so users can copy without building. Never hand-edit the generated
folders — change the shared body (or the snippet) and re-run the build.

Reference

shared/references/mcp-tools.md — what the Marker.io MCP can read and write.
shared/references/conventions.md — the operating contract every skill follows.

License

MIT. See LICENSE.

mcp-skills