GeoGeekLab/nature-reviewer-skills / nature-earth-system-reviewer-skills/skills/polar-earth-system-review-orchestrator
polar-earth-system-review-orchestrator
VerifiedCross-disciplinary polar Earth-system manuscript review orchestrator for Arctic, Antarctic and Southern Ocean research. Routes claims to existing domain reviewer skills and applies polar-specific evidence gates for sparse observations, cryosphere variables, product dependence, conservation budgets, coupled attribution, paleoclimate archives and regional research responsibility.
gates/research_responsibility_governance.md
View on GitHub# Research Responsibility Governance
Indigenous/community governance, sensitive data, Antarctic permits, disturbance, policy scope and legal-review boundary.
## Internal questions
- **Indigenous knowledge is treated as extractable data:** Community or Indigenous knowledge is incorporated without evidence of appropriate governance, consent, attribution, benefit, or interpretive authority. Resolution: Describe co-design and governance, permissions, data stewardship, attribution, benefits, and limits on reuse; involve relevant knowledge holders in interpretation.
- **Community relevance is claimed without participation:** The paper makes claims about Arctic community needs, impacts, adaptation, or policy without meaningful participation by affected communities. Resolution: Document engagement and co-production or narrow the claim to biophysical findings without asserting community relevance.
- **Sensitive location data are released without safeguards:** Coordinates or ecological, cultural, archaeological, subsistence, or protected-species data are shared without a sensitivity assessment. Resolution: Apply appropriate access controls, aggregate or redact locations, and document governance decisions.
- **Antarctic protected-area or permit context is absent:** Research in or affecting protected areas, fauna, flora, or regulated sampling does not report relevant authorization or management-plan compliance. Resolution: Report permits and area status where applicable, describe compliance and impacts, and avoid legal conclusions beyond the evidence.
- **Research disturbance is not considered:** Field installation, drilling, sampling, wildlife approach, tracer release, vehicle use, or repeated visitation may alter the system being measured. Resolution: Assess and minimize disturbance, describe controls and permits, and discuss whether the signal could be method-induced.
- **Policy recommendation exceeds evidence:** A local, model-conditional, or observational result is translated into broad mitigation, conservation, shipping, or governance advice without decision analysis. Resolution: Separate scientific findings from normative recommendations, define the decision context, and state evidence and uncertainty required for policy claims.
- **Data sovereignty and authorship are unexplained:** Community-generated, national-program, expedition, or long-term monitoring data are used without clear stewardship, contributor recognition, or reuse terms. Resolution: Document data agreements, access conditions, contributor roles, and attribution; follow community and programme requirements.
- **Compliance review is presented as legal advice:** The manuscript or review infers that a project is legally compliant or noncompliant from incomplete reporting. Resolution: Flag missing documentation as a research-reporting risk and request authoritative confirmation rather than making a legal determination.
Use only when relevant to a central claim. Do not expose this gate name or pattern IDs in the final referee report.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |