Pimp My IDE / Garage Dispatch
← Back to the garage
September 6, 2026 · agent skills / dependency maintenance

Your agent skill is a dependency. Give it a service interval.

Agent skills are crossing the line from clever prompt folders into installable operating parts. One popular collection offers managed, auto-updating bundles or editable copies. Another catalog has already been deprecated in favor of richer plugins. The format is settling; the maintenance contract is not.

The take: “write once, use everywhere” is a format promise, not an ownership policy. Decide whether you subscribe or vendor. Pin what ran, inspect what changed, test the behavior that matters, and keep a hand crank for the day the marketplace moves the shelves.
Raise the Skill Service Lift ↓

The shop manual learned how to install itself.

The Agent Skills specification describes a folder with a required SKILL.md plus optional scripts, references, and assets. Its best-practices guide recommends progressive disclosure: keep the main file focused and move detail into linked material. That is clean packaging. It is also enough surface area to deserve the same suspicion as any other dependency—especially when scripts can turn prose into execution.

The ecosystem is moving fast around that package shape. Matt Pocock’s current collection explicitly offers two ownership models: a managed, read-only plugin that updates from the publisher, or ordinary files copied into your repository and updated when you choose. The README warns that installing both duplicates every skill. That tiny warning is the whole dependency-management argument in miniature: acquisition mode changes behavior.

Prompt files stopped being stationery when they acquired installers, scripts, and automatic invocation.

A marketplace migration is not a footnote.

OpenAI’s skills catalog now marks itself deprecated and directs users to a plugins repository. The replacement manifest can bundle skills with MCP configuration, agents, commands, hooks, apps, and assets. That is not merely a renamed folder. It is a larger callable surface with more places for policy, credentials, network reach, and updates to hide.

This is normal ecosystem growth, not evidence of wrongdoing. But “deprecated” is operational information. If a team cannot answer which repository, revision, installer, update channel, and fallback produced the behavior in today’s session, it cannot reproduce the session—it can only remember the vibe.

Test the trigger, not the typography.

The Agent Skills evaluation guide separates triggering tests from functional tests. That distinction is excellent. A beautifully written skill that never activates is broken; a skill that activates for everything is also broken. Then the body still has to do useful work under realistic prompts.

Keep a tiny fixture deck beside every important skill: prompts that must trigger, prompts that must not, and one or two outputs whose invariants can be checked. Record the model and client used, because invocation behavior sits partly outside the folder. Do not chase exact prose. Test boundaries, required evidence, dangerous actions, and the promised artifact.

The garage service schedule.

  1. Choose ownership. Managed means you accept upstream motion; vendored means you own merges and drift.
  2. Pin the installed state. Record source URL, revision, acquisition command, client, and date.
  3. Diff before lift. Review instructions, scripts, hooks, external references, permissions, and invocation metadata.
  4. Run the fixture deck. Positive triggers, negative triggers, functional invariants, and one hostile edge case.
  5. Keep rollback boring. One documented move should restore the last known-good bundle without depending on the marketplace still existing.
Interactive makeover / dependency hygiene

Raise the Skill Service Lift.

Traditional purpose replaced: a one-line install command and faith. Better version: choose the ownership mode, age the installed revision, close four maintenance circuits, and export a reproducible service card.

Acquisition bay

Tell the lift who owns motion, then energize the evidence needed before the next update.

Ownership mode
14 days
Maintenance circuits

Maintenance lift

The car rises with maintenance debt, not quality. High means inspect before the next session; it does not mean the skill is malicious or broken.

43/100Inspect before update
3 / 4maintenance circuits closed
MANAGEDdeclared ownership mode
TEACHING PROXY — this gauge does not inspect a repository, verify safety, score quality, or predict failure. It reflects only the controls on this page.
Open the five-source service log
[1] Agent Skills specification — folder structure, required SKILL.md, optional scripts, references and assets [2] Agent Skills best practices — progressive disclosure, scoping and structure [3] Agent Skills evaluation guide — triggering and functional evaluations [4] Skills for Real Engineers — managed read-only bundle versus editable repository copies [5] OpenAI skills catalog — deprecation notice pointing to the richer plugins repository