Skip to content

Add community skill: Customer support reply drafter - #18

Merged
andrewm4894 merged 1 commit into
mainfrom
posthog/customer-support-reply-drafter
Nov 19, 2026
Merged

andrewm4894 merged 1 commit into
mainfrom
posthog/customer-support-reply-drafter

Conversation

@posthog

@posthog posthog Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Why

Support teams running their tickets through PostHog keep asking agents to turn a finished investigation into a customer reply, and the community catalog had no skill for that. This publishes a general-purpose version of a heavily used internal support-reply skill.

What

New skill skills/customer-support-reply-drafter/ (no install variables, allowed_tools: [conversations], trust_tier: community):

  • SKILL.md: thin index with the rules needed on every draft: customer-first structure in the customer's order, verified causes only (hypotheses become questions), link docs and the customer's own resources, no commitments on the sender's behalf, private context stays out, delivery format.
  • references/final-pass.md: the succinctness pass, now bundled and self-contained instead of fetched from an internal registry. Reads the thread with conversations-tickets-messages-retrieve or a pasted thread, uses a tool-less subagent for the cold read when one is available, and falls back to a self trace.
  • references/writing-rules.md, references/reviewing.md, references/templates.md: accuracy, change and roadmap wording, naming and linking, GitHub subscribe-not-notify, formatting, banned phrases, review scope, and feature-request templates.

Generalized from the source: removed the internal final-pass dependency, internal tooling and support-desk names, impersonation steps, internal skill cross-references, and PostHog-only policy and URLs (the roadmap link is now a placeholder the team fills in).

For reviewers: the source author is credited in plain text only (Steven Shults). author_handle is left empty because I could not confirm a GitHub handle. Please also decide whether the remaining PostHog worked example in the final pass (identify before capture) should stay.

Validation

  • python scripts/build_registry.py builds 10 skills, including the new entry with 4 bundled files. registry.json was restored and is not part of this PR.
  • python scripts/safety_scan.py prints Safety scan passed.

Created with PostHog Desktop from an inbox report

🤖 Generated with Claude Code

Origin

  • Scout: a custom scout
  • First signal: 2026-11-17
  • Inbox report: open
  • Task started by: a person, from the inbox

Drafts, revises, or reviews customer-facing support replies once an investigation has concluded. Generalized from an internal support skill: the internal final-pass dependency is replaced by a bundled, self-contained final pass, and internal tooling, channels, and PostHog-only policy are removed.

Generated-By: PostHog Desktop
Task-Id: 9dbf3521-89ae-4ffe-9996-3f36b82c07f2
@posthog posthog Bot added the self-driving label Nov 17, 2026
@posthog
posthog Bot marked this pull request as ready for review November 17, 2026 20:02
@posthog
posthog Bot requested a review from andrewm4894 November 17, 2026 20:02
@andrewm4894

Copy link
Copy Markdown
Member

@codex review

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-17T20:19:54.690499Z ae40be6 Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ae40be6f13

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +144 to +146
> Your events are arriving fine, but they're landing under a different distinct_id than the one
> you're querying. Your `identify()` call happens after your first `capture()`, so those early
> events stay on the anonymous profile.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Correct the identity-merging behavior in the worked example

For the normal frontend SDK flow, calling identify() after an anonymous capture() does not leave those earlier events on a separate anonymous profile. PostHog's identification documentation explains that identification merges the anonymous and identified people and links their previous event history. Both versions of this example therefore teach an unsupported diagnosis and present reordering the calls as its fix. Since agents must reread this file before every delivery, replace the example with a technically valid scenario rather than reinforcing incorrect customer-facing advice.

Useful? React with 👍 / 👎.

@andrewm4894
andrewm4894 merged commit ed91086 into main Nov 19, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant