troubleshoot-earl

Diagnose and fix Earl CLI, HCL template, Jinja render, authentication, MCP, and SSRF issues.

112|7|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/brwse/earl --skill troubleshoot-earl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: troubleshoot-earl
Source: https://github.com/brwse/earl/tree/main/skills/development/troubleshoot-earl
Command: npx skills add https://github.com/brwse/earl --skill troubleshoot-earl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a cold-start diagnostic workflow to identify and resolve Earl CLI installation problems, HCL template and Jinja render errors, authentication failures, MCP connectivity issues, and SSRF-related blocks so agents and humans can restore Earl functionality quickly.

Core Features & Use Cases

  • Sequential Diagnostics: Walks through earl doctor, template validation, template discovery, secret checks, MCP config verification, and reproducing failing commands to isolate the root cause.
  • Actionable Remediation: Maps common error messages to precise fixes and indicates when human intervention is required for secrets, OAuth flows, or agent restarts.
  • Use Case: When earl call returns errors or MCP tools are not visible, use this Skill to systematically validate templates, secrets, and MCP configuration and provide the commands and human steps needed to recover.

Quick Start

Run the Earl diagnostic sequence by running earl doctor, then validate templates, list templates and secrets, verify MCP config, and reproduce the failing earl call to collect and report errors.

Frequently Asked Questions about troubleshoot-earl

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I troubleshoot earl call errors and missing MCP tools?

To troubleshoot earl call errors, run a sequential diagnostic workflow starting with earl doctor, then validate templates, inspect secrets, verify MCP configuration, and reproduce the failing command to isolate the root cause.

Why does my HCL template validation fail during Earl rendering?

HCL template validation fails when syntax errors or missing variables prevent Jinja rendering. Use earl templates validate to check syntax, then run earl templates list to ensure the template is properly discovered and configured.

How do I fix OAuth authentication failures in Earl on local workstations?

OAuth authentication failures on local workstations require human intervention to complete browser-based authorization flows. The diagnostic process identifies these failures and prompts you to manually complete the OAuth login to restore access.

What should I do when Earl MCP connectivity issues block tool visibility?

MCP connectivity issues that block tool visibility are resolved by verifying MCP configuration files and connection settings. Run MCP config verification checks to identify misconfigurations, then restart the agent to refresh tool availability.

How do I resolve missing secrets errors when running Earl commands?

Missing secrets errors occur when required credentials are absent from the environment. The diagnostic workflow inspects secret stores and prompts you to manually provide the necessary secrets or configure environment variables before re-running commands.

Can I use Earl troubleshooting diagnostics in CI agents and local environments?

Earl troubleshooting diagnostics apply to both local workstations and CI agents. The sequential checks including earl doctor, template validation, and MCP verification work across environments, prompting for human actions when browser-based OAuth or secret entry is needed.