agentleFS
michaelnealemichaelneale/mesh-llm/.agents/skills/skippy-metrics/SKILL.md

skippy-metrics

Skill3.8k starsChanged 20 days agoApache-2.0View on GitHub

Use this skill when working on skippy telemetry attributes, OTLP emission, benchmark metric names, runtime lifecycle telemetry, or separating telemetry/reporting ownership from stage runtime serving.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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:

    Use this skill for telemetry attributes, lifecycle instrumentation, and benchmark/report integration.

    line 10
  2. Very specific:

    Keep canonical benchmark report export in metrics-server rather than inside stage serving.

    line 31

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “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

skippy-metrics

Use this skill for telemetry attributes, lifecycle instrumentation, and benchmark/report integration.

Ownership

skippy/crates/skippy-metrics owns shared attribute names. Stage servers may emit OTLP/telemetry, but request-path serving must not block on telemetry export. skippy/crates/metrics-server owns benchmark/debug telemetry ingest, SQLite storage, run lifecycle, and canonical report export.

Mesh API runtime status is not a telemetry dump. Keep public runtime status backend-neutral and stable; expose backend details only when intentionally part of the status shape.

Validation

cargo test -p skippy-serving --lib
cargo test -p mesh-llm --lib

Keep canonical benchmark report export in metrics-server rather than inside stage serving.

Download now (ZIP)

Trending

Quiet since April.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 4 mentionsApr 2026: 14 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the michaelneale/mesh-llm repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about michaelneale/mesh-llm

The biggest 5 of 18 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 18

Talked about on GitHub, Bluesky and Hacker News (18 times).

On GitHub · 15

10 more on GitHub

On Hacker News · 1

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

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.