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

Smj Writing Style

ASecurity

Use for late-stage prose polish of a Strategic Management Journal (SMJ) manuscript — clarity, structure, and house style. Improves the writing; it does not change the theory, analysis, or contribution claim.

1,052 stars
0 votes
0 copies
0 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 smj-writing-style --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Smj Writing Style?

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

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

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

Download with Pro
Files
SKILL.md
---
name: smj-writing-style
description: Use for late-stage prose polish of a Strategic Management Journal (SMJ) manuscript — clarity, structure, and house style. Improves the writing; it does not change the theory, analysis, or contribution claim.
---

# Writing Style & House Conventions (smj-writing-style)

## When to trigger

- Theory, analysis, and contribution are settled and you are polishing the full draft
- Prose is jargon-heavy, hedged, or buries the argument
- Section structure does not follow the expected strategy-empirical arc
- Reviewers flagged readability, redundancy, or an unclear through-line

> Polish late. Editing prose while the identification strategy or contribution is unsettled wastes effort — return to the earlier skills first.

## Expected structure (full empirical paper)

Introduction → Theory & Hypotheses → Methods (sample, measures, identification) → Results → Discussion (contribution, implications, limitations, future research) → References. Theory-building qualitative and formal papers vary this arc but still foreground the strategy contribution early.

- **Introduction** does heavy lifting: motivate, name the conversation, state the gap and the contribution, preview the design and findings. A reader should know your contribution by the end of page two.
- **Discussion** must add interpretation, not re-list results: what the findings mean for strategy theory, boundaries, honest limitations, and a forward agenda.

## Style rules SMJ readers reward

- **Argument-first sentences.** Lead with the claim; supporting detail follows. Avoid burying the point at the end of a long clause.
- **Active, precise verbs.** "We show / we find / the design rules out" beats "it could be argued that there may be a relationship."
- **Define constructs once, use consistently.** Do not switch between near-synonyms for the same variable.
- **Hedge only where warranted.** Over-hedging ("may possibly suggest a potential tendency") reads as weak evidence; state what the design supports and stop.
- **Signpost.** Each section opens by stating its job and how it connects to the argument.
- **Cut redundancy.** Intro, theory, and discussion should not repeat the same paragraphs; each advances the argument.
- **Strategy vocabulary, used correctly.** Use field terms (rents, isolating mechanisms, dynamic capabilities, governance) precisely — misuse signals an outsider.

## House conventions (verify current Author Guidelines)

- **Two abstracts**, each up to **125 words**: a *research summary* (precise, stands alone, no citations) **and** a *managerial summary* (plain, non-academic, for practitioners). This dual-summary requirement is distinctive to SMJ — AMJ and ASQ ask for a single abstract — so budget real time for the managerial summary.
- **Five (5) keywords** for indexing.
- **APA author-date** references ("(Author, 2021)"; "(Collins, 2005a, 2005b)") — set your citation manager to APA, not a default style.
- Respect the page budget (full articles ~40 pages incl. tables/figures/references; short research articles ~20 — verify the current limit on the official page); references single-spaced to conserve space.
- US spelling and standard academic register; expand acronyms on first use.

## Checklist

- [ ] Contribution is clear by the end of the introduction's second page
- [ ] Structure follows intro → theory → methods → results → discussion (or a justified variant)
- [ ] Sentences lead with the claim; verbs are active and precise
- [ ] Constructs are defined once and named consistently throughout
- [ ] Hedging is proportionate to the evidence
- [ ] No paragraph is repeated across intro/theory/discussion
- [ ] Discussion interprets (theory implications + limits + agenda), not re-lists
- [ ] Both summaries written: research summary (≤125 words) AND managerial summary (≤125 words); 5 keywords
- [ ] References in APA author-date style; headings/length match current SMJ guidelines (verified, not assumed)

## Anti-patterns

- Submitting one abstract when SMJ requires two (research + managerial); a managerial summary written in academic jargon
- A bland abstract that hides the contribution
- Throat-clearing introductions that delay the point for two pages
- Over-hedged prose that makes solid findings read as tentative
- Inconsistent construct naming across sections
- A discussion that restates the results table in prose
- Misused strategy jargon that signals the author is outside the field
- Guessing at format rules instead of checking the live author guidelines

## Output format

```
【Structure OK?】yes / fix: [...]
【Contribution visible by p.2?】yes / no
【Hedging level】appropriate / over-hedged
【Construct naming consistent】yes / fix
【Redundancy cut】[sections trimmed]
【Dual abstracts (≤125 each) + 5 keywords】present / fix
【Format vs. guidelines】APA author-date; verified on official page / to verify
【Next step】smj-submission
```

## Templates & resources

- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — SMJ dual-abstract, 5-keyword, APA reference, and page-limit rules

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', ...

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