Maintain the environment

The environment is what agents run with: permissions, global instructions, project instructions and skills. This skill is the starting point for a change to it. Choose the source the change belongs in, then follow that source's own guide. To set up a machine or a project, use /set-up-machine or /set-up-project instead.

• Write each change once, at its source, so changing it later is a one-place edit.
• Keep personal detail out of public files. The skills repo and most projects are public. Names, accounts, paths on the user's machine and other projects go only in the workstation repo, or in the shared global instructions file on a machine without one. In a skill or a public AGENTS.md, generalise the detail or make it a parameter.
• Keep harness memory features off. A memory is invisible to every other harness and lives outside any repository. Write what it would hold into a source instead.

Parameters

• <skills-repo>: the user's own skills repo on GitHub, as owner/repo.
• <path-to-skills-repo>: where that repo is cloned.
• <workstation-repo>: the user's own repo for their personal agent setup, usually private, as owner/repo.
• <path-to-workstation-repo>: where that repo is cloned, e.g. ~/code/agent-setup.

Where a change goes

Two questions choose the source. Who needs it: only this user, anyone on one project, or any agent doing a task? Must it be enforced, or is it guidance? The table runs from enforced to guidance. Go down it and use the first row that fits.