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 Workflow

ASecurity

Use when deciding which tar-* sub-skill to invoke next, or when sequencing manuscript work from topic selection through rebuttal for a The Accounting Review (TAR) manuscript. Routes — it does not replace — the specialized skills.

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-workflow --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Tar Workflow?

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

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

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

Download with Pro
Files
SKILL.md
---
name: tar-workflow
description: Use when deciding which tar-* sub-skill to invoke next, or when sequencing manuscript work from topic selection through rebuttal for a The Accounting Review (TAR) manuscript. Routes — it does not replace — the specialized skills.
---

# The Accounting Review Workflow (tar-workflow)

## Overview

This is the router. It does not replace any specialized skill; it tells you **which tar-* skill to use right now** for your TAR manuscript.

Default assumption: unless the user says otherwise, treat the target as **The Accounting Review (TAR)** — the flagship journal of the American Accounting Association (AAA, aaahq.org), covering archival/empirical and analytical accounting across financial accounting, capital markets, auditing and assurance, management accounting, taxation, and accounting information systems. TAR's stated policy is explicitly **open to all rigorous research methods** and names no preferred methodology; the single overriding publication criterion is the **significance of the contribution to the accounting literature**. In practice the published mix is dominated by large-sample archival/empirical work, alongside a substantial experimental stream and analytical/theory papers (待核实 as a characterization, not policy). The action editor and a minimum of two reviewers will ask "what do we learn about accounting that we did not know?" as hard as "is identification clean?"

> Editorial team: Senior Editor Kathryn Kadous (Emory), with Mohan Venkatachalam (Duke) succeeding her as Senior Editor in June 2026; named Lead Editors (Mittendorf, Maydew, Rennekamp, Hribar) handle assignments, decision letters, desk rejections, and appeals; Ad hoc Editors cover specialized topics/methods. Submission fee ($270 member / $645 non-member) and roster — 待核实; confirm on the official AAA pages.

## When to trigger

- "What should I do next?" with a half-built TAR manuscript
- You have a clean archival sample and a result but no sharp accounting contribution
- A reviewer pushes on identification, the data-authenticity/code-access policy, or contribution and you are unsure which stage is the bottleneck
- You received a TAR decision letter and need to switch into response mode
- You keep bouncing between identification, theory/model, and writing without a plan

## Routing table

| Current symptom                                                        | Next skill                  |
|------------------------------------------------------------------------|-----------------------------|
| Idea is vague; not sure it is contribution-driven or TAR-fit           | `tar-topic-selection`       |
| Predictions are descriptive; no economic mechanism or model            | `tar-theory-development`    |
| Front end reads as gap-spotting; the accounting conversation not joined | `tar-literature-positioning`|
| Design may not identify the effect (endogeneity, selection, timing)    | `tar-methods`               |
| Have data; unsure about estimator, clustering, FE, robustness          | `tar-data-analysis`         |
| Results exist but the "so what for accounting" is thin                 | `tar-contribution-framing`  |
| Tables/figures cluttered, off Chicago style, or not self-explanatory   | `tar-tables-figures`        |
| Prose is jargon-heavy, passive, or buries the result                   | `tar-writing-style`         |
| Ready to submit; need the Editorial Manager preflight                  | `tar-submission`            |
| Want to understand how TAR double-blind review/decisions work          | `tar-review-process`        |
| Received an R&R; need to plan and draft the response                   | `tar-rebuttal`              |

## Default order

1. `tar-topic-selection` — lock a contribution-driven question with TAR fit
2. `tar-theory-development` — build the economic mechanism / analytical model and predictions
3. `tar-literature-positioning` — engage the focal accounting literature; state the conversation
4. `tar-methods` — design identification (DiD, IV, RDD, setting, shock) matched to the question
5. `tar-data-analysis` — estimator, fixed effects, clustering, robustness, data-authenticity code
6. `tar-contribution-framing` — turn results into an explicit accounting contribution
7. `tar-tables-figures` — finalize main exhibits in Chicago house style
8. `tar-writing-style` — full-manuscript prose polish (result front-loaded, active voice)
9. `tar-submission` — Editorial Manager preflight (anonymization, AI disclosure, ORCID, files)
10. `tar-review-process` — set expectations for double-blind, multi-round review
11. `tar-rebuttal` — after an R&R, plan revisions then draft the response letter

> `tar-tables-figures` and `tar-writing-style` are **late-stage polish**. Do not invoke them while identification or the contribution is still unsettled — you will polish an argument you may still have to rebuild.

## Decision shortcuts

- "I have a finding but no accounting story" → `tar-topic-selection` then `tar-contribution-framing`
- "My intro says 'no one has studied X'" (gap-spotting) → `tar-literature-positioning`
- "My treatment is endogenous / staggered adoption" → `tar-methods` then `tar-data-analysis`
- "Reviewer asks for the code that builds my Compustat sample" → `tar-data-analysis` (data-authenticity)
- "An analytical model needs comparative statics" → `tar-theory-development`
- "Submitting this week" → `tar-submission`
- "Got an R&R with two reviewers + the editor" → `tar-review-process` then `tar-rebuttal`

## Difference vs. JAR / JAE and the AAA family

- **TAR**: AAA flagship; open to all rigorous methods, contribution-to-the-literature is the bar; double-blind review; Editorial Manager at editorialmanager.com/accr; 55-page initial limit; Chicago Manual of Style.
- **JAR** (Journal of Accounting Research, Chicago Booth) and **JAE** (Journal of Accounting and Economics, Elsevier) are the other two "top-3" archival accounting journals but are separately owned and run their own review and style norms — use a venue-specific stack.
- **Journal of Financial Reporting** is the one AAA journal using **single-blind** review; TAR is **double-blind**.

If your study is purely a methods demonstration with no accounting contribution, TAR is the wrong venue.

## Anti-patterns

- **Do not** skip `tar-theory-development` and report a correlation — TAR rejects atheoretical "regression-mining."
- **Do not** let `tar-tables-figures` beautify exhibits before identification and the contribution are settled.
- **Do not** let `tar-rebuttal` draft a response letter before you have actually revised the manuscript and the code.
- **Do not** treat `tar-writing-style` as a substitute for a clean identification strategy or a real contribution.

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 →