geospatial-skills
Copilot instructions78 starsChanged 8 months agoApache-2.0View on GitHub
Prioritize skill packaging correctness over generic style feedback.
Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.
Of the Copilot instructions files we read, the 2,343 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository19 other files it gives its agents.
- detect-objectsSkill
- gdalSkill
- geoparquet-validationSkill
- geospatial-frontendSkill
- geospatial-viewersSkill
- geozarrSkill
- overture-dataSkill
- parallel-geospatialSkill
- planet-bulk-downloadSkill
- pmtiles-pipelineSkill
- portolan-bootstrapSkill
- portolan-cliSkill
- portolan-thumbnailsSkill
- reading-portolanSkill
- register-catalogSkill
- search-stacSkill
- sourcecoopSkill
- tesseraSkill
- zarr-multiscalesSkill
The file
We split this copilot-instructions.md into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
if a source skill has references/, the Claude plugin copy has matching references
≈ “Common” is an estimate: at least 1 in 5 of the 3,779 Copilot instructions 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.
Files
Copilot Review Instructions
Prioritize skill packaging correctness over generic style feedback.
Review for
- each public skill lives under
skills/<name>/ - each Claude plugin lives under
plugins/<name>/ - each portable skill includes
skills/<name>/SKILL.md - each Claude plugin includes
plugins/<name>/.claude-plugin/plugin.json - each Claude plugin includes
plugins/<name>/skills/<name>/SKILL.md .claude-plugin/marketplace.jsonentries pointsourceto./plugins/<name>- plugin
namefields match the public skill slug - docs skill page paths and nav entries match actual skill slugs
- homepage catalog lists every public skill
- homepage catalog includes attribution like
Referenced from ... SKILL.mdfiles preserve valid YAML frontmatter- if a source skill has
references/, the Claude plugin copy has matching references - universal install examples use
.agent/skills/<name>
Flag as bugs
- stale old skill names after a rename
- marketplace entries pointing at repo root instead of plugin folders
- install commands pointing to the wrong skill slug
- missing docs pages for public skills
- broken or mangled
SKILL.mdfrontmatter - CI scripts validating the wrong directory layout
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
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.