← Browse

@zhangyanbo/vibe-paper-writing

A

Guide for integrating user-provided materials (chat logs, documents, citations) into academic papers with proper scholarly style. Use when the user wants to incorporate chat/email threads, personal documents, or references into a LaTeX paper, or asks for academic writing assistance that requires careful source attribution and style preservation.

skillclaude

Install

agr install @zhangyanbo/vibe-paper-writing --target claude

Writes 4 files into .claude/skills/, pinned to git-23db8db6.

  • .claude/skills/vibe-paper-writing/.gitignore
  • .claude/skills/vibe-paper-writing/LICENSE
  • .claude/skills/vibe-paper-writing/README.md
  • .claude/skills/vibe-paper-writing/SKILL.md

Document


name: vibe-paper-writing description: Guide for integrating user-provided materials (chat logs, documents, citations) into academic papers with proper scholarly style. Use when the user wants to incorporate chat/email threads, personal documents, or references into a LaTeX paper, or asks for academic writing assistance that requires careful source attribution and style preservation.

Vibe Paper Writing

Overview

This skill guides you in merging user-supplied materials into a professional academic paper. The core challenge is not mechanical insertion but intelligent integration: understanding what the user endorses, what belongs where, and how new content echoes existing arguments—all while preserving rigorous scholarly prose.


Task Types

When the user provides materials to incorporate, identify the task type and load the corresponding file for detailed guidance.

TaskWhen to useDetail file
Chat logs / email threadsUser pastes a conversation or email threadtasks/chat-and-email.md
User-authored documentsUser provides their own draft, notes, or memotasks/user-documents.md
Citations and referencesUser wants to add a paper, passage, or findingtasks/citations.md
Mathematical notationWriting or checking math expressions and symbolstasks/math-notation.md
Paper reviewChecking for contradictions, consistency, references, and privacytasks/paper-review.md
Writing improvementLinearizing logic, enforcing abbreviation policy, moving content to appendixtasks/writing-improvement.md
UpgradeUpdate the skill to the latest version from GitHubtasks/upgrade.md

Universal Rules

These apply to every task type. Deviations require explicit user instruction.

Academic style:

  • Professional English academic prose. No colloquialisms, no blog-post energy.
  • Do not use bullet points unless the user explicitly requests them. Prose paragraphs are the default.
  • Use subheadings sparingly. Prefer flowing paragraphs within a section.
  • Bold and italic are for technical terms and conventional academic emphasis only—not decoration.
  • Follow the paper's established voice ("we", impersonal, etc.) and do not switch without reason.
  • Match the epistemic hedging already present in the paper ("suggests," "indicates," "may").
  • Every inserted paragraph must connect to the one before and after via explicit transition sentences.

LaTeX compilation: After every substantive edit, compile and fix all errors before reporting completion. See tasks/latex-compilation.md for the full workflow.


Output Expectations

For every completed task, produce:

  1. The updated .tex section(s) with changes clearly scoped.
  2. A brief explanation of what was integrated, why, and where.
  3. Confirmation that LaTeX compilation succeeded (or the specific unresolved error).
  4. If endorsement was ambiguous in a chat log, explicitly flag omitted portions so the user can override.

Trustgrade A

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • passLicense

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-23db8db6e5792026-07-31