Skip to content

v0.10.0: 3rd-party discovery/search — detect capability gap, web-search, rank candidates #657

@ZaxShen

Description

@ZaxShen

Part of #656 (v0.10.0 — 3rd-party resource integration). Pipeline stage 1 of 4: discover.

Goal

When a task would benefit from a capability TMB doesn't have locally, bro autonomously searches for candidate 3rd-party resources (Claude Code skills, toolkits/MCP servers, plugins) and ranks them — rather than struggling with built-ins or asking the user to find tools.

What to design

  • Gap detection (trigger): how/when bro decides "I should look for external help." Heuristics: task names a domain with strong known tooling (frontend/UI, data viz, infra, mobile), or bro's first attempt stalls. Avoid over-triggering on trivial tasks.
  • Search: issue web searches like 2026 best Claude Code skills for <capability>, Claude Code plugin marketplaces, awesome-lists, GitHub topic search. Use WebSearch/WebFetch.
  • Candidate extraction + ranking: produce a small ranked list (name, source URL, type=skill|toolkit|plugin, why-relevant, popularity signal). Cap N; log what was searched and dropped (no silent truncation).
  • Output contract: a structured candidate list handed to the vetting stage (#NEXT_VET).

Out of scope

Installing or loading — that's stages 3/4. This issue only finds and ranks.

Acceptance

Given a task like "build a dashboard frontend," bro emits a ranked candidate list including at least one relevant real resource, with sources cited, and records the search in the trajectory.

Metadata

Metadata

Assignees

No one assigned

    Labels

    FeatureNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions