$npx -y skills add PHY041/claude-agent-skills --skill ship-digestDetect new GitHub repos and generate formatted ship announcements for social media. Monitors your GitHub profile for new repos pushed today, writes a technical digest, and drafts Twitter/Reddit posts for approval. Triggers on "ship digest", "new repos", "what did I ship", "github
| 1 | # Ship Digest Skill |
| 2 | |
| 3 | Automatically detect new GitHub repos and turn them into social media announcements. |
| 4 | |
| 5 | --- |
| 6 | |
| 7 | ## Setup |
| 8 | |
| 9 | ```bash |
| 10 | export GITHUB_USERNAME="yourusername" |
| 11 | ``` |
| 12 | |
| 13 | --- |
| 14 | |
| 15 | ## How It Works |
| 16 | |
| 17 | 1. Fetch your GitHub repos sorted by `pushed_at` |
| 18 | 2. Compare against a state file (`memory/ship-digest-state.json`) |
| 19 | 3. For any new repo pushed today → analyze README + commits |
| 20 | 4. Generate a technical digest + social media drafts |
| 21 | 5. Send drafts for approval (NEVER auto-post) |
| 22 | |
| 23 | --- |
| 24 | |
| 25 | ## Workflow |
| 26 | |
| 27 | ### Step 1: Fetch New Repos |
| 28 | |
| 29 | ```bash |
| 30 | gh api /users/$GITHUB_USERNAME/repos?sort=pushed&per_page=10 |
| 31 | ``` |
| 32 | |
| 33 | Compare `pushed_at` timestamps against state file. A repo is "new" if: |
| 34 | - Not in state file at all, OR |
| 35 | - `pushed_at` is today and has 3+ new commits since last check |
| 36 | |
| 37 | ### Step 2: Analyze Repo Content |
| 38 | |
| 39 | ```bash |
| 40 | # README |
| 41 | gh api /repos/$GITHUB_USERNAME/{repo}/readme --jq .content | base64 -d |
| 42 | |
| 43 | # Recent commits |
| 44 | gh api /repos/$GITHUB_USERNAME/{repo}/commits?per_page=5 |
| 45 | |
| 46 | # File tree (for tech stack detection) |
| 47 | gh api /repos/$GITHUB_USERNAME/{repo}/git/trees/HEAD?recursive=1 --jq '[.tree[].path] | join(", ")' |
| 48 | ``` |
| 49 | |
| 50 | ### Step 3: Generate Ship Digest |
| 51 | |
| 52 | Output format: |
| 53 | |
| 54 | ``` |
| 55 | 🚢 Ship Digest — [date] |
| 56 | |
| 57 | Caught a new repo: **{repo_name}**, pushed today. |
| 58 | |
| 59 | **What you shipped:** |
| 60 | [2-3 sentence technical description based on README + commits] |
| 61 | |
| 62 | 📊 **{N} lines** in initial commit. [Tech stack summary]. |
| 63 | → github.com/{username}/{repo} |
| 64 | |
| 65 | --- |
| 66 | |
| 67 | **✍️ DRAFT — Option A: [Hook type]** |
| 68 | [Twitter draft A] |
| 69 | |
| 70 | **✍️ DRAFT — Option B: [Hook type]** |
| 71 | [Twitter draft B] |
| 72 | |
| 73 | Reply "A" or "B" to post, or tell me what to change. |
| 74 | ``` |
| 75 | |
| 76 | ### Step 4: Await Approval |
| 77 | |
| 78 | User picks Option A or B (or requests edits). Then post using `social-post` skill or `twitter-cultivate` skill. |
| 79 | |
| 80 | NEVER auto-post without explicit user confirmation. |
| 81 | |
| 82 | --- |
| 83 | |
| 84 | ## Draft Generation Rules |
| 85 | |
| 86 | ### Voice |
| 87 | - First-person, authentic, no hype |
| 88 | - Lead with the problem solved OR the interesting technical choice |
| 89 | - Include one specific metric (lines of code, platforms supported, speed improvement) |
| 90 | |
| 91 | ### Hook Types to Try |
| 92 | 1. **Contrarian Hook** — "Everyone says X, but actually Y" |
| 93 | 2. **Data Hook** — "[Number] lines. [N] platforms. [capability]." |
| 94 | 3. **Problem Hook** — "Every [person] hits [pain point] eventually..." |
| 95 | 4. **Story Hook** — "Been thinking about [problem] for [time]. Finally shipped something." |
| 96 | |
| 97 | ### Banned Words |
| 98 | Never use: revolutionize, supercharge, game-changer, 10x, viral, hacks, disrupt, groundbreaking |
| 99 | |
| 100 | --- |
| 101 | |
| 102 | ## State File |
| 103 | |
| 104 | Location: `memory/ship-digest-state.json` |
| 105 | |
| 106 | ```json |
| 107 | { |
| 108 | "github_username": "yourusername", |
| 109 | "last_checked": "ISO8601", |
| 110 | "known_repos": { |
| 111 | "repo-name": { |
| 112 | "pushed_at": "ISO8601", |
| 113 | "last_commit_count": 42, |
| 114 | "announced": true |
| 115 | } |
| 116 | } |
| 117 | } |
| 118 | ``` |
| 119 | |
| 120 | --- |
| 121 | |
| 122 | ## Cron Schedule |
| 123 | |
| 124 | Runs 2x daily: 09:00 and 16:00 (your local time). |
| 125 | |
| 126 | If no new repos: reply `HEARTBEAT_OK`. |