pstack: Comment Sicko agent name has a space and Grok rejects the spawn
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- tooling
Research direction
Start with pstack/agents/comment-sicko.md and compare its frontmatter name with pstack/skills/no-comments/SKILL.md and the README spawn example. Check the Grok error and the working pstack:poteto-agent identifier as references. Done means the Comment Sicko agent uses the hyphenated spawn id consistently and /no-comments can start it.
Written by the indexing model from the issue text.
Description
Summary
pstack/agents/comment-sicko.md in pstack 0.15.5 sets:
name: Comment Sicko
pstack/skills/no-comments/SKILL.md tells the caller to spawn that agent:
Spawn `Task` with `subagent_type: "Comment Sicko"`.
The README documents the same subagent_type.
On Grok Build 1.0.46, grok inspect registers the agent as pstack:Comment Sicko. spawn_subagent with that exact type then fails, and the error lists the same string as available:
Unknown subagent type: pstack:Comment Sicko. Available types: ... pstack:Comment Sicko, pstack:poteto-agent, ...
pstack:poteto-agent spawns. Its frontmatter name is poteto-agent, with no space.
This repo has no issue template and no contributing guide. This report follows the shape of the other open pstack issues: the file, the failing value, and the error text.
Why it matters
/no-comments cannot start its reviewer. Comment Sicko is the read-only comment pass that skill is supposed to run before review.
Suggested fix
Set the frontmatter name to comment-sicko, so the Grok spawn id is pstack:comment-sicko. Point the /no-comments step and the README spawn example at that id. The heading in the agent file can stay "Comment Sicko".
This is not #237. That issue is the poteto-mode skill name Poteto Mode. This one is the Comment Sicko agent name.
- Dominant language
- TypeScript
- Stars
- 8.8k
- Forks
- 819
- Avg merge
- 14h 37m
- Merged PRs (30d)
- 66
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from cursor/plugins
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 Half a day Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
Maintainers usually reply within 1 day
Similar issues
-
enhancement providers-api ui-dashboard
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
external-issue to-triage
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
needs triage
Difficulty 1/5 Under an hour Newbie friendliness 88/100
homarr-labs/homarr#6976 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day