solo-github-outreach

Automating GitHub outreach involves scanning competitor dependents, evaluating target repositories based on activity and readmes, and drafting personalized issues. This Skill scales developer outreach campaigns by generating tailored GitHub issues for repositories likely to adopt your library.

Tracking pipeline status for GitHub issue drafts requires monitoring stages across enrichment, evaluation, drafting, and posting. This Skill maintains pipeline progress automatically, ensuring you can track outreach campaigns from initial repository scouting to final issue creation.

Yes, local access to GitHub via gh api is required to draft personalized issues for competitor repos. You also need a configured feature matrix to evaluate target repositories and generate tailored outreach drafts based on their repository signals and readmes.

Yes, this GitHub outreach automation applies to any package or crate. It evaluates repositories that would benefit from adopting your library by analyzing repository signals, readmes, and activity, then drafts personalized GitHub issues to guide outreach targets effectively.

Competitor repository scouting works by scanning dependents of competing libraries to identify repos likely to benefit from adopting your library. It evaluates repository readmes, signals, and activity to guide outreach targets and draft personalized GitHub issues for scalable campaigns.

Automating GitHub issue creation for outreach requires local gh api access and a configured feature matrix. It is limited to evaluating repository signals, readmes, and activity to guide outreach targets, and relies on templates to create issues or drafts for candidate repositories.