Agent skill

Wework Notifications

by wecode-ai in wecode-ai/Wegent

Send Wework in-app notifications when a user requests an alert, greeting, or automation notification.

Apache-2.0Auto-check passedAgent Workflows

Install Wework Notifications

skills CLI
$ npx skills add wecode-ai/Wegent --skill wework-notifications -a claude-code

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

GitHub CLI
$ gh skill install wecode-ai/Wegent wework-notifications --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/wecode-ai/Wegent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/wework/resources/bundled-plugins/wework-personal/plugins/wework-space/skills/wework-notifications .claude/skills/wework-notifications && 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
wework-notifications
GitHub stars
868
Token cost
~604 tokens
SKILL.md length
292 words
Files
1
Skills in repo
8
Repo updated
First seen
Licence
Apache-2.0

At a glance

Send Wework in-app notifications when a user requests an alert, greeting, or automation notification.

  • Agent Workflows work in your project
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Wework Notifications is an agent skill from wecode-ai/Wegent. 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.

Its SKILL.md is about 600 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows. The repository describes itself as: Plan, build, and deliver with an open-source, self-hostable AI workspace for coding, collaboration, and automation. The licence is Apache-2.0.

When your agent uses it

  • Agent Workflows work in your project

Example prompts

  • “/wework-notifications”

What it can do on your machine

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

Wework Notifications loads about 604 tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 292 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~62
When it runs · the whole SKILL.md, loaded when a task matches
~604

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

The full file from wecode-ai/Wegent at commit 428f207, republished under its Apache-2.0 licence (© wecode-ai). 292 words, ~604 tokens.

Download SKILL.mdSave it as .claude/skills/wework-notifications/SKILL.md (or your agent's skills folder).
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.

© wecode-ai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in wework/resources/bundled-plugins/wework-personal/plugins/wework-space/skills/wework-notifications of wecode-ai/Wegent.

Open the folder on GitHubat commit 428f207

Compare with similar skills

Wework Notifications 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.

Wework Notifications compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Wework Notifications this skillwecode-ai/Wegent868—~604Automated safety check: PassApache-2.0
MCP Server Builderanthropics/skills180k64 repos~2.3kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k11 repos~4.1kAutomated safety check: NotesApache-2.0
Using Superpowersfarm-fe/farm5.6k35 repos~1.4kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers296k2 repos~5.1kAutomated safety check: PassMIT
Claude Code Agent Developmentanthropics/claude-plugins-official38k8 repos~2.8kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 64 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    38k GitHub starsUsed in 11 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes
  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 35 repos~1.4k tokens
    Agent WorkflowsAuto-check passed
  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    296k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 8 repos~2.8k tokens
    Agent WorkflowsAuto-check passed
  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    795 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed

More from wecode-ai/Wegent

All 8 skills in this repo
  • Wework Plugin Creator

    wecode-ai/Wegent

    Create or extend Wework plugins, including native Connector login and account authentication for reuse on cloud devices.

    868 GitHub stars~990 tokensUpdated 3 days ago
    Auto-check passed
  • Develop Wework Plugin

    wecode-ai/Wegent

    Create, extend, and debug Wework Core DSH plugins and their optional nested Codex plugins.

    868 GitHub stars~3.5k tokensUpdated 3 days ago
    Auto-check passed
  • Interactive

    wecode-ai/Wegent

    Ask the user questions or present choices via an interactive form.

    868 GitHub stars~1.4k tokensUpdated 3 days ago
    Auto-check passed
  • Subscription Manager

    wecode-ai/Wegent

    Create and manage scheduled subscription tasks. An agent skill from wecode-ai/Wegent.

    868 GitHub stars~1.6k tokensUpdated 3 days ago
    Auto-check passed
  • Browser

    wecode-ai/Wegent

    Complete real user web tasks end-to-end via browser-tool, navigate, interact, wait for page state, extract results, and provide evidence when needed.

    868 GitHub stars~1k tokensUpdated 3 days ago
    Auto-check passed
  • Create Smart App

    wecode-ai/Wegent

    Create or update a Wework Smart app based on DeepSeek Harness, including environment preparation, DSH plugin discovery, composition, built-in-browser verification, packaging, and local installation…

    868 GitHub stars~927 tokensUpdated 3 days ago
    Auto-check: notes

Categories

Questions about Wework Notifications

What does Wework Notifications do?

Send Wework in-app notifications when a user requests an alert, greeting, or automation notification. Wework Notifications is an agent skill from wecode-ai/Wegent. Send Wework in-app notifications when a user requests an alert, greeting, or automation notification.

When should I use Wework Notifications?

Wework Notifications fits situations like: agent Workflows work in your project.

How do I install Wework Notifications in Claude Code?

Run `npx skills add wecode-ai/Wegent --skill wework-notifications -a claude-code`. Or copy the skill folder (wework/resources/bundled-plugins/wework-personal/plugins/wework-space/skills/wework-notifications in wecode-ai/Wegent) into .claude/skills/wework-notifications in your project. Claude Code loads it when a task matches its description.

How do I install Wework Notifications in Codex?

Run `npx skills add wecode-ai/Wegent --skill wework-notifications -a codex`. Or copy the skill folder (wework/resources/bundled-plugins/wework-personal/plugins/wework-space/skills/wework-notifications in wecode-ai/Wegent) into .agents/skills/wework-notifications in your project. Codex loads it when a task matches its description.

Can I use Wework Notifications 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 wecode-ai/Wegent --skill wework-notifications -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/wework-notifications, .gemini/skills/wework-notifications, .github/skills/wework-notifications and .opencode/skills/wework-notifications in your project.

What does Wework Notifications need to run?

SKILL.md names no scripts, command-line tools or credentials: Wework Notifications is instructions for the agent only.

Does Wework Notifications 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 Wework Notifications 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 Wework Notifications use?

Wework Notifications is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Wework Notifications use?

About 604 tokens (SKILL.md is roughly 2.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Wework Notifications?

Skills that share tags, products or a category with Wework Notifications: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 296k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Wework Notifications?

wecode-ai (a GitHub organization) maintains it in wecode-ai/Wegent, which has 868 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 5, 2026.

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