Writing Quotation
Formatting rules for quoting external sources (papers, articles, web pages, prompt templates) inside a Markdown document. Quotations always live in fenced code blocks (never the `>` blockquote syntax), original and translation sit together, source references go on the line after the fence, and bare numeric references like `[1]` are forbidden. Other sourced-writing skills (survey, ja-explainer, ...) reference this skill. Consult whenever you write or edit a quotation block.
Install
/plugin marketplace add mathbullet/skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add mathbullet/skills --skill writing-quotationgit clone --depth 1 https://github.com/mathbullet/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/plugins/writing-quotation/skills/writing-quotation ~/.claude/skills/writing-quotationPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Writing Quotation Formatting rules for quoting external sources inside a Markdown document. Other skills that produce sourced deliverables (`survey`, `ja-explainer`, and similar) reference this one. ## 1. Why quote the original A summary alone does not let the reader judge whether the writer's reading of the source is correct. Placing the original alongside lets the reader cross-check the writer's interpretation against the source itself. Quotations and prose (the writer's own summary or interpretation) must stay visually and structurally distinct. ## 2. Quotations always go inside code blocks Quote external sources inside a fenced code block, regardless of content type — prose, prompt templates, code, XML-tagged text, anything. Do not use the blockquote syntax (`>`). ## 3. Structure of a quotation block A quotation block has the following shape. - Opening code fence - Original text - One blank line - Translation into the writer's working language (only when the source is in a different language) - Closing code fence - The source reference `[label (YYYY/MM), location]` on the line immediately after the closing fence Rules: - Original and translation sit together inside the same code block. - One blank line separates them. - Do not insert a horizontal rule (`---`) between original and translation. - Do not move the translation outside the code block. Do not put it in parentheses next to the original.
Details
- Skill name
writing-quotation- Repository
- mathbullet/skills
- Path
plugins/writing-quotation/skills/writing-quotation/SKILL.md- License
- MIT
- Repo updated
- 11 November 2026
FAQ
What does the Writing Quotation skill do?
Formatting rules for quoting external sources (papers, articles, web pages, prompt templates) inside a Markdown document. Quotations always live in fenced code blocks (never the `>` blockquote syntax), original and translation sit together, source references go on the line after the fence, and bare numeric references like `[1]` are forbidden. Other sourced-writing skills (survey, ja-explainer, ...) reference this skill. Consult whenever you write or edit a quotation block.
How do I install the Writing Quotation skill?
Claude Code plugin: /plugin marketplace add mathbullet/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Writing Quotation popular?
It lives in mathbullet/skills, which has 198 GitHub stars and 5 forks.
Related skills
Documenting with Sources
198mathbullet/skills
Common conventions for writing Markdown documents that cite external sources (survey reports, paper explainers, and any deliverable that surfaces facts from outside). Defines mandatory citation, in-text reference format, quotation-versus-prose separation, the ban on fabricated associations, and the source-list format. Referenced by survey, ja-explainer, and any skill that produces sourced output.
Ja Text Communication
198mathbullet/skills
ユーザーとのあらゆるコミュニケーションの最初に、何かを書く・出力する前に必ず参照すること。チャット応答・レポート・解説・作業報告・ドキュメントなど、文章を書く・出力するすべての場面に適用される。
Survey
198mathbullet/skills
Investigate a topic across papers, articles, social-media posts, and industry signals, then deliver an indexed Markdown report. Use when the user asks to investigate, survey, gather sources, build an index, collect evidence, round up references, or otherwise wants a thorough cross-source roundup on a specific topic.
Bazel
293mohitmishra786/low-level-dev-skills
Bazel build system skill for C/C++ projects. Use when writing BUILD files with cc_library and cc_binary rules, registering toolchains, configuring remote execution, debugging sandbox issues, using query and cquery for dependency graphs, or migrating from CMake to Bazel. Activates on queries about Bazel, BUILD files, cc_library, cc_binary, Bzlmod, bazel query, remote execution, or Bazel toolchain registration.
Space Wechat Layout
189SpaceZephyr/design-buddy
微信公众号排版。Use when the user asks to turn an article, Markdown draft, longform post, essay, newsletter, review, or Chinese article into a WeChat Official Account-ready HTML layout with local preview, selectable Claude/OpenAI/Google-inspired styles, and a button to copy rich HTML for pasting into the WeChat editor.
Bootloaders Embedded
293mohitmishra786/low-level-dev-skills
Embedded bootloader skill for firmware update and app handoff. Use when writing a custom bootloader, jumping to application code, relocating VTOR, or implementing DFU/USB firmware update on Cortex-M. Activates on queries about bootloader jump, vector table relocation, application entry point, STM32 DFU, or dual-bank flash.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.