agentleFS
open-edge-platformopen-edge-platform/training_extensions/skills/application/geti-runtime-running-live-inference/SKILL.md

geti-runtime-running-live-inference

Skill1.4k starsChanged 17 days agoApache-2.0View on GitHub

Run and operate live inference in the Geti application pipeline. Use when a user wants to start, monitor, stop, or recover source -> model -> sink runtime execution, verify production readiness, or troubleshoot live pipeline behavior such as stalls, dropped outputs, and latency regressions.

1 other project uses a version of this.

Trending

More talk lately.about the whole repository

Dec 2025: 1 mentionJan 2026: 4 mentionsFeb 2026: 2 mentionsMar 2026: 2 mentionsApr 2026: 7 mentionsMay 2026: 2 mentionsJun 2026: 3 mentionsJul 2026: 2 mentionsAug 2026: 3 mentionsSep 2026: 4 mentionsOct 2026: 9 mentionsNov 2026: 5 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the open-edge-platform/training_extensions repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about open-edge-platform/training_extensions

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

See all 50

Talked about on GitHub (50 times).

On GitHub · 50

45 more on GitHub

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for operational control of live inference in Geti.

    line 8
  2. Distinctive:

    Check the pipeline status (Idle vs Running).

    line 33
  3. Distinctive:

    Verify frames are rendered with predictions, inference output is generated as per sink configuration.

    line 34
  4. Distinctive:

    If source degrades: reconnect or switch to a known-good source.

    line 40
  5. Distinctive:

    If model output degrades: verify loaded model version and thresholds.

    line 41
  6. Distinctive:

    If sink fails: apply fallback sink.

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Geti Runtime: Running Live Inference

Use this skill for operational control of live inference in Geti. This skill is for runtime execution and monitoring, not code changes.

When to Use

  • User asks how to start or stop live inference for a configured pipeline.
  • User needs runbook-style checks for runtime health and correctness.
  • User reports stalls, dropped outputs, or latency spikes during live execution.
  • User needs incident-style recovery steps with minimal disruption.

Scope

  • In scope: runtime start and stop flow, status monitoring, health verification, rollback and recovery.
  • Out of scope: backend implementation changes and model retraining.

Procedure

  1. Pre-flight checks.
    • Confirm pipeline configuration is complete (source, model, sink).
    • Confirm model is loaded and selected.
    • Confirm endpoints for source and sink are reachable.
  2. Start live inference.
    • Enable runtime execution through the application pipeline workflow.
    • Capture execution identifiers and current status.
  3. Monitor execution.
    • Check the pipeline status (Idle vs Running).
    • Verify frames are rendered with predictions, inference output is generated as per sink configuration.
    • Record key runtime metrics if available (throughput & latency).
  4. Validate output quality.
    • Spot-check predictions against known scenes or samples.
    • Confirm class distribution and confidence values are reasonable.
  5. Handle degradation.
    • If source degrades: reconnect or switch to a known-good source.
    • If model output degrades: verify loaded model version and thresholds.
    • If sink fails: apply fallback sink.

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.