agentleFS
Google DeepMindKnown publishergoogle-deepmind/agentic_ecology/skills/agentic-ecology-camera-traps/SKILL.md

agentic-ecology-camera-traps

Skill11 starsChanged 2 months agoApache-2.0View on GitHub

Provides capabilities to run SpeciesNet detector and classifier on camera trap images, extract crop-level feature embeddings, and populate a Hoplite vector database for downstream search and agile modeling. Use when ingesting camera trap images, classifying wildlife photos, or indexing camera trap data.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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. Distinctive:

    Use this skill when you need to process a collection of camera trap images, run species classification, extract vector representation …

    line 14
  2. Distinctive:

    Follow these sequential steps:

    line 20
  3. Very specific:

    Create a Hoplite database (SQLiteUSearchDB) at the destination folder.

    line 28
  4. Distinctive:

    Run the detector model to get bounding box coords for animal detections.

    line 42
  5. Very specific:

    Commit database changes periodically and at the end of ingestion via db.commit() to persist SQLite rows and flush the USearch vector index …

    line 48
  6. Distinctive:

    Context Preservation: Avoid displaying raw cropped images in the result cards.

    line 55

≈ “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

Camera Traps Skill

Use this skill when you need to process a collection of camera trap images, run species classification, extract vector representation embeddings, and store them inside a Hoplite vector database.

Workflow Overview

Follow these sequential steps:

  1. Identify Dataset and Limits:
    • Locate the target camera trap images directory.
    • Assess if a GPU is available on the system. If running on CPU-only, discuss with the user or apply a processing limit (e.g., first 1000 images) to prevent the ingestion pipeline from running excessively long.
  2. Initialize Hoplite Database:
    • Create a Hoplite database (SQLiteUSearchDB) at the destination folder.
    • Configure it with an embedding dimension of 1280 (EfficientNet-V2 M feature size), the metric set to Cos, and the data type set to float16.
  3. Run Ingestion Pipeline:
    • Instantiate the SpeciesNetDetector and SpeciesNetClassifier models (if running in an environment with pre-mounted read-only models like /kaggle/input/ on Colab, copy the model directory to a local writable path first; see the Technical Reference).
    • Register a PyTorch forward hook on the classifier's average pooling layer (SpeciesNet/efficientnetv2-m/avg_pool/Mean_Squeeze__3825) to intercept raw embeddings.
    • For each image:
      • Insert it into the database as a recording.
      • Run the detector model to get bounding box coords for animal detections.
      • Crop the PIL image to the bounding box, preprocess it, and run the classifier to extract the 1280-dim embedding vector.
      • Cast the vector to float16 and insert it into the database as a window.
    • Commit database changes periodically and at the end of ingestion via db.commit() to persist SQLite rows and flush the USearch vector index to disk.
  4. Agile Modeling and Search:
    • Once populated, use the Hoplite database to perform vector searches (ranking by similarity) or train active learning classifiers on top of the embeddings.
  5. Camera Trap Visualization Guidelines (M3 UI):
    • Context Preservation: Avoid displaying raw cropped images in the result cards. Instead, display the original (uncropped) image inside the card container and draw the animal detection as a red border box overlay dynamically using CSS absolute positioning and percentages (e.g., left: xmin * 100%, top: ymin * 100%, etc.).
    • Full-Resolution Modal Preview: Implement a click handler on the card media that triggers a floating fullscreen modal containing the uncropped image and the aligned bounding box overlay to allow the user to verify low-confidence detections.
    • Custom Query Search Support: The backend server supporting the Web UI must implement on-the-fly embedding extraction for custom HTTP/S query URIs by downloading the image, running the detector to identify target bounding boxes, preprocessing the crop, and capturing the embedding vector using the PyTorch forward hook on the classifier.

Technical Reference

For detailed model loading code, Kaggle/Colab read-only filesystem workarounds, PyTorch hook embedding extraction, and bounding box calculations, see:

  • Camera Traps Technical Reference

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.