WeCom Calendar Scheduler
WecomTeam/wecom-cli
Books, views, searches, updates, cancels or checks free/busy time on WeCom (Enterprise WeChat) calendars and meeting rooms, routed away from online-meeting creation.
Recommended repo-engineering guide when adding alerting to a PostHog product or extending the shared alerts platform.
Install Adding Product Alerting
$ npx skills add PostHog/posthog --skill adding-product-alerting -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PostHog/posthog adding-product-alerting --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/adding-product-alerting .claude/skills/adding-product-alerting && rm -rf skills-srcUse ~/.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/
Install the "adding-product-alerting" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/adding-product-alerting into .claude/skills/adding-product-alerting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-product-alerting", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/PostHog/posthog/tree/master/.agents/skills/adding-product-alertingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add PostHog/posthog --skill adding-product-alerting -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PostHog/posthog adding-product-alerting --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/adding-product-alerting .agents/skills/adding-product-alerting && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "adding-product-alerting" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/adding-product-alerting into .agents/skills/adding-product-alerting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-product-alerting", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add PostHog/posthog --skill adding-product-alerting -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PostHog/posthog adding-product-alerting --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/adding-product-alerting .cursor/skills/adding-product-alerting && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "adding-product-alerting" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/adding-product-alerting into .cursor/skills/adding-product-alerting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-product-alerting", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/PostHog/posthog.git --path .agents/skills/adding-product-alerting--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add PostHog/posthog --skill adding-product-alerting -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PostHog/posthog adding-product-alerting --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/adding-product-alerting .gemini/skills/adding-product-alerting && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "adding-product-alerting" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/adding-product-alerting into .gemini/skills/adding-product-alerting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-product-alerting", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install PostHog/posthog adding-product-alertingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add PostHog/posthog --skill adding-product-alerting -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/adding-product-alerting .github/skills/adding-product-alerting && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "adding-product-alerting" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/adding-product-alerting into .github/skills/adding-product-alerting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-product-alerting", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add PostHog/posthog --skill adding-product-alerting -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install PostHog/posthog adding-product-alerting --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/adding-product-alerting .opencode/skills/adding-product-alerting && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "adding-product-alerting" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/adding-product-alerting into .opencode/skills/adding-product-alerting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "adding-product-alerting", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
adding-product-alerting- GitHub stars
- 40k
- Token cost
- ~2.7k tokens
- SKILL.md length
- 1,090 words
- Files
- 5 (incl. references)
- Skills in repo
- 252
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Recommended repo-engineering guide when adding alerting to a PostHog product or extending the shared alerts platform.
- Works in 2 steps: Add platform alerting to a product by… → Extend the alerts platform when a…
- Product alert implementations
- SKILL.md covers Route first, Platform invariants, Review shared changes as one… and Treat alerting as an…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Adding Product Alerting is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Recommended repo-engineering guide when adding alerting to a PostHog product or extending the shared alerts platform. Routes lifecycle state machines, AlertPolicy, destinations, HogFunction dispatch, email, fixed-cadence and calendar scheduling, insight evaluation, the AlertWizard, and shared alert editor components. Use for product alert implementations, shared destination types, lifecycle or scheduling options, advanced alert settings, and platform alert infrastructure. Not for configuring alerts in an existing…
Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/adopting-platform-alerting.md`, `references/architecture.md` and `references/extending-platform-alerting.md`).
It sits in Productivity & Automation, covering Calendar and scheduling. It works with 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
- Product alert implementations
- Shared destination types
- Scheduling options
- Advanced alert settings
Example prompts
- “/adding-product-alerting”
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Add platform alerting to a product by composing the shared lifecycle, destination, delivery, scheduling, email, and frontend primitives.
- Extend the alerts platform when a reusable capability, option, or advanced behavior belongs in shared infrastructure.
What it can do on your machine
Read from SKILL.md and the folder at commit 10f9ad7. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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.
Context cost
Adding Product Alerting loads about 2.7k tokens when it runs, and up to ~13k if it reads all its reference files. Until then it costs about 138 tokens; SKILL.md has 1,090 words of instructions outside code blocks.
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); 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 1,090 words (~2,710 tokens).
“Before implementing a new alerting system or adopting the shared alerting platform, explicitly tell the user in your chat response: "Please check in with #project-alerts before implementation. The shared alerting infrastructure is actively changing, and the team can help avoid…”
- name
- adding-product-alerting
Files
SKILL.md and 4 other files (references) in .agents/skills/adding-product-alerting of PostHog/posthog.
- SKILL.md
- references/adopting-platform-alerting.md
- references/architecture.md
- references/extending-platform-alerting.md
- references/frontend-alerting.md
Open the folder on GitHubat commit 10f9ad7
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
Adding Product Alerting 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Adding Product Alerting this skillPostHog/posthog | 40k | — | ~2.7k | Automated safety check: Pass | Custom licence | |
| WeCom Calendar SchedulerWecomTeam/wecom-cli | 3.2k | 1 repos | ~3.7k | Automated safety check: Pass | MIT | |
| Telemetry AnalyticsOpenHands/OpenHands | 90k | — | ~305 | Automated safety check: Pass | MIT | |
| Zeleremorses/zele | 299 | — | ~1.5k | Automated safety check: Pass | None | |
| WeCom Meeting ManagerWecomTeam/wecom-cli | 3.2k | 1 repos | ~4.6k | Automated safety check: Pass | MIT | |
| Temps Best Practicesgotempsh/temps | 826 | — | ~2.9k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Telemetry Analytics
OpenHands/OpenHands
This skill should be used when the user asks to "add tracking", "add a PostHog event", "change telemetry consent", "instrument onboarding", "debug analytics", or changes telemetry.ts…
Zele
remorses/zele
zele is a multi-account email and calendar CLI for Gmail, IMAP/SMTP (Fastmail, Outlook, any provider), and Google Calendar.
WeCom Meeting Manager
WecomTeam/wecom-cli
Creates, finds, updates and cancels WeCom online meetings from the terminal, reads their details, summaries and transcripts, and keeps meetings apart from calendar events.
Temps Best Practices
gotempsh/temps
Best-practices reference for preparing and instrumenting applications on Temps.
Fantastical Calendar
twhsi/skills
Turns scheduling requests into Fantastical events or reminders on macOS, previewing the parsed item in the app first and adding it only when you confirm.
More from PostHog/posthog
All 252 skills in this repo- Official
Authoring Log Alerts
PostHog/posthog
Author useful, low-noise log alerts on services in a PostHog project.
- Official
Autoresolving PR Conflicts
PostHog/posthog
Operating procedure for the conflict-autoresolver agent: sweep open PostHog/posthog PRs that conflict with master, resolve the trivial conflicts (generated artifacts deterministically, source…
- Official
Diagnosing Stacktrace Symbolication
PostHog/posthog
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).
- Official
Exploring Apm Traces
PostHog/posthog
Investigates distributed application performance using PostHog APM (OpenTelemetry span) data via MCP.
- Official
Exploring LLM Traces
PostHog/posthog
Debug and inspect LLM/AI agent traces using PostHog's MCP tools.
- Official
Investigate Metric
PostHog/posthog
Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries.
Related
Works with
Categories
Questions about Adding Product Alerting
What does Adding Product Alerting do?
Recommended repo-engineering guide when adding alerting to a PostHog product or extending the shared alerts platform. Adding Product Alerting is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Recommended repo-engineering guide when adding alerting to a PostHog product or extending the shared alerts platform.
When should I use Adding Product Alerting?
Adding Product Alerting fits situations like: product alert implementations; shared destination types; scheduling options; advanced alert settings.
How do I install Adding Product Alerting in Claude Code?
Run `npx skills add PostHog/posthog --skill adding-product-alerting -a claude-code`. Or copy the skill folder (.agents/skills/adding-product-alerting in PostHog/posthog) into .claude/skills/adding-product-alerting in your project. Claude Code loads it when a task matches its description.
How do I install Adding Product Alerting in Codex?
Run `npx skills add PostHog/posthog --skill adding-product-alerting -a codex`. Or copy the skill folder (.agents/skills/adding-product-alerting in PostHog/posthog) into .agents/skills/adding-product-alerting in your project. Codex loads it when a task matches its description.
Can I use Adding Product Alerting 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 adding-product-alerting -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/adding-product-alerting, .gemini/skills/adding-product-alerting, .github/skills/adding-product-alerting and .opencode/skills/adding-product-alerting in your project.
What does Adding Product Alerting need to run?
SKILL.md names no scripts, command-line tools or credentials: Adding Product Alerting is instructions for the agent only.
Does Adding Product Alerting access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Adding Product Alerting 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. Review the folder before installing.
What licence does Adding Product Alerting use?
Adding Product Alerting 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 Adding Product Alerting use?
About 2.7k tokens (SKILL.md is roughly 11k 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 11k tokens, read only when the agent opens those files.
What are the alternatives to Adding Product Alerting?
Skills that share tags, products or a category with Adding Product Alerting: WeCom Calendar Scheduler (WecomTeam/wecom-cli, 3.2k stars), Telemetry Analytics (OpenHands/OpenHands, 90k stars), Zele (remorses/zele, 299 stars) and WeCom Meeting Manager (WecomTeam/wecom-cli, 3.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Adding Product Alerting?
PostHog (a GitHub organization, an official publisher) maintains it in PostHog/posthog, which has 40,182 GitHub stars. The repository holds 252 skills in this directory. The repository was last updated on October 8, 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.