Skip to content
Back to skills

Wework Notifications

ASecurity

Send Wework in-app notifications when a user requests an alert, greeting, or automation notification. Works in ordinary conversations without a project or board, with optional project links and delivery to connected IM sessions.

  • 866 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 20, 2026
ai-agentsshellbackend

Works with

  • cli

Security analysis

A100/100

Scanned September 20, 2026

npx -y skills add wecode-ai/Wegent --skill wework-notifications --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Wework Notifications?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Wework Notifications
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/wecode-ai-wework-notifications/badge)](https://www.skillsdirectory.com/skills/wecode-ai-wework-notifications)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: wework-notifications
description: Send Wework in-app notifications when a user requests an alert, greeting, or automation notification. Works in ordinary conversations without a project or board, with optional project links and delivery to connected IM sessions.
---

# Wework notifications

Use `wework_notifications.send_notification` to create a persistent user notification. It also attempts delivery to the recipient's connected IM sessions. An authenticated Backend connection is required; a project or board is not required to notify yourself.

- For an ordinary request such as “给我发个通知,说你好”, call `send_notification` with a concise title and `body: "你好"`. Do not require a project, create a board, or search for an Issue first.
- `space_id` and `item_id` are optional source context. Backend project conversations can use their bound context; ordinary and local-project conversations can send without it. Supply source IDs only when the notification relates to that accessible Backend project or Issue.
- For “notify me”, omit `recipient_user_id`; the tool uses the authenticated user. For another recipient, resolve their ID through `get_assignment_candidates` and use a member of the same project.
- Supply a concise `title` and `body` describing what happened and any requested action. Use optional `url` for the requested click destination independently of source context. For “给我发个你好的通知,然后点击打开看板页面”, send `title: "你好", body: "你好", url: "wework://boards"`. The page opens only when the notification is clicked; do not call `browser open` as a substitute. Other supported destinations are `wework://boards/{projectId}`, `wework://boards/{projectId}/issues/{encodedItemId}`, and `wework://tasks/{encodedDeviceId}/{encodedTaskId}`; use known identifiers and URL-encode each segment. Without `url`, a source link is generated if supplied; otherwise the notification has no click destination.
- An automation instruction such as “if the review fails, notify me in Wework” authorizes sending when that condition occurs. Do not send unrelated notifications.
- Assigning a board Issue to a different human automatically creates a notification by default. Do not send a second notification for the same assignment. Honor an explicit request not to notify.
- Report success only when the tool returns a saved notification. On an error, report it; do not substitute shell commands or external IM tools.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.