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

Official agent skill

Setting Up Support Slack Locally

by PostHog in PostHog/posthog

Connect a real Slack workspace to local PostHog Conversations (the SupportHog Slack app) so Slack messages become support tickets and replies post back.

OfficialCustom licenceAuto-check: notesBackend & APIs

Install Setting Up Support Slack Locally

skills CLI
$ npx skills add PostHog/posthog --skill setting-up-support-slack-locally -a claude-code

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

GitHub CLI
$ gh skill install PostHog/posthog setting-up-support-slack-locally --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/PostHog/posthog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/setting-up-support-slack-locally .claude/skills/setting-up-support-slack-locally && 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
setting-up-support-slack-locally
GitHub stars
40k
Token cost
~2.3k tokens
SKILL.md length
985 words
Files
2 (incl. references)
Skills in repo
254
Repo updated
First seen
Licence
Custom licence

At a glance

Connect a real Slack workspace to local PostHog Conversations (the SupportHog Slack app) so Slack messages become support tickets and replies post back.

  • Works in 4 steps: credentials → the Slack app → tunnel for inbound events → …
  • The user wants to test the conversations Slack integration locally
  • SKILL.md covers The endpoints, Step 1 — credentials, Step 2 — the Slack app and Step 3 — tunnel for inbound…, plus 2 more sections
  • Calls ngrok, cloudflared and curl; needs SUPPORT_SLACK_APP_CLIENT_SECRET and SUPPORT_SLACK_SIGNING_SECRET

What it does

