agentleFS
KakhramonKakhramon/usage-analyzer/skills/setup/SKILL.md

setup

Skill0 starsChanged 51 days agoMITView on GitHub

Configure usage-analyzer with your display name and the team dashboard URL, then do the first sync. Use when the user installs the plugin, says their usage is not showing up, wants to change the name they appear under, or wants to point at a different dashboard.

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 171 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
  1. Very specific:

    Check current config: cat ~/.usage-analyzer.json (missing file means not set up yet).

    line 11
  2. Distinctive:

    If nobody runs one yet, say so and point at the "Server" section of the plugin README.

    line 16
  3. Distinctive:

    Do the first sync and report the result.

    line 26
  4. Very specific:

    If step 4 fails with a connection error, the dashboard URL is wrong or the server is down.

    line 37

“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

Configure this machine to report usage. Arguments, possibly empty: $ARGUMENTS

  1. Check current config: cat ~/.usage-analyzer.json (missing file means not set up yet).
  2. You need three things. Take them from the arguments, else from what the user already said, else ask for the missing ones in a single question:
    • name — how they appear on the dashboard (alice, Bekzod). Short, no spaces.
    • url — the dashboard URL the team already runs, e.g. https://usage.example.com. If nobody runs one yet, say so and point at the "Server" section of the plugin README; do not start a server on their laptop unless they ask for it.
    • token — the shared secret that dashboard was started with. Optional only if the server runs without --token.
  3. Run:

    python3 "${CLAUDE_PLUGIN_ROOT}/scripts/collect.py" init --name NAME --url URL --token TOKEN
  4. Do the first sync and report the result. It reads every local session log once, so allow a minute on an old machine:

    python3 "${CLAUDE_PLUGIN_ROOT}/scripts/collect.py"
  5. Tell them: from now on every session end syncs automatically, and the dashboard is at the URL they gave. Mention once that only counts are sent — session ids, token totals, timestamps, model names, project paths — never prompt or file content.

If step 4 fails with a connection error, the dashboard URL is wrong or the server is down; with bad token, the secret does not match the server's --token.

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.