tech-press-relations skill (samber): press and analyst relations for devtools
Plans press coverage for a developer product: whether there is a story, the angle, the media map, the pitch and the embargo.
- Installs
- 12.5K
- on skills.sh
- Stars
- 7
- on GitHub
- Files
- 7
- besides SKILL.md
- Updated
- Nov 2026
- last repo commit
tech-press-relations decides whether there is a story, shapes it for a technical reporter, and puts it in front of the right people. It runs a 10-question interview and nine steps: qualify the news, choose the angle, build a media map of 20-40 verified reporters, ship a press page and briefing pack, write the pitch, plan the embargo, run announcement day, match the announcement type and handle analysts lightly. Recommending no pitch is a valid outcome.
It triggers on "getting press coverage", "pitching a journalist", "a press kit", "an embargo briefing" or "how do we get written about". It bundles no scripts. SKILL.md says it does not buy coverage: paid placement is advertising and out of scope. It tells Claude never to invent a reporter, outlet or email address.
Good for
- Founders and DevRel leads preparing a launch, release or funding announcement
- Maintainers who want mentions in developer newsletters
- Teams planning a licence change that may draw hostile coverage
Install tech-press-relations
Claude Code
- 1
Copy this prompt.
Install the tech-press-relations skill in Claude Code. Run this command: /plugin marketplace add samber/developer-relations-skills /plugin install developer-relations-skills@developer-relations-skills Then check that it loaded and tell me how to use it.
- 2
Paste it into Claude Code. It shows the change and asks before running it.
The README recommends installing the whole collection because its skills reference each other, and tech-press-relations names other skills in the collection to hand work to. The whole-collection routes add all 93 skills in the repo (counted from the git tree); the repo holds no hooks, agents, commands or MCP server files, and 14 of its skills bundle a script. Pick one route per agent.
From the project README. Source.
What's in the skill
When it loads
Runs press and light analyst relations for a developer-facing product - news qualification, the angle, a reporter-to-beat media map, the pitch, embargo and exclusive handling, the press page and briefing pack, and what coverage is worth. Use whenever someone raises tech press relations, getting press coverage, pitching a journalist, building a media list, a press kit, earning mentions in developer newsletters like JavaScript Weekly, an embargo briefing, announcing a funding round, an analyst briefing, or "how do we get written about" - even if they only say they want to be in the news. Not the announcement post itself - use samber/developer-relations-skills@engineering-blog-post. Not growing your own newsletter list - use samber/developer-relations-skills@devrel-newsletter-growth.
Sections in SKILL.md
- Invocations and what you produce
- Interview
- Step 1 - Qualify the news
- Step 2 - Choose the angle
- Step 3 - Build the media map
- Step 4 - Ship the assets before pitching
- Step 5 - Write the pitch
- Step 6 - Plan the embargo
- Step 7 - Run the announcement day
- Step 8 - Match the announcement type
- Step 9 - Analyst relations, lightly
- Between announcements
- Adoption motion changes the plan
- Measurement
- Pass threshold
- Failure modes
Key facts
- Skill version
- 1.1.1 (SKILL.md metadata)
- Installs on skills.sh
- 12,456 (Nov 2, 2026)
- Last repo commit
- Nov 1, 2026
- Audits on skills.sh
- Gen Agent Trust Hub: pass, Socket: pass, Snyk: warn
What it includes
Asks 10 questions; questions 1-3 gate drafting and 2, 4 and 6 set the angle ranking.
InterviewScores five tests; failing two means this is not a press story yet.
Scores newness, consequence, evidence, shift and tellability; failing two means no pitch yet.
Step 1: Qualify the newsOffers the shift, practitioner, broken system, number or underdog, and waits for you.
Offers the shift, practitioner, broken system, number or underdog, ranked, and waits for your choice.
Step 2: Choose the angleBuilds 20-40 verified reporters in three tiers from recent bylines.
Builds 20-40 verified reporters in three tiers from recent bylines, with a do-not-pitch list.
Step 3: Build the media mapSpecifies the press page, the briefing pack and the technical proof pack.
Step 4: Ship the assetsWrites one pitch per reporter under about 150 words, with banned words listed.
One pitch per reporter under about 150 words, with a banned-words list.
Step 5: Write the pitchCompares exclusive, embargo and pre-briefing, and runs an open-source leak check.
Step 6: Plan the embargoStaffs the day, picks a playbook per news type and runs light analyst briefings.
Steps 7-9: Announcement day, announcement types, analystsRequires five checks before sending, such as a verified byline per reporter.
Five checks before anything is sent, such as verified bylines for every reporter on the list.
Pass threshold
From the official docs
Permissions
Low risk
tech-press-relations is interview and writing instructions with no scripts, and it may store your media map and sends in memory or devrel-context.md.
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only mode
Watch out for
Embargoed news goes into the conversation and memory
SKILL.md tells Claude to store the media map, every send and every reply if memory is available. Keep embargoed details out of notes you commit. github.com
It may save notes to devrel-context.md
SKILL.md tells Claude to keep task and project context in devrel-context.md when memory lives in a file, or in the memory system your tool already uses. Check the file before you commit it. github.com
The whole-set install adds 93 skills, 14 with scripts
The README says to install every skill. The git tree has 93 skill folders, and 14 of them hold .py or .sh files. This skill bundles no scripts, and the tree holds no hooks, agents or MCP config files. github.com
Technical details
| Turning on read-only | SKILL.md describes no read-only mode. |
|---|---|
| Sign-in and keys | SKILL.md names no account, key or token. |
| Scopes |
|
Questions
What does tech-press-relations do?
It runs the press side of a developer product announcement. It tests whether you have a story, picks the angle, builds a media map, writes pitches and plans the embargo and announcement day.
How do I install it?
Use the install box at the top. The README says to install every skill in the repo, because the skills point to each other. The box shows the whole-set route for each app.
Can it buy coverage or promise sign-ups?
No. SKILL.md says paid placement is advertising and out of scope, and that press does not convert developers. It tells Claude to refuse to promise sign-ups.
Will it invent reporters or email addresses?
SKILL.md tells Claude never to invent a reporter, an outlet or an email address, and never to guess a contact address into a pitch. If it cannot browse, it hands you a checklist to fill in.
Is it safe to install?
The skill bundles no scripts. Embargoed news, funding details and reporter notes you share go into your conversation, and SKILL.md tells Claude to store the media map and every send when memory is available. The whole-set install adds 93 skills, 14 of which bundle scripts.
Does it write the announcement post too?
No. SKILL.md routes the announcement post to samber/developer-relations-skills@engineering-blog-post and open-source release sequencing to samber/developer-relations-skills@oss-launch.
Information
updated Nov 2, 2026
- Repository
- samber/developer-relations-skills
- Folder
skills/tech-press-relations
Sources
Docs, issue trackers and discussions this page is built from.
Show all 3Hide
- README · github.com
- tech-press-relations SKILL.md · github.com
- LICENSE · github.com