Skip to content

docs: fix broken skill reference in mcp-config.md (#897) #933

Closed

Description

@diberry

Gap

Issue #897: mcp-config.md and squad.agent.md reference non-existent skill. Broken references erode user trust.

Specific Broken Reference

Files containing the broken reference:

  • .squad/mcp-config.md (line ~line 10, in the blockquote callout)
  • .squad-templates/squad.agent.md (line ~line 10, in the blockquote callout)
  • templates/mcp-config.md (line ~line 10, in the blockquote callout)
  • .squad/templates/mcp-config.md (line ~line 10, in the blockquote callout)
  • .squad-templates/mcp-config.md (line ~line 10, in the blockquote callout)

Exact broken reference:

Read `.squad/skills/mcp-tool-discovery/SKILL.md` for discovery patterns, domain-specific usage, and graceful degradation.

Where it appears: Inside a blockquote that starts with > **Full patterns:**

The skill does not exist in the bradygaster/squad repository. The path .squad/skills/mcp-tool-discovery/SKILL.md is referenced but the directory/file is not present.

What's Needed

  1. Remove or update broken reference — either:
    • Remove the broken reference line entirely if this skill is not planned, OR
    • Create the missing .squad/skills/mcp-tool-discovery/SKILL.md documentation if the skill is intentional
  2. Verify all skill references in templates and agent configs
  3. Add acceptance criteria — verify by searching the repo for any remaining references to non-existent skills

Acceptance Criteria

Related

Source: docs-opportunity-scanner (2026-04-08)

Activity

  1. diberry commented on Apr 8, 2026

    @diberry
    ContributorAuthor

    ⚠️ Needs refinement

    Missing specificity:

    • Which skill reference is broken? (need exact file/line or skill name)
    • What is the correct reference or should it be removed?
    • What does 'verify all skill references' entail? (scope of verification audit)

    Suggest: Add the broken reference details and acceptance criteria for 'verify all references'.

  2. added 3 commits that reference this issue on Apr 10, 2026
    42c0e0e
    2d785dc
    7682c7b
  3. added a commit that references this issue on Apr 12, 2026
    bd919af
  4. added a commit that references this issue on Apr 21, 2026
    e784988
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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions