migrate-to-earl

Scan codebases and replace raw API/CLI calls with Earl templates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the migration of raw API/CLI calls within a codebase to more manageable and discoverable Earl templates, streamlining agent interactions with external services.

Core Features & Use Cases

  • Automated Discovery: Scans codebases to identify common API/CLI tool usage (curl, gh, stripe-cli, etc.).
  • Provider-Based Migration: Migrates one API provider at a time, ensuring reviewability and reversibility.
  • Template Management: Imports pre-built Earl templates or guides the creation of custom ones.
  • Secret Handling: Manages necessary API secrets securely.
  • Use Case: You have a project that heavily relies on curl commands to interact with the GitHub API. This Skill can automatically find these calls, import the github Earl template, and replace the curl commands with earl call github.some_action commands, making the code cleaner and the API interactions more robust.

Quick Start

Use the migrate-to-earl skill to scan your codebase for raw API calls and convert them to Earl templates, starting with the GitHub provider.

Frequently Asked Questions about migrate-to-earl

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

FAQPage Schema
How do I migrate raw curl commands to Earl templates in my codebase?

To migrate curl commands to Earl templates, scan your codebase to identify raw API calls and replace them with pre-built or custom Earl templates, migrating one provider at a time to ensure reversibility and review.

What is provider-based migration for API CLI calls?

Provider-based migration is the process of scanning a codebase and replacing raw API or CLI calls with Earl templates one provider at a time, ensuring changes are reviewable and reversible before rewriting call sites.

Can I import pre-built Earl templates for the GitHub API?

Yes, you can import pre-built Earl templates such as the github provider template to automatically replace raw HTTP calls or CLI tool usage with verified earl call commands.

How do I manage API secrets when replacing HTTP calls with Earl templates?

When replacing HTTP calls with Earl templates, the migration process handles secret management securely, ensuring necessary API secrets are managed and verified before rewriting call sites.

Does Earl template migration verify commands before rewriting call sites?

Yes, Earl template migration verifies Earl commands before rewriting call sites, ensuring the imported pre-built templates or custom templates function correctly prior to final codebase modernization.

What are the limitations of automated codebase modernization for API calls?

Automated codebase modernization for API calls migrates one provider at a time and requires reviewing custom template creation and secret management, meaning bulk migrations across multiple providers simultaneously are not supported.