agentleFS
Sign inStart free
fontezbrooksfontezbrooks/loomDaddy/skills/setup/SKILL.md

setup

Skill1 starsChanged 3 months agoMITView on GitHub

Check the Loom pipeline environment (Loom session, data dir, optional Drive, Notion MCP) and guide first-time setup.

  • 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

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

  • 0

    Common

    Most of the 171 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run the environment check (migrates any legacy session into the stable data dir, then reports):

    line 8
  2. Very specific:

    No LLM API key is needed (analysis runs on the Claude subscription).

    line 29

“Common” is measured: kept by at least 6 in 10 of the 171 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

Run the environment check (migrates any legacy session into the stable data dir, then reports):

cd "${CLAUDE_PLUGIN_ROOT}" && npx tsx --env-file-if-exists=.env scripts/doctor.ts

The script can only check what a local process can see. After it runs, also do the two checks it cannot, then guide the user:

  1. Loom session (REQUIRED): if missing, run /loom-daddy:loom-auth. This is the only hard requirement for analyzing recordings.
  2. Notion MCP (REQUIRED for publishing, script cannot check): confirm a Notion MCP is connected and callable in this session (interactive uses the notion-search/notion-create-pages tools). If none is connected, tell the user to connect their Notion integration; publishing needs it. No NOTION_TOKEN is required.
  3. Notion destination: if none is cached yet, tell the user they will name a target database on their first /loom-daddy:publish (e.g. "publish to my Meeting Notes database"); it is then remembered.
  4. Drive (OPTIONAL): only needed to also upload a transcript + markdown copy. If unset, Drive is skipped and Notion publishing still works. To enable, set DRIVE_FOLDER_ID + GOOGLE_APPLICATION_CREDENTIALS in ${CLAUDE_PLUGIN_ROOT}/.env.

No LLM API key is needed (analysis runs on the Claude subscription). When the session is present, suggest /loom-daddy:list to see recent recordings.

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