Menu
Skills in this repository
SkillsMP has collected 184 skills from jluo41/Tools. Open a skill to review its source and details.
jluo41/ToolsShowing 40 of 184 collected skills.
Scaffold a paper folder's CONTENTS, quickly and minimally: README + .gitignore + 0-lifecycle/ carrying board.md and one S01 Opening page, so a new paper is runnable on day 0. Every other page is absent-until-allocated; probes are nested below their S03/S04…
Project approved Paper Board S-page content into isolated, deterministic LaTeX candidates using 2-src/projection.yaml. Validates exact source/target coverage (G0), reads only explicitly GATED pages (G1), generates under a content-addressed 3-dist/tex run…
Submission rebuttal pipeline specialist (was: rebuttal). Parses external reviews, enforces coverage and grounding, drafts a safe text-only rebuttal under venue limits, and manages follow-up rounds. Venue-agnostic. Called by /haipipe-paper orchestrator. Direct…
Manage dated paper work rounds as first-class Board S pages under `0-lifecycle/7-round/`. Subcommands enter|new|triage|apply|close open or resume an S-Round page, create the next page, turn discussion/review into its Items queue, route work, record applied…
Two-way sync between a local paper directory and an Overleaf project via the Overleaf Git bridge (Premium feature). Lets you keep ARIS audit/edit workflows on the local copy while collaborators edit in the Overleaf web UI. Token never touches the agent — user…
Export ONE stage page's ## Content to a .docx for a coauthor who does not use LaTeX, carrying every citation, value and Display pointer in ANCHORED WORD COMMENTS authored as `haipipe`. The apparatus the LaTeX column drops survives here, bound to the exact…
Paper-specific PROBE phase worker (internal). Owns the whole five-step loop from each stage Page Q-consumer through a neutral Q-executor and returned A-executor to the Page-facing A-consumer. S03 is the discovery route and S04 is the task route. A nested…
The shared probe model: a consumer-level Q/A map that binds a neutral Q-executor by PATH to a QA-bank file in the probe-unaware task/discovery bank. Consumer families own their persisted QA-probe record and local overlay; this skill owns stake stripping, the…
Quick project setup: create the container folders and stop. Two kinds by name: Project-* = repo-backed (gh repo under a user-chosen org, never assumed; submodule at examples/<name>; if the repo already exists, adopt and pull it) and ProjX-* = plain directory…
Remove AI-writing patterns from academic prose while preserving scholarly precision, evidence-tied claims, and venue voice. Six-layer audit plus a venue-grounded SciWrite clarity pass. Default mode applies fixes directly with %% {CC-humanizer}: why-comments;…
Record a meeting from the computer with screenpipe and turn it into a raw markdown transcript routed into the vault. Verb-routed — `start` launches a scoped recording (AUDIO-ONLY by default, add vision for slides), `end` stops it and extracts the transcript,…
The single human-facing vault intake command. Use /note for anything the user wants saved to Obsidian: quick notes, todos, meetings, emails, decisions, people updates, project/matter updates, timelines, and raw pasted material. Routes one input into the…
Support skill for explicit Obsidian Bases work: creating or editing .base files, views, filters, formulas, summaries, table/card views, and database-like note views. Do not use for ordinary note capture; use /note instead.
Legacy/support skill for writing a concise Claude Code session summary to an Obsidian daily note. Prefer /note for normal capture. Use only when the user explicitly asks for the old session-summary format or names /obsidian-cc-session.
Support skill for explicit Obsidian CLI operations: search/read vault content, run commands, inspect a running Obsidian app, or develop/debug plugins and themes. Do not use for ordinary note capture; use /note instead.
Support skill for Obsidian Markdown syntax only. Use when the user explicitly asks about wikilinks, embeds, callouts, frontmatter/properties, tags, or Obsidian-specific Markdown formatting. Do not use for ordinary note capture; use /note instead.
Connect a Whoop wearable device to the bot. Guides the user step-by-step through creating a Whoop developer app, OAuth login, and daily sync setup. Use when the user says connect my whoop, link whoop, set up whoop, or /whoop-connect.
The SENTENCE contract of a board, as a loadable spec: the sentence as the board's atomic unit, its dotted address, the > comment lanes and who may write one, the evidence card on a span of words, editing, per-location chat focus, and the lifecycle of attached…
The CHECK phase contract for any Board Page. CHECK judges one concrete rendered version against its purpose, Aims, evidence, Page Type, and local closing rule, records findings where they apply, and routes the work to close, REVISE, PROBE, or a new DRAFT…
Turn a compiled paper into a conference poster: extract the poster-worthy content into a content plan, then hand it to /haipipe-display-poster to lay out (A0/A1 PDF + PPTX + SVG). Use when user says "做海报", "制作海报", "conference poster", "make poster",…
Turn a compiled paper into a conference talk: extract the slide-by-slide talk outline, then hand it to /haipipe-display-slides to lay out (beamer → PDF + PPTX, speaker notes, talk script). Use when user says "做PPT", "做幻灯片", "make slides", "conference talk",…
Migrate an existing paper into the layout ruled 2026-07-26 (design board QA6, the delete test): un-number the deliverable, split a monolithic driver into sections/ + appendices/, rewire the \input tree, normalize NN-MM naming, unitize loose assets into…
THE MANUSCRIPT UPGRADE: add the LaTeX toolchain to a paper that has reached the Display or section frontier. Writes the unnumbered driver tex, sections/ wrappers + leaf stubs with paragraph banners, appendices/, displays/, the venue shell, and…
CHECK phase worker (internal). Called as a stage's declared human gate. All current paper stages declare one gate here; earlier declared phases run unattended. Runs automated sub-checkers, seeds in-file CHECK comments, and presents the approval or restart…
DRAFT phase worker (internal). Called by a paper stage to produce the first-pass S-page artifact and raise every unresolved Q-consumer question. Reads that stage's stage.md and template, writes no probe entries, and opens no human gate unless stage.md…
Paper-specific REVISE phase worker (internal). Called whenever the Page router enters REVISE to improve manuscript realization under fixed purpose and Aims. Default REVISE changes prose directly; an explicit author request enables candidate-diff mode. If…
Review and edit prose CONTENT at section → paragraph → weave → sentence. REVISE phase (fully automatic): applies changes directly, leaves %% {CC-content}: why-comments for CHECK. Self-contained — carries its own structure/claim/flow checks including the weave…
Guide authors through the full rebuttal process for ML conference/journal reviews. Four phases (Understand → Task → Rebuttal → Revise) producing artifacts under 1-review/. Use when the user has received peer reviews and needs to write rebuttal responses, plan…
Use when responding to journal or conference reviewer comments and you need a structured author response, aligned manuscript edits, and clear decisions about when to clarify, add evidence, concede, or respectfully disagree.
Orchestrator for the paper delivery group (3-deliver) — everything downstream of the written argument. Routes build (including manifest-driven S-page projection), audit, polish, and ship intents to leaf skills. The artifact-side mirror of…
Application-specific DRAFT phase worker (internal). Called whenever a stage enters DRAFT to define or reopen its purpose, Aims, and artifact shape, then raise stake-bearing Q-consumers for what it cannot answer. It writes no Probe record or executor-side…
Application-specific PROBE phase worker (internal). Owns the whole five-step loop from each stage Page Q-consumer through a neutral Q-executor and returned A-executor to the Page-facing A-consumer. The persisted Probe file uses the existing QX schema, binds…
Application-specific REVISE phase worker (internal). Called whenever the Page router enters REVISE to improve a stage doc under fixed purpose and Aims: weave any landed evidence, tighten wording, and enforce applicable venue and audience profiles. A changed…
Application-specific CHECK phase worker (internal). Runs when a stage's local contract declares its human gate. It opens with markdown and probe-file checks whose failures block green, seeds CHECK comments in stage docs while keeping deliverable artifacts…
Zero-context verification that every number, comparison, and scope claim in the paper matches raw result files. Uses a fresh cross-model reviewer with NO prior context to prevent confirmation bias. Use when user says "审查论文数据", "check paper claims", "verify…
Use when reviewing or revising an academic manuscript whose central claim, evidence chain, figures, terminology, and prose may have drifted out of sync before submission or resubmission.
Whole-paper polish pass over a finished LaTeX draft — three passes in order: consistency (terminology, notation, \label/\ref integrity), format (venue style: abbreviations, units, headings, reference style), then typeset (widows, orphans, overfull boxes, bad…
Use when acting as a journal or grant reviewer and writing formal reviewer-side evaluations focused on methodology, statistics, reporting standards, reproducibility, and constructive feedback.
The WRITE verb of the board family, at BOTH altitudes. Page altitude: take ONE input (a decision made in chat, a finding, a correction, a status change) and land it on the board, by finding the owning page and section and appending an anchored write; it loads…
The WRITING verb: take prose someone already wrote and make it readable by a person whose English is weak, recording every edit as a word-level change under the sentence it changed. Not a style guide and not a spec: it rewrites, and it leaves a trail a…