evergreen-setup
Get a skill running on this machine: check what it needs outside itself (a tool, a package, an API key, a local server, an AI model, an MCP server, or access to a database, Application Insights, a cloud role or an API), tell the user what each missing piece is for, install what is safe after saying so, walk the user through sign-ins and access requests, re-check, and record what worked and how it went for this operating system and agent harness. Use whenever a skill fails for a missing piece ('command not found', 'No module named', connection refused, model not found, a missing MCP tool) or a refused permission (401, 403, 'AuthorizationFailed', 'permission denied for table'), on the first use of a skill on a new machine or harness, and on 'what does X need', 'set up X', 'I don't have access to', 'get me access to the database', 'X does not work on my laptop'. Also when writing a skill's SETUP.md. Not for installing a dependency into the user's own project, or granting access in the user's own systems.
Pinned to revision 946faeac0810, so it is the text this page describes rather than whatever the author pushed since.
Files
Every link opens the file at its source, pinned to the revision this page describes.