Citation Verification Guide
Galaxy-Dawn/claude-scholar
Reference guidance for checking every citation in academic writing against canonical sources such as DOI, arXiv, CrossRef and Semantic Scholar, to catch fake or wrong references.
A skill your agent uses when writing or revising scientific manuscripts, abstracts, figures, or references for journal submission and you need full-paragraph prose, scientific structure…
$ npx skills add Yrzsh/paper-workbench --skill scientific-writing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Yrzsh/paper-workbench scientific-writing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Yrzsh/paper-workbench.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/scientific-writing .claude/skills/scientific-writing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "scientific-writing" agent skill from https://github.com/Yrzsh/paper-workbench/tree/main/skills/scientific-writing into .claude/skills/scientific-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scientific-writing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Yrzsh/paper-workbench/tree/main/skills/scientific-writingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Yrzsh/paper-workbench --skill scientific-writing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Yrzsh/paper-workbench scientific-writing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Yrzsh/paper-workbench.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/scientific-writing .agents/skills/scientific-writing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "scientific-writing" agent skill from https://github.com/Yrzsh/paper-workbench/tree/main/skills/scientific-writing into .agents/skills/scientific-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scientific-writing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Yrzsh/paper-workbench --skill scientific-writing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Yrzsh/paper-workbench scientific-writing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Yrzsh/paper-workbench.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/scientific-writing .cursor/skills/scientific-writing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "scientific-writing" agent skill from https://github.com/Yrzsh/paper-workbench/tree/main/skills/scientific-writing into .cursor/skills/scientific-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scientific-writing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Yrzsh/paper-workbench.git --path skills/scientific-writing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Yrzsh/paper-workbench --skill scientific-writing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Yrzsh/paper-workbench scientific-writing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Yrzsh/paper-workbench.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/scientific-writing .gemini/skills/scientific-writing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "scientific-writing" agent skill from https://github.com/Yrzsh/paper-workbench/tree/main/skills/scientific-writing into .gemini/skills/scientific-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scientific-writing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Yrzsh/paper-workbench scientific-writingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Yrzsh/paper-workbench --skill scientific-writing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Yrzsh/paper-workbench.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/scientific-writing .github/skills/scientific-writing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "scientific-writing" agent skill from https://github.com/Yrzsh/paper-workbench/tree/main/skills/scientific-writing into .github/skills/scientific-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scientific-writing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Yrzsh/paper-workbench --skill scientific-writing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Yrzsh/paper-workbench scientific-writing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Yrzsh/paper-workbench.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/scientific-writing .opencode/skills/scientific-writing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "scientific-writing" agent skill from https://github.com/Yrzsh/paper-workbench/tree/main/skills/scientific-writing into .opencode/skills/scientific-writing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scientific-writing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
scientific-writingA skill your agent uses when writing or revising scientific manuscripts, abstracts, figures, or references for journal submission and you need full-paragraph prose, scientific structure…
Scientific Writing is an agent skill from Yrzsh/paper-workbench. Use when writing or revising scientific manuscripts, abstracts, figures, or references for journal submission and you need full-paragraph prose, scientific structure, citation-style guidance, or reporting-guideline support.
Its SKILL.md is about 7.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science, covering Scientific writing and Citation management. The repository describes itself as: Paper Workbench — 论文写作审查全流程工作台 / End-to-end academic writing & review workbench. The licence is MIT.
10 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 801516a. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
pythonFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
OPENROUTER_API_KEYFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Scientific Writing loads about 7.4k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 3,368 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from Yrzsh/paper-workbench at commit 801516a, republished under its MIT licence (© Yrzsh). 3,368 words, ~7,443 tokens.
.claude/skills/scientific-writing/SKILL.md (or your agent's skills folder).This is the core journal-writing skill in this repository. Use it to turn a stable scientific story into clear, well-structured manuscript prose while keeping citations, figures, and reporting standards aligned.
Scientific writing is a process for communicating research with precision and clarity. Write manuscripts using IMRAD structure, citations (APA/AMA/Vancouver), figures/tables, and reporting guidelines (CONSORT/STROBE/PRISMA). Apply this skill for research papers and journal submissions.
Critical Principle: Always write in full paragraphs with flowing prose. Never submit bullet points in the final manuscript. Use a two-stage process: first create section outlines with key points from verified notes, literature, and results, then convert those outlines into complete paragraphs.
For revision-heavy journal manuscripts, do not jump from stale prose directly to polishing. First stabilize the section with a reverse outline and a claim-evidence map, then rewrite the paragraphs.
This skill should be used when:
For title, abstract, cover-letter, or top-level logic decisions, read references/editor-first-impression.md.
When a manuscript would benefit from a schematic, workflow diagram, or conceptual figure, use this repository's nature-figure skill, which ships an OpenRouter AI-schematic route. It is not in the default recommended set because it needs a plotting backend or an OPENROUTER_API_KEY; install it from the Figure Stack (see the installation docs).
Before finalizing any document:
How to generate figures:
nature-figure skill's OpenRouter route to generate publication-style schematics.figures/ directory in the current project.Example command (via the nature-figure skill, once installed):
export OPENROUTER_API_KEY="sk-or-..."
python ~/.codex/skills/nature-figure/scripts/generate_openrouter_schematic.py \
--title "Your method" \
--panel-map "left: problem; center: proposed mechanism; right: validated outcome" \
--outdir figures --basename schematic --resolution 2K
# Claude Code (global install): replace ~/.codex/skills with ~/.claude/skills
# Claude Code (project-local install): replace ~/.codex/skills with .claude/skillsRequires OPENROUTER_API_KEY. Iterate on the panel map and title until the figure is publication-ready. See nature-figure's references/openrouter-image-generation.md for full options.
When to add figures:
For detailed guidance on creating figures, refer to the nature-figure skill.
IMRAD Format: Guide papers through the standard Introduction, Methods, Results, And Discussion structure used across most scientific disciplines. This includes:
For detailed guidance on IMRAD structure, refer to references/imrad_structure.md.
Alternative Structures: Support discipline-specific formats including:
Editor-First Front Door: Make the title, abstract, introduction, Results, discussion, and cover letter answer the same four questions in the same order:
If these sections answer different versions of the story, the manuscript will feel fragmented even when the prose is locally strong.
Abstract Composition: Craft concise, standalone summaries (100-250 words) that capture the paper's purpose, methods, results, and conclusions. Support both structured abstracts (with labeled sections) and unstructured single-paragraph formats. Make the abstract state the problem, the aim/method, the key result, and the implication. Do not spend most of the space on generic background or report only that results were significant.
Title and Cover Letter: Make the title a concise summary of the main contribution, ideally about 20 words or fewer. Prefer concrete keywords, avoid question-form titles, avoid unnecessary abbreviations, and avoid making the method the title unless the method itself is the main contribution. Make the cover letter about one page, state significance, journal fit, readership fit, and one or two key findings, and do not turn it into a second abstract or a full result list.
Top-Level Logic: Keep one visible chain across the manuscript:
Introduction Development: Build compelling introductions that:
Methods Documentation: Ensure reproducibility through:
Results Presentation: Present findings with:
Discussion Construction: Synthesize findings by:
Apply citation styles correctly across disciplines. For comprehensive style guides, refer to references/citation_styles.md.
Major Citation Styles:
Best Practices:
Create effective data visualizations that enhance comprehension. For detailed best practices, refer to references/figures_tables.md.
When to Use Tables vs. Figures:
Design Principles:
Common Figure Types:
Ensure completeness and transparency by following established reporting standards. For comprehensive guideline details, refer to references/reporting_guidelines.md.
Key Guidelines:
Each guideline provides checklists ensuring all critical methodological elements are reported.
Apply fundamental scientific writing principles. For detailed guidance, refer to references/writing_principles.md.
Clarity:
Conciseness:
Accuracy:
Objectivity:
CRITICAL: Always write in full paragraphs, never submit bullet points in scientific papers.
Scientific papers must be written in complete, flowing prose. Use this two-stage approach for effective writing:
Stage 1: Create Section Outlines with Key Points
When starting a new section:
Example outline (Introduction section):
- Background: AI in drug discovery gaining traction
* Cite recent reviews (Smith 2023, Jones 2024)
* Traditional methods are slow and expensive
- Gap: Limited application to rare diseases
* Only 2 prior studies (Lee 2022, Chen 2023)
* Small datasets remain a challenge
- Our approach: Transfer learning from common diseases
* Novel architecture combining X and Y
- Study objectives: Validate on 3 rare disease datasetsStage 2: Convert Key Points to Full Paragraphs
Once the outline is complete, expand each bullet point into proper prose:
Example conversion to prose:
Artificial intelligence approaches have gained significant traction in drug discovery
pipelines over the past decade (Smith, 2023; Jones, 2024). While these computational
methods show promise for accelerating the identification of therapeutic candidates,
traditional experimental approaches remain slow and resource-intensive, often requiring
years of laboratory work and substantial financial investment. However, the application
of AI to rare diseases has been limited, with only two prior studies demonstrating
proof-of-concept results (Lee, 2022; Chen, 2023). The primary obstacle has been the
scarcity of training data for conditions affecting small patient populations.
To address this challenge, we developed a transfer learning approach that leverages
knowledge from well-characterized common diseases to predict therapeutic targets for
rare conditions. Our novel neural architecture combines convolutional layers for
molecular feature extraction with attention mechanisms for protein-ligand interaction
modeling. The objective of this study was to validate our approach across three
independent rare disease datasets, assessing both predictive accuracy and biological
interpretability of the results.Key Differences Between Outlines and Final Text:
| Outline (Planning Stage) | Final Manuscript |
|---|---|
| Bullet points and fragments | Complete sentences and paragraphs |
| Telegraphic notes | Full explanations with context |
| List of citations | Citations integrated into prose |
| Abbreviated ideas | Developed arguments with transitions |
| For your eyes only | For publication and peer review |
Common Mistakes to Avoid:
When Lists ARE Acceptable (Limited Cases):
Lists may appear in scientific papers only in specific contexts:
Integration with Literature Search:
Verified literature gathering is essential for Stage 1 (creating outlines):
This two-stage process ensures you:
When revising an existing manuscript section rather than drafting from scratch:
Claim: ... | Evidence: ... | Status: supported / partial / missingpartial or missing, do one of three things only:Use this especially when:
Before treating a section as finished, ask:
If the answer is not clearly defensible from the manuscript itself, revise the section before polishing style.
Adapt manuscripts to journal requirements:
Adapt language, terminology, and conventions to match the specific scientific discipline. Each field has established vocabulary, preferred phrasings, and domain-specific conventions that signal expertise and ensure clarity for the target audience.
Identify Field-Specific Linguistic Conventions:
Biomedical and Clinical Sciences:
Molecular Biology and Genetics:
Chemistry and Pharmaceutical Sciences:
Ecology and Environmental Sciences:
Physics and Engineering:
Neuroscience:
Social and Behavioral Sciences:
General Principles:
Match Audience Expertise:
Define Technical Terms Strategically:
Maintain Consistency:
Avoid Field Mixing Errors:
Verify Terminology Usage:
Top Rejection Reasons:
Writing Quality Issues:
Stage 1: Planning
Stage 2: Drafting (Use two-stage writing process for each section)
Remember: Bullet points are for planning only—the final manuscript must be in complete paragraphs.
Stage 3: Revision
Stage 4: Final Preparation
This skill works effectively with:
This skill includes comprehensive reference files covering specific aspects of scientific writing:
references/imrad_structure.md: Detailed guide to IMRAD format and section-specific contentreferences/citation_styles.md: Complete citation style guides (APA, AMA, Vancouver, Chicago, IEEE)references/figures_tables.md: Best practices for creating effective data visualizationsreferences/reporting_guidelines.md: Study-specific reporting standards and checklistsreferences/writing_principles.md: Core principles of effective scientific communicationreferences/latex-layout.md: LaTeX float placement and typesetting fixes (loose pages, stranded headings, figures that do not fill the page, "Float too large")Load these references as needed when working on specific aspects of scientific writing.
Rule: Every sentence in the polished output must be ≤30 words and span no more than 2 lines at standard formatting.
Cohesion strategies:
| Strategy | Example |
|---|---|
| Restate the subject | "The resulting serial sections exhibit inherent spatial asymmetry. Such asymmetry makes pixel-level alignment unattainable." |
| Adverbial connective | "PAS captures only one dimension of the pathology. Therefore, special stains are essential." |
| Pronoun reference | "Pathologists employ a panel of histochemical stains. Each targets a distinct feature." |
| Definite article + noun | "The renal biopsy specimen is small. The limited tissue complicates multi-modal analysis." |
| Demonstrative + noun | "This heterogeneity makes IgAN an ideal test case." |
Before: To characterise phenotypic evolution and spatial reorganisation within this microenvironment during kidney injury, pathologists employ a panel of histochemical stains. PAS, Masson's trichrome, PAM and H&E each interrogate distinct pathological dimensions, including basement membrane lesions, collagen deposition and cellular infiltration, enabling a composite assessment of tissue damage. (38 words)
After: To characterise phenotypic evolution and spatial reorganisation within this microenvironment during kidney injury, pathologists employ a panel of histochemical stains. PAS, Masson's trichrome, PAM and H&E each interrogate distinct pathological dimensions. These include basement membrane lesions, collagen deposition and cellular infiltration. Together, they enable a composite assessment of tissue damage.
© Yrzsh, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/scientific-writing of Yrzsh/paper-workbench.
Open the folder on GitHubat commit 801516a
Scientific Writing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Scientific Writing this skillYrzsh/paper-workbench | 112 | — | ~7.4k | Automated safety check: Pass | MIT | |
| Citation Verification GuideGalaxy-Dawn/claude-scholar | 5.7k | 2 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Citation ManagementK-Dense-AI/claude-scientific-writer | 2.4k | 2 repos | ~3.9k | Automated safety check: Notes | MIT | |
| Academic Paper Writing PipelineImbad0202/academic-research-skills | 51k | — | ~16k | Automated safety check: Pass | Custom licence | |
| Academic HumanizerAIScientists-Dev/academic-humanizer | 1.9k | 1 repos | ~4.2k | Automated safety check: Pass | MIT | |
| Academic Research Suite for CodexImbad0202/academic-research-skills-codex | 12k | — | ~12k | Automated safety check: Pass | Custom licence |
Galaxy-Dawn/claude-scholar
Reference guidance for checking every citation in academic writing against canonical sources such as DOI, arXiv, CrossRef and Semantic Scholar, to catch fake or wrong references.
K-Dense-AI/claude-scientific-writer
Finds papers in OpenAlex, PubMed and Google Scholar, turns DOIs, PMIDs and arXiv IDs into clean BibTeX, and validates citations for a manuscript or thesis.
Imbad0202/academic-research-skills
Runs a 12-agent pipeline that plans, drafts, cites, reviews and formats academic papers, with modes for revision, rebuttals, abstracts and citation checks.
AIScientists-Dev/academic-humanizer
Improve the clarity and voice of AI-assisted academic writing (papers, theses, rebuttals) and funding proposals (NSF Project Summary/Description, NIH Specific Aims): preserve scholarly conventions…
Imbad0202/academic-research-skills-codex
A router skill that sends academic work such as literature reviews, drafting, citation checks, peer review and revision to the right workflow in the ARS suite.
federicodeponte/opendraft
An 18-agent pipeline that turns one topic line into a drafted research paper, literature review, or thesis chapter.
Yrzsh/paper-workbench
A skill your agent uses when generating or regenerating a full manuscript with the DSH Paper Workbench staged pipeline — contract-first, per-section generation with citation-pool gates, programmatic…
Yrzsh/paper-workbench
Diagnose and repair the clarity and logic of manuscript prose, journal-agnostic.
Categories
A skill your agent uses when writing or revising scientific manuscripts, abstracts, figures, or references for journal submission and you need full-paragraph prose, scientific structure…. Scientific Writing is an agent skill from Yrzsh/paper-workbench. Use when writing or revising scientific manuscripts, abstracts, figures, or references for journal submission and you need full-paragraph prose, scientific structure, citation-style guidance, or reporting-guideline support.
Scientific Writing fits situations like: revising scientific manuscripts; references for journal submission and you need full-paragraph prose; scientific structure; citation-style guidance.
Run `npx skills add Yrzsh/paper-workbench --skill scientific-writing -a claude-code`. Or copy the skill folder (skills/scientific-writing in Yrzsh/paper-workbench) into .claude/skills/scientific-writing in your project. Claude Code loads it when a task matches its description.
Run `npx skills add Yrzsh/paper-workbench --skill scientific-writing -a codex`. Or copy the skill folder (skills/scientific-writing in Yrzsh/paper-workbench) into .agents/skills/scientific-writing in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Yrzsh/paper-workbench --skill scientific-writing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/scientific-writing, .gemini/skills/scientific-writing, .github/skills/scientific-writing and .opencode/skills/scientific-writing in your project.
Going by SKILL.md and its folder, Scientific Writing needs the command-line tools its instructions call (python) and credentials named OPENROUTER_API_KEY. Our summary lists: Python 3; A credential in OPENROUTER_API_KEY.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Scientific Writing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 7.4k tokens (SKILL.md is roughly 30k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Scientific Writing: Citation Verification Guide (Galaxy-Dawn/claude-scholar, 5.7k stars), Citation Management (K-Dense-AI/claude-scientific-writer, 2.4k stars), Academic Paper Writing Pipeline (Imbad0202/academic-research-skills, 51k stars) and Academic Humanizer (AIScientists-Dev/academic-humanizer, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Yrzsh (a GitHub user) maintains it in Yrzsh/paper-workbench, which has 112 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on September 7, 2026.
Source: Yrzsh/paper-workbench on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.