Agent skill

Open Source Marketing

by sickn33 in sickn33/agentic-awesome-skills

When the user wants to market an open source project authentically.

MITAuto-check passedMarketing & SEO

Install Open Source Marketing

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill open-source-marketing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills open-source-marketing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/open-source-marketing .claude/skills/open-source-marketing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
open-source-marketing
GitHub stars
47k
Used in
1 other repo
Token cost
~3.2k tokens
SKILL.md length
1,035 words
Files
2
Skills in repo
1,497
Repo updated
First seen
Licence
MIT

At a glance

When the user wants to market an open source project authentically.

  • Wants to market an open source project authentically
  • SKILL.md covers When to Use, Before You Start, The OSS Marketing Mindset and GitHub Optimization, plus 5 more sections
  • Reaches github.com and conventionalcommits.org
  • Phrases include open source marketing

What it does

Open Source Marketing is an agent skill from sickn33/agentic-awesome-skills. When the user wants to market an open source project authentically. Trigger phrases include "open source marketing," "OSS marketing," "GitHub marketing," "promote my library," "grow stars," "launch open source," "open source growth," or "contributor marketing."

Its SKILL.md is about 3.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `README.md`).

It sits in Marketing & SEO, covering Product launch strategy. It works with GitHub. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

When your agent uses it

  • Wants to market an open source project authentically
  • Phrases include open source marketing
  • GitHub marketing
  • Promote my library

Example prompts

  • “open source marketing,”
  • “OSS marketing,”
  • “GitHub marketing,”
  • “/open-source-marketing”

Requirements

  • Node.js

What it can do on your machine

Read from SKILL.md and the folder at commit b84d35a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com
    • conventionalcommits.org

    Also links to:

    • octolens.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Open Source Marketing loads about 3.2k tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 1,035 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~71
When it runs · the whole SKILL.md, loaded when a task matches
~3.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sickn33/agentic-awesome-skills at commit b84d35a, republished under its MIT licence (© sickn33). 1,035 words, ~3,169 tokens.

Download SKILL.mdSave it as .claude/skills/open-source-marketing/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
open-source-marketing
description
When the user wants to market an open source project authentically. Trigger phrases include "open source marketing," "OSS marketing," "GitHub marketing," "promote my library," "grow stars," "launch open source," "open source growth," or "contributor marketing."
risk
critical
source
https://github.com/jonathimer/devmarketing-skills/tree/main/skills/open-source-marketing
source_repo
jonathimer/devmarketing-skills
source_type
community
date_added
2026-07-01
license
MIT
license_source
https://github.com/jonathimer/devmarketing-skills/blob/main/LICENSE

Open Source Marketing

When to Use

Use this skill when you need when the user wants to market an open source project authentically. Trigger phrases include "open source marketing," "OSS marketing," "GitHub marketing," "promote my library," "grow stars," "launch open source," "open source growth," or "contributor marketing.".

This skill helps you market open source projects without being cringe. Covers GitHub optimization, community building, contributor experience, launch strategies, and sustainable growth.


Before You Start

Load your audience context first. Read .agents/developer-audience-context.md to understand:

  • Who would use this project (role, tech stack, problem)
  • Where they discover tools (communities, social, search)
  • What alternatives exist (why would they switch?)
  • How they evaluate OSS (stars, activity, docs, community)

If the context file doesn't exist, run the developer-audience-context skill first.


The OSS Marketing Mindset

What Works vs. What Doesn't
WorksDoesn't Work
Building in publicSpamming "check out my project"
Solving real problemsBuilding solutions seeking problems
Genuine community engagementTransactional follows/unfollows
Great docs and DX"The code is self-documenting"
Celebrating contributorsTaking sole credit
Consistent presenceLaunch and disappear
The Growth Equation
Growth = (Real value) × (Discoverability) × (First-use experience)

If any factor is zero, growth is zero.


GitHub Optimization

README Excellence

Your README is your landing page. Optimize it.

Structure:

markdown
# Project Name

[One-line description that explains what it does]

[Badges: build status, version, license, downloads]

[Screenshot or GIF showing it in action]

## Why [Project Name]?

- ✅ [Benefit 1 - specific, not fluffy]
- ✅ [Benefit 2]
- ✅ [Benefit 3]

## Quick Start

