agentsclimarketplace

Marketing feedback

Skill etrebels/claude-code-growth-os/.claude/skills/marketing-feedback

Claude Code Growth Operating System (OS): Sales, Marketing, Product and Retention as one Revenue system

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

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 17 stars17 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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 should marketing know", or "field intel".

SKILL.md

2.4 KB, as published. Nobody here has run it

Marketing Feedback

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 — made concrete as a tagged line in a shared log.

From a source — a note in ops/daily-log.md, a file in demo/meetings/, a call recap, a deal update:

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.

  1. Scan for the five signal types:
    • Recurring objection — the same pushback in 3+ conversations.
    • Competitor mention — who showed up, and how the buyer described them.
    • Buyer language — the words they actually used (use them in content; don't translate them into your own).
    • Missing proof — evidence they asked for that doesn't exist yet.
    • Win/loss reason — the real one, not the polite one.
  2. Log each as a tagged line in ops/feedback-log.md, so marketing can act on it without a meeting:
    • MARKETING-ACTION: [signal] — [the content or proof that would answer it]
    • MARKETING-ACTION-URGENT: when a live deal was affected.
    • MARKETING-STRATEGIC: when it signals a positioning or new-segment shift.
  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.

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.

Depth

  • quick: scan one note, emit any MARKETING-ACTION lines.
  • standard: the full five-signal scan across recent notes, tagged and ranked by urgency.
  • deep: + a one-line content brief for the top signal (who it's for, the claim to make, the proof to find).

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.