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

Orgsci Writing Style

ASecurity

Use when polishing the prose of an Organization Science manuscript — front-loading the organizational argument and contribution, writing for an interdisciplinary micro-to-macro audience, and conforming to INFORMS author-date house style. Late-stage polish; do not invoke while the theoretical contribution is still unsettled.

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

Security Analysis

A100/100

Scanned 6/6/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Orgsci Writing Style?

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

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

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

Download with Pro
Files
SKILL.md
---
name: orgsci-writing-style
description: Use when polishing the prose of an Organization Science manuscript — front-loading the organizational argument and contribution, writing for an interdisciplinary micro-to-macro audience, and conforming to INFORMS author-date house style. Late-stage polish; do not invoke while the theoretical contribution is still unsettled.
---

# Writing Style (orgsci-writing-style)

## When to trigger

- The prose buries the argument or the contribution
- The paper reads to only one audience (pure micro or pure macro) when it should reach both
- Citations and formatting are not in INFORMS author-date style
- You are doing a final polish before submission

## Write for an interdisciplinary, micro-to-macro audience

Organization Science readers come from organization theory, strategy, sociology, economics, and psychology, and work at every level from individual to population. Write so that a macro reader follows a micro paper and vice versa: define constructs on first use, name the level of analysis explicitly, and translate discipline-specific jargon into organizational terms. The opening pages must make the **organizational phenomenon, the conversation joined, and the contribution** unmistakable — front-load the argument rather than withholding it until the discussion.

## INFORMS house style

- **Citations:** author-date, e.g., Norman 1977 or (Norman 1977); reference list alphabetical by author in journal style.
- **Format:** double-spaced, 1-inch margins, Garamond- or Times-New-Roman-like fonts (explicitly **no Helvetica Narrow**); minimize footnotes; PDF or MS Word.
- **Abstract:** **no more than 250 words.**
- **Anonymization:** for double-anonymous review, remove author names, affiliations, and acknowledgements, and write self-citations in the third person or suppress them.
- **Length:** respect the all-inclusive ~50-page norm; tighten prose rather than spilling into the appendix what belongs in the argument.

## Voice and structure

- Prefer active voice and a clear narrative line; the journal values readable theory.
- For inductive papers, let the data structure and process model anchor the narrative; for deductive papers, foreground the mechanism and propositions.
- State boundary conditions as part of the theory, not as hedging.
- Avoid effusive throat-clearing and avoid combative framing of prior work — engage it generously.

## Anti-patterns

- A first page that withholds the contribution until page 30.
- Discipline jargon left untranslated for the cross-level audience.
- Passive, nominalized prose that hides who does what.
- Helvetica Narrow, numeric citation styles, or an over-250-word abstract.

## Output format

```
【Front-loading】phenomenon + conversation + contribution clear on page 1?
【Audience reach】readable to both micro and macro readers; jargon translated?
【House style】author-date, no Helvetica Narrow, abstract ≤250 words, anonymized
【Length/voice】within ~50-page norm; active, non-combative
【Next step】orgsci-submission
```

Attribution

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

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

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

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

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 →