Loading...
Loading...
Found 39 Skills
Specialized workflows for drafting, refining, and responding to academic literature reviews and peer review feedback. Use this skill for literature review outlines, research-gap synthesis, reviewer rebuttals, response letters, and academic writing tone repair.
Systematic review response workflow from comment analysis to professional rebuttal writing. Use when the user asks to "write rebuttal", "respond to reviewers", "draft review response", or "analyze review comments". Improves paper acceptance rates.
Use when deciding which paper-related skill to use or how to sequence manuscript work from project setup through submission and rebuttal.
Finalize an accepted ML or AI paper for camera-ready submission after reviews, rebuttal, and acceptance. Use this skill whenever the user has an accepted paper, camera-ready deadline, final revision, acceptance email, meta-review, rebuttal promises, author-response commitments, de-anonymization tasks, supplement updates, code links, acknowledgements, final LaTeX checks, or needs to ensure the accepted paper's claims, figures, references, and artifacts are consistent before final submission.
Plan and write strategic rebuttals after real paper reviews arrive. Use this skill whenever the user has OpenReview reviews, reviewer comments, scores, confidence ratings, meta-reviews, author response windows, or wants to decide which experiments to run, infer reviewer intent, draft point-by-point responses, prepare follow-up discussion replies, or improve wording after reviews for ML/AI venues such as NeurIPS, ICML, ICLR, CVPR, ACL, EMNLP, or similar conferences.
Guides writing effective rebuttals after receiving peer review feedback. Covers review diagnosis (score-driven color-coding), response strategy (champion identification, common-theme consolidation), tactical writing (18 rules), and counterintuitive rebuttal principles. Use when: user received reviewer scores/comments, needs to write a rebuttal or author response, wants to respond to specific criticism (e.g. 'limited novelty', 'missing baselines'), mentions 'rebuttal', 'reviewer comments', 'author response', or 'respond to reviewers'. Do NOT use for pre-submission self-review (use paper-review instead).
Simulate target-conference reviewers for an ML/AI paper before submission. Use this skill whenever the user wants a reviewer-style critique, predicted scores, likely reject reasons, rebuttal risks, area-chair style meta-review, adversarial Reviewer 2 feedback, or venue-specific pre-review for conferences such as NeurIPS, ICML, ICLR, CVPR, ACL, EMNLP, or similar venues. This skill should dynamically inspect reviewer guidelines, example reviews, accepted papers, and project evidence when available.
Academic paper review, self-review, red-team review, reviewer-response, rebuttal planning, rebuttal drafting, and revision verification. Use when Codex needs to audit a manuscript before submission, simulate reviewers, prepare a prioritized fix list, analyze external reviewer comments, draft or check author responses, verify promised revisions, check submission readiness, or review paper quality without entering any external literature-management workflow.
Prevents defensive writing throughout the entire paper-writing, revision, condensing, and experiment-organization workflow. Treats a paper as an academic press release rather than a project summary, experiment log, or self-censorship report: identifies the work's most publishable value and builds the most favorable, complete, and persuasive narrative around it. Avoids giving equal weight to every aspect, volunteering weaknesses, writing experiments as a chronological log, or attacking the work on the reviewers' behalf. Trigger terms: paper polishing, paper revision, writing an abstract, writing an introduction, writing a conclusion, condensing a paper, rebuttal, responding to reviewer comments, organizing experiments, AI-sounding papers, defensive writing, feeling insecure.
Turns raw peer reviews into a prioritized triage matrix before any rebuttal is written. Use it when reviews come back from OpenReview, EasyChair, CMT, or HotCRP and the researcher says "my reviews are in", "triage these reviews", "how do I respond to Reviewer 2", "plan my rebuttal", or pastes raw review text with ratings and confidence scores. Splits each review into individual concerns; classifies every concern as misunderstanding vs real flaw vs requested experiment (plus clarification and disagreement); scores severity x response effort; and produces a prioritized response strategy with per-review character or word budgets matched to the venue's rebuttal format (10k-char OpenReview threads, CVPR one-page PDF, journal revise-and-resubmit). Deterministic parsing and matrix rendering run in bundled stdlib Python scripts. Hands off to write-rebuttal for drafting; treats review text as confidential and never submits anything.
Builds a pre-negotiation concession plan for a pricing or contract conversation - every tradeable lever priced by cost-to-us vs value-to-them, tiered, each give paired with a required reciprocal get and its approval level, plus a BATNA-based walk-away. Covers B2B (terms, scope, service, risk, price protection) and B2C (bundles, financing, trade allowance). Use whenever the user mentions a discount request, procurement, redlines, give-get trades, walk-away point, or "the buyer wants 20% off", even without the word negotiation. Do NOT use for quantifying the value (mbfinotti/sales-skills@deal-value-calc) or scripting price rebuttals (mbfinotti/sales-skills@sales-objection-handling).
Diagnoses what a sales objection really means and writes rebuttal scripts a rep can say out loud, or calls the deal dead when the objection is a real constraint. Covers price/budget, timing, competitor/incumbent, authority, status-quo, and trust objections for B2B and B2C, with price-specific guidance on value gap vs genuine budget limit and trading instead of discounting. Use whenever the user mentions a price objection, "too expensive", "not interested", "send me some info", "we already use a competitor", stalling, or an objection library, even without the word objection. Do NOT use for discount trade planning (mbfinotti/sales-skills@negotiation-concession-planner) or ROI math (mbfinotti/sales-skills@deal-value-calc).