New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Wework Plugin Creator

by wecode-ai in wecode-ai/Wegent

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

Apache-2.0Auto-check passedAgent Workflows

Install Wework Plugin Creator

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

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

GitHub CLI
$ gh skill install wecode-ai/Wegent wework-plugin-creator --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/sdk/plugin-creator .claude/skills/wework-plugin-creator && 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-plugin-creator
GitHub stars
868
Token cost
~990 tokens
SKILL.md length
456 words
Files
5 (incl. scripts, references)
Skills in repo
8
Repo updated
First seen
Licence
Apache-2.0

At a glance

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

  • Works in 5 steps: Resolve the source location from the… → For native account authentication, use… → Implement the requested… → …
  • Wework Plugin Creator tasks
  • SKILL.md covers Choose the authentication path, Create and iterate and Validate
  • Runs Python scripts from its folder; calls uv

What it does

Wework Plugin Creator is an agent skill from wecode-ai/Wegent. Create or extend Wework plugins, including native Connector login and account authentication for reuse on cloud devices. Use for Wework Plugin Creator tasks; preserve the selected Task workspace or managed personal marketplace.

Its SKILL.md is about 990 tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts and reference files (for example `references/account-auth.en.md`, `references/account-auth.md` and `scripts/validate_wework_plugin.py`).

It sits in Agent Workflows, covering Hooks and plugins. 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

  • Wework Plugin Creator tasks
  • Preserve the selected Task workspace
  • Managed personal marketplace

Example prompts

  • “/wework-plugin-creator”

Requirements

  • Python 3

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Resolve the source location from the task environment. For DEVICE_TYPE=cloud,
  2. For native account authentication, use scripts/auth-sdk/tool.py scaffold as
  3. Implement the requested skills/MCP/business commands. Keep the existing native
  4. Run the Wework validator below, then test provider behavior with synthetic
  5. Locally, keep both managed marketplace manifests consistent and install/update

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

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • uv

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.

    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 Plugin Creator loads about 990 tokens when it runs, and up to ~3.1k if it reads all its reference files. Until then it costs about 62 tokens; SKILL.md has 456 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
~990
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.1k

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); the scripts in this folder are not scanned.

SKILL.md

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

Download SKILL.mdSave it as .claude/skills/wework-plugin-creator/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
wework-plugin-creator
description
Create or extend Wework plugins, including native Connector login and account authentication for reuse on cloud devices. Use for Wework Plugin Creator tasks; preserve the selected Task workspace or managed personal marketplace.

Wework Plugin Creator

Use the installed Codex plugin-creator skill for common plugin structure, metadata, skills, and marketplace helpers. Apply the Wework workflow below to storage, authentication, and validation. This skill and its authentication SDK are shipped by the Executor and work without a Wegent source checkout.

Choose the authentication path

Before generating a plugin, establish how its business commands authenticate:

  • Public data or a skill without authenticated commands: do not add Connectors.
  • An existing platform-managed remote Connector/MCP: reuse that connection; do not export platform credentials or wrap it in a local account adapter.
  • A plugin-owned local CLI/session, password, API token, or OAuth authorization that must work on cloud devices: read references/account-auth.md, generate the adapter using the bundled SDK, and route business calls through that SDK.

connectors and localAuth alone do not enable account synchronization. Each supported local credential flow needs connectors[].accountAuth, a working provider implementation, and a delegated business entrypoint. If the provider cannot safely support this, explain the concrete limitation; do not advertise cloud authentication support or invent credential copying.

Create and iterate

  1. Resolve the source location from the task environment. For DEVICE_TYPE=cloud, use $WEGENT_TASK_WORKSPACE/plugins/<plugin-name>. Otherwise resolve the registered wework-personal marketplace and use its existing plugin directory. Do not use upstream defaults under ~/plugins or ~/.agents.
  2. For native account authentication, use scripts/auth-sdk/tool.py scaffold as described in the reference. For other plugins, use the upstream scaffold with the explicit destination. Preserve existing source and manifest fields when extending a plugin; scaffold into a temporary directory to obtain templates.
  3. Implement the requested skills/MCP/business commands. Keep the existing native Connector login entry; authentication setup remains a host operation, and cloud tasks must never request passwords, tokens, or exported credentials.
  4. Run the Wework validator below, then test provider behavior with synthetic credentials and the unpacked distributable. A scaffold passing validation does not mean its provider is implemented or authenticated.
  5. Locally, keep both managed marketplace manifests consistent and install/update through the existing managed marketplace flow. In cloud tasks, leave the source in the Task workspace and run plugin-workspace describe with the Executor. Return the complete [WEGENT_PLUGIN_RESULT] line verbatim. Publish only when requested, using the same source and the host's publication workflow.
Show full SKILL.md (94 more words)Show less

Validate

Run from this skill directory (use absolute script paths from another directory):

bash
uv run --no-project --with pyyaml python scripts/validate_wework_plugin.py <plugin-root>

The validator reuses the installed upstream validator for standard manifest fields, assets, and skills, and separately validates Wework Connectors. It does not alter the plugin manifest. Do not run the upstream validator directly on a Wework manifest containing connectors, or remove that declaration to make it pass. For a Python adapter, also check the bundled SDK:

