<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Samuel Berthe</title>
    <description>The latest articles on DEV Community by Samuel Berthe (@samber).</description>
    <link>https://dev.to/samber</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F7260%2Fe2148c3d-a89f-43b5-8e9d-b1469a9ffb05.jpg</url>
      <title>DEV Community: Samuel Berthe</title>
      <link>https://dev.to/samber</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/samber"/>
    <language>en</language>
    <item>
      <title>4 agent skill collections for technical marketers</title>
      <dc:creator>Samuel Berthe</dc:creator>
      <pubDate>Mon, 14 Sep 2026 17:35:02 +0000</pubDate>
      <link>https://dev.to/samber/4-agent-skill-collections-for-technical-marketers-4jno</link>
      <guid>https://dev.to/samber/4-agent-skill-collections-for-technical-marketers-4jno</guid>
      <description>&lt;p&gt;Your agent writes decent developer demo. It never asks the audience first. A skill collection fixes that: it forces the sequence, the questions, and the shape of the output.&lt;/p&gt;

&lt;p&gt;Three worth installing, in this order.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;a href="https://github.com/coreyhaines31/marketingskills" rel="noopener noreferrer"&gt;coreyhaines31/marketingskills&lt;/a&gt; (50 skills, MIT). The base layer: conversion, copy, SEO, lifecycle, measurement, pricing. Start here, because it builds the product context everything downstream depends on. Breadth costs depth, though: one entry covers every paid channel at once.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href="https://github.com/mbfinotti/advertising-skills" rel="noopener noreferrer"&gt;mbfinotti/advertising-skills&lt;/a&gt; (31 skills, MIT). Paid media only, written for people running real budgets: budget policy, bidding, audiences, creative testing, account diagnosis. It assumes you already have a product, a page and an ad budget.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href="https://github.com/samber/developer-relations-skills" rel="noopener noreferrer"&gt;samber/developer-relations-skills&lt;/a&gt; (56 skills, MIT). For when the buyer writes code, where most marketing advice inverts: the README is the landing page, gated capture costs more than it returns. Docs, OSS, community, devtool pricing. Useless if you sell to anyone else.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a href="https://github.com/samber/developer-platform-skills" rel="noopener noreferrer"&gt;samber/developer-platform-skills&lt;/a&gt; (32 skills, MIT). The outlier, written for platform PMs and API engineers rather than marketers. Worth it only when growth runs through integrations, and marketplace listings, partner onboarding and launch co-marketing become your channel.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Install all four and dozens of skills descriptions compete for every request, while the agent routes on description matching alone. The ad-creative entries in the first two collections want the same prompt, and the agent picks by guessing.&lt;/p&gt;

&lt;p&gt;Instead, put routing rules in CLAUDE.md:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;describe ICP first&lt;/li&gt;
&lt;li&gt;then list the objectives/KPIs&lt;/li&gt;
&lt;li&gt;then the routing: name the skills per task&lt;/li&gt;
&lt;li&gt;general instructions at the end&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;None of them can act without it. They produce a plan, a brief, an audit. Execution still needs MCP servers holding real credentials, a separate problem you meet about an hour after solving this one.&lt;/p&gt;

&lt;p&gt;All MIT. Fork the closest and fix what is wrong for you.&lt;/p&gt;

&lt;p&gt;Disclosure: 2 collections are mine.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>marketing</category>
      <category>devrel</category>
      <category>skills</category>
    </item>
  </channel>
</rss>
