Wework Project Space

by wecode-ai

Wework Project Space is an Automation skill for Claude Code, published by wecode-ai in Wegent.

712 stars125 forkson wecode-ai/WegentAdded 2026/08/23Repository updated 2026/08/23

View source on GitHub Download repo ZIP

agentaichatbotclaude-codecodexllmwework

Install in seconds

Install Wework Project Space

Copy Wework Project Space into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/wecode-ai/Wegent/tree/main/wework/src-tauri/bundled-plugins/wework-personal/plugins/wework-space/skills/wework-project-space ~/.claude/skills/wework-project-space

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/wecode-ai/Wegent.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: wework/src-tauri/bundled-plugins/wework-personal/plugins/wework-space/skills/wework-project-space/SKILL.md in wecode-ai/Wegent
Installs to: ~/.claude/skills/wework-project-space
Collection: One of 18 skills cataloged from this repository
Category: Automation — 1523 skills

What Wework Project Space does

Wework Project Space reads or updates the active Wework project space, current Issue, attachments, deliveries, members, and board items. Use it when a Wework project or Issue context is already active.

Wework Project Space is cataloged under Automation on DirSkills. Wework Project Space comes from a repository tagged agent, ai, chatbot, claude-code and codex.

Documentation

README

From the original repository

Wework project space

Use the wework_space MCP tools for project-space work.

Call get_current_context before answering questions about the current Issue.
Call get_board_item with that context before interpreting the Issue description.
Use list_item_attachments and read_item_attachment to inspect Issue attachments.
Use the current context instead of asking the user to repeat a project or Issue identifier.
Do not probe MCP resources, use Shell or curl, scrape the browser, or parse wegent:// attachment URLs.
Never substitute Git or provider APIs when wework_space reports an offline, authorization, or capability error.
Do not claim Issue content is unavailable until the matching wework_space call returns an error.

Frequently asked about Wework Project Space

What else does wecode-ai publish alongside Wework Project Space?
Wework Project Space is one of 18 skills that DirSkills catalogs from wecode-ai/Wegent, the repository it ships in. Its siblings there include Browser Control, Conversation To Prompt and Create Smart App. Each one is a separate skill with its own page in this directory, installs the same way Wework Project Space does, and is maintained by wecode-ai in that same repository. The rest of the collection is listed on the wecode-ai/Wegent page.
How does Wework Project Space compare to other Automation skills?
Wework Project Space ranks #1061 by stars among the 1523 Automation skills in this catalog. The most-starred ones next to it are Autonomous Loops, Autonomous Agent Harness and Automation Audit Ops. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Wework Project Space against them. Open each page to compare what they document and how they install.