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

Jar Workflow

ASecurity

Use when deciding which jar-* sub-skill to invoke next, or when sequencing manuscript work from topic selection through rebuttal for a Journal of Accounting Research (JAR) 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 jar-workflow --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Jar Workflow?

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

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

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

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

# Journal of Accounting Research Workflow (jar-workflow)

## Overview

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

Default assumption: unless the user says otherwise, treat the target as the **Journal of Accounting Research (JAR)** — one of the "top three" accounting journals, founded in 1963, sponsored by the **Chookaszian Accounting Research Center at the University of Chicago Booth School of Business** and published with Wiley-Blackwell (five issues a year). JAR publishes original research in all areas of accounting drawing on finance, economics, statistics, psychology, and sociology, using analytical, empirical-archival, experimental, and field-study methods. Its defining identity is rigorous **empirical-archival capital-markets** research in the **Ball-Brown** lineage. The non-negotiable bar: a clean **identification** strategy answering a question that matters for how accounting information is produced, disclosed, audited, or used in markets — credible causal inference and an economic story weigh as heavily as a sound regression.

> Governance is by a panel of **Senior Editors** (Berger, Costello, Hail, Nikolaev, Sapra, van Lent, Wittenberg Moerman), not a single editor-in-chief; Editorial Manager Lisa M. Heiberger. Fees, the conference theme, and the masthead change — verify on the Chookaszian Center JAR pages. Three things make JAR distinctive: a **tiered submission fee** ($750/$500/$50), a **mandatory data-and-code sharing policy**, and the **Ray Ball JAR Annual Conference** with its June conference issue. Impact factor (~4.9, 2023) is **approximate**.

## When to trigger

- "What should I do next?" with a half-built JAR manuscript
- You have an archival result but no clean identification or economic story
- A referee pushes on endogeneity, the channel, or "what do we learn about accounting?"
- You received a JAR decision letter (R&R or reject) and need to switch into response mode
- You are weighing the **Registered Reports** track or a **Ray Ball Conference** submission

## Routing table

| Current symptom                                                          | Next skill                  |
|--------------------------------------------------------------------------|-----------------------------|
| Idea is vague; unsure it is a real accounting question or JAR-fit        | `jar-topic-selection`       |
| No economic mechanism; predictions are atheoretical correlations         | `jar-theory-development`    |
| Front end reads as gap-spotting; the accounting literature not engaged   | `jar-literature-positioning`|
| Design/identification may not support the causal claim                   | `jar-methods`               |
| Have data; unsure about clustering, endogeneity, measurement of constructs | `jar-data-analysis`       |
| Results exist but "so what for accounting" is thin                        | `jar-contribution-framing`  |
| Tables/figures cluttered, off house style, or not self-explanatory       | `jar-tables-figures`        |
| Prose buries the research design and the economic argument               | `jar-writing-style`         |
| Ready to submit; need the Research Exchange + fee + data/code preflight   | `jar-submission`            |
| Want to understand JAR review, fees, or the conference/RR tracks          | `jar-review-process`        |
| Received an R&R; need to plan revisions and draft the response            | `jar-rebuttal`              |

## Default order

1. `jar-topic-selection` — lock an accounting question with a credible setting and JAR fit
2. `jar-theory-development` — build the economic mechanism and sign the predictions
3. `jar-literature-positioning` — engage the accounting conversation; state the marginal contribution
4. `jar-methods` — choose the identification strategy and the sample/setting
5. `jar-data-analysis` — clustering, endogeneity, construct measurement, robustness
6. `jar-contribution-framing` — turn the estimate into a contribution to accounting knowledge
7. `jar-tables-figures` — finalize the main descriptive/results/identification exhibits
8. `jar-writing-style` — full-manuscript prose polish (design-forward, economically literate)
9. `jar-submission` — Research Exchange preflight (anonymization, fee, data-and-code package)
10. `jar-review-process` — set expectations for the editor-panel, multi-round process
11. `jar-rebuttal` — after an R&R, revise then draft the point-by-point response

> `jar-tables-figures` and `jar-writing-style` are **late-stage polish**. Do not invoke them while identification or the economic story is still unsettled.

## Decision shortcuts

- "Archival result, treatment looks endogenous" → `jar-methods` then `jar-data-analysis`
- "Two-way clustering vs. firm-only?" → `jar-data-analysis`
- "Referee says the channel is unidentified" → `jar-theory-development` then `jar-methods`
- "High-outcome-risk study with new data collection" → consider **Registered Reports** via `jar-review-process`
- "Targeting the Ray Ball Conference" → `jar-review-process` (deadline, eligibility) then the design skills
- "Submitting next week" → `jar-submission` (fee within a week; data/code package)
- "Got an R&R from the editor panel" → `jar-review-process` then `jar-rebuttal`

## Difference vs. TAR / JAE / RAST / CAR stacks

- **JAR**: Chicago Booth (Chookaszian Center) / Wiley; empirical-archival capital-markets identity; **requires** data-and-code sharing; tiered fee; Ray Ball Conference; Registered Reports. Identification + economic story weighted heavily.
- **The Accounting Review (TAR)**: American Accounting Association journal; broad scope; no equivalent mandatory replication-hosting infrastructure.
- **Journal of Accounting & Economics (JAE)**: Elsevier; positive/economics-based, contracting and disclosure; **encourages** rather than requires code sharing.
- **Review of Accounting Studies (RAST)** / **Contemporary Accounting Research (CAR)**: strong empirical outlets with their own scopes and norms.

If your paper is purely a methods/statistics contribution with no accounting question, or has no identification leverage, JAR is likely the wrong venue.

## Anti-patterns

- **Do not** skip `jar-theory-development` and present a regression with no economic channel.
- **Do not** let `jar-tables-figures` beautify exhibits before identification is settled.
- **Do not** start `jar-submission` without the runnable data-and-code package the policy requires.
- **Do not** let `jar-rebuttal` draft a response before the manuscript is actually revised.

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 →