Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Gec Writing Style

ASecurity

Use when drafting or polishing the prose of a Global Environmental Change (GEC) manuscript so it reads for an interdisciplinary, policy-relevant audience within the word and abstract caps. GEC values clarity and rigor that travel across disciplines. Polishes the writing; it does not draft the analysis.

1,052 stars
0 votes
0 copies
1 views
Added 6/5/2026
ai-agentsgo

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill gec-writing-style --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Gec Writing Style?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Gec Writing Style
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-gec-writing-style/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-gec-writing-style)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: gec-writing-style
description: Use when drafting or polishing the prose of a Global Environmental Change (GEC) manuscript so it reads for an interdisciplinary, policy-relevant audience within the word and abstract caps. GEC values clarity and rigor that travel across disciplines. Polishes the writing; it does not draft the analysis.
---

# Writing Style (gec-writing-style)

A GEC paper must be **rigorous and readable across disciplines**. Reviewers and readers come from
environmental social science, governance, economics, geography, and the natural sciences, and many read
for policy relevance. Write so each of them can follow the argument — within the length caps.

## When to trigger

- Drafting the introduction, abstract, or discussion
- A reviewer said the paper is "hard to follow," "jargon-heavy," or "buries the contribution"
- Cutting to meet the word cap (Research Articles up to ~8,000 words; abstract ≤ ~250 words — verify)
- Writing the abstract and the plain-language framing

## What GEC prose does well

1. **Front-load the contribution.** The introduction states the human/policy problem, the gap, the
   framework, and the contribution within the first page — not after a long literature tour.
2. **Define terms once, use them consistently.** Contested concepts (vulnerability, resilience,
   governance, transition) get one definition and stick to it.
3. **Minimize discipline-specific jargon.** Explain unavoidable technical terms; an interdisciplinary
   reader should not need a glossary. Spell out acronyms on first use.
4. **Connect to scale and stakes.** Remind the reader why the result matters across scales and for
   societies — without overclaiming.
5. **Discussion that earns the conclusion.** Interpret results against the framework, state scope
   conditions and limitations honestly, and set up the policy implications (`gec-policy-relevance-and-implications`).

## The abstract (≤ ~250 words — verify on the live page)

- State the **problem, approach, key finding, and significance** for the human/policy dimension.
- Avoid undefined jargon; an editor from another field decides desk-fate partly on the abstract.

## Length discipline (verify caps)

- Research Articles **up to ~8,000 words** (excl. references); cut method minutiae to supplementary
  material rather than diluting the argument.
- Every section should advance the contribution; if a paragraph does not, cut or move it.

## Anti-patterns

- A long literature review before the reader knows the contribution
- Jargon or acronyms unexplained for an interdisciplinary audience
- Inconsistent use of a key concept across sections
- Overclaiming policy impact the evidence does not support
- Going over the word/abstract cap (front-page issue at submission)

## Output format

```
【Contribution stated by】page/paragraph (front-loaded? Y/N)
【Jargon check】terms defined; acronyms spelled out? [Y/N]
【Abstract】word count (≤ ~250) + states problem/approach/finding/significance?
【Length】within ~8,000 words (excl. refs)? [Y/N]
【Limitations】stated honestly? [Y/N]
【Next】gec-policy-relevance-and-implications
```

## Supplementary resources

- [`../../resources/external_tools.md`](../../resources/external_tools.md) — reference managers and typesetting
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — word/abstract caps and style notes

Attribution

brycewang-stanfordbrycewang-stanford
View sourceMore from brycewang-stanford →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1066601 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693161 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →