JF Garbage Overflow Inspection for Openclaw

An AI-powered JF camera inspection skill that captures images, detects garbage overflow, and produces actionable inspection reports.

jftech
v1.0.1
Oct 8, 2026
0
482
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install jf-open-pro-garbage-inspection

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install jf-open-pro-garbage-inspection using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is JF Garbage Overflow Inspection?

JF Garbage Overflow Inspection connects JF monitoring devices with an AI agent that captures and downloads camera images, visually analyzes garbage-bin conditions, and classifies each inspection as normal, minor overflow, severe overflow, or indeterminate. It supports individual cameras, batch inspections, offline-device reporting, and image presentation for transparent review.

As part of Openclaw Skills, it provides a practical workflow for environmental sanitation teams, property managers, and facility operators. Persistent camera configuration, configurable detection sensitivity, structured JSON capture results, and scheduled IM notifications make recurring garbage inspections easier to operate and audit.

JF Garbage Overflow Inspection Use Cases

  • Inspect one specific garbage bin on demand using its device serial number or configured name.
  • Run a batch inspection across all configured JF cameras and prioritize severe overflow conditions.
  • Detect garbage extending beyond the bin rim, waste hanging from the edge, litter on the ground, or lids that cannot close properly.
  • Manage inspection cameras by listing configured devices, adding bound devices, or removing obsolete entries.
  • Configure low, moderate, or high overflow sensitivity for different sanitation requirements.
  • Schedule daily, twice-daily, or custom cron-based inspections and send summarized results to an IM conversation.
  • Review downloaded inspection images alongside the AI-generated report when visual verification is required.
  • Diagnose offline devices, capture API failures, download errors, missing credentials, and images that cannot be reliably analyzed.

How JF Garbage Overflow Inspection Works

  1. The agent checks the environment and reads config/cameras.json to determine whether credentials and inspection cameras are configured.
  2. When a camera must be added, it uses jf-open-pro-device-list to find bound devices and jf-open-pro-device-status to confirm that the selected device is online.
  3. The agent stores the selected device serial number, display name, password, location, and inspection settings in the persistent camera configuration.
  4. For an inspection request, it selects either one matching camera or all configured cameras.
  5. scripts/capture_and_download.py authenticates with the JF API, captures an image, downloads it locally, and returns JSON results for each device.
  6. The agent reads each successful image and checks for visible garbage bins, overflow beyond the rim, hanging waste, ground litter, lid condition, tilt, image quality, and other relevant observations.
  7. Based on overflow_threshold, it assigns one of four outcomes: normal, minor overflow, severe overflow, or unable to determine.
  8. The agent aggregates successful, failed, offline, and indeterminate results into a report ordered from most severe to least severe.
  9. Captured images are presented to the user with present_files so each reported result can be visually verified.
  10. For recurring inspections, a qoder_cron task repeats capture, image analysis, report generation, and IM delivery on the selected schedule.

JF Garbage Overflow Inspection Setup

1. Install the Python dependency

pip install requests

2. Configure JF API credentials

Set the required environment variables before running an inspection:

export JF_UUID="your-user-uuid"
export JF_APP_KEY="your-app-key"
export JF_APP_SECRET="your-app-secret"
export JF_MOVE_CARD="2"
export JF_ENDPOINT="api-cn.jftechws.com"

Use the regional endpoint appropriate for the deployment: api-cn.jftechws.com, api-as.jftechws.com, api-eu.jftechws.com, or api-na.jftechws.com. JF_ENDPOINT is optional and defaults to the China endpoint.

3. Prepare device prerequisites

Ensure each JF monitoring device has completed network configuration and binding, is online, and is available through the dependent jf-open-pro-device-list and jf-open-pro-device-status skills.

4. Configure inspection cameras

Create config/cameras.json with the devices and analysis settings:

{
  "cameras": [
    {
      "sn": "device-serial-number",
      "name": "Building A Floor 1 Garbage Bin",
      "password": "device-password",
      "location": "Building A Lobby"
    }
  ],
  "settings": {
    "overflow_threshold": "moderate",
    "default_channel": 0
  }
}

5. Run a batch inspection

PYTHONIOENCODING=utf-8 python {skill_dir}/scripts/capture_and_download.py \
  --action inspect-batch \
  --config {skill_dir}/config/cameras.json \
  --output-dir {workspace}/captures/{YYYYMMDD}/ \
  --json

6. Run a single-device inspection

PYTHONIOENCODING=utf-8 python {skill_dir}/scripts/capture_and_download.py \
  --action inspect-single \
  --device-sn "device-serial-number" \
  --device-name "Building A Garbage Bin" \
  --device-location "Building A Lobby" \
  --output-dir {workspace}/captures/{YYYYMMDD}/ \
  --json

The agent then reads successful image files, analyzes them, generates the inspection report, and presents the captured images. Keep device passwords and API secrets protected because they are used for authentication and token retrieval.

JF Garbage Overflow Inspection Data Schema & Taxonomy

Configuration file

Path or field Purpose
config/cameras.json Persistent inspection camera and analysis configuration
cameras[] Array of configured JF inspection devices
cameras[].sn Unique JF device serial number
cameras[].name Human-readable camera or garbage-bin name
cameras[].password Device password used to obtain an access token
cameras[].location Location context included in reports
settings.overflow_threshold Sensitivity: low, moderate, or high
settings.default_channel Default camera capture channel, normally 0

Generated files and result data

  • scripts/capture_and_download.py handles capture, download, authentication, and JSON output.
  • scripts/crypto.py provides signing, encryption, and timestamp utilities imported by the capture script.
  • {workspace}/captures/{YYYYMMDD}/ stores downloaded inspection images grouped by inspection date.
  • The capture script returns JSON entries containing device metadata, success or failure status, image file paths, and error information.
  • Successful image paths are read for visual analysis and supplied to present_files for user review.

Report taxonomy

Status Meaning
normal Bin is not full or only just full, with a clean rim and no external overflow
minor overflow Waste slightly exceeds the rim, limited waste is outside, or the lid may not fully close
severe overflow Significant waste is outside the bin or visible litter is spread on the ground
unable to determine The bin is not visible or the image is too dark, blurry, obstructed, or poorly framed
offline / failed Device status, capture API, or image download operation failed

Reports include inspection time, total devices, successful and failed counts, device name, serial number, location, status, analysis details, failure reasons, and a prioritized summary.

JF Garbage Overflow Inspection Advanced Features

  • Supports both single-device and batch inspection modes through a reusable CLI.
  • Uses dependent device-list and device-status skills to discover bound JF devices and validate online status before configuration.
  • Provides configurable overflow sensitivity: low flags only severe overflow, moderate also flags minor overflow, and high treats bins near approximately 80% capacity as abnormal.
  • Handles multiple garbage bins visible in one image by evaluating them individually.
  • Preserves location and device metadata so reports remain actionable for field teams.
  • Includes explicit failure taxonomy for offline devices, API errors, download failures, missing credentials, and poor image quality.
  • Automatically retries an image download once before marking the device as failed.
  • Presents all successfully captured images after the text report for visual auditability.
  • Supports scheduled automation through qoder_cron, including custom cron expressions and IM-channel delivery.
  • Can query available IM conversations with qoder_list_channel_conversations so scheduled reports reach the selected recipient.
  • Uses region-specific JF API endpoints for China, Asia, Europe, and North America deployments.
  • Fits Openclaw Skills workflows by combining persistent configuration, command-line capture, agent vision analysis, structured reporting, and scheduled notifications.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*