Clipmivo Video
BarneyD66/clipmivo-tools
Create and manage AI video tasks through ClipmivoAI using its MCP server, CLI or REST API.
A skill your agent uses when generating or editing video with Luma Ray models on Scenario via MCP: cinematic text-to-video, image-to-video from a start frame, start plus end frame anchors, seamless…
Install Scenario Luma Video
$ npx skills add scenario-labs/skills --skill scenario-luma-video -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install scenario-labs/skills scenario-luma-video --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/scenario-labs/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/scenario-luma-video .claude/skills/scenario-luma-video && 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 "scenario-luma-video" agent skill from https://github.com/scenario-labs/skills/tree/main/skills/scenario-luma-video into .claude/skills/scenario-luma-video/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-luma-video", 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/scenario-labs/skills/tree/main/skills/scenario-luma-videoType 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 scenario-labs/skills --skill scenario-luma-video -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install scenario-labs/skills scenario-luma-video --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/scenario-labs/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/scenario-luma-video .agents/skills/scenario-luma-video && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "scenario-luma-video" agent skill from https://github.com/scenario-labs/skills/tree/main/skills/scenario-luma-video into .agents/skills/scenario-luma-video/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-luma-video", 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 scenario-labs/skills --skill scenario-luma-video -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install scenario-labs/skills scenario-luma-video --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/scenario-labs/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/scenario-luma-video .cursor/skills/scenario-luma-video && 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 "scenario-luma-video" agent skill from https://github.com/scenario-labs/skills/tree/main/skills/scenario-luma-video into .cursor/skills/scenario-luma-video/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-luma-video", 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/scenario-labs/skills.git --path skills/scenario-luma-video--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 scenario-labs/skills --skill scenario-luma-video -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install scenario-labs/skills scenario-luma-video --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/scenario-labs/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/scenario-luma-video .gemini/skills/scenario-luma-video && 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 "scenario-luma-video" agent skill from https://github.com/scenario-labs/skills/tree/main/skills/scenario-luma-video into .gemini/skills/scenario-luma-video/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-luma-video", 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 scenario-labs/skills scenario-luma-videoInstalls 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 scenario-labs/skills --skill scenario-luma-video -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/scenario-labs/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/scenario-luma-video .github/skills/scenario-luma-video && 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 "scenario-luma-video" agent skill from https://github.com/scenario-labs/skills/tree/main/skills/scenario-luma-video into .github/skills/scenario-luma-video/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-luma-video", 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 scenario-labs/skills --skill scenario-luma-video -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install scenario-labs/skills scenario-luma-video --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/scenario-labs/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/scenario-luma-video .opencode/skills/scenario-luma-video && 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 "scenario-luma-video" agent skill from https://github.com/scenario-labs/skills/tree/main/skills/scenario-luma-video into .opencode/skills/scenario-luma-video/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scenario-luma-video", 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.
Facts
- Skill name
scenario-luma-video- GitHub stars
- 946
- Token cost
- ~1.6k tokens
- SKILL.md length
- 771 words
- Files
- 1
- Skills in repo
- 146
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when generating or editing video with Luma Ray models on Scenario via MCP: cinematic text-to-video, image-to-video from a start frame, start plus end frame anchors, seamless…
- Works in 7 steps: search with target="models",… → model_schema_get with the generator id:… → upload_asset the product still (see the… → …
- Editing video with Luma Ray models on Scenario via MCP: cinematic text-to-video
- SKILL.md covers Overview, Quick reference, Two editors, one strength ladder and Prompt motion, not adjectives, plus 2 more sections
- Calls npx
What it does
Scenario Luma Video is an agent skill from scenario-labs/skills. Use when generating or editing video with Luma Ray models on Scenario via MCP: cinematic text-to-video, image-to-video from a start frame, start plus end frame anchors, seamless looping clips, HDR output, restyling footage while preserving motion with edit strengths and face, pose, depth, or trajectory controls, reframing to another aspect ratio by outpainting, or budget prompt edits on real footage. Keywords: Luma, Dream Machine, Ray 3.2, Ray 3, Modify Video, Reframe, T2V, I2V, V2V, loop, HDR.
Its SKILL.md is about 1.6k 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 Media & Creative, covering AI video generation. It works with Model Context Protocol. The repository describes itself as: Get production-ready images, video, audio, and 3D from any AI agent: skills that pick the right model, price before spending, and keep characters and brands consistent through… The licence is MIT.
When your agent uses it
- Editing video with Luma Ray models on Scenario via MCP: cinematic text-to-video
- Image-to-video from a start frame
- Start plus end frame anchors
- Seamless looping clips
Example prompts
- “/scenario-luma-video”
Requirements
- Node.js
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- search with target="models", query="luma", public=true. Prefer the newest non-deprecated generation, e.g. model_luma-ray-3-2 and its Edit…
- model_schema_get with the generator id: options and their vetoes before anything else.
- upload_asset the product still (see the scenario skill) to get an asset id.
- model_run with that model_id, dry_run=true, and the exact parameters={"prompt": "A crystal perfume bottle catches soft window light as a…
- Repeat model_run with wait=false, then jobs_wait with the returned job id, re-called with pending_job_ids on timeout, never a second…
- model_schema_get the Reframe sibling, then model_run with parameters={"video": "", "aspectRatio": "9:16", "prompt": "continue the marble…
- asset_display both and inspect the outpainted edges before delivery.
What it can do on your machine
Read from SKILL.md and the folder at commit f6f8ab7. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
Shell commands in SKILL.md call:
npx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Scenario Luma Video loads about 1.6k tokens when it runs. Until then it costs about 130 tokens; SKILL.md has 771 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from scenario-labs/skills at commit f6f8ab7, republished under its MIT licence (© scenario-labs). 771 words, ~1,550 tokens.
Download SKILL.mdSave it as
.claude/skills/scenario-luma-video/SKILL.md (or your agent's skills folder).- name
- scenario-luma-video
- description
- Use when generating or editing video with Luma Ray models on Scenario via MCP: cinematic text-to-video, image-to-video from a start frame, start plus end frame anchors, seamless looping clips, HDR output, restyling footage while preserving motion with edit strengths and face, pose, depth, or trajectory controls, reframing to another aspect ratio by outpainting, or budget prompt edits on real footage. Keywords: Luma, Dream Machine, Ray 3.2, Ray 3, Modify Video, Reframe, T2V, I2V, V2V, loop, HDR.
- license
- MIT
Scenario Luma Video
Overview
Luma's video line on Scenario is four sibling models, one per mode: Ray 3.2 generates from text or frame anchors, Ray 3.2 Edit restyles footage under structural controls, Ray 3.2 Reframe outpaints to a new aspect ratio, and Modify Video makes budget prompt edits. Route by member before tuning anything; Luma's image models belong to the scenario-luma-image skill. Discover the live set with search and treat model_schema_get as the contract.
Connection and the core loop: see the scenario skill in this repo; model-agnostic video work: the scenario-video skill. If a sibling skill named here is missing from your available skills, ask the user to install it (npx skills add scenario-labs/skills --skill <name>); unattended, proceed from tool schemas and flag the gap.
Quick reference
Each mode is its own model (names from the live schemas, caps as of authoring time):
| Member | Inputs | Behavior |
|---|---|---|
| Ray 3.2 | prompt (+ startFrame, endFrame) | text or image to video; endFrame is only valid alongside startFrame |
| Ray 3.2 Edit | video + prompt | restyles while keeping motion and timing; editStrength plus controls |
| Ray 3.2 Reframe | video + prompt + aspectRatio | fits a new ratio by outpainting, never cropping; prompt fills the canvas |
| Modify Video | video (+ prompt, firstFrame) | budget prompt edits via a mode ladder; source up to 30 seconds, 100 MB |
On Ray 3.2 the options veto one another. At authoring time duration was a unit string, "5s" or "10s", never a number; "10s" refused loop, hdr, startFrame, and endFrame. hdr required 720p or 1080p from the 540p, 720p, 1080p resolution list; six aspectRatio values ran 9:16 through 21:9. Edit and Reframe share that resolution list; Modify Video has no resolution parameter. duration, resolution, and hdr each move the price (1080p ran several times 720p's cost and wait), so dry_run the option set before a batch.
Two editors, one strength ladder
Ray 3.2 Edit and Modify Video restyle through the same nine-value ladder, adhere_1 through reimagine_3 (adhere stays close, flex restyles but keeps recognizable elements, reimagine transforms), and share little else. Edit names the ladder editStrength; Modify names it mode. Edit takes a guide image as startFrame; Modify's firstFrame is an edited copy of the source's own first frame, not an arbitrary style image. Edit alone offers keyframes (up to 64 image-and-index anchors, mutually exclusive with the single startFrame guide), face, pose, depth, normals, and trajectory conditioning toggles, resolution choice, and hdr; or pass autoControls: true instead of a manual editStrength. The price gap ran near two orders of magnitude at authoring time, so dry_run the same clip on both and pay for Edit's controls only when the edit needs them.
Show full SKILL.md (338 more words)Show less
Prompt motion, not adjectives
Ray rewards natural-language prompts of roughly 50 to 300 words built around motion: a subject mid-action, one named camera move (slow push-in, handheld follow), and one physical consequence of the action (droplets scattering, dust rising). Concrete lighting language lands directly. With loop, hold motion intensity constant (steady rain, drifting steam) so the cycle closes cleanly. On Reframe, prompt only the edges: describe what the new canvas should contain and leave the original subject alone.
Worked example: a 16:9 hero clip recut for 9:16
searchwithtarget="models",query="luma",public=true. Prefer the newest non-deprecated generation, e.g.model_luma-ray-3-2and its Edit and Reframe siblings (live hits at authoring time: re-discover each session).model_schema_getwith the generator id: options and their vetoes before anything else.upload_assetthe product still (see thescenarioskill) to get an asset id.model_runwith thatmodel_id,dry_run=true, and the exactparameters={"prompt": "A crystal perfume bottle catches soft window light as a single drop arcs off the stopper, slow push-in, product commercial style.", "startFrame": "asset_a", "duration": "5s", "resolution": "1080p", "aspectRatio": "16:9"}; re-estimate after any option change.- Repeat
model_runwithwait=false, thenjobs_waitwith the returned job id, re-called withpending_job_idson timeout, never a secondmodel_run. model_schema_getthe Reframe sibling, thenmodel_runwithparameters={"video": "<generated asset id>", "aspectRatio": "9:16", "prompt": "continue the marble counter downward and the softly lit wall upward", "resolution": "1080p"}, same wait discipline.asset_displayboth and inspect the outpainted edges before delivery.
Common mistakes
duration: 5or"5": Ray 3.2 takes the unit string,"5s"or"10s".- A 10 second loop, HDR grade, or frame anchor:
"10s"excludes all three; drop to"5s". - Ray parameter names on Modify Video: it takes
firstFrameandmode, notstartFrameandeditStrength. editStrengthwithautoControls, orstartFramewithkeyframes: each pair is mutually exclusive on Edit.- Prompting the whole scene on Reframe: the prompt describes only the added canvas; the source subject stays.
- Vibrant, whimsical, or hyper-realistic in a Ray prompt: they degrade quality in this family.
© scenario-labs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/scenario-luma-video of scenario-labs/skills.
Open the folder on GitHubat commit f6f8ab7
Compare with similar skills
Scenario Luma Video 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 |
|---|---|---|---|---|---|---|
| Scenario Luma Video this skillscenario-labs/skills | 946 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Clipmivo VideoBarneyD66/clipmivo-tools | 142 | — | ~945 | Automated safety check: Pass | MIT | |
| ComfyUI Local DriverSlavaSexton/ComfyUI-Agent-Kit | 105 | — | ~12k | Automated safety check: Pass | Apache-2.0 | |
| Generate VideoArcReel/ArcReel | 5.4k | — | ~1.3k | Automated safety check: Warn | AGPL-3.0 | |
| Generate StoryboardArcReel/ArcReel | 5.4k | — | ~816 | Automated safety check: Pass | AGPL-3.0 | |
| Manage ProjectArcReel/ArcReel | 5.4k | — | ~1.6k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
ComfyUI Local Driver
SlavaSexton/ComfyUI-Agent-Kit
Drives a local ComfyUI install over its HTTP API to generate and edit images, video and audio, with per-model prompt recipes and workflow guidance.
Generate Video
ArcReel/ArcReel
为分镜或自包含视频单元生成视频。当用户要求生成或重做视频时使用；支持整集、单项与批量自选. An agent skill from ArcReel/ArcReel.
Generate Storyboard
ArcReel/ArcReel
为分镜生成分镜图。当用户说"生成分镜"、"预览分镜画面"、想重新生成某些分镜图、或剧本中有分镜缺少分镜图时使用。自动保持角色和画面连续性。
Manage Project
ArcReel/ArcReel
项目管理工具集。使用场景：新增/修改角色/场景/道具到 project.json（经 patchproject 工具，按 table+name upsert）、级联重命名资产（renameasset 工具）、合并同一身份被重复登记的资产（mergeasset 工具）、写顶层 settings 字段、编辑项目概述…
Image Edit Workbench
henjicc/Henji-AI
在痕迹AI修图、调色、抠出或选中主体、移除物体、修补瑕疵、编辑图层与蒙版、导出图片或流转图片产物时使用。视频时间线与成片用 video-edit-workbench；写代码画面用 video-edit-code-creation。
More from scenario-labs/skills
All 146 skills in this repoScenario Blender Grease Pencil
scenario-labs/skills
A skill your agent uses when drawing or animating with Grease Pencil in Blender 5.x from Python: 2D or 2.5D illustration, frame-by-frame animation, a cutout or part-based 2D character, strokes with…
Scenario Blender Hair
scenario-labs/skills
A skill your agent uses when grooming hair or fur in Blender with hair curves, such as a character hairstyle, animal fur, procedural fur in geometry nodes, or hair cards and mesh hair for games.
Scenario Blender Lighting Rendering
scenario-labs/skills
A skill your agent uses when lighting, rendering or compositing in Blender: light a character, product or hero shot, interior at dusk or night, three-point or motivated lighting, sun and sky, HDRI…
Scenario Chatgpt Pet Create
scenario-labs/skills
A skill your agent uses when creating a ChatGPT pet or Codex pet with Scenario: hatching an animated companion from a text idea, a character, mascot or brand cue, or reference photos and art; making…
Scenario Godot Animation
scenario-labs/skills
A skill your agent uses when animating characters or scenes in Godot 4.7: AnimationPlayer clips and RESET, AnimationTree state machines and blend spaces built in code, Mixamo or glTF import, loop…
Scenario Godot Audio
scenario-labs/skills
A skill your agent uses when adding or fixing sound in Godot 4.7: audio buses and effects, volume sliders, 'too many sounds', combat audio with hundreds of enemies, sounds clipping or distorting, 3D…
Related
Works with
Categories
Questions about Scenario Luma Video
What does Scenario Luma Video do?
A skill your agent uses when generating or editing video with Luma Ray models on Scenario via MCP: cinematic text-to-video, image-to-video from a start frame, start plus end frame anchors, seamless…. Scenario Luma Video is an agent skill from scenario-labs/skills. Use when generating or editing video with Luma Ray models on Scenario via MCP: cinematic text-to-video, image-to-video from a start frame, start plus end frame anchors, seamless looping clips, HDR output, restyling footage while preserving motion with edit strengths and face, pose, depth, or trajectory controls, reframing to another aspect ratio by outpainting, or budget prompt edits on real footage.
When should I use Scenario Luma Video?
Scenario Luma Video fits situations like: editing video with Luma Ray models on Scenario via MCP: cinematic text-to-video; image-to-video from a start frame; start plus end frame anchors; seamless looping clips.
How do I install Scenario Luma Video in Claude Code?
Run `npx skills add scenario-labs/skills --skill scenario-luma-video -a claude-code`. Or copy the skill folder (skills/scenario-luma-video in scenario-labs/skills) into .claude/skills/scenario-luma-video in your project. Claude Code loads it when a task matches its description.
How do I install Scenario Luma Video in Codex?
Run `npx skills add scenario-labs/skills --skill scenario-luma-video -a codex`. Or copy the skill folder (skills/scenario-luma-video in scenario-labs/skills) into .agents/skills/scenario-luma-video in your project. Codex loads it when a task matches its description.
Can I use Scenario Luma Video in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add scenario-labs/skills --skill scenario-luma-video -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/scenario-luma-video, .gemini/skills/scenario-luma-video, .github/skills/scenario-luma-video and .opencode/skills/scenario-luma-video in your project.
What does Scenario Luma Video need to run?
Going by SKILL.md and its folder, Scenario Luma Video needs the command-line tools its instructions call (npx). Our summary lists: Node.js.
Does Scenario Luma Video access the network?
SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Scenario Luma Video safe to install?
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.
What licence does Scenario Luma Video use?
Scenario Luma Video is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Scenario Luma Video use?
About 1.6k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Scenario Luma Video?
Skills that share tags, products or a category with Scenario Luma Video: Clipmivo Video (BarneyD66/clipmivo-tools, 142 stars), ComfyUI Local Driver (SlavaSexton/ComfyUI-Agent-Kit, 105 stars), Generate Video (ArcReel/ArcReel, 5.4k stars) and Generate Storyboard (ArcReel/ArcReel, 5.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Scenario Luma Video?
scenario-labs (a GitHub organization) maintains it in scenario-labs/skills, which has 946 GitHub stars. The repository holds 146 skills in this directory. The repository was last updated on October 10, 2026.
Source: scenario-labs/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.