# Wework Project Space

> Read or update the Wework project space, current Issue, attachments, deliveries, members, or board items when a Wework project or Issue context is active.

- Skill: `wecode-ai/wework-project-space` (Agent Skill)
- Install (CLI): `npx skillmds@latest add wecode-ai/wework-project-space`
- Raw SKILL.md: https://api.skillmd.com/api/skills/wecode-ai/wework-project-space/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: wecode-ai (https://skillmd.com/u/wecode-ai)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/wecode-ai/wework-project-space

---


# Wework project space

Use the `wework_space` MCP tools for project-space work.

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

Human assignee changes notify the new owner by default. Do not send a duplicate notification. For user-requested alerts or automation conditions, use `send_notification`; omit `recipient_user_id` to notify the authenticated user.