@opendirectory.dev/skills 0.1.0

package/skills/kill-the-standup/README.md

@@ -0,0 +1,84 @@
+# kill-the-standup
+
+<img width="1280" height="640" alt="kill-the-standup" src="https://github.com/user-attachments/assets/4fcf306d-7ef9-455a-b5f1-02532c292f65" />
+
+
+Write your daily standup in seconds. The skill reads yesterday's Linear issues and GitHub commits, formats a done/doing/blockers update, and posts it to Slack.
+
+## What It Does
+
+- Fetches yesterday's Linear issues assigned to you (completed and in-progress)
+- Fetches yesterday's GitHub commits from your configured repo
+- Formats a three-section standup: Done, Doing, Blockers
+- Posts to your Slack channel via Incoming Webhook
+
+## Requirements
+
+| Requirement | Purpose | How to Set Up |
+|------------|---------|--------------|
+| Linear API key | Fetching your issues | Linear, Settings, API, Personal API keys |
+| Slack Incoming Webhook | Posting the standup | api.slack.com/apps, Your App, Incoming Webhooks |
+| `gh` CLI (optional) | Fetching GitHub commits | https://cli.github.com, then run `gh auth login` |
+
+No LLM API key needed. The agent reads your activity directly.
+
+## Setup
+
+```bash
+cp .env.example .env
+```
+
+Edit `.env` and fill in:
+- `LINEAR_API_KEY` (required)
+- `SLACK_WEBHOOK_URL` (required)
+- `GITHUB_REPO` (optional, format: `owner/repo`)
+- `GITHUB_USERNAME` (optional, defaults to your gh auth username)
+
+## How to Use
+
+Write and post standup:
+
+```
+"Write my standup"
+"Post my standup to Slack"
+"Generate standup update"
+```
+
+Output only, no Slack post:
+
+```
+"Write my standup but don't post it"
+"What did I do yesterday?"
+"Give me my standup text"
+```
+
+## Output Format
+
+```
+Done
+- [ENG-123] Fix session timeout bug
+- fix: remove duplicate middleware registration
+
+Doing
+- [ENG-124] Migrate auth to OAuth2
+
+Blockers
+No blockers.
+```
+
+## Project Structure
+
+```
+kill-the-standup/
+├── SKILL.md
+├── README.md
+├── .env.example
+├── evals/
+│   └── evals.json
+└── references/
+    └── standup-format.md
+```
+
+## License
+
+MIT

package/skills/kill-the-standup/SKILL.md

@@ -0,0 +1,169 @@
+---
+name: kill-the-standup
+description: 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".
+compatibility: [claude-code, gemini-cli, github-copilot]
+author: OpenDirectory
+version: 1.0.0
+---
+
+# 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` field from the response. Store as `LINEAR_USER_ID`.
+
+**Fetch issues assigned to me, updated since yesterday:**
+```bash
+curl -s -X POST https://api.linear.app/graphql \
+  -H "Authorization: Bearer $LINEAR_API_KEY" \
+  -H "Content-Type: application/json" \
+  -d '{
+    "query": "query($since: DateTime!, $userId: ID!) { issues(first: 50, filter: { assignee: { id: { eq: $userId } } updatedAt: { gte: $since } }) { edges { node { identifier title state { name } url completedAt updatedAt createdAt } } } }",
+    "variables": {"since": "YESTERDAY_ISO", "userId": "LINEAR_USER_ID"}
+  }'
+```
+
+**Categorize issues:**
+- `completedAt` is non-null → **Done**
+- `state.name` is "In Progress", "Started", or "In Review" → **Doing**
+- `state.name` is "Cancelled" → skip
+- `state.name` is "Todo" or "Backlog" → skip (not worked on)
+
+If zero issues: note "No Linear activity found for yesterday."
+
+---
+
+## Step 3: Fetch GitHub Commits
+
+Skip this step silently if GITHUB_REPO is not set.
+
+If GITHUB_REPO is set:
+
+```bash
+gh api "repos/$GITHUB_REPO/commits?author=${GITHUB_USERNAME:-$(gh api user --jq .login)}&since=YESTERDAY_ISO&per_page=30" \
+  --jq '[.[] | {message: .commit.message, url: .html_url}]'
+```
+
+**Process commits:**
+- Extract the first line of each commit message (everything before the first newline)
+- Skip merge commits: drop any message starting with "Merge"
+- Deduplicate by message text
+
+If GITHUB_REPO is set but returns zero commits: note "No commits found yesterday."
+
+---
+
+## Step 4: Format Standup
+
+Read `references/standup-format.md` in full before writing.
+
+Produce the standup in this exact structure:
+
+```
+**Done**
+- [ENG-123] Title of completed issue
+- fix: commit message here
+
+**Doing**
+- [ENG-124] Title of in-progress issue
+
+**Blockers**
+No blockers.
+```
+
+Rules from standup-format.md:
+- No first-person pronouns ("I", "we")
+- Past tense for Done items, present continuous for Doing items
+- Each Linear item uses the `[IDENTIFIER] Title` format
+- Each GitHub commit uses the first line of the commit message
+- If no Done items: write "Nothing completed." under Done
+- If no Doing items: write "Nothing in progress." under Doing
+- If no blockers: write "No blockers."
+- Under 200 words total
+
+---
+
+## Step 5: Post to Slack or Output
+
+Present the formatted standup to the user.
+
+Ask: "Post this to Slack, or output only?"
+
+**On confirmation to post:**
+
+```bash
+curl -s -X POST "$SLACK_WEBHOOK_URL" \
+  -H "Content-Type: application/json" \
+  -d '{
+    "blocks": [
+      {
+        "type": "section",
+        "text": {
+          "type": "mrkdwn",
+          "text": "*Standup — DATE_HERE*\n\n*Done*\nITEMS\n\n*Doing*\nITEMS\n\n*Blockers*\nITEMS"
+        }
+      }
+    ]
+  }'
+```
+
+Pass the body via a temp file or heredoc to avoid shell quoting issues with special characters in commit messages or issue titles:
+
+```bash
+cat > /tmp/standup-payload.json << 'ENDJSON'
+{
+  "blocks": [
+    {
+      "type": "section",
+      "text": {
+        "type": "mrkdwn",
+        "text": "STANDUP_CONTENT_HERE"
+      }
+    }
+  ]
+}
+ENDJSON
+curl -s -X POST "$SLACK_WEBHOOK_URL" -H "Content-Type: application/json" -d @/tmp/standup-payload.json
+```
+
+After posting: "Standup posted."
+
+**On "output only":** Print the standup in a code block for copy-paste.
+
+

package/skills/kill-the-standup/evals/evals.json

@@ -0,0 +1,35 @@
+{
+  "skill_name": "kill-the-standup",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Write my standup",
+      "expected_output": "Agent checks for LINEAR_API_KEY and SLACK_WEBHOOK_URL — both present. GITHUB_REPO is set. Runs Linear viewer query to get user ID. Runs issues query filtered by assignee + updatedAt >= yesterday. Runs gh api repos/OWNER/REPO/commits filtered by author + since yesterday. Produces three-section standup: Done (completed Linear issues + commits), Doing (in-progress issues), Blockers (No blockers). Presents standup to user and asks: Post to Slack or output only?",
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Generate my standup — I haven't set GITHUB_REPO",
+      "expected_output": "Agent detects GITHUB_REPO is not set. Skips Step 3 silently. Fetches Linear issues only. Produces standup with Done and Doing from Linear, no GitHub commits section. Blockers: No blockers. Asks user to confirm before posting. Does not error or mention GitHub unless noting it was skipped.",
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "Post my standup to Slack",
+      "expected_output": "Agent runs full workflow. If Linear returns zero issues for yesterday, notes 'No Linear activity found for yesterday' but still checks GitHub if GITHUB_REPO is set. Produces valid standup (may show 'Nothing completed.' and 'Nothing in progress.'). Presents to user, confirms, then POSTs JSON payload to SLACK_WEBHOOK_URL using a temp file to avoid shell quoting issues. Confirms 'Standup posted.' after successful curl response.",
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "Write my standup — I didn't do anything yesterday",
+      "expected_output": "Agent fetches Linear and GitHub (if configured). Both return zero results. Produces minimal standup: Done section shows 'Nothing completed.', Doing section shows 'Nothing in progress.', Blockers shows 'No blockers.' Agent presents this to the user and asks if they want to add context or post as-is. Does not invent activity.",
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "Post standup to Slack",
+      "expected_output": "Agent checks SLACK_WEBHOOK_URL — it is missing from environment. Agent stops immediately at Step 1. Tells 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.' Does not proceed to fetch Linear or GitHub data.",
+      "files": []
+    }
+  ]
+}

