marketing-feedback

Name: marketing-feedback
Author: etrebels

17stars1forks

How to install marketing-feedback?

etrebels/claude-code-growth-os/marketing-feedback

$npx -y skills add etrebels/claude-code-growth-os --skill marketing-feedback

Installs into the current project.

Summary

Turn what sales hears in the field into marketing actions. Trigger when a meeting note or call recap surfaces a recurring objection, a competitor mention, the buyer's own language, a missing proof point, or a win/loss reason — or when the user says "log this for marketing", "what

Files · 1

View on GitHub

SKILL.md

1	# Marketing Feedback
2
3	The loop that keeps sales and marketing as one system: field intelligence flows from sales back to marketing on a cadence, instead of dying inside a meeting note. This is mechanism #5 from [`docs/why-align.md`](../../../docs/why-align.md) — made concrete as a tagged line in a shared log.
4
5	From a source — a note in `ops/daily-log.md`, a file in `demo/meetings/`, a call recap, a deal update:
6
7	> Tagged lines live in one place: `ops/feedback-log.md`. That's the single home the SessionStart hook surfaces and `/weekly-review` clears — write `MARKETING-ACTION` lines there, not in the daily log, so they don't go invisible.
8
9
10	1. Scan for the five signal types:
11	- Recurring objection — the same pushback in 3+ conversations.
12	- Competitor mention — who showed up, and how the buyer described them.
13	- Buyer language — the words they actually used (use them in content; don't translate them into your own).
14	- Missing proof — evidence they asked for that doesn't exist yet.
15	- Win/loss reason — the real one, not the polite one.
16	2. Log each as a tagged line in `ops/feedback-log.md`, so marketing can act on it without a meeting:
17	- `MARKETING-ACTION: [signal] — [the content or proof that would answer it]`
18	- `MARKETING-ACTION-URGENT:` when a live deal was affected.
19	- `MARKETING-STRATEGIC:` when it signals a positioning or new-segment shift.
20	3. Don't invent signals. One offhand comment isn't a pattern — tag it only when it recurs across deals or clearly cost one. A log full of false patterns is worse than an empty one.
21
22	The tag is the hand-off. One file, both functions read it — that's the loop, version-controlled, with a diff and a history. Marketing's job is to clear the `MARKETING-ACTION` lines; sales' job is to keep them honest and current.
23
24	## Depth
25	- quick: scan one note, emit any `MARKETING-ACTION` lines.
26	- standard: the full five-signal scan across recent notes, tagged and ranked by urgency.
27	- deep: + a one-line content brief for the top signal (who it's for, the claim to make, the proof to find).

People who liked this also viewed

6 picks

Type

marketing-feedback

17stars1forks

View on GitHub

How to install marketing-feedback?

etrebels/claude-code-growth-os/marketing-feedback

$npx -y skills add etrebels/claude-code-growth-os --skill marketing-feedback

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Marketing Feedback
2
3	The loop that keeps sales and marketing as one system: field intelligence flows from sales back to marketing on a cadence, instead of dying inside a meeting note. This is mechanism #5 from [`docs/why-align.md`](../../../docs/why-align.md) — made concrete as a tagged line in a shared log.
4
5	From a source — a note in `ops/daily-log.md`, a file in `demo/meetings/`, a call recap, a deal update:
6
7	> Tagged lines live in one place: `ops/feedback-log.md`. That's the single home the SessionStart hook surfaces and `/weekly-review` clears — write `MARKETING-ACTION` lines there, not in the daily log, so they don't go invisible.
8
9
10	1. Scan for the five signal types:
11	- Recurring objection — the same pushback in 3+ conversations.
12	- Competitor mention — who showed up, and how the buyer described them.
13	- Buyer language — the words they actually used (use them in content; don't translate them into your own).
14	- Missing proof — evidence they asked for that doesn't exist yet.
15	- Win/loss reason — the real one, not the polite one.
16	2. Log each as a tagged line in `ops/feedback-log.md`, so marketing can act on it without a meeting:
17	- `MARKETING-ACTION: [signal] — [the content or proof that would answer it]`
18	- `MARKETING-ACTION-URGENT:` when a live deal was affected.
19	- `MARKETING-STRATEGIC:` when it signals a positioning or new-segment shift.
20	3. Don't invent signals. One offhand comment isn't a pattern — tag it only when it recurs across deals or clearly cost one. A log full of false patterns is worse than an empty one.
21
22	The tag is the hand-off. One file, both functions read it — that's the loop, version-controlled, with a diff and a history. Marketing's job is to clear the `MARKETING-ACTION` lines; sales' job is to keep them honest and current.
23
24	## Depth
25	- quick: scan one note, emit any `MARKETING-ACTION` lines.
26	- standard: the full five-signal scan across recent notes, tagged and ranked by urgency.
27	- deep: + a one-line content brief for the top signal (who it's for, the claim to make, the proof to find).

People who liked this also viewed

6 picks

Type