New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Post PR To Slack

by imbue-ai in imbue-ai/sculptor

Post a one-line PR announcement to a Slack channel, and mark it :merged: when the PR merges.

MITAuto-check passed

Install Post PR To Slack

skills CLI
$ npx skills add imbue-ai/sculptor --skill post-pr-to-slack -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install imbue-ai/sculptor post-pr-to-slack --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/imbue-ai/sculptor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/post-pr-to-slack .claude/skills/post-pr-to-slack && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
post-pr-to-slack
GitHub stars
238
Token cost
~1.6k tokens
SKILL.md length
828 words
Files
2 (incl. scripts)
Skills in repo
29
Repo updated
First seen
Licence
MIT

At a glance

Post a one-line PR announcement to a Slack channel, and mark it :merged: when the PR merges.

  • Works in 3 steps: Read recent channel history to match the… → Post it and capture the message… → Report the channel and ts back to the…
  • Meaningfully adjust a Sculptor PR
  • SKILL.md covers When to run, Inputs, Setup and Steps — initial post, plus 5 more sections
  • Runs Shell scripts from its folder; calls gh, glab and jq

What it does

Post PR To Slack is an agent skill from imbue-ai/sculptor. Post a one-line PR announcement to a Slack channel, and mark it :merged: when the PR merges. Use whenever you open or meaningfully adjust a Sculptor PR.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/slack_pr.sh`). Compatibility notes: Requires latchkey with a working Slack credential, plus jq and gh. Run scripts/slackpr.sh check to verify; see the latchkey skill to set it up.

It works with Slack. The repository describes itself as: Build product with grounded, parallel coding agents. The licence is MIT.

When your agent uses it

  • Meaningfully adjust a Sculptor PR

Example prompts

  • “/post-pr-to-slack”

Requirements

  • Node.js
  • A Bash shell
  • Compatibility (from SKILL.md): Requires latchkey with a working Slack credential, plus `jq` and `gh`. Run `scripts/slack_pr.sh check` to verify; see the latchkey skill to set it up.

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Read recent channel history to match the house style (terse vs.
  2. Post it and capture the message timestamp (ts). The text is sent
  3. Report the channel and ts back to the user, and remember the ts — the

What it can do on your machine

Read from SKILL.md and the folder at commit f847102. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • gh
    • glab
    • jq
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, glab and npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires latchkey with a working Slack credential, plus `jq` and `gh`. Run `scripts/slack_pr.sh check` to verify; see the latchkey skill to set it up.

    From compatibility in the SKILL.md frontmatter.

Context cost

Post PR To Slack loads about 1.6k tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 828 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~42
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from imbue-ai/sculptor at commit f847102, republished under its MIT licence (© imbue-ai). 828 words, ~1,627 tokens.

Download SKILL.mdSave it as .claude/skills/post-pr-to-slack/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
post-pr-to-slack
description
Post a one-line PR announcement to a Slack channel, and mark it :merged: when the PR merges. Use whenever you open or meaningfully adjust a Sculptor PR.
compatibility
Requires latchkey with a working Slack credential, plus `jq` and `gh`. Run `scripts/slack_pr.sh check` to verify; see the latchkey skill to set it up.
argument-hint
[pr-number | pr-url] [#channel]

Post PR to Slack

Announce Sculptor pull requests in the team's merges channel with a single standalone line, then mark each announcement :merged: once its PR merges. This file covers when to post and what the message should say; the Slack mechanics (channel lookup, posting, reacting) live in scripts/slack_pr.sh.

The skill is agent-agnostic — it depends only on latchkey, jq, gh, and bash, not on any agent-specific tooling.

When to run

  • When you open a PR for Sculptor. After gh pr create --base main succeeds, post to #project-sculptor-merges. This is a standing instruction — just post; see Authorization.
  • When you meaningfully adjust an open PR — a force-push that changes the approach, a scope change, or a retitle. Reply in the existing thread; don't start a new top-level post. Skip trivial edits (typo fixes, rebases, minor doc tweaks). If unsure, ask the user.
  • When a PR merges (you observe it, or the user says so). Add a :merged: reaction to the original post. Do not post a separate "merged" message — the reaction is the convention.

Inputs

  • Channel — #project-sculptor-merges for Sculptor PRs unless the user says otherwise.
  • PR URL — infer from git when not given:
    • current branch: gh pr view --json url -q .url
    • a specific PR: gh pr view <number> --json url -q .url
  • One-line description — draft from the PR title/body (see Drafting). If the PR already has a crisp one-liner (its title, or a ## Summary bullet), reuse it verbatim so Slack and the PR stay in lockstep.

The only PR-host-specific step is fetching the URL with gh. On a GitLab repo, swap in glab mr view --output json | jq -r .web_url; everything else is the same.

Setup

Point a variable at the helper script and confirm Slack is reachable, once per session:

bash
SLACK=.claude/skills/post-pr-to-slack/scripts/slack_pr.sh
"$SLACK" check          # prints "slack ok: team '…' as '…'", or says how to fix auth

If the check fails, run latchkey services info slack and follow its setup (a browser login if supported, otherwise latchkey auth set). The script puts an nvm-installed latchkey back on PATH itself; if check still reports it missing, install it with npm install -g latchkey.

Steps — initial post

  1. Read recent channel history to match the house style (terse vs. emoji-led, where the URL goes, capitalization), then draft the line per Drafting:

    bash
    "$SLACK" history '#project-sculptor-merges'

  2. Post it and capture the message timestamp (ts). The text is sent verbatim, so include the PR URL — Slack unfurls it into a preview:

    bash
    TEXT="Fix login crash when the token contains a colon  $PR_URL"
TS=$("$SLACK" post '#project-sculptor-merges' "$TEXT")
echo "posted ts=$TS"

    slack_pr.sh builds the JSON with jq, so backticks, quotes, or & in the text are safe.

  3. Report the channel and ts back to the user, and remember the ts — the merge-time :merged: step needs it.

Steps — adjusting an open PR

If a post for this PR already exists (use the ts you remembered, or find it), reply in its thread — don't post a new top-level message for the same PR, which splits the discussion:

bash
TS=$("$SLACK" find-ts '#project-sculptor-merges' "$PR_URL")
"$SLACK" reply '#project-sculptor-merges' "$TS" "Revised approach: now …"

Steps — PR merged

bash
TS=$("$SLACK" find-ts '#project-sculptor-merges' "$PR_URL")
"$SLACK" done '#project-sculptor-merges' "$TS"

find-ts matches the bare URL even when Slack has wrapped it in <…>. done is idempotent — an already-present :merged: counts as success. Don't post anything else; the reaction is the "merged" signal.

Show full SKILL.md (333 more words)Show less

Drafting the one-liner

The audience is teammates and future reviewers skimming the channel. The line must convey the PR's one key outcome and read standalone — no thread, repo, or commit-history context required. Lead with a verb in the channel's imperative style ("Fix X", "Migrate Y", "Speed up Z"). Draft it directly; if your harness lets you delegate prose to a smaller/faster model, you may, but it's not required.

Check the draft against these guardrails:

  • Outcome, not process. Describe what the PR achieves in the codebase as it now exists — not the bootstrap, onboarding, or workflow that produced it.
  • Timeless. No "follow-up commit does Y", "next we'll…", or "still to come". Frame it as if every commit on the branch has already landed and is the new normal. A channel post is a record, not a roadmap or a per-commit changelog.
  • One sentence, one outcome. No parenthetical hedging in a secondary change. If a second change is genuinely co-equal, that's a sign it should be its own PR.
  • Plain, not hype. "Improve performance" — not "Massive perf win!" — unless the channel actually talks that way.
  • Ends with the PR URL; no ticket IDs unless the channel uses them.

Authorization

The #project-sculptor-merges post-and-:merged: flow is pre-authorized for Sculptor PRs — this skill living in the repo is the standing instruction. Don't pause to ask "should I post this?" after gh pr create succeeds; just post. Posting and reacting are still visible to others, so do ask before any scope expansion: a different channel, @-mentioning people, a reaction other than :merged:, or cross-posting to a non-Sculptor PR.

Notes

  • Re-resolve the channel ID each invocation. Looking up by name tolerates renames; a cached ID can go stale across sessions.
  • Track the ts of your initial post in conversation memory so the merge-time reaction doesn't have to scan history.
  • Raw API / fallback. Every call routes through latchkey curl against the Slack Web API; the exact endpoints and payloads are in scripts/slack_pr.sh if you ever need to run them by hand.

© imbue-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (scripts) in .claude/skills/post-pr-to-slack of imbue-ai/sculptor.

  • SKILL.md
  • scripts/slack_pr.sh

Open the folder on GitHubat commit f847102

Compare with similar skills

Post PR To Slack next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Post PR To Slack compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Post PR To Slack this skillimbue-ai/sculptor238—~1.6kAutomated safety check: PassMIT
Agent Browser CLIvercel-labs/agent-browser44k24 repos~864Automated safety check: PassApache-2.0
Slack GIF Creatoranthropics/skills180k29 repos~2kAutomated safety check: PassApache-2.0
Electron App Automationvercel-labs/agent-browser44k5 repos~1.7kAutomated safety check: PassApache-2.0
Slack Browser Automationvercel-labs/agent-browser44k1 repos~2.1kAutomated safety check: PassApache-2.0
ComposioComposioHQ/composio30k1 repos~1.7kAutomated safety check: PassMIT

Similar skills

  • Agent Browser CLI

    vercel-labs/agent-browser

    Official

    Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking…

    44k GitHub starsUsed in 24 repos~864 tokens
    Productivity & AutomationAuto-check passed

  • Slack GIF Creator

    anthropics/skills

    Official

    Provides Slack size and frame limits, Python animation helpers and validators for building animated GIFs sized for emoji and messages.

    180k GitHub starsUsed in 29 repos~2k tokens
    Media & CreativeAuto-check passed

  • Electron App Automation

    vercel-labs/agent-browser

    Official

    Automates Electron desktop apps such as VS Code, Slack or Discord by connecting agent-browser to their Chrome DevTools Protocol port.

    44k GitHub starsUsed in 5 repos~1.7k tokens
    Productivity & AutomationAuto-check passed

  • Slack Browser Automation

    vercel-labs/agent-browser

    Official

    Drives the Slack web app with the agent-browser CLI to check unread channels, search, read channel details and extract information, with screenshots as evidence.

    44k GitHub starsUsed in 1 repo~2.1k tokens
    Productivity & AutomationAuto-check passed

  • Composio

    ComposioHQ/composio

    Route and complete Composio work across Composio For You and Composio Platform.

    30k GitHub starsUsed in 1 repo~1.7k tokens
    Productivity & AutomationAuto-check passed

  • Patch Release Check

    ClickHouse/ClickHouse

    Check whether ClickHouse's supported versions (last 3 majors + latest LTS) have recent stable patch releases, diagnose why the scheduled AutoReleases pipeline failed, and identify which releases…

    50k GitHub stars~4k tokensUpdated today
    DatabasesAuto-check: notes

More from imbue-ai/sculptor

All 29 skills in this repo

  • Auto QA Iphone

    imbue-ai/sculptor

    QA the Sculptor mobile web UI on a real iOS Simulator, driven headlessly from a Mac.

    238 GitHub stars~3.1k tokensUpdated yesterday
    Auto-check passed

  • Measure React Renders

    imbue-ai/sculptor

    Compare React component render counts between origin/main and the current branch during a user-defined UI scenario (e.g.

    238 GitHub stars~603 tokensUpdated yesterday
    Auto-check passed

  • Batch Claude Runner

    imbue-ai/sculptor

    Run Claude programmatically against collections of files in the codebase.

    238 GitHub stars~308 tokensUpdated yesterday
    Auto-check passed

  • Build Sculptor Extension

    imbue-ai/sculptor

    Build or modify a Sculptor extension — a runtime ESM module loaded into the Sculptor UI.

    238 GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed

  • Code Review Checklist

    imbue-ai/sculptor

    Review a set of code changes against Sculptor's review categories and produce a markdown findings table.

    238 GitHub stars~3.6k tokensUpdated yesterday
    Auto-check passed

  • Cut Release

    imbue-ai/sculptor

    Cut a new Sculptor release candidate from main: run just cut-release (which creates the release/sculptor-vX.Y.0 branch at X.Y.0rc1, pushes the tag that triggers the RC build, and opens a PR bumping…

    238 GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed

Works with

Questions about Post PR To Slack

What does Post PR To Slack do?

Post a one-line PR announcement to a Slack channel, and mark it :merged: when the PR merges. Post PR To Slack is an agent skill from imbue-ai/sculptor. Post a one-line PR announcement to a Slack channel, and mark it :merged: when the PR merges.

When should I use Post PR To Slack?

Post PR To Slack fits situations like: meaningfully adjust a Sculptor PR.

How do I install Post PR To Slack in Claude Code?

Run `npx skills add imbue-ai/sculptor --skill post-pr-to-slack -a claude-code`. Or copy the skill folder (.claude/skills/post-pr-to-slack in imbue-ai/sculptor) into .claude/skills/post-pr-to-slack in your project. Claude Code loads it when a task matches its description.

How do I install Post PR To Slack in Codex?

Run `npx skills add imbue-ai/sculptor --skill post-pr-to-slack -a codex`. Or copy the skill folder (.claude/skills/post-pr-to-slack in imbue-ai/sculptor) into .agents/skills/post-pr-to-slack in your project. Codex loads it when a task matches its description.

Can I use Post PR To Slack in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add imbue-ai/sculptor --skill post-pr-to-slack -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/post-pr-to-slack, .gemini/skills/post-pr-to-slack, .github/skills/post-pr-to-slack and .opencode/skills/post-pr-to-slack in your project.

What does Post PR To Slack need to run?

Going by SKILL.md and its folder, Post PR To Slack needs a shell for the scripts in its folder and the command-line tools its instructions call (gh, glab, jq and npm). Our summary lists: Node.js; A Bash shell. Compatibility (from SKILL.md): Requires latchkey with a working Slack credential, plus `jq` and `gh`. Run `scripts/slack_pr.sh check` to verify; see the latchkey skill to set it up..

Does Post PR To Slack access the network?

SKILL.md contains no URLs. Its commands use gh and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Post PR To Slack safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Post PR To Slack use?

Post PR To Slack is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Post PR To Slack use?

About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Post PR To Slack?

Skills that share tags, products or a category with Post PR To Slack: Agent Browser CLI (vercel-labs/agent-browser, 44k stars), Slack GIF Creator (anthropics/skills, 180k stars), Electron App Automation (vercel-labs/agent-browser, 44k stars) and Slack Browser Automation (vercel-labs/agent-browser, 44k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Post PR To Slack?

imbue-ai (a GitHub organization) maintains it in imbue-ai/sculptor, which has 238 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on October 9, 2026.

Source: imbue-ai/sculptor on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.