package/skills/kill-the-standup/references/standup-format.md

@@ -0,0 +1,102 @@
+# Standup Format Guide
+
+## Structure
+
+Always three sections, always in this order:
+
+```
+**Done**
+- [ENG-123] Title of completed issue
+- fix: commit message here
+
+**Doing**
+- [ENG-124] Title of in-progress issue
+
+**Blockers**
+No blockers.
+```
+
+---
+
+## Section Rules
+
+### Done
+What was completed yesterday.
+
+- One bullet per Linear issue with `completedAt` set
+- One bullet per GitHub commit (first line of message, deduplicated, skip merges)
+- Format for Linear items: `[IDENTIFIER] Title` — e.g. `[ENG-42] Fix session timeout bug`
+- Format for commits: first line of commit message — e.g. `fix: remove duplicate auth check`
+- Tense: past tense implied by the format (no verb prefix needed unless the commit message has one)
+- If nothing was completed: write `Nothing completed.` as the only bullet
+
+### Doing
+What is in progress right now.
+
+- One bullet per Linear issue with state In Progress, Started, or In Review
+- Format: `[IDENTIFIER] Title` — same as Done
+- Tense: present continuous implied — no need to add "working on" or "continuing"
+- If nothing is in progress: write `Nothing in progress.` as the only bullet
+
+### Blockers
+What is blocked and why.
+
+- Write `No blockers.` if nothing is blocked
+- Only add a blocker entry if the user explicitly mentions one, or if an issue has been In Progress for more than 3 days without a state change (createdAt vs updatedAt gap > 3 days)
+- Format: `[ENG-125] Waiting on design approval` — issue + reason
+- Never invent blockers
+
+---
+
+## Writing Rules
+
+- No first-person pronouns: no "I", "we", "my", "our"
+- No filler phrases: no "today I will", "yesterday I", "as per the discussion", "going to"
+- No markdown headers inside the standup body — use bold `**Section**` labels only
+- Under 200 words total
+- Bullet list only — no paragraphs, no sentences that span multiple lines
+- Each bullet is one issue or one commit, nothing more
+- No hashtags, no em dashes
+
+---
+
+## Examples
+
+**Full standup (Linear + GitHub):**
+```
+**Done**
+- [ENG-88] Add Redis caching for session lookups
+- fix: remove duplicate middleware registration
+- chore: bump Next.js to 14.2.0
+
+**Doing**
+- [ENG-91] Migrate auth to OAuth2
+
+**Blockers**
+No blockers.
+```
+
+**Linear only (no GitHub repo configured):**
+```
+**Done**
+- [OPS-14] Set up staging deployment pipeline
+
+**Doing**
+- [OPS-15] Configure load balancer health checks
+- [OPS-16] Document rollback procedure
+
+**Blockers**
+No blockers.
+```
+
+**No activity:**
+```
+**Done**
+Nothing completed.
+
+**Doing**
+Nothing in progress.
+
+**Blockers**
+No blockers.
+```

package/skills/linkedin-post-generator/.env.example

