Skip to content

fix(recipe): correct Maverick recipe tool names, remove CLI-only card call, fix brand casing#8060

Open
DOsinga wants to merge 2 commits intomainfrom
triage/maverick-recipe-fixes
Open

fix(recipe): correct Maverick recipe tool names, remove CLI-only card call, fix brand casing#8060
DOsinga wants to merge 2 commits intomainfrom
triage/maverick-recipe-fixes

Conversation

@DOsinga
Copy link
Collaborator

@DOsinga DOsinga commented Mar 22, 2026

Fixes for #8058 (authored by @smartrickpicks) — pushing here because the fork's maintainer-edits flag is set but the credential doesn't have access to that fork.

Closes #8058

Changes

  • Prefix all MCP tool calls with maverick__ — goose exposes stdio extension tools as <extension>__<tool>; the original used bare names like maverick_profile which would fail at runtime with "Tool not found"
  • Remove maverick_card from the prompt — that is a CLI command (maverick card), not an MCP tool; instructions now note it as a CLI command instead
  • Remove the Developer Card activity bullet that implied it could be triggered via the agent
  • Replace Goosegoose throughout (brand guideline for the documentation directory)

smartrickpicks and others added 2 commits March 22, 2026 11:19
Adds an MCP-based recipe that adapts Goose's communication style to
match each developer's behavioral profile. 10-question assessment
detects working style across four drives (Dominance, Extraversion,
Patience, Formality), then adjusts pacing, tone, autonomy, and
decision style accordingly.

Features:
- Profile detection via behavioral assessment
- Adaptive communication (response length, tone, checkpoint frequency)
- Shareable Developer Card visualization
- Local-only storage (~/.maverick/), zero telemetry
- Published on PyPI: uvx maverick-mcp serve

Repository: https://github.com/get-airlock/maverick-mcp
… casing

- Prefix all MCP tool calls with maverick__ (goose exposes stdio extension
  tools as <extension>__<tool>, not bare names)
- Remove maverick_card from the prompt — that is a CLI command, not an MCP
  tool; note it in instructions as `maverick card` instead
- Remove the corresponding activity bullet about Developer Card visualization
- Replace Goose → goose throughout (brand guideline)

Signed-off-by: Douwe Osinga <douwe@squareup.com>
@DOsinga DOsinga requested a review from angiejones as a code owner March 22, 2026 15:57
@github-actions
Copy link
Contributor

🔍 Recipe Security Scan Results

⚠️ Status: SCAN FAILED - Technical issues during scanning

📊 Scan Summary:

  • Total recipes scanned: 1
  • Failed scans: 1

📋 Individual Recipe Results:
❓ Recipe 1: UNKNOWN (UNKNOWN risk)

🔗 View detailed scan results in the workflow artifacts.

@github-actions
Copy link
Contributor

PR Preview Action v1.8.1

QR code for preview link

🚀 View preview at
https://block.github.io/goose/pr-preview/pr-8060/

Built to branch gh-pages at 2026-03-22 16:00 UTC.
Preview will be ready when the GitHub Pages deployment is complete.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants