Claude Skills by thedixitjain

Use when building the theoretical argument for a Journal of Business Venturing (JBV) manuscript — constructing a multidisciplinary mechanism (economics, psychology, sociology) for an entrepreneurial phenomenon, and choosing between hypothesis-testing and narrative/interpretive theorizing. Builds the argument; it does not pick the question (jbv-topic-selection) or run the analysis (jbv-data-analysis).

Use when deciding which jbv-* sub-skill to invoke next, or when sequencing manuscript work from topic selection through rebuttal for a Journal of Business Venturing (JBV) manuscript. Routes — it does not replace — the specialized skills.

Use when sharpening the stated contribution of a Journal of Corporate Finance (JCF) manuscript — turning a result into a crisp \"what is new and why it matters to corporate finance\" claim that survives the editor's desk screen. It frames the pitch (abstract, intro, cover letter); it does not run analysis.

Use when building and running the empirical analysis for a Journal of Corporate Finance (JCF) paper — assembling WRDS-era firm panels (Compustat/CRSP/SDC/DealScan), constructing variables, estimating with fixed effects and clustered errors, and layering robustness. It guides the empirical build; pair it with jcf-identification-strategy for the design itself.

Use when designing or defending the causal identification strategy for a Journal of Corporate Finance (JCF) empirical paper — choosing and stressing a design (DID/staggered shocks, IV/GMM, RDD, event study, matching) for firm-level data with endogenous corporate decisions. It evaluates and hardens the design; it does not run the regressions.

Use when positioning a manuscript within the corporate-finance literature for the Journal of Corporate Finance (JCF) — locating the paper in the right strand (capital structure, governance, payout, contracting, M&A, international) and stating the marginal contribution. It frames citations and gap statements; it does not draft full sections.

Use when preparing a revise-and-resubmit response for the Journal of Corporate Finance (JCF) — a point-by-point reply to two-or-more single-anonymized reviewers and the handling editor, reconciling divergent demands without over-claiming. It structures the response letter and revision plan; it does not run new analysis on its own.

Use when planning around the Journal of Corporate Finance (JCF) review process — single-anonymized (single-blind) refereeing, a minimum of two reviewers, an active desk-rejection policy, decision-letter interpretation, and required Elsevier declarations. It sets expectations and timing strategy; it does not draft the manuscript or the rebuttal.

Use when running the final pre-submission preflight for the Journal of Corporate Finance (JCF) via Editorial Manager — the US$340 non-refundable fee, single-anonymized (non-anonymized) manuscript, ≤250-word abstract, author-date \"your paper, your way\" references, Option C data statement, declarations, and the optional free SSRN preprint. Final checks; it does not draft content.

Use when building the tables and figures for a Journal of Corporate Finance (JCF) empirical paper — summary statistics, main regression tables with fixed effects and clustering disclosed, event-study/CAR plots, and self-contained notes. It shapes the exhibits; pair with jcf-data-analysis for the underlying estimates.

Use when judging whether a corporate-finance question fits the Journal of Corporate Finance (JCF) and whether it suits a full-length or \"shorter format\" paper. Helps scope the idea to JCF's empirical/theoretical corporate-finance remit; it does not run analysis or draft text.

Use when orchestrating the full Journal of Corporate Finance (JCF) manuscript lifecycle — from a corporate-finance question through identification, robustness, the US$340 fee submission via Editorial Manager, single-anonymized review, and R&R. Routes to the other eleven jcf-* skills with stage gates; it coordinates, it does not draft content.

Use when pitching a survey to the Journal of Economic Literature (JEL) editor before writing it — the ~10-page proposal route, the pre-proposal email, and understanding the commissioning process. Builds the proposal; it does not write the survey or run the AEA portal preflight (jel-submission).

Use when crafting a proposal to the Journal of Economic Perspectives (JEP) editors — a short article proposal or a symposium pitch — since JEP is largely invited and editor-organized. Builds the pitch and its contents; it does not write the full article or run the final submission preflight.

Use when designing or stress-testing an asset-pricing test for a The Journal of Finance (JF) manuscript — factor models, Fama–MacBeth vs. panel, standard-error corrections, out-of-sample discipline. For corporate causal claims use jf-identification.

