Migrate hardcoded tools to markdown skills

t-382·WorkTask·
·
·
Created1 month ago·Updated1 month ago

Description

Edit

Philosophy: skill-max, tool-min.

Core tools to keep (in Haskell):

  • read_file
  • edit_file
  • write_file
  • run_bash
  • skill (to load skills)

Everything else should become skills that teach the agent HOW to use bash/python:

Tools to migrate to skills:

  • WebSearch → skill that uses curl + Kagi API
  • WebReader → skill that uses curl/lynx/python
  • Browser → skill that uses playwright via python/node
  • Vision → skill that uses python + vision API
  • Pdf → skill that uses pdftotext/python
  • Transcribe → skill that uses whisper CLI
  • Calendar → skill that uses gcalcli or API
  • Email → skill that uses msmtp/API
  • Http → skill that explains curl patterns
  • etc.

Benefits:

  • No recompilation to add/change capabilities
  • Skills are self-documenting
  • Users can customize/extend
  • Smaller agent binary
  • Skills can reference other skills

Timeline (6)

🔄[human]Open → InProgress1 month ago
💬[human]1 month ago

Core toolset reduced to read_file/write_file/edit_file/run_bash/skill; removed web search tool wiring; updated Coder subagent guidance to use rg via run_bash; added new skills (browser, code-search, http, pdf, transcribe, calendar, email, vision) and updated PLAN tool list.

🔄[human]InProgress → Done1 month ago
💬[human]1 month ago

Follow-up: removed unused undo_edit stub after shrinking core tools (fixes build warning/error).