agentleFS
MEKXHMEKXH/golem/skills/remote-sensing/SKILL.md

remote-sensing

Skill203 starsChanged 8 months agoMITView on GitHub

Guide agent through raster and satellite imagery analysis with the built-in, learned, and fabricated geo tools

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. BuildHarbor/sciagent-skills★ 1same name
    2. Muhammad-Tariq/webgis-claude-skills★ 1same name
    3. Pratikrishi97/sciagent-skills★ 1same name
    4. TerraLabAI/geoai-skills★ 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 repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 4 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the task involves satellite imagery, raster products, vegetation indices, terrain, or image preprocessing.

    line 8
  2. Very specific:

    If the user does not already provide raster files, discover likely datasets first with geo_data_catalog.

    line 11
  3. Very specific:

    Start with geo_info and geo_crs_detect.

    line 14
  4. Very specific:

    Before creating a new raster workflow, inspect whether pipelines/geo/ already captures a similar scene-prep or raster-analysis sequence.

    line 17
  5. Very specific:

    Use geo_format_convert when the result needs a simpler output format.

    line 23
  6. Very specific:

    If a raster workflow is clearly reusable and not covered by learned pipelines or built-in tools, fabricate a workspace geo tool under …

    line 26
  7. Distinctive:

    Prefer learned pipelines before fabricating a new raster tool.

    line 30
  8. Distinctive:

    Prefer GeoTIFF for raster outputs unless the user asks for a web-ready preview.

    line 31
  9. Distinctive:

    Keep all generated outputs inside the workspace.

    line 32

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

Remote Sensing Workflow

Use this skill when the task involves satellite imagery, raster products, vegetation indices, terrain, or image preprocessing.

Step 1: Discover Candidate Imagery

If the user does not already provide raster files, discover likely datasets first with geo_data_catalog.

Step 2: Inspect and Verify CRS

Start with geo_info and geo_crs_detect.

Step 3: Reuse Learned Pipelines First

Before creating a new raster workflow, inspect whether pipelines/geo/ already captures a similar scene-prep or raster-analysis sequence.

Step 4: Use GDAL for Raster Processing

Typical operations go through geo_process.

Step 5: Convert Deliverables

Use geo_format_convert when the result needs a simpler output format.

Step 6: Fabricate a Reusable Raster Tool

If a raster workflow is clearly reusable and not covered by learned pipelines or built-in tools, fabricate a workspace geo tool under tools/geo/.

Conventions

  • Prefer learned pipelines before fabricating a new raster tool.
  • Prefer GeoTIFF for raster outputs unless the user asks for a web-ready preview.
  • Keep all generated outputs inside the workspace.

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.