Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Use when targeting 《财贸经济》(Finance and Trade Economics — 中国社会科学院主管、财经战略研究院主办的月刊, 2016 年起仅网络在线投稿) or deciding whether a public-finance/tax/trade-circulation manuscript fits this venue. Encodes the journal's online-only submission, 匿名正文/顺序编码制 house style, official re-check, and desk-reject heuristics.
Use when targeting Financial Cryptography and Data Security (FC) or deciding whether a computer-science manuscript fits this venue. Encodes conference fit, framing, evidence bar, submission-cycle checks, rebuttal posture, and desk-reject risks for financial security.
Use when targeting Financial Management (FM) or deciding whether an applied corporate-finance manuscript fits this venue. Encodes the journal's fit, framing, method-and-evidence bar, house style, official-submission re-check, and desk-reject heuristics.
Use when a Financial Management (FM) decision letter arrives (R&R or conditional accept) and a response-to-referees letter plus a revision plan must be drafted. Plans and structures the response; it does not run the new analysis (finman-identification / finman-robustness) or the resubmission preflight (finman-submission).
Use when pre-empting the objections a Financial Management (FM) referee is likely to raise, before pressing submit — red-teaming the paper from the perspective of an applied-finance reviewer who weighs relevance, rigor, and the "so-what." Anticipates pushback; it does not run the submission preflight (finman-submission) or draft a response to an actual report (finman-rebuttal).
Use when deciding whether a topic fits Financial Management (FM) and is worth aiming there — testing the question for general-interest finance relevance, topicality, and managerial/market payoff before the literature and design work begins. Sets the target; it does not run analysis or write the paper.
Use when the prose, abstract, or introduction of a Financial Management (FM) manuscript buries the idea or its managerial/market payoff — FM's brand is "articles people actually read." Shapes exposition for a general finance audience; it does not establish results (finman-identification) or run the submission preflight (finman-submission).
Use when managing author-side communication around a FOCS (IEEE Symposium on Foundations of Computer Science) submission, where no rebuttal round exists — discharging objections inside the paper before submission, handling rare chair-mediated queries, and converting a rejection into a disciplined autumn resubmission.
Use when drafting or revising a FOCS (IEEE Symposium on Foundations of Computer Science) paper — making the first ten pages carry the whole case to a broad theory committee, pairing informal and formal theorem statements, keeping single-column 11-point prose readable, and writing double-blind-safe self-references.
Use when positioning an ESEC/FSE submission against the software-engineering literature across ICSE, FSE, ASE, ISSTA, MSR, and the SE journals (EMSE, TSE, TOSEM), writing delta-first contrast rather than a citation catalog, keeping self-citations double-anonymous, and handling concurrent, preprint, and prior-version overlap.