agentleFS
steerlabssteerlabs/opensteer/.agents/skills/setup/SKILL.md

setup

Skill204 starsChanged 6 days agoMITView on GitHub

Use when enrolling a computer in an Opensteer Deployment or resolving its SSH, Full Disk Access and app access setup, registering an integration OAuth app or configuring managed or custom consent and testing an integration authorization flow, or setting up, adding or testing a messaging provider and its channel transport.

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

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

  • 0

    Common

    Most of the 170 edited versions we read keep these.

  • 3

    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
  1. Distinctive:

    Stop everything you start by captured PID or serial, even after a failure.

    line 15
  2. Very specific:

    Never drive the host screen: GUI and Electron checks run only in the VM (pnpm test:vm).

    line 16
  3. Distinctive:

    Never read or operate signing keys, Apple accounts or release credentials.

    line 17
  4. Distinctive:

    Never use a person's real profile, credentials, saved passwords, Messages or personal stores.

    line 18
  5. Very specific:

    Never touch the live install: ~/Library/Application Support/Opensteer, ~/Opensteer, Opensteer Beta.

    line 19

“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

Lending a computer, connecting integrations and wiring messaging. Computers, Integration OAuth and Messaging hold the authority rules.

Safety rules

  • Devices have one owner: never take another task's simulator, emulator, USB phone or VM slot.
  • Stop everything you start by captured PID or serial, even after a failure; never kill by name.
  • Never drive the host screen: GUI and Electron checks run only in the VM (pnpm test:vm).
  • Never read or operate signing keys, Apple accounts or release credentials.
  • Never use a person's real profile, credentials, saved passwords, Messages or personal stores.
  • Never touch the live install: ~/Library/Application Support/Opensteer, ~/Opensteer, Opensteer Beta.
  • Skipped, blocked or unrun checks are unverified, never passed.
  • Owners enter provider secrets and bot tokens through the product, never in commits or logs.

Procedures

  • Computers: enrollment, app access, agent SSH.
  • Integration OAuth: managed and custom apps, checks.
  • Messaging: Slack, new providers, checks.

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.