Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Use when drafting or polishing the prose of a Global Environmental Change (GEC) manuscript so it reads for an interdisciplinary, policy-relevant audience within the word and abstract caps. GEC values clarity and rigor that travel across disciplines. Polishes the writing; it does not draft the analysis.
Use when articulating the central legal claim and normative payoff of a Harvard Law Review (HLR) piece so it reads as an original contribution, not a doctrinal survey. Forges the thesis; it does not search for preemption (hlr-preemption-check) or build the argument's internal structure (hlr-argument-structure).
Use when shaping the prose and structure of a Harvard Law Review (HLR) piece for a generalist, student-edited audience — clear introductions, disciplined Parts, and the heavy-footnote register of legal scholarship. Polishes how it reads; it does not forge the claim (hlr-thesis-and-contribution) or format citations (hlr-sources-and-bluebook).
Use when the theoretical argument and hypotheses are the bottleneck for a Human Resource Management (Wiley "HRM") manuscript — building an HRM/OB mechanism (AMO, HR-system strength, signaling, social exchange) and deriving testable predictions a priori. Builds the theory; it does not run the analysis (hrm-data-analysis).
Use when staking a Human Relations (HR) manuscript's contribution against the relevant scholarly conversation and adjacent journals. Positions the paper; it does not develop the theory or run analysis.
Use when writing the related-work and positioning of an ICALP (EATCS) theory paper — comparing against the best known bounds in the TCS literature, crediting the right prior venues (STOC/FOCS/SODA/LICS/CCC and TCS journals), stating the delta precisely, and keeping self-citations third-person under lightweight double-blind.
Use when responding to IEEE ICDE reviews, whether drafting a rebuttal to reviewer concerns or preparing a revise-and-resubmit change document for an invited ICDE revision under the 4-week window, coordinating with area chairs, addressing systems-reviewer pushback on baselines and cost, and deciding what is feasible before the revision deadline.
Use when revising an IEEE ICDE paper for the first-page data-engineering contract, a reconstructable mechanism description, the running-example device, performance claims scoped to the workloads actually run, single-blind first-person phrasing, and 12-page IEEE two-column compression that survives a builder-heavy program committee.
Use when drafting an IEEE ICSME author response during the double-anonymous author-response period, covering the early-decision cut that decides whether you respond at all, answering the PC's specific "Response Recommended" questions with existing evidence, staying anonymous, and doing it in one round with no Major Revision safety net.
Use when positioning an IEEE ICSME submission against the software-maintenance and evolution literature across ICSME, SANER, MSR, ICPC, SCAM, ICSE/FSE, and the SE journals (TSE, EMSE), writing delta-first contrast rather than a citation catalog, keeping self-citations double-anonymous, and handling replication overlap and prior-version eligibility.