Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Transparency & Spatial Data (aaag-transparency-and-data) — measured AI agent skill | DecimalAI

brycewang-stanford/aaag-transparency-and-data

NewSkillScoreMaintained

Use when handling data documentation, sharing, and spatial-data ethics for an Annals of the American Association of Geographers manuscript — provenance (sources, projections, processing), reproducibility, and geoprivacy / human-subjects protection. Prepares documentation; it does not over-state a verification gate the policy does not impose.

Documentationby brycewang-stanford

Links this skill to your agents and keeps it current with the author’s updates.

Automatic

Research pack

decimalai skills pull brycewang-stanford-aaag-transparency-and-data

Get this skill — curl · raw file

curl -fsSL https://app.decimal.ai/s/brycewang-stanford-aaag-transparency-and-data/SKILL.md

Raw file: /s/brycewang-stanford-aaag-transparency-and-data/SKILL.md ↗ · machine-readable summary at /s/brycewang-stanford-aaag-transparency-and-data.json ↗

In productionGlobal

how this skill behaves on real traffic · last 30 days

No production data for this skill yet — usage numbers appear here once agents start running it.

Anonymized aggregate across every org using this skill — proof from real production use, not a demo.

Does this skill help? · Benchmark: with vs. withoutsign in to run this on your agents

22 test cases from the publisher’s eval.yaml · each run twice on gemini-3.6-flash — with the skill injected, then without · last run 3h ago

Yes — +14% lift+21% tokens0% turns86% of whole cases pass with skill (19/22)

Test case	Without → With	Effect	Δ tokens	Δ turns
case-01	✗→✓	▲ Improved	15%	0%
case-02	✗→✓	▲ Improved	0%	0%
case-03	✗→✓	▲ Improved	51%	0%
case-07	✗→✓	▲ Improved	33%	0%
case-08	✗→✓	▲ Improved	24%	0%

Showing 5 of 22 cases

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v4 — 8/3/2026

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

brycewang-stanford / awesome-journal-skills

Annals-of-the-American-Association-of-Geographers-Skills/skills/aaag-transparency-and-data/SKILL.md

View on GitHub ↗

License MITImported 8/3/2026Version v1

Skill contents

SKILL.md

Transparency & Spatial Data (aaag-transparency-and-data)

The Annals (Taylor & Francis, for the AAG) follows publisher and disciplinary norms for data availability and research integrity rather than (as at some journals) a mandatory, editor-run replication check before publication. The right posture is: document spatial-data provenance thoroughly, share what you ethically can, and protect location privacy. Confirm the current data- availability / sharing policy on the Taylor & Francis journal page (检索于 2026-06；以官网为准).

When to trigger

Preparing data documentation, a data-availability statement, or supplementary materials
Deciding what spatial data can be shared given geoprivacy, IRB, license, or proprietary limits
Documenting qualitative or restricted location data so claims remain credible
A reviewer asked how others could verify or reproduce the spatial analysis

Spatial-data provenance (the geography-specific core)

Document enough that another geographer could locate, re-project, and rebuild the dataset:

Sources & licenses for every layer (census, satellite, OSM, administrative, field-collected),

with access dates and terms.

Projection / CRS and any re-projection; areal units and how they were defined or aggregated.
Processing chain — classification, geocoding, spatial joins, resampling, filtering — as a logged,

ordered pipeline, not "cleaned in GIS."

Temporal alignment — vintages of layers and how they were harmonized.

Geoprivacy & human subjects (overrides sharing)

Do not publish precise locations of identifiable individuals/households; use geographic masking

(aggregation, jittering, areal reporting) and state the method.

IRB/consent for interviews, fieldwork, and participatory mapping; protect informant and site identity.
Sensitive sites (sacred, endangered-species, conflict) may require deliberate spatial coarsening — say so.

Reproducibility (good practice even without a pre-publication gate)

Master script regenerates every table, figure, and map from raw/constructed data.
README/codebook: provenance, projections, construction steps, and how to reproduce each exhibit.
Seeds set for stochastic steps; software/package versions pinned (renv.lock / requirements.txt).
Restricted data: a data-availability statement explaining what is shared, what is not and why,

and an access path; provide synthetic/masked data so code can run where feasible.

Transparency posture by data type (geography-specific)

Because the Annals spans four areas, the availability expectation lands differently on different evidence. This grid keeps the posture honest; confirm mechanics against the current T&F policy.

| Data type | Typically shareable | Restricted | Provenance to document | |-----------|---------------------|------------|------------------------| | Public geospatial (census, OSM) | data + code | none | source, vintage, CRS, join keys | | Satellite / DEM | processing code + IDs | bulk imagery (host link instead) | sensor, dates, correction, resolution | | Field GPS of people/sites | masked/aggregated data | exact coordinates | masking method, IRB, consent | | Interviews / ethnography | coding scheme | identifiable transcripts/locations | anonymization, composite-disclosure note | | Proprietary/licensed layers | code + access path | the layer itself | license terms, how to obtain |

Checklist

] Every layer's source, license, access date, and CRS documented
] Processing pipeline logged (classification/geocoding/joins/resampling)
] Geoprivacy handled — masking method stated for identifiable locations
] IRB/consent documented for human-subjects and field/participatory work
] Master script + README + seeds + pinned versions (where quantitative)
] Data-availability statement drafted; access path / synthetic data for restricted layers
] Current T&F data policy confirmed (do not assert a gate it does not impose)

Anti-patterns

"Data cleaned in GIS" with no provenance, CRS, or processing log
Publishing exact coordinates of vulnerable people or sensitive sites
Claiming open data that license or geoprivacy will not permit
Asserting an editor-verified replication mandate the policy does not state
Un-seeded, unpinned code that "works on my machine"

Output format

【Provenance】sources + licenses + CRS + processing log documented? [Y/N]
【Geoprivacy】masking/aggregation for identifiable locations? [Y/N/NA]
【Human subjects】IRB/consent handled? [Y/N/NA]
【Reproducibility】master script + README + seeds + versions? [Y/N]
【Data-availability statement】shared / restricted (why) / access path / synthetic?
【Policy check】current T&F data policy confirmed? [Y/N/待核实]
【Next】aaag-review-process

Supplementary resources

../../resources/external_tools.md — reproducibility tooling, repositories, and geomasking options
../../resources/official-source-map.md — T&F data-availability and AAG ethics references

Want to see if brycewang-stanford/aaag-transparency-and-data would activate on your phrasing? Try it before you install — no LLM call, no signup.

Other measured skills in the registry, with their headline benchmark lift.