agentleFS
Sign inStart free
davidmosiahdavidmosiah/garmin-mcp/skill/SKILL.md

garmin

Skill13 starsChanged 6 months agoMITView on GitHub

Unofficial Garmin Connect data for AI agents. Prefer MCP tools if connected; otherwise the package CLI. Use when the user wants Garmin data or actions through an agent.

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. eddmann/jeeves★ 2same name
    2. ai-ecoverse/skills★ 1same name
    3. dbhq-uk/garmin-skill★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository3 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not put mutation flags in that snippet.

    line 20
  2. Very specific:

    If MCP tools named garmin_* are already available, use them.

    line 28
  3. Very specific:

    Call garmin_connection_status (or doctor --json when that exists).

    line 32
  4. Distinctive:

    Use read tools as asked.

    line 33
  5. Very specific:

    Stop on USER_ACTION_REQUIRED.

    line 34

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

Garmin — skill or MCP

Same binary either way. Do not duplicate the API client.

Choose a surface

MCP — tools appear natively after stdio/HTTP config:

{ "mcpServers": { "garmin": { "command": "npx", "args": ["-y", "garmin-mcp-unofficial"] } } }

Do not put mutation flags in that snippet.

Skill / CLI — no MCP client required. Same tools:

npx -y garmin-mcp-unofficial call garmin_connection_status --json '{}'

If MCP tools named garmin_* are already available, use them. Do not also shell out.

Loop

  1. Call garmin_connection_status (or doctor --json when that exists).
  2. Use read tools as asked.
  3. Stop on USER_ACTION_REQUIRED. Do not invent env flags. Do not enable mutations from this skill.

Never

  • Paste tokens into git, chat logs, or the prompt
  • Copy a mutations-enabled assignment into config

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