Setting Up Support Slack Locally is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Connect a real Slack workspace to local PostHog Conversations (the SupportHog Slack app) so Slack messages become support tickets and replies post back. Use when the user wants to test the conversations Slack integration locally, hits "Support Slack OAuth client ID is not configured", gets a white screen or "Network error" on the OAuth callback, or asks how to set SUPPORTSLACKAPPCLIENTID / a tunnel for supporthog Slack events. Covers the Slack app + scopes, the SUPPORTSLACK dynamic settings, and the key split…

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/troubleshooting.md`).

It sits in Backend & APIs, covering OAuth and OpenID Connect, Customer support and Messaging and chat bots. It works with Slack and PostHog. The repository describes itself as: :hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error…

When your agent uses it

  • The user wants to test the conversations Slack integration locally
  • Hits Support Slack OAuth client ID is not configured
  • Gets a white screen
  • Network error on the OAuth callback

Example prompts

  • “Support Slack OAuth client ID is not configured”
  • “Network error”
  • “/setting-up-support-slack-locally”

Requirements

  • A credential in SUPPORT_SLACK_APP_CLIENT_SECRET
  • A credential in SUPPORT_SLACK_SIGNING_SECRET

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. credentials
  2. the Slack app
  3. tunnel for inbound events
  4. connect and test

What it can do on your machine

Read from SKILL.md and the folder at commit c012c8d. 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

    Shell commands in SKILL.md call:

    • ngrok
    • cloudflared
    • curl

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

  • Network

    Links to these hosts (documentation or services it may open):

    • api.slack.com

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

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • SUPPORT_SLACK_APP_CLIENT_SECRET
    • SUPPORT_SLACK_SIGNING_SECRET

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

Context cost

Setting Up Support Slack Locally loads about 2.3k tokens when it runs, and up to ~4.5k if it reads all its reference files. Until then it costs about 157 tokens; SKILL.md has 985 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~157
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.5k

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:53
    app's values in `.env.local` (gitignored) and restart the backend:
  • NoteMentions a .env fileSKILL.md:79
    ning Secret from Basic Information into `.env.local` (Step 1).

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); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 985 words (~2,282 tokens).

“Slack is SaaS-only, so "local" means a throwaway Slack workspace + app whose OAuth and events reach your laptop. The job has one non-obvious idea that avoids almost every wall: the OAuth connect and the event webhook have opposite reachability…”

— opening of SKILL.md by PostHog, Custom licence
name
setting-up-support-slack-locally

Read the full SKILL.md on GitHub

Files

SKILL.md and 1 other file (references) in .agents/skills/setting-up-support-slack-locally of PostHog/posthog.

  • SKILL.md
  • references/troubleshooting.md

Open the folder on GitHubat commit c012c8d

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in PostHog/posthog, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Setting Up Support Slack Locally 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.

Setting Up Support Slack Locally compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Setting Up Support Slack Locally this skillPostHog/posthog40k—~2.3kAutomated safety check: NotesCustom licence
Openloomi Connectorsmelandlabs/openloomi1k—~3.3kAutomated safety check: PassApache-2.0
Implementing Zero Trust For SaaS Applicationsmukul975/Anthropic-Cybersecurity-Skills34k—~2.9kAutomated safety check: PassApache-2.0
Socialite Developmenthexlet-volunteers/hexlet-sicp1145 repos~1.2kAutomated safety check: PassMIT
Add Channel Connect Buttonnovuhq/novu40k—~1.6kAutomated safety check: PassCustom licence
Add OAuth Integrationrome-os/rome743—~3.6kAutomated safety check: PassMIT

Similar skills

  • Openloomi Connectors

    melandlabs/openloomi

    openloomi Connectors tools - manage the native 7 messaging integrations and pair with the composio skill for the 1000+ apps OAuth layer (Slack, Discord, X, Gmail, Outlook, Google…

    1k GitHub stars~3.3k tokensUpdated 16 days ago
    Productivity & AutomationAuto-check passed

  • Implementing Zero Trust For SaaS Applications

    mukul975/Anthropic-Cybersecurity-Skills

    Secures SaaS apps (Microsoft 365, Google Workspace, Salesforce, Slack) via CASB/SSPM deployment, conditional access policies, OAuth app governance, and session-level DLP controls enforcing identity…

    34k GitHub stars~2.9k tokensUpdated 1 mo ago
    Backend & APIsAuto-check passed

  • Socialite Development

    hexlet-volunteers/hexlet-sicp

    Manages OAuth social authentication with Laravel Socialite. An agent skill from hexlet-volunteers/hexlet-sicp.

    114 GitHub starsUsed in 5 repos~1.2k tokens
    Backend & APIsAuto-check passed

  • Add Channel Connect Button

    novuhq/novu

    Build a new channel Connect button (e.g. An agent skill from novuhq/novu.

    40k GitHub stars~1.6k tokensUpdated today
    Backend & APIsAuto-check passed

  • Add OAuth Integration

    rome-os/rome

    Add a new Rome-managed OAuth integration for a third-party service so a user can delegate access by clicking Connect, and Rome can act on the service with the delegated token (the GitHub/Slack model…

    743 GitHub stars~3.6k tokensUpdated today
    Backend & APIsAuto-check passed

  • Feishu Auth Request

    Ninglo/remotelab

    飞书调用缺权限时，区分 Bot 应用权限、用户 OAuth 和资源访问权限；为缺少的 Bot scope 生成单独的权限申请页。适用于 99991672、permissionviolations 或用户要求申请应用权限。

    109 GitHub stars~456 tokensUpdated today
    Backend & APIsAuto-check passed

More from PostHog/posthog

All 254 skills in this repo

  • Authoring Log Alerts

    PostHog/posthog

    Official

    Author useful, low-noise log alerts on services in a PostHog project.

    40k GitHub stars~3k tokensUpdated today
    Auto-check passed

  • Autoresolving PR Conflicts

    PostHog/posthog

    Official

    Operating procedure for the conflict-autoresolver agent: sweep open PostHog/posthog PRs that conflict with master, resolve the trivial conflicts (generated artifacts deterministically, source…

    40k GitHub stars~4.2k tokensUpdated today
    Auto-check passed

  • Diagnosing Stacktrace Symbolication

    PostHog/posthog

    Official

    Help users debug PostHog Error Tracking stack-trace symbolication for any supported platform — JavaScript/TypeScript web, React Native (Hermes), Android (Proguard / R8), or iOS / macOS (dSYM).

    40k GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Exploring Apm Traces

    PostHog/posthog

    Official

    Investigates distributed application performance using PostHog APM (OpenTelemetry span) data via MCP.

    40k GitHub stars~3.5k tokensUpdated today
    Auto-check passed

  • Exploring LLM Traces

    PostHog/posthog

    Official

    Debug and inspect LLM/AI agent traces using PostHog's MCP tools.

    40k GitHub stars~4.4k tokensUpdated today
    Auto-check passed

  • Investigate Metric

    PostHog/posthog

    Official

    Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries.

    40k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Setting Up Support Slack Locally

What does Setting Up Support Slack Locally do?

Connect a real Slack workspace to local PostHog Conversations (the SupportHog Slack app) so Slack messages become support tickets and replies post back. Setting Up Support Slack Locally is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Connect a real Slack workspace to local PostHog Conversations (the SupportHog Slack app) so Slack messages become support tickets and replies post back.

When should I use Setting Up Support Slack Locally?

Setting Up Support Slack Locally fits situations like: the user wants to test the conversations Slack integration locally; hits Support Slack OAuth client ID is not configured; gets a white screen; network error on the OAuth callback.

How do I install Setting Up Support Slack Locally in Claude Code?

Run `npx skills add PostHog/posthog --skill setting-up-support-slack-locally -a claude-code`. Or copy the skill folder (.agents/skills/setting-up-support-slack-locally in PostHog/posthog) into .claude/skills/setting-up-support-slack-locally in your project. Claude Code loads it when a task matches its description.

How do I install Setting Up Support Slack Locally in Codex?

Run `npx skills add PostHog/posthog --skill setting-up-support-slack-locally -a codex`. Or copy the skill folder (.agents/skills/setting-up-support-slack-locally in PostHog/posthog) into .agents/skills/setting-up-support-slack-locally in your project. Codex loads it when a task matches its description.

Can I use Setting Up Support Slack Locally 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 PostHog/posthog --skill setting-up-support-slack-locally -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/setting-up-support-slack-locally, .gemini/skills/setting-up-support-slack-locally, .github/skills/setting-up-support-slack-locally and .opencode/skills/setting-up-support-slack-locally in your project.

What does Setting Up Support Slack Locally need to run?

Going by SKILL.md and its folder, Setting Up Support Slack Locally needs the command-line tools its instructions call (ngrok, cloudflared and curl) and credentials named SUPPORT_SLACK_APP_CLIENT_SECRET and SUPPORT_SLACK_SIGNING_SECRET. Our summary lists: A credential in SUPPORT_SLACK_APP_CLIENT_SECRET; A credential in SUPPORT_SLACK_SIGNING_SECRET.

Does Setting Up Support Slack Locally access the network?

SKILL.md names 1 domain. As links in the text: api.slack.com. This is read from the text; nothing was executed.

Is Setting Up Support Slack Locally safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Setting Up Support Slack Locally use?

Setting Up Support Slack Locally has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Setting Up Support Slack Locally use?

About 2.3k tokens (SKILL.md is roughly 9.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.2k tokens, read only when the agent opens those files.

What are the alternatives to Setting Up Support Slack Locally?

Skills that share tags, products or a category with Setting Up Support Slack Locally: Openloomi Connectors (melandlabs/openloomi, 1k stars), Implementing Zero Trust For SaaS Applications (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Socialite Development (hexlet-volunteers/hexlet-sicp, 114 stars) and Add Channel Connect Button (novuhq/novu, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Setting Up Support Slack Locally?

PostHog (a GitHub organization, an official publisher) maintains it in PostHog/posthog, which has 40,209 GitHub stars. The repository holds 254 skills in this directory. The repository was last updated on October 10, 2026.

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