Find the best CLAUDE.md, AGENTS.md and Claude skills

One search for your own team's files and the public ecosystem. See how real projects write their agent instructions, and bring the good ideas home.

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.

Worked for most · soon

jaakla Hiding risky files

jaaklaAGENTS.md

openmapstack

jaakla/openmapstack/AGENTS.md

This file is the canonical maintainer guide for coders (including AI coding agents) working on the OpenMapStack repository. Keep repository-wide development guidance here and keep it vendor-neutral. OpenMapStack is a managed agent-skill codebase, not an OpenMapStack GIS analysis project. The repository develops and quality-assures a distributable geospatial agent skill: Do not treat a shipped SKILL.md as maintainer instructions for this repository. Read or edit it when the task concerns the shipped skill behavior, but do not preload or follow its…

7645d agoReviewMount

jaaklaCLAUDE.md

openmapstack

jaakla/openmapstack/CLAUDE.md

Repository-wide maintainer instructions are vendor-neutral and live in AGENTS.md. Keep this file as a thin Claude Code bootstrap only; do not add generic project guidance here.

7645d agoReviewMount

jaaklaSkill

neon-postgres-egress-optimizer

jaakla/openmapstack/.claude/skills/neon-postgres-egress-optimizer/SKILL.md

Diagnose and fix excessive Postgres egress (network data transfer) in a codebase. Use when a user mentions high database bills, unexpected data transfer costs, network transfer charges, egress spikes, "why is my Neon bill so high", "database costs jumped", SELECT * optimization, query overfetching, reduce Neon costs, optimize database usage, or wants to reduce data sent from their database to their application. Also use when reviewing query patterns for cost efficiency, even if the user doesn't explicitly mention egress or data transfer.

4 projects use a version of this

7645d agoReviewMount

jaaklaSkill

geospatial-data-discovery

jaakla/openmapstack/skills/geospatial-data-discovery/SKILL.md

Find and assess authoritative geospatial datasets or catalogs against known requirements: coverage, feature meaning, access, license, completeness, versions and reproducible pinning. Use for public sources, STAC/Portolan catalogs and read-only discovery of user data. Route joint source/compute/storage/delivery architecture to open-map-stack; do not turn a bounded lookup into a full analysis project.

7645d agoReviewMount

jaaklaSkill

open-map-stack

jaakla/openmapstack/skills/open-map-stack/SKILL.md

Plan and execute ambiguous or multi-stage GIS work, jointly choosing authoritative sources, compute, storage and delivery for the scale and team. Covers vector/raster/point-cloud analysis, routing, QGIS, tiles and web maps. Use for unresolved geospatial architecture and end-to-end analysis; prefer installed geospatial-data-discovery, spatial-sql or reproducible-gis-project for their bounded tasks. Retains standalone GIS support when specialists are absent. Do not use for casual place lookups, ordinary travel directions or non-spatial coding.

7645d agoReviewMount

jaaklaSkill

reproducible-gis-project

jaakla/openmapstack/skills/reproducible-gis-project/SKILL.md

Compile, validate or maintain a reproducible GIS project from an existing analysis or chosen workflow: project.yaml, canonical pipeline, pinned sources, executable corrections, validation, reruns and QGIS/web presentation. Use when delivery and reproducibility are the task. Route unresolved source/compute/storage architecture to open-map-stack; a bounded SQL review or dataset lookup does not need a project.

7645d agoReviewMount

jaaklaSkill

spatial-sql

jaakla/openmapstack/skills/spatial-sql/SKILL.md

Write, review, debug or optimize spatial SQL on an already chosen engine, including DuckDB Spatial, PostGIS, BigQuery GIS, Snowflake and Sedona. Use for spatial predicates, joins, indexes, query plans, CRS and metric/geodesic correctness. Route unresolved engine or cross-system architecture choices to open-map-stack; ordinary non-spatial SQL and casual place questions are outside this skill.

7645d agoReviewMount

CLAUDE.md vs AGENTS.md

Agent instruction files

What are agent instruction files?

Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.

CLAUDE.md or AGENTS.md?

CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.

What is a skill?

A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.

Can I search my own team's files too?

Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.