CtrlK
BlogDocsLog inGet started
Tessl Logo

setting-up-support-slack-locally

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 SUPPORT_SLACK_APP_CLIENT_ID / a tunnel for supporthog Slack events. Covers the Slack app + scopes, the SUPPORT_SLACK_* dynamic settings, and the key split: localhost for OAuth and the UI, a public tunnel only for inbound events.

76

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tightly sequenced, executable setup guide with concrete commands and explicit verification steps, and it correctly pushes failure-mode detail into a well-signaled single reference file. Its only soft spot is density/length, leaving a little room to trim.

Suggestions

Tighten the intro and endpoints prose where the localhost/tunnel split is restated; the table and Step 3 already convey it, so a small trim would lift conciseness toward the lean anchor.

Consider collapsing the duplicated constance-override note (mentioned in Step 1 and again via the reference) so the body states it once and links for the rest.

The events list and scopes list could be referenced from the troubleshooting file if token budget tightens, though keeping them inline is justified for actionability.

DimensionReasoningScore

Conciseness

High-signal and assumes Claude knows the codebase, with no padding about what Slack/PostHog is, but the body is dense and long enough that minor trims are possible; sits just below the lean/every-token-earns-its-place anchor.

4 / 5

Actionability

Copy-paste ready throughout: an .env.local block, ngrok/cloudflared commands with exact flags, a curl preflight check, and enumerated bot scopes — concrete executable guidance covering the common cases.

5 / 5

Workflow Clarity

A clear four-step sequence with explicit validation checkpoints — the _preflight curl, the url_verification challenge, reinstall-after-scope-change — plus an HMAC replay feedback loop in the reference, with no destructive/batch cap applying to this config task.

5 / 5

Progressive Disclosure

SKILL.md stays a focused overview and defers failure modes to references/troubleshooting.md (a real, one-level-deep file) signaled clearly twice, with content appropriately split and easy to navigate.

5 / 5

Total

19

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, third-person, and rich with verbatim trigger phrases tied to real error strings users would encounter. It clearly answers both what the skill does and when to use it, and is tightly scoped to the SupportHog/Conversations Slack variant.

DimensionReasoningScore

Specificity

Multiple concrete actions are named — "Connect a real Slack workspace", "messages become support tickets and replies post back", "set SUPPORT_SLACK_APP_CLIENT_ID / a tunnel" — plus the precise localhost/tunnel split, matching the comprehensive-coverage anchor.

5 / 5

Completeness

An explicit "Use when..." clause with concrete triggers pairs with a clear statement of what it does (connect a Slack workspace so messages become tickets and replies post back), matching the what-and-when anchor.

5 / 5

Trigger Term Quality

Quotes verbatim user-facing phrases as triggers — "Support Slack OAuth client ID is not configured", "white screen", "Network error", "set SUPPORT_SLACK_APP_CLIENT_ID" — exactly what a user would say, hitting the comprehensive natural-terms anchor.

5 / 5

Distinctiveness Conflict Risk

Niche-scoped to the Conversations/SupportHog Slack app and SUPPORT_SLACK_* settings, and even distinguishes itself from the PostHog Desktop Slack app, giving it a clear niche with minimal conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository
PostHog/posthog
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.