bash
uv run --no-project python scripts/auth-sdk/tool.py vendor <plugin-root> --check

Report structural validation, provider tests, local login/synchronization, and real cloud business execution separately. Do not claim the latter from generated code or synthetic tests alone.

© 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

SKILL.md and 4 other files (scripts, references) in sdk/plugin-creator of wecode-ai/Wegent.

  • SKILL.md
  • references/account-auth.en.md
  • references/account-auth.md
  • scripts/validate_wework_plugin.py
  • tests/test_validation.py

Open the folder on GitHubat commit 428f207

Compare with similar skills

Wework Plugin Creator 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 Plugin Creator compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Wework Plugin Creator this skillwecode-ai/Wegent868—~990Automated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k11 repos~4.1kAutomated safety check: NotesApache-2.0
Claude Code Agent Developmentanthropics/claude-plugins-official38k8 repos~2.8kAutomated safety check: PassApache-2.0
Claude Code Skill Developer Guidediet103/claude-code-infrastructure-showcase10k11 repos~3.5kAutomated safety check: PassMIT
Plugin Settings Patternanthropics/claude-plugins-official38k7 repos~3kAutomated safety check: PassApache-2.0
MCP Integration for Pluginsanthropics/claude-plugins-official38k11 repos~3.1kAutomated safety check: PassApache-2.0

Similar skills

  • 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

  • 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

  • Claude Code Skill Developer Guide

    diet103/claude-code-infrastructure-showcase

    A guide to creating and managing Claude Code skills with auto-activation: skill-rules.json triggers, hooks, enforcement levels, YAML frontmatter and progressive disclosure.

    10k GitHub starsUsed in 11 repos~3.5k tokens
    Agent WorkflowsAuto-check passed

  • Plugin Settings Pattern

    anthropics/claude-plugins-official

    Official

    Shows how Claude Code plugins keep per-project settings and state in .claude/plugin-name.local.md files with YAML frontmatter and a markdown body.

    38k GitHub starsUsed in 7 repos~3k tokens
    Agent WorkflowsAuto-check passed

  • MCP Integration for Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.

    38k GitHub starsUsed in 11 repos~3.1k tokens
    Agent WorkflowsAuto-check passed

  • Claude Code Command Development

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code slash commands: Markdown files with YAML frontmatter, arguments, file references, bash context and interactive prompts.

    38k GitHub starsUsed in 10 repos~4.8k tokens
    Agent WorkflowsAuto-check passed

More from wecode-ai/Wegent

All 8 skills in this repo

  • 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 2 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 2 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 2 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 2 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 2 days ago
    Auto-check: notes

  • Wework Notifications

    wecode-ai/Wegent

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

    868 GitHub stars~604 tokensUpdated 2 days ago
    Auto-check passed

Categories

Questions about Wework Plugin Creator

What does Wework Plugin Creator do?

Create or extend Wework plugins, including native Connector login and account authentication for reuse on cloud devices. Wework Plugin Creator is an agent skill from wecode-ai/Wegent. Create or extend Wework plugins, including native Connector login and account authentication for reuse on cloud devices.

When should I use Wework Plugin Creator?

Wework Plugin Creator fits situations like: wework Plugin Creator tasks; preserve the selected Task workspace; managed personal marketplace.

How do I install Wework Plugin Creator in Claude Code?

Run `npx skills add wecode-ai/Wegent --skill wework-plugin-creator -a claude-code`. Or copy the skill folder (sdk/plugin-creator in wecode-ai/Wegent) into .claude/skills/wework-plugin-creator in your project. Claude Code loads it when a task matches its description.

How do I install Wework Plugin Creator in Codex?

Run `npx skills add wecode-ai/Wegent --skill wework-plugin-creator -a codex`. Or copy the skill folder (sdk/plugin-creator in wecode-ai/Wegent) into .agents/skills/wework-plugin-creator in your project. Codex loads it when a task matches its description.

Can I use Wework Plugin Creator 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-plugin-creator -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-plugin-creator, .gemini/skills/wework-plugin-creator, .github/skills/wework-plugin-creator and .opencode/skills/wework-plugin-creator in your project.

What does Wework Plugin Creator need to run?

Going by SKILL.md and its folder, Wework Plugin Creator needs Python for the scripts in its folder and the command-line tools its instructions call (uv). Our summary lists: Python 3.

Does Wework Plugin Creator access the network?

SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Wework Plugin Creator 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Wework Plugin Creator use?

Wework Plugin Creator 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 Plugin Creator use?

About 990 tokens (SKILL.md is roughly 4k 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 2.1k tokens, read only when the agent opens those files.

What are the alternatives to Wework Plugin Creator?

Skills that share tags, products or a category with Wework Plugin Creator: Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Claude Code Agent Development (anthropics/claude-plugins-official, 38k stars), Claude Code Skill Developer Guide (diet103/claude-code-infrastructure-showcase, 10k stars) and Plugin Settings Pattern (anthropics/claude-plugins-official, 38k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Wework Plugin Creator?

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.