getgaal

[getgaal @getgaal]

MCP Monday: GitHub MCP
Issues, PRs, code search, repo ops, all from inside your coding agent. No more tab-switching to GitHub.
https://t.co/Ds1g928v5y

[getgaal @getgaal]

Skill Spotlight: mcp-builder
Anthropic's official skill that walks your agent through building a spec-compliant MCP server.
https://t.co/sznnTMwSWA

[getgaal @getgaal]

MCP Monday: Playwright MCP
Lets your coding agent drive a real browser. Click, type, screenshot, test. Great for frontend work.
https://t.co/9PSkhqco98

[getgaal @getgaal]

Friday tip: keep your gaal.yaml in your dotfiles.
New laptop? Clone, run gaal sync, and every agent comes back with its skills and MCP servers wired.
Restore, not rebuild.

[getgaal @getgaal]

Early call we still love: gaal upserts, never overwrites.
It merges new entries into your agent config. Your hand-tuned settings stay.
Overwriting was simpler. It also eats a config exactly once.

[getgaal @getgaal]

Honest question.
Last time you added one MCP server, how many config files did you edit by hand to get it everywhere?
Reply with your number. We bet nobody's is "one."

[getgaal @getgaal]

One of the most-starred coding skills on GitHub for a reason.
https://t.co/lZ5TGrnM0t

[getgaal @getgaal]

Skill Spotlight: the Karpathy guidelines
Make your agent code like Andrej: tasteful, legible, small. Think before coding, simplicity first, surgical changes.

[getgaal @getgaal]

Every agent wants your project instructions under its own filename.
gaal maps one source to each agent's expected spot. Write the rules once, not once per agent.

[getgaal @getgaal]

Another coding agent launched recently. Looks great, I'll try it.
It's also one more config format, one more path, one more place to re-add your skills.
Better agents, worse plumbing.

[getgaal @getgaal]

Your agent skills are dependencies. Treat them like one.
gaal pins a skill, repo, or MCP to a revision. Upstream changes it? Your agents don't move till you bump the pin.

[getgaal @getgaal]

Before gaal sync touches disk, run --dry-run.
You get the full diff: every skill, every MCP, every agent it would change. Nothing written.
Read the plan, then run it.

[getgaal @getgaal]

Editing config by hand is fine. You edit package.json by hand.
The problem is editing the same MCP into four configs by hand.
One source of truth: fine. Six copies of one fact: that's the drift.

[getgaal @getgaal]

MCP Monday: Context7
Pulls current library docs into your coding agent so it stops hallucinating APIs from two versions ago.
https://t.co/wBmXCksrXz

[getgaal @getgaal]

It's why we're building gaal: https://t.co/SExHW1YTGl
https://t.co/t5l5iKON1S

[getgaal @getgaal]

AI agent configs are now part of your dotfiles whether you planned for it or not. The tool sprawl is real.

[getgaal @getgaal]

Every new AI coding agent that ships makes the config problem worse. And a new one ships every week.

[getgaal @getgaal]

https://t.co/OrKDHbOQh7

[getgaal @getgaal]

The biggest MCP pain: portability. 5 agents x 10 servers = 50 config entries by hand.
Or one YAML. https://t.co/SExHW1YTGl

[getgaal @getgaal]

We think your AI coding config should be declarative, version-controlled, and non-destructive. One file, synced everywhere, nothing overwritten.