--as user

• --as user

  (Recommended): Create, read, and manage presentations as the currently logged-in user. Complete user authorization before execution:

lark-cli auth login --domain slides

• --as bot

  : Only used when the user explicitly requires operation as the application identity, or when the bot needs to hold/create resources. When using the bot identity, additionally confirm whether the bot actually has access permission to the target presentation.

1. For creation, reading, adding/deleting slides, and continuing to edit existing PPT according to the link provided by the user, use

   --as user

   by default first.
2. If there is insufficient permission, first check whether the bot identity is misused currently; do not fall back to bot by default.
3. Only switch to

   --as bot

   when the user explicitly requires "operation with application identity / bot identity", or the current workflow is that the bot creates resources and then grants collaboration authorization.

lark-cli slides +create --title "Presentation Title" --slides '[
  "<slide xmlns=\"http://www.larkoffice.com/sml/2.0\"><style><fill><fillColor color=\"rgb(245,245,245)\"/></fill></style><data><shape type=\"text\" topLeftX=\"80\" topLeftY=\"80\" width=\"800\" height=\"100\"><content textType=\"title\"><p>Page Title</p></content></shape><shape type=\"text\" topLeftX=\"80\" topLeftY=\"200\" width=\"800\" height=\"200\"><content textType=\"body\"><p>Body Content</p><ul><li><p>Key Point 1</p></li><li><p>Key Point 2</p></li></ul></content></shape></data></slide>"
]'

The above is the minimum usable example. For richer page effects (gradient background, cards, charts, tables, etc.), refer to the Workflow and XML templates below.

Important:

references/slides_xml_schema_definition.xml

is the only correct source of XML protocol for this skill; other md files are only summaries of it and the CLI schema.

This is a presentation, not a document. Each slide is an independent visual page, with low information density and sufficient white space in typesetting.

Step 1: Requirement clarification & knowledge reading
  - Clarify user requirements: theme, audience, number of pages, style preference
  - If the user has no clear style, recommend according to the theme (see the style judgment table below)
  - Read XML Schema reference:
    · xml-schema-quick-ref.md — Element and attribute quick reference
    · xml-format-guide.md — Detailed structure and examples
    · slides_demo.xml — Real XML example

Step 2: Generate outline → user confirmation → creation
  - Generate a structured outline (title per page + key points + layout description), submit to the user for confirmation
  - Less than 10 pages: Use slides +create --slides '[...]' to create PPT and add all pages in one step
  - More than 10 pages: First use `slides +create` to create a blank PPT, then use `xml_presentation.slide.create` to add pages one by one
  - Each slide requires complete XML: background, text, graphics, color scheme
  - Complex elements (table, chart) need to refer to the original XSD

Step 3: Review & delivery
  - After creation, use xml_presentations.get to read the full text XML, confirm:
    · Is the number of pages correct? Is the content of each page complete?
    · Is the color scheme unified? Is the font size hierarchy reasonable?
  - If there is a problem → Use xml_presentation.slide.delete to delete the problematic page and recreate it
  - No problem → Delivery: Inform the user of the presentation ID and access method

Note: Gradient colors must use

rgba()

format with percentage stop points, such as

linear-gradient(135deg,rgba(15,23,42,1) 0%,rgba(56,97,140,1) 100%)

. Using

rgb()

or omitting stop points will cause the server to fall back to white.

linear-gradient(135deg,rgba(15,23,42,1) 0%,rgba(56,97,140,1) 100%)

rgb(59,130,246)

rgb(248,250,252)

rgb(30,60,114)

rgb(30,41,59)

rgb(255,255,255)

rgb(34,197,94)

rgb(51,65,85)

linear-gradient(135deg,rgba(88,28,135,1) 0%,rgba(190,24,93,1) 100%)

rgb(248,250,252)

rgb(59,130,246)

rgb(15,23,42)

1. Use

   wiki.spaces.get_node

   to query node information

lark-cli wiki spaces get_node --as user --params '{"token":"wiki_token"}'

1. Extract key information from the returned result

   • node.obj_type

     : Document type, slides correspond to

     slides

   • node.obj_token

     : Real presentation token (used for subsequent operations)

   • node.title

     : Document title
2. After confirming that

   obj_type

   is

   slides

   , use

   obj_token

   as

   xml_presentation_id

lark-cli schema slides.<resource>.<method>    # Must check parameter structure before calling API
lark-cli slides <resource> <method> [flags]  # Call API

Important: When using native API, you must first run

schema

to view the

--data

/

--params

parameter structure, do not guess the field format.

• get

  — Read full PPT information, return in xml format

• create

  — Create a page under the specified xml presentation

  • delete

    — Delete a page under the specified xml presentation

1. Outline first before operation: Generate an outline and submit it to the user for confirmation before creating PPT to avoid rework
2. Creation process: For less than 10 pages, it is recommended to use

   slides +create --slides '[...]'

   to create in one step; for more than 10 pages, first use

   slides +create

   to create a blank PPT, then use

   xml_presentation.slide.create

   to add pages one by one
3. Only

   <style>

   ,

   <data>

   ,

   <note>

   are direct child elements of

   <slide>

   : Text and graphics must be placed inside

   <data>

4. Text is expressed through

   <content>

   : Must use

   <content><p>...</p></content>

   , cannot write text directly in shape
5. Save key IDs: Subsequent operations require

   xml_presentation_id

   ,

   slide_id

   ,

   revision_id

6. Be careful with deletion: Deletion operation is irreversible, and at least one slide must be retained

• Is the background color/gradient set for each page? Is the style consistent with the whole?
• Title uses large font size (28-48), body uses small font size (13-16), with clear hierarchy?
• Is the color matching of similar elements consistent? (e.g. all indicator cards are in the same color system, all body text is the same color)
• Is the color of decorative elements (dividers, color blocks, vertical lines) coordinated with the primary color?
• Is the text box size sufficient to accommodate the content? (width × height)
• Is the

  type

  of shape correct? (use

  text

  for text boxes,

  rect

  for decoration)
• Are all XML tags closed correctly? Are special characters (

  &

  ,

  <

  ,

  >

  ) escaped?

--slides

Note: If the content of md files is inconsistent with the output of

slides_xml_schema_definition.xml

or

lark-cli schema slides.<resource>.<method>

, the latter two shall prevail.