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

Tar Writing Style

ASecurity

Use when polishing the prose of a The Accounting Review (TAR) manuscript — front-loading the result, writing for an accounting audience, enforcing Chicago Manual of Style house conventions, the 150-word abstract, and full author anonymization for double-blind review. Polishes prose and style; it does not fix a thin contribution (tar-contribution-framing) or run the submission preflight (tar-submission).

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

Works with

api

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Tar Writing Style?

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

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

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

Download with Pro
Files
SKILL.md
---
name: tar-writing-style
description: Use when polishing the prose of a The Accounting Review (TAR) manuscript — front-loading the result, writing for an accounting audience, enforcing Chicago Manual of Style house conventions, the 150-word abstract, and full author anonymization for double-blind review. Polishes prose and style; it does not fix a thin contribution (tar-contribution-framing) or run the submission preflight (tar-submission).
---

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

## When to trigger

- The intro buries the result; the reader cannot tell the finding by the end of page 2
- The prose is passive, jargon-laden, or written for a generic business audience
- References are in APA or a reference-manager default rather than Chicago
- The abstract exceeds 150 words or the manuscript leaks author identity
- A reviewer says "hard to follow," "what did you find?", or flags style issues

## Write for the accounting reader, result first

TAR's audience is accounting researchers, editors, and a minimum of two expert reviewers. The intro
should, within the first page or two, state **the question, the setting/identification, the finding,
and the contribution** — do not make the reader wait for the result. Use the standard archival
structure (introduction, hypothesis/model development, research design, results, conclusion) and
keep terminology precise: "discretionary accruals," "abnormal audit fees," "cash effective tax
rate," "cost of equity capital" mean specific things — use them exactly.

## TAR house style (verify against the AAA Manuscript Preparation Guide)

- **Citations & references:** **The Chicago Manual of Style (16th ed.)** — *not* APA. Configure your
  reference manager to a Chicago author-date style and reconcile by hand.
- **Spelling:** Webster's Collegiate Dictionary.
- **Abstract:** **no more than 150 words**, beginning the article file; concrete about question,
  setting, finding, and contribution — not a teaser.
- **Manuscript format:** 12-pt Times New Roman, double-spaced, 1-inch margins, serially numbered
  pages; initial submission within the 55-page limit (including references, tables, figures,
  appendices).
- **AI disclosure statement:** placed immediately after the abstract and before the body (drafted
  here, finalized in `tar-submission`).

## Anonymization is a writing task, not just a file task

Double-blind review means the prose itself must not identify the authors. Write self-citations in
the third person ("consistent with prior work (Author 2020)"), not "in our earlier study"; remove
acknowledgments, funding, institution names, and data-provider thank-yous from the manuscript body;
neutralize tell-tale phrasing that points to a known research group.

## Prose discipline

- Prefer active voice and short declaratives; one idea per sentence.
- Define every construct at first use; avoid undefined acronyms.
- State hypotheses/predictions in plain directional terms.
- Be precise about causality in words (mirror the calibration from `tar-contribution-framing`).
- Cut throat-clearing ("It is important to note that...") and redundancy to protect the page budget.

## Checklist

- [ ] The finding and contribution are stated on the first page or two
- [ ] References and citations follow Chicago (16th ed.), not APA
- [ ] Abstract ≤ 150 words and concrete (question, setting, finding, contribution)
- [ ] Accounting terminology is precise and consistent throughout
- [ ] Manuscript is anonymized in prose (third-person self-cites; no acknowledgments/funding inline)
- [ ] Format matches the AAA guide (12-pt TNR, double-spaced, 1-inch margins, numbered pages)
- [ ] AI disclosure statement drafted for placement after the abstract

## Anti-patterns

- **Buried lede**: the result appears only in the results section.
- **APA references** straight from the reference manager (TAR uses Chicago).
- **150-word abstract overflow** or a vague teaser abstract.
- **Self-identifying prose** ("our 2019 paper") defeating double-blind review.
- **Imprecise accounting terms** used loosely or interchangeably.
- **Passive throat-clearing** that wastes the 55-page budget.

## Output format

```
【Lede】finding + contribution on page 1–2? yes/no
【House style】Chicago references? Webster spelling? format ok? yes/no
【Abstract】≤150 words and concrete? yes/no
【Anonymization (prose)】third-person self-cites; no inline acknowledgments? yes/no
【Terminology】accounting terms precise and consistent? yes/no
【AI disclosure】drafted for post-abstract placement? yes/no
【Next step】tar-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', ...

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 →