wework-project-space

Solid

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

AI & Automation 848 stars 139 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 86/100

Stars 20%
98
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
50
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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.

Details

Author
wecode-ai
Repository
wecode-ai/Wegent
Created
8 months ago
Last Updated
today
Language
TypeScript
License
Apache-2.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category