agentleFS
Sign inStart free
odytriceodytrice/metaskills/skills/setup/SKILL.md

setup

Skill1 starsChanged 14 days agoMITView on GitHub

Configure project environments from AGENTS.md. Use to set up, install, bootstrap, or repair local, Docker Compose, or CI environments.

  • Reads credentials

191 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use add-voice-transcription, add-discord and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • juancruzmunozalbeloSkill

    add-voice-transcription

    Add voice message transcription to NanoClaw using OpenAI's Whisper API. Automatically transcribes WhatsApp voice notes so the agent can read and respond to them.

    Also in 5 projects that use this

  • MicrosoftSkill

    add-discord

    Add Discord bot channel integration via Chat SDK.

    Also in 11 projects that use this

  • MicrosoftSkill

    add-slack

    Add Slack channel integration via Chat SDK.

    Also in 11 projects that use this

  • juancruzmunozalbeloSkill

    add-telegram-swarm

    Add Agent Swarm (Teams) support to Telegram. Each subagent gets its own bot identity in the group. Requires Telegram channel to be set up first (use /add-telegram). Triggers on "agent swarm", "agent teams telegram", "telegram swarm", "bot pool".

    Also in 7 projects that use this

  • +8 more from microsoft

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 170 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Toolchain: Verify every documented tool/version.

    line 14
  2. Very specific:

    Infrastructure: Start backing services with documented compose commands/targets.

    line 15
  3. Very specific:

    Never commit secrets (.env, credentials, API keys, user overrides).

    line 22
  4. Distinctive:

    Run § Build & Validation minimum checks per layer.

    line 28

“Common” is measured: kept by at least 6 in 10 of the 170 edited versions of this file we could read. “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

Setup

From AGENTS.md: § Build & Validation (versions, commands, compose targets; missing: name it and stop, never guess), § Code Layout & Tech Stack, § Agent Login (local/mock auth).

Modes: local; Docker Compose (container infrastructure, host app unless documented otherwise); CI. Ask if unclear.

Local Development

  1. Toolchain. Verify every documented tool/version. Missing tools are environment gaps, not code failures.
  2. Infrastructure. Start backing services with documented compose commands/targets. Reset local DB only when explicitly needed (docker compose down -v, then restart).
  3. Restore, build, test each layer using exact § Build & Validation commands/directories; skip undefined targets.
  4. Run with the documented run command.

Rules

  • Host-to-container: 127.0.0.1, not localhost; container-to-container: compose service names. Only explicit AGENTS.md overrides.
  • Never commit secrets (.env, credentials, API keys, user overrides); examples stay non-secret. Production uses CI/CD or external secret management, never source control. Config secrets: stop, rotate real ones, replace with placeholders before continuing.
  • Mock auth only as § Agent Login documents, runtime development, never staging/production config. Otherwise configure its real provider.
  • Report PATH/version/sandbox-network restore failures as environment issues, not code failures.

Verification And Output

Run § Build & Validation minimum checks per layer; full build for complete setup. Report mode, verified tool versions, started services, changed configs, validation commands/results, remaining manual steps.

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.

Check your setup, free