agentleFS
IgorGanapolskyIgorGanapolsky/mac-yolo-safeguards/.agents/skills/background-agent-hold-gate/SKILL.md

background-agent-hold-gate

Skill3 starsChanged 4 days agoMITView on GitHub

Refuse a background agent that keeps running after someone steps away, and refuse an unattended write into a design project file.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this before an agent keeps working after a person leaves, or before it writes a native design project.

    line 8

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Background agent hold gate

Use this before an agent keeps working after a person leaves, or before it writes a native design project.

The idea taken from https://news.adobe.com/news/2026/11/adobe-powers-new-era-of-creativity is that an agent can keep going in the background and can change a project file in place. This gate refuses both. It does not install a creative suite, call a model, or write a project file. Their detail and conference claims stay theirs. Local fields stay null.

A note that only cites that page stays clear. Saying a video app is closed, or leaving a media cache alone, stays clear. Opening a project file stays clear. Saving or exporting one does not.

What this gate does

  • install, or install / add / enable next to Firefly, Creative Cloud, GenStudio, a creative agent, or a local MCP connector, is blocked with vendor_install.
  • background, always-on, or a note that starts, leaves, keeps, or runs an always-on or background agent is blocked with background_agent and humanReview true. The gate does not leave the agent running.
  • write-project, edit-project, or save / export / copy onto a .psd, .ai, .prproj, or .aep file is blocked with project_write.
  • "richer detail" or "world's largest creativity conference" as our result is blocked with vendor_claim_as_local, unless the note names Adobe.
  • applied, agentLeftRunning, and projectWritten stay false. localSpeedup and localDetailGain stay null.

Commands

node tools/background-agent-hold-gate.js --action note --note "Premiere is closed."
node tools/background-agent-hold-gate.js --action background
node tests/test-background-agent-hold-gate.js

A clear review exits 0. A blocked review exits 2.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.