Full GitHub launch in ~4-6 minutes. Parallel delegated agents. SEO name scoring, competitor README research, auto-embedded social preview, GitHub Pages, scored descriptions, 7-day distribution calendar.

Works in Hermes Agent — no CLI setup, one trigger phrase.

The Hermes-native evolution of github-launch-agent. Same full pipeline — 3 parallel delegated subagents in each phase (sized for Hermes's delegate_task ceiling) cut launch time from 20+ minutes to 4-6 while improving README quality through live competitor research.

---

The Problem

Sequential launch works. But on step 6 of 14, attention drops. The README becomes "good enough." Distribution content gets copy-pasted without reading. The social preview upload is skipped because you're already exhausted.

Time compounds attention. Every extra minute in the pipeline costs output quality.

The Fix

github launch

Phase 1 spawns 3 agents simultaneously (Hermes's delegate_task ceiling):

• Agent A reads your project, extracts the value prop and measurable benefit
• Agent B researches the top 3 similar repos and mines their README patterns
• Agent C generates the social preview SVG and writes all supporting files (CHANGELOG, .gitignore, CONTRIBUTING, LICENSE, SECURITY, FUNDING, PR template, issue templates, CI workflow)

While you wait 4-6 minutes instead of 20+, Agent B is benchmarking your README against repos that already converted visitors into stars.

Install

This is a skill for Hermes Agent. Drop the file into your Hermes skills directory and triggers activate automatically.

mkdir -p ~/.hermes/skills/hermes-github-launch
curl -L https://github.com/Rishiidev/hermes-github-launch/releases/latest/download/hermes-github-launch.skill \
  -o ~/.hermes/skills/hermes-github-launch/SKILL.md

That's it. No CLI, no plugin manager, no marketplace. Open a new Hermes session and say:

github launch

The skill loads, the pipeline starts. Three questions, then full parallel execution.

Triggers

Mode	Triggers
Launch (full pipeline)	github launch · launch on github · push to github · publish repo · ship to github · agentic github launch · parallel launch · github release setup · github seo · github everything · full github setup
Lite (skip distribution)	fast push · quick push · push now · lite launch
Improve (existing repos)	improve my repo · upgrade github repo · audit my github repo · fix my readme · enhance my repo · github health check · what's missing from my repo
Help	github launch help · what can you do · show me github launch

What You Get

Launch Mode — ~4-6 min

STEP -1   SEO name scoring         5 candidates ranked; user picks
STEP  0   Minimal inputs           3 questions (everything else auto-detected)
STEP  1   Pre-flight safety        auth · secrets · git state · gh availability
─────────────────────────────────────────────────────────────
PARALLEL PHASE 1  (3 subagents simultaneous)
  A  Project intelligence          value prop, before/after, measurable benefit
  B  Competitor research           topics, README patterns, description candidates
  C  Social preview SVG + supporting files
─────────────────────────────────────────────────────────────
PHASE 1 SYNTHESIS  (sequential)
  Refine SVG · choose description · choose 20 topics · write README
  · write GitHub Pages index.html · write CI workflows
─────────────────────────────────────────────────────────────
GIT OPS   init → create repo → push
─────────────────────────────────────────────────────────────
PARALLEL PHASE 2  (3 subagents simultaneous)
  D  Topics + description + settings
  E  Labels + good-first-issue
  F  GitHub release v1.0.0
─────────────────────────────────────────────────────────────
GitHub Pages   commit docs/ → enable → verify → set homepage
Validation     7-check pass/fail with auto-fix
─────────────────────────────────────────────────────────────
PARALLEL PHASE 3  (3 subagents simultaneous)  [LITE: skip entirely]
  G  Reddit post + Show HN
  H  X/Twitter thread + LinkedIn
  I  Product Hunt + DEV.to + newsletter pitches
─────────────────────────────────────────────────────────────
7-Day Launch Calendar   absolute dates from TODAY
Final Report

Improve Mode — audit + fix existing repos

• 6 parallel audit agents score 18 README dimensions, repo settings, version consistency, growth stage, and benchmark against 3 top competitors
• Health Score: current/100 → projected/100
• Every gap ranked by ROI — Quick Wins flagged first
• Never overwrites without showing a diff + getting confirmation
• Fixes: topics, description, README, CHANGELOG, version consistency, repo settings, branch protection, Dependabot, labels, good-first-issue

Adaptations from the Claude Code original

This skill is the Hermes-native version. The original (github-launch-agent by Rishiidev) targets Claude Code's Agent tool with 16 parallel agents. This one:

	github-launch-agent (Claude)	hermes-github-launch (Hermes, this)
Agent tool	Agent (up to 16 concurrent)	delegate_task (up to 3 concurrent per turn)
Phase sizes	4 + 4 + 8 agents	3 + 3 + 3 agents
Distribution	Inline gh api from skill	Delegated to Phase 3 subagents
Resume state	.launch-state file	Same — .launch-state
Rate-limit guard	gh_safe() shell function	Same — gh_safe()
Skill packaging	.skill zip + GitHub release	Raw SKILL.md + GitHub release
Install	/plugin install or upload .skill	curl to ~/.hermes/skills/

The full agent prompts, variable registry, routing logic, IMPROVE mode, 7-day calendar, and "What Not To Do" guardrails are all preserved — see skills/hermes-github-launch/SKILL.md for the canonical source.

How Parallel Phases Work in Hermes

Hermes's delegate_task accepts a tasks array — pass all parallel agents as items in one single call. This is the only way to get true concurrency. Sequential calls defeat the purpose.

delegate_task(tasks=[
    {"goal": "...", "toolsets": ["file", "web", "terminal"]},  # Agent A
    {"goal": "...", "toolsets": ["web", "terminal"]},          # Agent B
    {"goal": "...", "toolsets": ["file"]},                     # Agent C
])

Ceiling: delegation.max_concurrent_children is set per user (default 3 for this distribution). Each phase is sized to that ceiling. If you have more logical agents, batch them across two delegate_task calls within the phase.

The 3 Questions

The skill auto-detects everything it can:

• gh auth + active user → owner
• Project files → stack and category
• LICENSE → defaults to MIT
• Discussions, custom domain → sensible defaults

It only asks:

1. Project directory path? (Default: <auto-detected cwd>)
   Public or private? (Default: public)
2. GitHub Pages landing page? (Default: yes)
   → If yes: custom domain? (e.g. tools.yourdomain.com — leave blank for default)
3. Anything to skip? (Default: nothing — full Phase 3 distribution)

What "Good" Looks Like

A repo that ran through this pipeline has:

• ✓ A README with a number-led value prop, social preview SVG as the first element, install command in the first 30 lines
• ✓ 20 SEO topics derived from top competitors, not guessed
• ✓ 5 scored description candidates — you picked the winner
• ✓ A v1.0.0 GitHub release with notes matching the README
• ✓ 5 standard labels + a genuine good-first-issue tailored to the actual project
• ✓ GitHub Pages live with a custom landing page
• ✓ All standard files (LICENSE, CHANGELOG, CONTRIBUTING, SECURITY, FUNDING, PR + issue templates)
• ✓ CI workflow validating the basics
• ✓ Ready-to-paste distribution content for Reddit, Show HN, X, LinkedIn, Product Hunt, DEV.to, and 3 newsletters — each in its own voice
• ✓ A 7-day calendar with absolute dates

What's Not Included

• Code generation. This ships your repo. It doesn't write the code that goes in it.
• Issue triage / PR review. Use a different skill.
• Continuous deployment. The release is one-shot.
• Distribution posting. Phase 3 generates the copy. You click "post." (This is intentional — agents posting to your accounts without your review is a footgun.)

Repository Layout

hermes-github-launch/
├── README.md                          ← you are here
├── LICENSE
├── CHANGELOG.md
├── CONTRIBUTING.md
├── SECURITY.md
├── .gitignore
├── assets/
│   └── social-preview.svg             ← 1280x640 dark GitHub-style
├── docs/
│   └── index.html                     ← GitHub Pages landing
├── .github/
│   ├── FUNDING.yml
│   ├── PULL_REQUEST_TEMPLATE.md
│   ├── ISSUE_TEMPLATE/
│   │   ├── bug-report.yml
│   │   └── feature-request.yml
│   └── workflows/
│       ├── validate.yml
│       └── package-skill.yml
└── skills/
    └── hermes-github-launch/
        └── SKILL.md                   ← the actual installable skill

Contributing

PRs welcome. The skill itself is in skills/hermes-github-launch/SKILL.md — keep it within Hermes's delegate_task ceiling (3 concurrent per turn). If you're adding a new agent to a phase, document its prompt template and toolsets in the SKILL.md variable registry.

License

MIT © 2026 Rishiidev

---

If this saves you the "I launched but nobody found it" problem — star it. Takes 2 seconds.
⭐ Star on GitHub