OSS Promoter

Batch promote open source projects to tech weeklies and communities using GitHub CLI.

What This Skill Does

This skill automates the process of promoting open source projects to multiple tech weeklies and community newsletters. It handles:

1. **Search for weeklies**: Use WebSearch to find new tech weeklies that accept submissions

2. **Extract project info**: Use `gh` CLI to get repo description, README, stars, and other metadata

3. **Generate submissions**: Create tailored issue content for each weekly using templates

4. **Batch submit**: Use `gh issue create` or `gh issue comment` to submit to multiple weeklies

Step-by-Step Instructions

When the user wants to promote an open source project:

1. **Gather project information**

- If the user hasn't provided a GitHub repo URL, ask for it

- Use `gh repo view <repo> --json name,description,url,stargazerCount,readme` to get comprehensive project info

- Parse the README to extract core features and usage examples

2. **Load weekly configurations**

- Read the weeklies config from `${CLAUDE_PLUGIN_ROOT}/config/weeklies.json`

- Filter for enabled weeklies that match the project's language/topic

- Validate each weekly's required fields (repo, type, title_template)

3. **Generate tailored submissions**

- For each enabled weekly, use its `title_template` to generate the submission title

- For Chinese weeklies, use this template for the body:

```markdown

## 项目介绍

[{name}]({url}) - {description}

## 核心功能

{features_from_readme}

## 使用示例

{usage_example}

## 链接

- GitHub: {url}

- Stars: {stars}

```

- For English weeklies, adapt the template to English or follow the weekly's specific format in their README

4. **Check for existing submissions**

- Before creating, use `gh issue list --repo <weekly_repo> --search "<project_name>" --json number,title` to check if a similar issue already exists

- If found, ask the user whether to skip or comment with an update

5. **Batch submit**

- For each weekly:

- If `type` is "issue": use `gh issue create --repo <weekly_repo> --title "<title>" --body "<body>"`

- If `type` is "comment": use `gh issue comment <issue_number> --repo <weekly_repo> --body "<body>"`

- Add a 2-3 second delay between submissions to respect rate limits

- Track success/failure for each submission

6. **Report results**

- Show a summary table with weekly name, status (success/failed/skipped), and issue URL

- If any submissions failed, suggest troubleshooting steps

Available Commands

`/oss-promoter:promote <repo-url>` - Promote a project to all enabled weeklies

`/oss-promoter:search` - Search for new weeklies to add to config using WebSearch

`/oss-promoter:list` - List all configured weeklies and their enabled/disabled status

Tools You Should Use

**WebSearch** - Search for new tech weeklies (e.g., "tech weekly submissions", "developer newsletter submissions")

**Bash with gh CLI** - GitHub CLI for repo info (`gh repo view`), issue creation (`gh issue create`), and commenting (`gh issue comment`)

**Read** - Read the weeklies config file at `${CLAUDE_PLUGIN_ROOT}/config/weeklies.json`

Important Constraints

**Always check for duplicates**: Use `gh issue list` to search for existing submissions before creating new issues

**Respect rate limits**: Add 2-3 second delays between submissions using `sleep 2` in Bash

**Validate weekly formats**: Some weeklies require specific formats - check their README or CONTRIBUTING.md first using `gh repo view <weekly_repo> --json readme`

**Language matching**: Only submit to weeklies that match the project's primary language (check `languages_url` or README)

**Config management**: Set `enabled: false` for weeklies that are too niche or don't match the project's topic

Example Usage

**User:** "Promote my repo https://github.com/user/awesome-tool to weeklies"

**Assistant should:**

1. Run `gh repo view user/awesome-tool --json name,description,url,stargazerCount,readme`

2. Read `${CLAUDE_PLUGIN_ROOT}/config/weeklies.json`

3. Generate submissions for 5 enabled weeklies

4. Create issues/comments using `gh issue create` or `gh issue comment`

5. Report: "Submitted to 5 weeklies: [list with links]. 1 skipped (already submitted)."

OSS Promoter

OSS Promoter

What This Skill Does

Step-by-Step Instructions

When the user wants to promote an open source project:

Available Commands

Tools You Should Use

Important Constraints

Example Usage

Reviews (0)