\`\`\`bash
npm install project-name
\`\`\`

\`\`\`javascript
// 5 lines that show immediate value
\`\`\`

## Installation

[Detailed installation for all platforms]

## Usage

[Core usage patterns with examples]

## Documentation

[Link to full docs]

## Contributing

We love contributions! See [CONTRIBUTING.md](https://github.com/jonathimer/devmarketing-skills/tree/main/skills/open-source-marketing/CONTRIBUTING.md).

## License

[License type] - see [LICENSE](https://github.com/jonathimer/devmarketing-skills/tree/main/skills/open-source-marketing/LICENSE)
README Checklist
ElementWhy It Matters
Clear nameMemorable, searchable, spellable
One-liner"A [type] for [audience] that [does what]"
BadgesSocial proof, health signals
VisualGIF > Screenshot > Nothing
Quick start<5 lines to first value
Why this?Differentiation from alternatives
InstallationAll platforms, copy-paste
ExamplesReal use cases, not contrived
Docs linkMore detail available
ContributingCommunity welcome
Repository Optimization
ElementBest Practice
Description100 chars max, keyword-rich
Topics5-10 relevant tags for discoverability
WebsiteLink to docs or landing page
ReleasesSemantic versioning, changelogs
IssuesTemplates for bugs/features
DiscussionsEnable for community Q&A
SponsorsEnable if you want funding
Issue & PR Templates

Bug report template:

markdown
---
name: Bug Report
about: Report a bug to help us improve
---

## Bug Description
[Clear description]

## Steps to Reproduce
1.
2.
3.

## Expected Behavior
[What should happen]

## Actual Behavior
[What actually happens]

## Environment
- OS:
- Node version:
- Package version:

## Additional Context
[Screenshots, logs, etc.]

Feature request template:

markdown
---
name: Feature Request
about: Suggest an idea for this project
---

## Problem
[What problem does this solve?]

## Proposed Solution
[How would you like it to work?]

## Alternatives Considered
[Other approaches you've thought about]

## Additional Context
[Examples, mockups, etc.]

Community Building

Community Spaces
PlatformBest ForSetup Effort
GitHub DiscussionsQ&A, announcementsLow
DiscordReal-time chat, community feelMedium
SlackEnterprise communitiesMedium
Forum (Discourse)Async, searchable discussionsHigh

Start with GitHub Discussions. Add Discord when you have 50+ active users.

Community Principles
PrincipleImplementation
Be responsiveRespond to issues within 48 hours (even if just "looking into it")
Celebrate contributionsThank every contributor publicly
Be transparentShare roadmap, explain decisions
Set expectationsClear SLA for maintainer response
Welcome newcomers"good first issue" labels, mentorship
Contributor Funnel
User → Star → Issue → PR → Regular Contributor → Maintainer

Optimize each transition:

TransitionHow to Improve
User → StarGreat README, visible value
Star → IssueClear issue templates, welcoming tone
Issue → PR"good first issue" labels, CONTRIBUTING.md
PR → RegularQuick review, encouraging feedback
Regular → MaintainerTrust, shared ownership

Contributor Experience

CONTRIBUTING.md Essentials
markdown
# Contributing to [Project]

First off, thanks for considering contributing! ❤️

## Quick Start

1. Fork the repo
2. Clone your fork
3. Install dependencies: `npm install`
4. Create a branch: `git checkout -b my-feature`
5. Make your changes
6. Run tests: `npm test`
7. Commit: `git commit -m "Add my feature"`
8. Push: `git push origin my-feature`
9. Open a Pull Request

## Development Setup

[Detailed setup instructions]

## Code Style

- We use [Prettier/ESLint config]
- Run `npm run lint` before committing
- [Other conventions]

## Commit Messages

We follow [Conventional Commits](https://conventionalcommits.org/):
- `feat: add new feature`
- `fix: resolve bug`
- `docs: update readme`
- `chore: update dependencies`

## Pull Request Process

1. Update docs if needed
2. Add tests for new features
3. Ensure CI passes
4. Get one approval

## Good First Issues

Look for issues labeled `good first issue` — these are great starting points!

## Questions?

Open a Discussion or reach out on Discord.
"Good First Issue" Strategy

Create genuinely approachable issues:

GoodNot Good
"Add TypeScript types for X function""Refactor the entire codebase"
"Fix typo in README""Performance optimization"
"Add test for Y method""Debug intermittent CI failure"
"Update dependency Z""Implement feature from RFC"

For each good first issue:

  • Explain context and why it matters
  • Link to relevant code files
  • Describe expected outcome
  • Offer to help in comments

Launch Strategies

Pre-Launch Checklist
TaskDone?
README polished☐
Quick start works☐
Docs exist☐
3+ examples/demos☐
Tests passing☐
License chosen☐
CONTRIBUTING.md☐
Issue templates☐
Social preview image☐
5-10 GitHub topics☐
Launch Day Playbook

Timeline:

TimeAction
Day beforeFinal README review, prep all posts
Launch morningHN post (best: 6-8am PT, Tuesday-Thursday)
+1 hourTwitter thread
+2 hoursReddit post to relevant subreddits
Throughout dayRespond to all comments/questions
End of dayThank everyone, share metrics
Show full SKILL.md (457 more words)Show less
Platform-Specific Tactics

Hacker News:

  • Title: Descriptive, no hype ("Show HN: X — a Y for Z")
  • First comment: Explain motivation, tech decisions
  • Be available to respond for hours
  • Don't ask for upvotes (instant death)

Reddit:

  • Find 2-3 relevant subreddits (not just r/programming)
  • Read the rules first
  • Be a community member, not a marketer
  • Share genuinely useful context

Twitter/X:

  • Thread format: Problem → Solution → Demo → Link
  • Include GIF/video
  • Tag relevant accounts (framework authors, etc.)
  • Share builds-in-public journey

Dev.to / Hashnode:

  • Write a "Why I Built This" article
  • Technical depth, personal story
  • Cross-post from your blog
Post-Launch
WeekFocus
Week 1Respond to all feedback, fix bugs
Week 2Blog post: "What I learned from launch"
Week 3Start regular updates, ship new feature
Month 1Community building, contributor docs
OngoingConsistent presence, regular releases

Sustainable Growth

Growth Tactics
TacticEffortImpactTimeline
SEO-optimized docsMediumHigh3-6 months
Integration tutorialsMediumHigh1-2 months
Conference talksHighMedium3-6 months
Comparison contentLowMedium1-2 months
Guest blog postsMediumMedium1-2 months
Newsletter featuresLowLow-Medium2-4 weeks
Twitter presenceMediumMediumOngoing
Content Strategy for OSS
Content TypePurpose
"Why we built X"Launch story, motivation
"X vs Y vs Z"Capture comparison searches
"Migrating from Y to X"Convert competitor users
"X + [Popular Tool]"Capture integration searches
"How We Use X at [Company]"Social proof, real use case
"X Performance Benchmarks"Technical credibility
Avoiding Burnout
RiskMitigation
Overwhelming issuesSet response SLA expectations
Feature demandsPublic roadmap, RFC process
Solo maintenanceActively recruit co-maintainers
Always-on pressureScheduled "office hours" vs. 24/7
Negative feedbackCode of conduct, moderation

Metrics That Matter

Vanity vs. Value
Vanity MetricValue Metric
StarsActive issues + PRs
ForksReturned contributors
DownloadsWeekly active users
Twitter followersCommunity engagement
What to Track
MetricWhere to Find It
Stars over timeGitHub Insights, Star History
ClonesGitHub Traffic
ReferrersGitHub Traffic
npm downloadsnpm-stat.com
Community sizeDiscord/Slack member count
Contributor countGitHub Insights
Issue response timeManual tracking

Tools

ToolUse Case
OctolensMonitor mentions of your project across GitHub, HN, Reddit, Twitter, and Stack Overflow. Track competitor projects. Find contributors asking questions.
Star HistoryTrack star growth over time
npm-statDownload statistics
GitHub TrafficViews, clones, referrers
Shield.ioDynamic badges
All ContributorsRecognize all contributors
ProbotAutomate GitHub workflows

  • developer-audience-context — Know who your users are
  • community-building — Build Discord/Slack community
  • devrel-content — Create supporting content
  • developer-advocacy — Conference talks, podcasts
  • hacker-news-strategy — Launch and engage on HN

Limitations

  • Use this skill only when the task clearly matches its upstream source and local project context.
  • Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
  • Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.

© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/open-source-marketing of sickn33/agentic-awesome-skills.

  • SKILL.md
  • README.md

Open the folder on GitHubat commit b84d35a

Used in 1 other repository

We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Open Source Marketing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Open Source Marketing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Open Source Marketing this skillsickn33/agentic-awesome-skills47k1 repos~3.2kAutomated safety check: PassMIT
Content Launch Plannereunomia-bpf/eunomia.dev236—~1.9kAutomated safety check: PassMIT
Daily HuntMagicCube/agentara516—~1.3kAutomated safety check: PassNone
News Aggregator Skillsundial-org/awesome-openclaw-skills663—~1.3kAutomated safety check: PassNone
Gingiris Growth Playbooksdavepoon/buildwithclaude3.6k—~458Automated safety check: PassMIT
Dx RoasterVarnan-Tech/opendirectory674—~2.5kAutomated safety check: PassMIT

Similar skills

  • Content Launch Planner

    eunomia-bpf/eunomia.dev

    Plan contribution-first cross-platform launches for eunomia.dev content, GitHub projects, papers, tutorials, demos, and public updates.

    236 GitHub stars~1.9k tokensUpdated today
    Marketing & SEOAuto-check passed
  • Daily Hunt

    MagicCube/agentara

    Daily tech product and open-source discovery digest. An agent skill from MagicCube/agentara.

    516 GitHub stars~1.3k tokensUpdated 5 mo ago
    Marketing & SEOAuto-check passed
  • News Aggregator Skill

    sundial-org/awesome-openclaw-skills

    Comprehensive news aggregator that fetches, filters, and deeply analyzes real-time content from 8 major sources: Hacker News, GitHub Trending, Product Hunt, 36Kr, Tencent News, WallStreetCN, V2EX…

    663 GitHub stars~1.3k tokensUpdated 7 mo ago
    Marketing & SEOAuto-check passed
  • Gingiris Growth Playbooks

    davepoon/buildwithclaude

    Open-source growth playbooks for AI products, B2B SaaS, and developer tools.

    3.6k GitHub stars~458 tokensUpdated yesterday
    Marketing & SEOAuto-check passed
  • Dx Roaster

    Varnan-Tech/opendirectory

    Brutally honest developer-experience audit for a GitHub repo.

    674 GitHub stars~2.5k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Remove bracketed NemoClaw tags from GitHub issue and PR titles.

    23k GitHub stars~693 tokensUpdated today
    Marketing & SEOAuto-check passed

More from sickn33/agentic-awesome-skills

All 1,497 skills in this repo
  • Liuguang Banlan UI

    sickn33/agentic-awesome-skills

    Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Using LWC Memory and Graphs

    sickn33/agentic-awesome-skills

    Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed
  • Find Complementary Founders

    sickn33/agentic-awesome-skills

    Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.

    47k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed
  • Whatsapp Cloud API

    sickn33/agentic-awesome-skills

    Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~4.5k tokens
    Auto-check passed
  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Works with

Categories

Questions about Open Source Marketing

What does Open Source Marketing do?

When the user wants to market an open source project authentically. Open Source Marketing is an agent skill from sickn33/agentic-awesome-skills. When the user wants to market an open source project authentically.

When should I use Open Source Marketing?

Open Source Marketing fits situations like: wants to market an open source project authentically; phrases include open source marketing; GitHub marketing; promote my library.

How do I install Open Source Marketing in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill open-source-marketing -a claude-code`. Or copy the skill folder (skills/open-source-marketing in sickn33/agentic-awesome-skills) into .claude/skills/open-source-marketing in your project. Claude Code loads it when a task matches its description.

