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

Conbio Writing Style

ASecurity

Use when drafting or polishing a Conservation Biology manuscript so it reads accessibly for a broad conservation audience, follows the journal Style Guide, and fits the per-type word caps (e.g., Contributed Papers ~6,000–7,000; abstract <= 300 words). Tightens prose and format; it does not invent content.

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 conbio-writing-style --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Conbio Writing Style?

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

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

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

Download with Pro
Files
SKILL.md
---
name: conbio-writing-style
description: Use when drafting or polishing a Conservation Biology manuscript so it reads accessibly for a broad conservation audience, follows the journal Style Guide, and fits the per-type word caps (e.g., Contributed Papers ~6,000–7,000; abstract <= 300 words). Tightens prose and format; it does not invent content.
---

# Writing Style (conbio-writing-style)

A *Conservation Biology* paper must be readable by conservation scientists and practitioners beyond
the author's own system, formatted to the journal **Style Guide**, and disciplined to the per-type word
cap. This skill is about clarity, accessibility, and format — not about generating claims. (Verify the
current per-type caps; they drift between Style Guide versions — see `resources/official-source-map.md`.)

## When to trigger

- Drafting the introduction, framing the contribution, or final polish
- Over the word cap and needing to cut without losing the argument
- Writing the **≤ 300-word abstract**
- Aligning citations/headings/format to the Style Guide before submission

## Reach a broad conservation audience

1. **Front-load the conservation contribution.** By the end of the introduction the reader knows the
   problem, the question, the approach, and **why it matters for conserving biodiversity.** Don't make
   a generalist dig for the "so what."
2. **Minimize system jargon** or define it on first use; a practitioner should follow a population-model
   paper, and a modeler should follow a field study. Spell out acronyms; use accepted species names.
3. **Argument-first prose.** Lead with claims; use evidence to support them. Avoid "the data show…"
   without saying what they show and why it matters for conservation.
4. **Signpost and follow IMRAD.** Contributed Papers, Research Notes, and Practice & Policy follow
   Abstract → Introduction → Methods → Results → Discussion; do not combine Results and Discussion, and
   do not add a separate Conclusion (conclusions belong in the Discussion).

## Format to the Style Guide

- **Citations**: author-date per the journal Style Guide; keep one consistent style (manage with
  Zotero/BibTeX). Literature Cited is included in the word count.
- **Title**: clear and concise; avoid hanging (colon/dash) titles, full-sentence titles, and
  interrogative titles per the Style Guide.
- **Anonymize**: the journal is **double-blind** — no author names/affiliations in the manuscript, and
  neutralize obvious self-references; strip identifying file metadata (see `conbio-submission`).
- **Abstract**: **≤ 300 words**, stating problem, approach, and finding (no abstract for Letters,
  Comments, or Diversity).

## Fit the word cap (count runs from first word of Abstract through last word of Literature Cited)

- Note: the count **excludes tables, figure legends, and text inside tables.** Move full model output,
  balance tables, and extended robustness to **Supporting Information**.
- Cut throat-clearing and literature dumps; engage the debate, not every paper (see
  `conbio-literature-positioning`).
- Prefer one decisive figure to three redundant tables (and respect the ~one-exhibit-per-four-pages rule).

## Anti-patterns

- A system-insider intro that never states conservation relevance
- Burying the contribution in the middle of the paper
- An abstract over 300 words or one that hides the finding
- Hanging/interrogative/full-sentence titles; mixed citation styles
- Self-references that break the double-blind; padding a Research Note toward Contributed-Paper length

## Output format

```
【Conservation contribution stated by end of intro?】[Y/N]
【Reads past the system?】jargon defined / acronyms spelled? [Y/N]
【Abstract】word count (≤300)
【Word count】within the article-type cap (Abstract→Literature Cited)?
【Style Guide + anonymized + title style】[Y/N]
【Next】conbio-conservation-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, Style Guide, IMRAD, title rules

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.

651 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 →