Thanks @ShayNehmad and the Cup o' Go crew for the surprise gaal shout-out. You nailed it: it's a bit stupid such a tool needs to exist, but the problem's real, so we're glad to be the glue.

Skill Spotlight: Trail of Bits security skills Security review skills from an actual security firm. A real auditor's checklist, not vibes. github.com/VoltAgent/awesome…

MCP Monday: Postgres MCP Let your coding agent query your database directly. Inspect schemas, run read-only queries. github.com/modelcontextproto…

Skill Spotlight: Anthropic's document skills pdf, docx, pptx, xlsx. Your agent builds a real slide deck or spreadsheet, not just talk about one. github.com/anthropics/skills

MCP Monday: GitHub MCP Issues, PRs, code search, repo ops, all from inside your coding agent. No more tab-switching to GitHub. github.com/github/github-mcp…

Skill Spotlight: mcp-builder Anthropic's official skill that walks your agent through building a spec-compliant MCP server. github.com/anthropics/skills

MCP Monday: Playwright MCP Lets your coding agent drive a real browser. Click, type, screenshot, test. Great for frontend work. github.com/microsoft/playwri…

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.

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.

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."

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.

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.

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.

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.

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.

MCP Monday: Context7 Pulls current library docs into your coding agent so it stops hallucinating APIs from two versions ago. github.com/upstash/context7