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 Literature Positioning

ASecurity

Use when the front end of a The Accounting Review (TAR) manuscript reads as gap-spotting or an incremental database extension — positioning the paper inside a live accounting conversation against the closest TAR/JAR/JAE/CAR work. Positions the contribution; it does not derive the mechanism (tar-theory-development) or write the contribution paragraph (tar-contribution-framing).

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

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-literature-positioning --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Tar Literature Positioning?

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

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

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

Download with Pro
Files
SKILL.md
---
name: tar-literature-positioning
description: Use when the front end of a The Accounting Review (TAR) manuscript reads as gap-spotting or an incremental database extension — positioning the paper inside a live accounting conversation against the closest TAR/JAR/JAE/CAR work. Positions the contribution; it does not derive the mechanism (tar-theory-development) or write the contribution paragraph (tar-contribution-framing).
---

# Literature Positioning (tar-literature-positioning)

## When to trigger

- Your intro says "no prior study examines X" (gap-spotting) instead of joining a debate
- The paper looks like "Smith (2015) on a newer/bigger sample" with no new question
- You cite the foundational disclosure/audit/tax literature but do not engage its open tensions
- A reviewer says "incremental," "what is new relative to [closest paper]?", or "wrong conversation"

## What "positioning" means at TAR

TAR's bar is the **significance of the contribution to the accounting literature**, so positioning
is not a citation dump — it is showing which accounting conversation you advance and how. The strong
move is **problematization**: surface a tension, an unexplained result, or a maintained assumption in
the literature that your setting lets you resolve. A new shock, a richer dataset, or a cleaner
identification is valuable only insofar as it settles something the field actually disputes.

## Map the conversation, not just the topic

- **Name the focal stream** precisely (e.g., the disclosure–cost-of-capital debate; the
  audit-quality / fee literature; the real-effects-of-accounting literature; the tax-avoidance and
  reputational-cost literature; the earnings-management vs. earnings-informativeness debate).
- **Identify the 3–6 closest papers** — the ones a reviewer will say you must beat — and state what
  each found and where they disagree or stop.
- **Locate your paper** as resolving a specific tension, not filling a void: "Prior work finds both
  X and not-X; this setting isolates the condition under which X holds."

## Position against the right venue

The closest competing work often sits in JAR, JAE, Contemporary Accounting Research, or Review of
Accounting Studies as much as in TAR. Engage that work directly; do not pretend the conversation is
TAR-only. If the nearest neighbors are all in a finance journal, reconsider whether the accounting
construct is really central (see `tar-topic-selection`).

## Incremental-extension red flags

- The only novelty is a longer panel, a new country, or a newer database vintage.
- The contribution sentence could be written before seeing your results.
- You "extend" a paper without engaging why its limitation mattered.

## Checklist

- [ ] The focal accounting conversation is named, not just the topic
- [ ] The 3–6 nearest papers are engaged, including the single closest competitor
- [ ] The paper resolves a stated tension (problematization), not an asserted gap
- [ ] Competing findings in the literature are reconciled by your setting
- [ ] Positioning engages JAR/JAE/CAR/RAST neighbors, not only TAR
- [ ] The novelty is a new answer, not merely new data

## Anti-patterns

- **Gap-spotting**: "no one has studied X" as the whole justification.
- **Citation carpet**: listing thirty references without saying who disagrees with whom.
- **Straw-man neighbor**: misstating the closest paper to manufacture novelty.
- **Database extension**: same question, newer/bigger sample, no new insight.
- **Venue blindness**: ignoring that the real debate lives partly in JAR/JAE/CAR.

## Output format

```
【Focal conversation】... (disclosure / audit / tax / real effects / managerial)
【Closest competitors】1... 2... 3... (the must-beat paper: ...)
【Tension / problematization】the literature disputes ... ; this setting resolves ...
【Your position】not a gap — you settle ...
【Cross-venue neighbors engaged】JAR/JAE/CAR/RAST: ...
【Next step】tar-methods, then tar-contribution-framing
```

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 →