Use when the causal-identification strategy is the bottleneck for a corporate / empirical The Journal of Finance (JF) manuscript — natural experiments, IV, DID, RDD. Stress-tests the design; for asset-pricing tests use jf-empirical-design.

Use when deciding what belongs in the Internet Appendix vs. the main text of a The Journal of Finance (JF) manuscript. Allocates content and structures the appendix per JF's actual policy; it does not generate the results.

Use when the introduction and related-work sections of a The Journal of Finance (JF) manuscript fail to state a crisp marginal contribution against the finance literature. Positions the paper; it does not survey it.

Use when drafting the response to a The Journal of Finance (JF) revise-and-resubmit (or addressing a reject-with-comments). Structures the response letter and revision plan after the manuscript is revised.

Use when anticipating referee objections and selecting suggested/opposed reviewers before or during a The Journal of Finance (JF) submission. Plans for review; it does not write the rebuttal (use jf-rebuttal).

Use when planning or auditing the robustness, sensitivity, and multiple-testing battery for a The Journal of Finance (JF) manuscript. Decides which checks are load-bearing; it does not design the main test.

Use when running the final pre-submission preflight for The Journal of Finance (JF) — the AFA online portal, the tiered submission fee, the 60-page limit, the bundled Internet Appendix, code sharing, and disclosure statements.

Use when finalizing tables and figures for a The Journal of Finance (JF) manuscript for the AFA flagship. Enforces accessible, self-contained, general-interest exhibits with Roman-numeral tables, economic-magnitude reporting, and matching Internet Appendix numbering; it does not decide which results to run.

Use when judging whether a research question is general-interest and economically significant enough for The Journal of Finance (JF), and when sharpening the framing. Tests fit and contribution; it does not design the empirics.

Use when deciding which jf-* sub-skill to invoke next, or when sequencing manuscript work from topic selection through rebuttal for The Journal of Finance (JF). Routes — it does not replace — the specialized skills.

Use when settling the measurement and estimation choices of a Journal of Financial Economics (JFE) manuscript — factor construction, portfolio sorts, Fama-MacBeth/GMM, standard-error clustering, and multiple-testing discipline. Covers the design/estimator layer; for causal identification of corporate-finance effects use jfe-identification.

Use when the causal identification or inference design is the bottleneck for a Journal of Financial Economics (JFE) manuscript — natural experiments, IV, staggered DID, RDD, and explicit endogeneity/selection treatment. Stress-tests the design before drafting tables; it does not finalize factor construction or estimators (see jfe-empirical-design).

Use when organizing the journal-hosted Internet Appendix for a Journal of Financial Economics (JFE) manuscript — what to move off the main text, how to cross-reference it, and how to keep it self-contained. Structures the appendix; it does not decide which robustness tests to run (jfe-robustness).

Use when drafting the response to a Journal of Financial Economics (JFE) revise-and-resubmit — the response letter, point-by-point replies, and the revision-tracking that JFE's demanding rounds require. Drafts the response after revisions are made; it does not invent new results you have not run.

Use when anticipating and pre-empting the objections a Journal of Financial Economics (JFE) referee will raise — endogeneity, fragility, multiple testing, alternative explanations. Builds a defense plan before or during review; it does not draft the post-R&R response letter (jfe-rebuttal).

Use when running the final pre-submission preflight for a Journal of Financial Economics (JFE) manuscript — formatting, anonymity, references, exhibits, code/data deposit, the editorial system, and the submission fee. Checks submission readiness; it does not revise the science.

Use when the exhibits of a Journal of Financial Economics (JFE) manuscript need to meet house standards — readable tables, self-contained notes, and figures that carry the argument. Handles exhibit craft; it does not decide which robustness tests to run (jfe-robustness).

Use when deciding which jfe-* sub-skill to invoke next, or when sequencing manuscript work from topic selection through rebuttal for a Journal of Financial Economics (JFE) manuscript. Routes — it does not replace — the specialized skills.

Use when framing the contribution of a Journal of Financial Intermediation (JFI) paper around what it teaches about intermediation — the institution, the friction, the mechanism, and the economic consequence — so it clears the desk screen and reads as banking, not generic finance. It frames; it does not write the paper.

Use when planning an R&R response letter for the Journal of Financial Intermediation (JFI) — single-blind review where referees know you, often a small number of expert reports, a narrow appeal path, and pushback centered on the intermediation channel. It structures the response; it does not fabricate results.

Use when navigating the Journal of Financial Intermediation (JFI) editorial process — the active desk-rejection policy, single-anonymized (single-blind) review with at least one expert referee when sent out, the tightly limited appeal path, and the option to choose the Managing Editor. It sets expectations; it does not draft content.

Use when running the final pre-submission preflight for the Journal of Financial Intermediation (JFI) via Editorial Manager — the US$500 non-refundable new-submission fee, the system-built review PDF, a <=250-word abstract, 1-7 English keywords, optional Highlights and SSRN preprint, Option C data links/statements, and the mandatory generative-AI disclosure. Final checks; it does not draft content.

Use when working on Journal of Financial Intermediation (JFI) manuscripts to test whether the paper is centrally about banking and financial intermediation — whether an intermediary mechanism is load-bearing, how it differs from a Journal of Banking and Finance fit, and whether to lead with theory or empirics — before investing in the draft.

Use when the identification argument is the bottleneck for a Journal of Financial Markets (JFM) manuscript — causal effects on market quality, or what pins down a microstructure model. Stress-tests the design against JFM's microstructure-insider bar before exhibits are finalized.

Use when assembling the Internet Appendix, data codebook, and replication materials for a Journal of Financial Markets (JFM) manuscript — what stays in the main text vs. the appendix, and the TAQ/proprietary-data access path. Organizes supporting material; it does not invent evidence or citations.

Use when drafting the response to an R&R or referee report for a Journal of Financial Markets (JFM) manuscript — turning microstructure objections into a point-by-point response and a revised draft. Plans and drafts the rebuttal; it does not invent evidence or citations.

Use when anticipating the microstructure referee's objections for a Journal of Financial Markets (JFM) manuscript — a pre-submission pre-mortem and, post-decision, a triage of the report. Anticipates and triages; it does not invent evidence or citations.

Use when results may be sensitive to liquidity-measure choice, sample filters, microstructure noise, or inference for a Journal of Financial Markets (JFM) manuscript. Builds the design-based robustness ledger; it does not invent evidence or citations.

Use when running the final pre-submission preflight for a Journal of Financial Markets (JFM) manuscript via Elsevier Editorial Manager — file set, blinding, declarations, data statement, and house formatting. Final checks; it does not draft content.

Use when microstructure exhibits — spreads, depth, price-impact, order-flow, and event-study plots — are the bottleneck for a Journal of Financial Markets (JFM) manuscript. Sharpens the exhibits; it does not invent evidence or citations.

Use when deciding whether a question belongs at the Journal of Financial Markets (JFM) — i.e., whether it is genuinely about market microstructure / how markets trade rather than broad asset pricing or corporate finance. Scopes and reroutes; it does not invent evidence or citations.

Use when deciding which jfm-* sub-skill to invoke next, or when sequencing work on a Journal of Financial Markets (JFM) manuscript from topic selection through rebuttal. Routes — it does not replace — the specialized microstructure-focused skills.

Use when framing the contribution of a Journal of Financial and Quantitative Analysis (JFQA) paper — write the strict one-paragraph abstract of no more than 100 words and an introduction that states what is new in finance terms, so the quantitative contribution lands within JFQA's tight abstract cap and high selectivity.

Use when running and documenting the empirical analysis for a Journal of Financial and Quantitative Analysis (JFQA) paper — finance data construction (CRSP/Compustat/TAQ/IBES), winsorizing, fixed effects, clustered and Newey-West standard errors, robustness, and heterogeneity — so results survive double-anonymous JFQA review and reproduce from the archived code. For theory papers, lighten this and document numerical examples instead.

Use when planning the strategy and structure for a Journal of Financial and Quantitative Analysis (JFQA) revise-and-resubmit response — point-by-point replies to double-anonymous referees and the handling Managing Editor, new robustness/identification evidence, and code-archive readiness.