Skip to content

New team members should leverage configured plugin marketplace #29

Closed

Description

@GreenCee

When generating new team members configured marketplaces should be browsed to find an appropriate template or starting point. For example, if If I prompt for a team member to do Azure cloud development it should recommend or install the azure-cloud-development plugin as part of that team member's skills

/plugin marketplace list
● Registered Marketplaces:

• awesome-copilot
  Source: GitHub: github/awesome-copilot

• anthropic-agent-skills
  Source: GitHub: anthropics/skills

/plugin marketplace browse awesome-copilot

Plugins in "awesome-copilot":
• awesome-copilot
Meta prompts that help you discover and generate curated GitHub Copilot agents, collections, instructions, prompts, and skills.
• azure-cloud-development
Azure cloud development tools including Infrastructure as Code, architecture patterns, and cost optimization.
• cast-imaging
A comprehensive collection of specialized agents for software analysis, impact assessment, structural quality advisories, and architectural
review using CAST Imaging.
• clojure-interactive-programming
Tools for REPL-first Clojure workflows featuring Clojure instructions, the interactive programming chat mode and supporting guidance.
• copilot-sdk
Build applications with the GitHub Copilot SDK across multiple programming languages. Includes comprehensive instructions for C#, Go,
Node.js/TypeScript, and Python.

etc. etc.

Docs
● Marketplace Subcommands:
/plugin marketplace add - Add a marketplace
/plugin marketplace remove - Remove a marketplace
/plugin marketplace list - List registered marketplaces
/plugin marketplace browse - Browse plugins in a marketplace

Examples:
/plugin marketplace add anthropics/skills
/plugin marketplace browse anthropic-agent-skills

Activity

  1. bradygaster commented on Feb 12, 2026

    @bradygaster
    Collaborator

    I've thought about this idea a lot. Your idea is the origin of import and export. Thanks for the "idea validation!"

  2. bradygaster commented on Feb 13, 2026

    @bradygaster
    Collaborator

    Implementation Plan: Marketplace-Driven Team Member Creation

    Verdict: ✅ GO for v0.4.0

    This is the natural evolution of Squad's plugin architecture—turning the marketplace from a passive catalog into an active skill-sourcing engine. Brady's right that this is the origin of import/export: we're building the "import skills from marketplace" pipeline that makes new team members immediately productive.

    Architecture

    Core Insight: Team member creation should be marketplace-aware by default.

    Integration Points

    1. Member Creation Flow (squad init / add member):

      • After capturing role/domain input, query configured marketplaces
      • Match plugins by role tags, keywords, domain expertise
      • Present recommendations ranked by relevance
      • On selection, install plugin as agent skill bundle
    2. Plugin → Skill Mapping:

      • Plugin structure: {instructions, tools, examples, charter-snippet}
      • Installation target: .ai-team/agents/{member}/skills/{plugin-name}/
      • Charter auto-augmentation: append plugin's charter snippet to member's charter.md
    3. Marketplace Query Strategy:

      • Use /plugin marketplace browse {name} output + semantic matching
      • Example: "Azure cloud development" → search for tags: �zure, cloud, infrastructure
      • Fallback: keyword matching in plugin descriptions
    4. Import/Export Foundation:

      • This builds the import side: pulling external skills into agents
      • Future export side: publishing Squad agents as marketplace plugins
      • Completes the cycle: Squad consumes AND produces marketplace plugins

    Work Items

    WI-1: Marketplace Discovery Integration

    Owner: Fenster
    Scope: Modify member creation flow to query marketplaces
    Acceptance Criteria:

    • When creating a new member, Squad checks /plugin marketplace list
    • If marketplaces exist, Squad runs /plugin marketplace browse {name} for each
    • Matches plugins by role/domain keywords (e.g., "Azure" → �zure-cloud-development)
    • Presents top 3 matches to user: "Found plugins for this role—install?"

    WI-2: Plugin-to-Skill Mapping

    Owner: Verbal
    Scope: Design plugin installation structure
    Acceptance Criteria:

    • Define plugin schema: {name, instructions, tools, charter-snippet}
    • Implement installer that writes to .ai-team/agents/{member}/skills/{plugin}/
    • Auto-append charter snippet to member's charter.md
    • Support multiple plugins per agent

    WI-3: Auto-Recommendation UX

    Owner: McManus
    Scope: Design the recommendation prompt
    Acceptance Criteria:

    • Clear prompt: "🔌 Found 2 plugins for Azure development: [azure-cloud-development], [cast-imaging]. Install?"
    • Options: Install all / Pick one / Skip
    • Confirmation message: "✅ Installed azure-cloud-development as skill for {member}"

    WI-4: Documentation

    Owner: McManus
    Scope: Document marketplace-member integration
    Acceptance Criteria:

    • Add section to README: "Marketplace-Powered Team Members"
    • Document plugin schema for marketplace authors
    • Example walkthrough: creating an Azure-focused agent with marketplace plugins

    WI-5: Testing

    Owner: Hockney
    Scope: Test scenarios for marketplace integration
    Acceptance Criteria:

    • Test: Create member with no marketplaces configured (skip flow)
    • Test: Create member with marketplace, no matching plugins (skip gracefully)
    • Test: Create member with marketplace, 1 match (auto-recommend)
    • Test: Create member with marketplace, 3+ matches (show top 3)
    • Test: Install plugin and verify skills directory structure

    Connection to Import/Export

    This is Phase 1: Import—Squad pulls skills from the ecosystem.

    • Now (v0.4.0): Squad imports plugins as agent skills
    • Next (v0.5.0): Squad exports agents as shareable plugins
    • Vision: Marketplace becomes the exchange layer—users build agents with imported skills, then publish those agents back as new plugins

    This closes the loop: Squad becomes both a consumer and producer in the plugin ecosystem.


    — 🏗️ Keaton (Lead) · Posted by Squad

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions