Repository navigation
feat: add wework prompt - #359
Conversation
📝 WalkthroughWalkthroughThis PR adds a new public Wegent-WeWork integration suite to the backend initialization resources, comprising a Ghost resource with extensive system prompts and capabilities, a corresponding Bot resource, and a Team resource. The same set of resources appears to be duplicated later in the file. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Fix all issues with AI agents
In `@backend/init_data/02-public-resources.yaml`:
- Around line 663-666: The manifest's spec.skills list currently contains only
"mermaid-diagram", "browser", and "document" but the prompt/summary advertises
additional tools ("xlsx", "pptx", "docx", "pdf", "skill-creator"); update the
CRD to keep them in sync by either adding the missing skill names to spec.skills
(add "xlsx", "pptx", "docx", "pdf", "skill-creator") so the actual exposed tools
match the prompt, or remove those tool names from the prompt/summary so it
matches the existing spec.skills; locate and update the spec.skills array (and
the prompt/summary text that lists available skills) to ensure both lists are
identical.
- Line 1352: Update the Team resource's description field in the
02-public-resources.yaml entry that currently reads like a NotebookLM agent;
replace the NotebookLM-specific wording with a concise Wework-aligned
description that reflects the Wework prompt and use-case (e.g.,
workspace-focused, company/office-related assistant) so the user-visible
metadata correctly represents this Team. Locate the "description:" value for the
Team entry and edit it to remove references to NotebookLM and instead summarize
the Wework intent and scope.
| skills: | ||
| - mermaid-diagram | ||
| - browser | ||
| - document |
There was a problem hiding this comment.
Align declared skills with the prompt’s advertised capabilities.
Line 663-666 only declares mermaid-diagram, browser, document, but Line 1275-1289 claims xlsx, pptx, docx, pdf, and skill-creator are available. If those skills aren’t actually exposed, users will hit missing-tool behavior. Either add the missing skills to spec.skills or trim the summary to match.
🔧 Proposed fix (add skills to match the prompt)
skills:
- mermaid-diagram
- browser
- document
+ - xlsx
+ - pptx
+ - docx
+ - pdf
+ - skill-creatorAlso applies to: 1272-1291
🤖 Prompt for AI Agents
In `@backend/init_data/02-public-resources.yaml` around lines 663 - 666, The
manifest's spec.skills list currently contains only "mermaid-diagram",
"browser", and "document" but the prompt/summary advertises additional tools
("xlsx", "pptx", "docx", "pdf", "skill-creator"); update the CRD to keep them in
sync by either adding the missing skill names to spec.skills (add "xlsx",
"pptx", "docx", "pdf", "skill-creator") so the actual exposed tools match the
prompt, or remove those tool names from the prompt/summary so it matches the
existing spec.skills; locate and update the spec.skills array (and the
prompt/summary text that lists available skills) to ensure both lists are
identical.
| displayName: Wegent Wework | ||
| namespace: default | ||
| spec: | ||
| description: A research and writing assistant inspired by Google NotebookLM, focused on material-centric, evidence-first analysis. |
There was a problem hiding this comment.
Update the Team description to match Wework (not NotebookLM).
Line 1352 reads like a copy of the NotebookLM agent description, which doesn’t match the Wework prompt. This is user‑visible metadata and can confuse selection in UIs.
✏️ Proposed fix
- description: A research and writing assistant inspired by Google NotebookLM, focused on material-centric, evidence-first analysis.
+ description: A versatile Wework assistant for document creation, analysis, research, and automation in the desktop app.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| description: A research and writing assistant inspired by Google NotebookLM, focused on material-centric, evidence-first analysis. | |
| description: A versatile Wework assistant for document creation, analysis, research, and automation in the desktop app. |
🤖 Prompt for AI Agents
In `@backend/init_data/02-public-resources.yaml` at line 1352, Update the Team
resource's description field in the 02-public-resources.yaml entry that
currently reads like a NotebookLM agent; replace the NotebookLM-specific wording
with a concise Wework-aligned description that reflects the Wework prompt and
use-case (e.g., workspace-focused, company/office-related assistant) so the
user-visible metadata correctly represents this Team. Locate the "description:"
value for the Team entry and edit it to remove references to NotebookLM and
instead summarize the Wework intent and scope.
Summary by CodeRabbit
New Features
Bug Fixes
✏️ Tip: You can customize this high-level summary in your review settings.