yananlong
- 20 skills
- 0 followers
- 6 hours ago last updated
- ▌ Research Zotero · yananlong bundleSync, inspect, and export Zotero user or group libraries for literature-heavy research workflows. Use when Codex needs to reuse a Zotero library or collection as a curated paper corpus, export BibTeX or CSL-JSON, inspect collections/tags/groups, prepare citation artifacts for paper planning, or seed literature review and novelty review from an existing Zotero library. Default to the current user's library when an API key is available and no explicit library is provided.
- ▌ Research Rebuttal · yananlong bundleDraft venue-aware academic rebuttals and author responses from reviewer comments, scores, and paper artifacts. Use when concrete reviewer comments already exist and Codex needs to analyze reviews, build a reviewer issue board, plan evidence or manuscript fixes, draft a rebuttal, respond to AC or meta-review feedback, manage multi-round author-reviewer discussion, or prepare a paste-ready response for conference or journal review systems. Prefer `research-paper-review` for initial manuscript diagnosis before reviews arrive, `research-review-loop` for internal tracked review without external reviewer comments, and `research-novelty-review` for prior-art positioning disputes.
- ▌ Prose Flow Improver · yananlong bundleImprove the flow, shape, and readability of existing prose while preserving substance, specificity, tone, and constraints, including planned multi-agent section, paragraph-range, or chunk-level revision for substantial documents when workers are available. Use when Codex needs to make explanatory writing less choppy, less list-heavy, less fragmented, or less over-paragraphed; combine related sentences or paragraphs aggressively but readably; add connective reasoning; favor conjunctions, relative clauses, subordinate clauses, and clean participial phrasing over semicolons; or turn terse notes into natural connected prose. Do not use when the content is inherently list-shaped, procedural, tabular, or governed by a stricter task-specific format.
- ▌ PDF Book Assembler · yananlong bundleAssemble book-style PDFs from one or more source PDFs using CLI PDF tools. Use when Codex needs to collate PDFs in a specific order, drop repeated cover/JSTOR pages, add chapter/section bookmarks, rotate landscape pages to portrait, or optionally crop shared whitespace proportionally across pages.
- ▌ Research Paper Plan · yananlong bundleTurn supported claims and evidence into a research paper plan that works either as a standalone manuscript-structuring pass or as the paper stage inside a coordinated research workflow. Use when asked to outline a paper, map claims to evidence, bind audited results to manuscript claims, plan figures and citations, align experiments to manuscript language, or keep limitations and threats to validity explicit.
- ▌ Research Review Loop · yananlong bundleRun iterative adversarial review over research plans, experiment outputs, and drafts with claim ledgers, issue tracking, evidence checks, and explicit closure criteria. Use when asked to red-team a research artifact across multiple rounds, maintain issue state across revisions, or pressure-test whether revised results and prose actually support a claim. Prefer `research-paper-review` for an initial single-paper critique or OCR/extraction workflow, and prefer `research-rebuttal` when concrete external reviewer comments already exist and the task is to draft a venue response.
- ▌ Research Paper Review · yananlong bundleRun academic paper review with OCR extraction, ChatGPT-native multi-agent critique, local visualization, and section-level review workflows integrated into the research skill suite. Use when Codex needs an initial or first-pass review of one paper artifact or arXiv URL, including OCR, extraction, default Claude-style or multi-agent review, contextualized critique, or viz JSON generation. Prefer `research-review-loop` once a tracked review state or revised artifact already exists, `research-novelty-review` for prior-art and positioning questions, `research-rebuttal` when concrete reviewer comments already exist, and `adversarial-doc-review` for non-paper documents.
- ▌ Adversarial Doc Review · yananlong bundlePedantic, adversarial stress-testing of documents with claim-by-claim scrutiny, internal consistency checks, citation auditing, and up-to-date fact-checking. Use when asked to critique, peer-review, red-team, verify references, pressure-test time-sensitive statements, or assess whether validation, verification, independence, immutability, isolation, replay, auditability, or route-readiness claims are actually supported; default deliverable is a structured report in chat.
- ▌ Exposition To Notebook · yananlong bundleConvert mathematical derivations, research notes, and textual specs into runnable, product-ready Jupyter notebooks (.ipynb) with clear narrative, LaTeX, modular code, plots, and sanity checks/tests. Use when asked to turn an exposition/paper/spec into a notebook, prototype a method in Jupyter, create a demo notebook, or convert Markdown/LaTeX notes into an executable notebook.
- ▌ Research Idea Discovery · yananlong bundleGenerate, filter, rank, and hand off grounded research ideas from a broad research direction, problem area, literature landscape, Zotero corpus, paper limitation, or user notes. Use when asked to brainstorm publishable research ideas, find a direction, turn a broad area into candidate claims, choose what to work on, evaluate idea quality before novelty review, or create an ideation stage inside a coordinated research workflow. Prefer research-novelty-review when the user already has one concrete idea to pressure-test, research-experiment-plan when the claim is already frozen, and research-pipeline-planner when the main request is multi-stage project sequencing rather than ideation itself.
- ▌ Research Novelty Review · yananlong bundleRun a stringent, adversarial novelty review over a concrete research idea, method, protocol, artifact, or claimed finding. Use when asked to assess novelty, position a paper or project, build a prior-art matrix, decide whether something is incremental, or pressure-test whether the right move is to proceed, reframe, or abandon. Prefer `research-paper-review` for first-pass technical critique of a single paper artifact and `research-rebuttal` when the task is to answer concrete reviewer comments rather than establish novelty positioning from scratch.
- ▌ Document Memory Builder · yananlong bundleRead a specified set of documents and distill them into a reusable, source-grounded memory pack. Use when Codex is asked to ingest project documents, papers, specs, notes, policies, or mixed corpora and create durable memory artifacts such as canonical facts, terminology, workflows, constraints, entity maps, and open questions for later reuse. Also use for long-form or chaptered material such as books, long reports, multi-section drafts, or large corpus updates that require section-aware extraction and synthesis.
- ▌ Research Experiment Plan · yananlong bundleConvert a concrete research claim into a tracked, decisive experiment plan that works either as a standalone planning artifact or as the experiment stage inside a coordinated research workflow. Use when asked to design experiments, define baselines or ablations, decide run order, separate must-run from nice-to-have evidence, or turn a claim plus evaluation goal into a validation plan.
- ▌ Research Results Auditor · yananlong bundleAudit ML/statistics experiment outputs for validity, confounds, statistical support, calibration, and mismatch between measured results and claimed conclusions. Use when asked to interpret results, sanity-check benchmarks, review ablations, assess robustness claims, decide whether an experiment supports a paper claim, or produce a machine-readable result-audit record for downstream paper planning.
- ▌ Technical Writing Reviser · yananlong bundleRevise existing technical writing into clear, audience-facing prose while preserving evidence, technical meaning, uncertainty, and scope, including planned multi-agent section or issue-cluster revision for substantial artifacts when workers are available. Use for academic manuscripts, industrial technical reports, whitepapers, evaluation summaries, methods/results/limitations prose, technical claims, contribution or decision framing, and terminology conversion from internal shorthand to reader-facing language. Use after critique from research-paper-review or research-review-loop when the task is to revise the artifact's prose and claims, not to re-review it. Do not use when the main task is generic prose flow, citation work, paper planning, novelty review, experiment design, market strategy, or writing unsupported claims.
- ▌ Proportional PDF Trimmer · yananlong bundleTrim a user-specified proportion of removable whitespace from PDF pages while preserving the document page aspect ratio and enforcing one common output crop size across all pages. Use for PDFs with oversized margins, uneven whitespace, scanned or generated pages that should be uniformly cropped, or requests to identify the page(s) with the largest visual content footprint and use that footprint to determine a proportional crop for the whole document. Before trimming, ask how much removable whitespace to trim unless the user already supplied a proportion such as 2/3, 0.67, or 67%. Supports text, vector, image, and scanned PDFs through raster-based content detection while applying non-destructive PDF crop boxes.
- ▌ Research Pipeline Planner · yananlong bundleCoordinate research as either a standalone staged planning pass or a durable orchestrated multi-skill workflow with shared artifacts, explicit work items, paper-level commitment, verifier-backed transitions, checkpoints, replay, observability, stage gates, evidence assurance, and controlled pivots. Use when asked to scope a research direction, inspect existing research artifacts, choose the next research stage, create a research brief or task board, coordinate a reusable research workflow, build a research roadmap or agenda, organize a research repo, turn notes into a phase plan, define milestones, decide what to do next, coordinate literature, ideation, novelty, experiments, auditing, review, paper planning, and rebuttal work, or prevent a project from drifting between paper identities.
- ▌ Market Patent Diligence · yananlong bundlesource-grounded market, competitor, procurement, funding, regulatory, and patent-landscape diligence for academic research commercialization. use when codex needs to search public market or patent information for a research asset, technology, prototype, dataset, method, device, or commercialization thesis; map incumbents, substitutes, buyers, assignees, patent families, citations, ownership signals, public funding, procurement demand, regulatory/reimbursement constraints, and evidence gaps; prepare diligence artifacts for commercialize-academic-research or related research skills.
- ▌ Research Systematic Literature Review · yananlong bundleRun or audit literature discovery and evidence synthesis with explicit review profiles, high-recall discovery, seed and challenge-set testing, citation searching, corpus freezing, PRISMA 2020 core accounting, evidence extraction, confidence grading, and adversarial stress-testing across publications. Prefer peer-reviewed published versions over preprints. Use for systematic reviews, bounded evidence maps, state-of-the-art surveys with explicit methods, citation-integrity checks, novelty-critical prior-art searches, confidence-rated conclusions, or when a research commitment depends on reliable literature coverage.
- ▌ Commercialize Academic Research · yananlong bundleRun evidence-gated commercialization analysis for academic research by translating a bounded research asset into workflow pain, current workarounds, buyer and budget logic, commercialization paths, risk-retirement tests, and kill/pivot/continue decisions. Use when Codex needs to evaluate market pull for a paper, prototype, dataset, device, algorithm, lab result, or platform technology; distinguish user, buyer, operator, procurement, and budget roles; compare startup, licensing, partnership, service, or component routes; identify beachhead wedges; build validation sprints; or red-team unsupported commercialization claims.