Read or update the Wework project space, current Issue, attachments, deliveries, members, or board items when a Wework project or Issue context is active.
Scanned 8/31/2026
Install to Claude Code
npx -y skills add wecode-ai/Wegent --skill wework-project-space --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Wework Project Space?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/wecode-ai-wework-project-space)More formats (shields.io, HTML) on the badges page.
---
name: wework-project-space
description: Read or update the Wework project space, current Issue, attachments, deliveries, members, or board items when a Wework project or Issue context is active.
---
# 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.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...