Docker-build-backed session fails to start when attaching a Team Marketplace skill in the first message.
Steps to Reproduce
Create an environment from github repo based on a docker build, let build get ready etc…
Create a Github repo for team marketplace plugins, with a skill (e.g., /implement-project)
Import that repo into default Team Marketplace
Start new session based on that environment, and use the skill in first message by ATTACHING it (e.g., /imple… to bring up the list of skills, then hit enter so the text goes yellow)
Note: if you just write the text and don’t hit enter to properly “attach” the skill to the message, then the session seems to start.
Workaround: Say “Hi” first, let the environment setup and agent respond. Then attach the skill as above, then it works.
Expected Behavior
The environment sets up successfully and the agent locates the skill and uses it to drive the session.
Second image attachment: I say “hi” first, let the environment setup, let the agent respond. Then I attach the skill to the next message and it works.
Hey @Branden_Visser, thanks for the report and the clear repro steps!
This is a known issue we’re tracking: when a Team Marketplace skill is attached as a chip, the cloud agent sometimes can’t match it to the plugin it loaded and stops with that error. I’ve added your report to it.
In the meantime, writing the skill name as plain text instead of attaching the chip should get you going, for example: Use the implement-project skill to build a cat simulator app. The agent still has your team’s skills available and can pick it up from there.
To help us narrow it down, could you try this and let us know what happens?
Start a new cloud agent on the same environment.
Type / and pick a different skill from the same Team Marketplace plugin, then press Enter so it turns into a chip.
Send the message.
Start another new agent and repeat steps 2 and 3 with /implement-project, two or three times.
Does /implement-project fail every time while other skills from that plugin work? Please also paste the header of the implement-projectSKILL.md (the lines between the --- markers at the top) and the folder path it lives in within the repo.
/implement-project: always fails (when it’s the first message). /define-ticket always succeeds as first message.
Works:
---
name: define-ticket
description: Define a mid-sized deliverable (about 3 to 8 story points) in the team's issue tracker (e.g. Linear) as one parent ticket with one-point sub-issues, through one-question-at-a-time Q&A. Covers investigating the code, deciding whether the work is really a project, settling user-visible behavior with worked examples, and splitting it into sub-issues with blockers. Use when the user wants to scope, break down, or resume defining work that is too big for one PR but smaller than a project.
---
Fails:
---
name: implement-project
description: Own a large project end to end as its sole developer. Implements tickets in dependency and story order, keeps one small PR open at a time, follows up on review feedback, picks up the next ticket when a PR is merged. Always makes sure work is pending human review: an open PR or a stalled Linear ticket status. Use when handed a project or epic to carry to completion.
---
I wouldn’t notice a difference, but something is wrong with /implement-ticket, because the github preview parser is actually giving an error on line 2 (see screenshots) for implement-project, but not define-project.
Will have to dig into what’s actually different about these
Ok, there is a colon followed by a space, so it’s invalid yaml. Will fix it up and it will probably work. And hopefully I remember this when it bites us again some day (or you guys fix the handling…)
(or you guys fix the handling…)