agentsclimarketplace

Ship digest

Skill PHY041/claude-agent-skills/skills/ship-digest

Detect 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 ship", or any shipping announcement request.From its SKILL.md

Install
npx -y skills add PHY041/claude-agent-skills --skill ship-digest

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 18 stars18 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.6 KB, 774 tokens by cl100k_base, as published. Nobody here has run it

Ship Digest Skill

Automatically detect new GitHub repos and turn them into social media announcements.


Setup

export GITHUB_USERNAME="yourusername"

How It Works

  1. Fetch your GitHub repos sorted by pushed_at
  2. Compare against a state file (memory/ship-digest-state.json)
  3. For any new repo pushed today β†’ analyze README + commits
  4. Generate a technical digest + social media drafts
  5. Send drafts for approval (NEVER auto-post)

Workflow

Step 1: Fetch New Repos

gh api /users/$GITHUB_USERNAME/repos?sort=pushed&per_page=10

Compare pushed_at timestamps against state file. A repo is "new" if:

  • Not in state file at all, OR
  • pushed_at is today and has 3+ new commits since last check

Step 2: Analyze Repo Content

# README
gh api /repos/$GITHUB_USERNAME/{repo}/readme --jq .content | base64 -d

# Recent commits
gh api /repos/$GITHUB_USERNAME/{repo}/commits?per_page=5

# File tree (for tech stack detection)
gh api /repos/$GITHUB_USERNAME/{repo}/git/trees/HEAD?recursive=1 --jq '[.tree[].path] | join(", ")'

Step 3: Generate Ship Digest

Output format:

🚒 Ship Digest β€” [date]

Caught a new repo: **{repo_name}**, pushed today.

**What you shipped:**
[2-3 sentence technical description based on README + commits]

πŸ“Š **{N} lines** in initial commit. [Tech stack summary].
β†’ github.com/{username}/{repo}

---

**✍️ DRAFT β€” Option A: [Hook type]**
[Twitter draft A]

**✍️ DRAFT β€” Option B: [Hook type]**
[Twitter draft B]

Reply "A" or "B" to post, or tell me what to change.

Step 4: Await Approval

User picks Option A or B (or requests edits). Then post using social-post skill or twitter-cultivate skill.

NEVER auto-post without explicit user confirmation.


Draft Generation Rules

Voice

  • First-person, authentic, no hype
  • Lead with the problem solved OR the interesting technical choice
  • Include one specific metric (lines of code, platforms supported, speed improvement)

Hook Types to Try

  1. Contrarian Hook β€” "Everyone says X, but actually Y"
  2. Data Hook β€” "[Number] lines. [N] platforms. [capability]."
  3. Problem Hook β€” "Every [person] hits [pain point] eventually..."
  4. Story Hook β€” "Been thinking about [problem] for [time]. Finally shipped something."

Banned Words

Never use: revolutionize, supercharge, game-changer, 10x, viral, hacks, disrupt, groundbreaking


State File

Location: memory/ship-digest-state.json

{
  "github_username": "yourusername",
  "last_checked": "ISO8601",
  "known_repos": {
    "repo-name": {
      "pushed_at": "ISO8601",
      "last_commit_count": 42,
      "announced": true
    }
  }
}

Cron Schedule

Runs 2x daily: 09:00 and 16:00 (your local time).

If no new repos: reply HEARTBEAT_OK.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most ship operate skills give in 774 tokens

Counted across 779 of the 1,178 authors here whose files we hold, read 2026-08-07

  • Document a rollback plan before deploymentin 41 of 779, across 22 files
  • Update the changelogin 21 of 779, across 19 files
  • Run the test suitein 20 of 779
  • Create an annotated git tagin 20 of 779
  • Clean up feature flags after full rolloutin 18 of 779, across 10 files
  • Verify deployment health after launchin 18 of 779, across 10 files
  • Test both feature flag statesin 17 of 779, across 9 files
  • Verify the working tree is cleanin 17 of 779
  • Make database migrations backward-compatiblein 16 of 779, across 8 files
  • Set up error monitoring before launchin 15 of 779, across 7 files
  • Monitor metrics at each rollout stagein 14 of 779, across 5 files
  • Create a GitHub releasein 14 of 779

Said here and by no other author read

  • fetch repos sorted by pushed_at
  • compare repos against state file
  • analyze readme and commits for new repos
  • generate technical digest and social drafts
  • lead drafts with problem solved
  • include one specific metric

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,569. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.