@@ -0,0 +1,14 @@
+# linkedin-post-generator — Environment Variables
+# =================================================
+# The AI agent writes the post — no LLM API key needed.
+# Composio is the only optional dependency, for direct LinkedIn posting.
+
+# Required for direct posting via Composio.
+# Without this key, the agent outputs the formatted post as text for manual copy-paste.
+#
+# Setup steps:
+# 1. Get your API key at: https://app.composio.dev/settings
+# 2. Connect your LinkedIn account at: https://app.composio.dev/app/linkedin
+# 3. Complete the OAuth flow
+# 4. The agent will call linkedin_create_linkedin_post when you confirm posting
+COMPOSIO_API_KEY=your_composio_api_key_here

package/skills/linkedin-post-generator/README.md

@@ -0,0 +1,107 @@
+# linkedin-post-generator
+
+<img width="1376" height="768" alt="LinkedIn_post_generator" src="https://github.com/user-attachments/assets/dc71e06b-8b3c-486a-adbf-d56a7b22cdc1" />
+
+Generate LinkedIn posts from any content: blog posts, articles, GitHub PRs, or a description of what you built. The agent reads your source material, applies LinkedIn's content patterns, and produces a post with the right hook, story arc, and formatting.
+
+## Post Styles
+
+| Style | Use When | Example Input |
+|-------|----------|---------------|
+| Founder/Ship | Personal story of building or shipping | "We merged our streaming SDK after 3 weeks" |
+| Insight | Educational observation or lesson | Blog article, pattern you noticed, lesson learned |
+| Product Launch | Announcing a new tool or feature | PR description, launch brief, feature going GA |
+| Tutorial Summary | Distilling a long technical post | Tutorial URL, deep-dive article, step-by-step guide |
+
+The agent auto-detects the right style. You override it by asking for a specific one.
+
+## Requirements
+
+No LLM API key needed. The agent writes the post.
+
+Composio is optional. Add it to post directly to LinkedIn.
+
+## Setup
+
+### Composio (Optional)
+
+Without Composio, the agent outputs formatted text for copy-paste. No configuration needed.
+
+To enable direct posting:
+1. Get your API key at https://app.composio.dev/settings
+2. Connect your LinkedIn account at https://app.composio.dev/app/linkedin
+3. Complete the OAuth flow
+4. Add the key to your .env file:
+
+```bash
+cp .env.example .env
+# Edit .env and add your COMPOSIO_API_KEY
+```
+
+## How to Use
+
+From a URL:
+```
+"Turn this into a LinkedIn post: https://yourblog.com/my-post"
+"Write a LinkedIn post about this article: [URL]"
+```
+
+From pasted text:
+```
+"Here's a case study, turn it into a LinkedIn post: [paste text]"
+"Convert this to a LinkedIn post: [paste article]"
+```
+
+From a PR or shipped feature:
+```
+"Write a LinkedIn post about this PR we merged: [paste PR description]"
+"Announce our new feature on LinkedIn: [describe the feature]"
+```
+
+With a style override:
+```
+"Write a LinkedIn post in Tutorial Summary style about: [topic]"
+"Use the Product Launch style for this: [description]"
+```
+
+With direct posting:
+```
+"Post this to LinkedIn: [paste content]"
+"Generate and post a LinkedIn update about [topic]"
+```
+
+## Output
+
+| Output | Description |
+|--------|-------------|
+| LinkedIn post | Formatted text, 900-1,300 characters, ready to publish |
+| First comment | Text with source links. Post this immediately after publishing. |
+| Hook alternatives | 2 additional hook lines in different formats |
+| Posted confirmation | If Composio is configured and you confirm posting |
+
+## How Posts Are Formatted
+
+Four rules drive every post the agent writes:
+
+- Hook first. The first line is all most people see. It works standalone.
+- Short paragraphs. 1-3 lines, then a blank line. LinkedIn is mobile-first.
+- Links in the first comment. URLs in the post body reduce LinkedIn's distribution.
+- Question or CTA at the end. One or the other, not both.
+
+## Project Structure
+
+```
+linkedin-post-generator/
+├── SKILL.md
+├── README.md
+├── .env.example
+├── evals/
+│   └── evals.json
+└── references/
+    ├── linkedin-format.md
+    └── output-template.md
+```
+
+## License
+
+MIT