Skip to content
Back to skills

Github Marketing

ASecurity

When the user wants to use open source as a distribution strategy, grow on GitHub, convert README traffic, design open-core, or build community-led funnels (stars, deploys, sponsors, plugins).

  • 666 stars
  • 0 votes
  • 0 copies
  • 15 views
  • Added February 8, 2026
content-marketingrustgit

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add majiayu000/claude-skill-registry --skill github-marketing --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Github Marketing?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Github Marketing
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-github-marketing/badge)](https://www.skillsdirectory.com/skills/majiayu000-github-marketing)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: github-marketing
description: When the user wants to use open source as a distribution strategy, grow on GitHub, convert README traffic, design open-core, or build community-led funnels (stars, deploys, sponsors, plugins).
---

# GitHub Marketing

## Purpose

Turn GitHub attention into real users, community, and revenue without eroding trust.

## When to Use

- Open source as a distribution strategy or open-core planning
- Grow GitHub traction (stars, installs, contributors, sponsors)
- Convert README traffic into deploys or signups
- Design community-led funnels or plugin ecosystems

## Core Principles

### 1. Open Core Clarity
Make the boundary obvious:
- What is free forever
- What is paid and why
- No surprise lockouts

### 2. 10-Second Time-to-Value
If it takes >10s to see value, you lose. Reduce steps, give defaults, add deploy buttons.

### 3. Trust Before CTA
Open source is credibility marketing. Earn trust before asking for upgrade.

### 4. Loops, Not One-Offs
Stars → users → contributors → referrals. Build loops, not launches.

### 5. Community as Product Surface
Docs, examples, templates, and plugins are product. Treat them as such.

## Workflow Summary

1. Run discovery using initial assessment + questions. See `references/assessment.md` and `references/questions.md`.
2. Pick distribution playbooks. See `references/playbooks.md`.
3. Choose metrics to track. See `references/metrics.md`.
4. Produce artifacts in the required format. See `references/output-format.md`.

## Related Skills

- **programmatic-seo**: If you need scalable GitHub Pages content
- **copywriting**: For README and launch copy

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.