DocsWriting

Writing

Scripts, Metadata, and Publishing Packs

15 min read

On this page

  1. 01Use Creator Mode for open-ended writing
  2. 02Use Skills for repeatable deliverables
  3. 03Common output chain
  4. 04Useful slash commands
  5. 05Start from a brief when possible
  6. 06Ask for a complete publishing pack
  7. 07Rewrite by platform instead of copying
  8. 08Review before recording or publishing

Use Creator Mode for open-ended writing

Creator Mode adds creator-specific workflow rules: infer missing fields when reasonable, produce concrete deliverables, include CTA and publishing notes, and suggest the next Skill after a task.

Use Skills for repeatable deliverables

Bundled creator Skills cover content scripts, metadata packs, platform tone rewriting, content repurposing, Shorts splitting, subtitle proofreading, cover generation, content calendars, and research.

Common output chain

A typical flow is: content calendar entry -> script -> metadata pack -> cover -> final publishing review. Artifact actions can suggest the next step from an existing output, so you do not need to restart from scratch.

Useful slash commands

These are examples of creator-facing Skill triggers. The exact installed list depends on the current build and enabled Skills.

Example
/content-creator Create YouTube and Instagram versions of this script
/metadata-pack-generator Generate title, description, tags, and CTA from this script
/platform-tone-rewriter Adapt this narration for Instagram, TikTok, LinkedIn, and YouTube
/shorts-splitter Split the subtitles into 6 candidate Shorts/Reels clips

Start from a brief when possible

Scripts improve when the task includes a topic, audience, platform, target length, source material, and the action you want viewers to take. If you do not have those yet, ask Lumo to produce a short brief first, then draft from that brief instead of jumping straight into a final script.

Ask for a complete publishing pack

For creator work, a useful output is often more than the script. Ask for the opening hook, outline, full draft, shot list, title options, description, tags, CTA, pinned comment, thumbnail direction, and platform notes when the piece is close to publishing.

Rewrite by platform instead of copying

Do not reuse the same script everywhere. Use platform-tone-rewriter when the same idea needs different pacing, opening, vocabulary, or CTA. Keep the core message stable, then let each platform version change the surface structure.

Review before recording or publishing

Before using a draft, check factual claims, sponsor requirements, names, numbers, platform length, spoken rhythm, and whether the CTA matches the piece. For sensitive topics, treat Lumo's draft as an editing surface, not a final authority.

Lumo can organize and draft, but you are still the final publisher.

Docs feedback

Tell us if this page does not match your current build.

Send feedback
PreviousNext
Lumo

One focused workspace for every step from creating to publishing.

Product

  • Features
  • Use Cases
  • Pricing
  • Download
  • Changelog

Resources

  • Documentation
  • FAQ
  • Support
  • Blog

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service

© 2026 Lumo. All rights reserved.

|

Built for creators. Free, Pro, and Max plans available now.

Download Lumo
Skip to main content
Lumo
FeaturesUse CasesPricingFAQBlog
Download