Summary
After installing a skill from ClawHub via Enterprise settings, searching ClawHub again still lists the same skill with no "installed" state. This is confusing and suggests the install failed.
Current behavior
GET /skills/clawhub/search proxies ClawHub only; results do not include tenant-local install status.
- Enterprise ClawHub modal removes the row from the list only in current React state after install; a new search shows the skill again with a normal Install flow.
- Agent Browse ClawHub modal always shows an Install button and does not remove or mark installed skills.
Expected behavior
- Search (or detail) should reflect whether the skill is already in the tenant global registry (and optionally per-agent workspace for agent-level import), e.g.
installed: true or disabled Install + "Installed" badge.
- Prefer resolving against DB (
Skill / source_url / slug) after ClawHub search returns.
Suggested scope
- Backend: enrich
/skills/clawhub/search (or a parallel endpoint) with install flags for the current tenant.
- Frontend: Enterprise settings + Agent detail ClawHub modals consume the flag.
Notes
Not a crash; UX / feature gap unless product spec already requires installed indicators.
Summary
After installing a skill from ClawHub via Enterprise settings, searching ClawHub again still lists the same skill with no "installed" state. This is confusing and suggests the install failed.
Current behavior
GET /skills/clawhub/searchproxies ClawHub only; results do not include tenant-local install status.Expected behavior
installed: trueor disabled Install + "Installed" badge.Skill/source_url/ slug) after ClawHub search returns.Suggested scope
/skills/clawhub/search(or a parallel endpoint) with install flags for the current tenant.Notes
Not a crash; UX / feature gap unless product spec already requires installed indicators.