kill-the-standup
Reads yesterday's Linear issues and GitHub commits for the authenticated user, formats a standup update (done / doing / blockers), and posts it to Slack. Use when asked to write a standup, generate a standup update, post to the standup channel, summarize yesterday's work, or automate the daily standup. Trigger when a user says "write my standup", "post standup", "generate standup update", "what did I do yesterday", or "kill the standup".
npx skills add Varnan-Tech/opendirectory --skill kill-the-standup --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Kill the Standup Read yesterday's Linear issues and GitHub commits. Format a standup update. Post it to Slack. --- ## Step 1: Setup Check Confirm required env vars are set: ```bash echo "LINEAR_API_KEY: ${LINEAR_API_KEY:+set}" echo "SLACK_WEBHOOK_URL: ${SLACK_WEBHOOK_URL:+set}" echo "GITHUB_REPO: ${GITHUB_REPO:-not set}" echo "GITHUB_USERNAME: ${GITHUB_USERNAME:-not set}" ``` **If LINEAR_API_KEY is missing:** Stop. Tell the user: "LINEAR_API_KEY is required. Get it from Linear → Settings → API → Personal API keys. Add it to your .env file." **If SLACK_WEBHOOK_URL is missing:** Stop. Tell the user: "SLACK_WEBHOOK_URL is required. Create an Incoming Webhook at api.slack.com/apps → Your App → Incoming Webhooks. Add it to your .env file." **If GITHUB_REPO is missing:** Continue. GitHub commits will be skipped. Note this to the user. --- ## Step 2: Fetch Linear Activity Compute yesterday's date in ISO 8601 format (e.g. `2026-04-09T00:00:00.000Z`). **Get current user ID:** ```bash curl -s -X POST https://api.linear.app/graphql \ -H "Authorization: Bearer $LINEAR_API_KEY" \ -H "Content-Type: application/json" \ -d '{"query": "query { viewer { id name email } }"}' ``` Extract the `id` fi
- Step 1: Setup Check
- Step 2: Fetch Linear Activity
- Step 3: Fetch GitHub Commits
- Step 4: Format Standup
- Step 5: Post to Slack or Output
echo "LINEAR_API_KEY: ${LINEAR_API_KEY:+set}"
echo "SLACK_WEBHOOK_URL: ${SLACK_WEBHOOK_URL:+set}"
echo "GITHUB_REPO: ${GITHUB_REPO:-not set}"
echo "GITHUB_USERNAME: ${GITHUB_USERNAME:-not set}"
curl -s -X POST https://api.linear.app/graphql \
gh api "repos/$GITHUB_REPO/commits?author=${GITHUB_USERNAME:-$(gh api user --jq .login)}&since=YESTERDAY_ISO&per_page=30" \
curl -s -X POST "$SLACK_WEBHOOK_URL" \
cat > /tmp/standup-payload.json << 'ENDJSON'
curl -s -X POST "$SLACK_WEBHOOK_URL" -H "Content-Type: application/json" -d @/tmp/standup-payload.jsonWhat does the kill-the-standup skill do?
Reads yesterday's Linear issues and GitHub commits for the authenticated user, formats a standup update (done / doing / blockers), and posts it to Slack. Use when asked to write a standup, generate a standup update, post to the standup channel, summarize yesterday's work, or automate the daily standup. Trigger when a user says "write my standup", "post standup", "generate standup update", "what did I do yesterday", or "kill the standup".
How do I install it?
Run `npx skills add Varnan-Tech/opendirectory --skill kill-the-standup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Varnan-Tech/opendirectory, a repository with 571 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.