How do I install Open Source Marketing in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill open-source-marketing -a codex`. Or copy the skill folder (skills/open-source-marketing in sickn33/agentic-awesome-skills) into .agents/skills/open-source-marketing in your project. Codex loads it when a task matches its description.

Can I use Open Source Marketing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill open-source-marketing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/open-source-marketing, .gemini/skills/open-source-marketing, .github/skills/open-source-marketing and .opencode/skills/open-source-marketing in your project.

What does Open Source Marketing need to run?

SKILL.md names no scripts, command-line tools or credentials: Open Source Marketing is instructions for the agent only. Our summary lists: Node.js.

Does Open Source Marketing access the network?

SKILL.md names 3 domains. In commands or code: github.com and conventionalcommits.org; the agent is likely to contact these when it follows the instructions. As links in the text: octolens.com. This is read from the text; nothing was executed.

Is Open Source Marketing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Open Source Marketing use?

Open Source Marketing is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Open Source Marketing use?

About 3.2k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Open Source Marketing?

Skills that share tags, products or a category with Open Source Marketing: Content Launch Planner (eunomia-bpf/eunomia.dev, 236 stars), Daily Hunt (MagicCube/agentara, 516 stars), News Aggregator Skill (sundial-org/awesome-openclaw-skills, 663 stars) and Gingiris Growth Playbooks (davepoon/buildwithclaude, 3.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Open Source Marketing?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,405 GitHub stars. The repository holds 1,497 skills in this directory. The repository was last updated on October 9, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.