Agent skill

Glmv PDF To Ppt

by zai-org in zai-org/GLM-skills

Convert a PDF (research paper, report, or any document) into a polished multi-slide HTML presentation with a structured outline JSON and summary markdown.

Apache-2.0Auto-check passedDocuments & Office

Install Glmv PDF To Ppt

skills CLI
$ npx skills add zai-org/GLM-skills --skill glmv-pdf-to-ppt -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install zai-org/GLM-skills glmv-pdf-to-ppt --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/zai-org/GLM-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/glmv-pdf-to-ppt .claude/skills/glmv-pdf-to-ppt && rm -rf skills-src

Use ~/.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/

Facts

Skill name
glmv-pdf-to-ppt
GitHub stars
476
Token cost
~3.5k tokens
SKILL.md length
1,281 words
Files
5 (incl. scripts)
Skills in repo
16
Repo updated
First seen
Licence
Apache-2.0

At a glance

Convert a PDF (research paper, report, or any document) into a polished multi-slide HTML presentation with a structured outline JSON and summary markdown.

  • Works in 8 steps: Create Output Directory → Convert PDF Pages to Images (DPI 120) → Read All Pages in Order → …
  • This skill when the user mentions making slides
  • SKILL.md covers Dependencies, When to Use, Output Directory Convention and Input, plus 4 more sections
  • Runs Python scripts from its folder; calls python, pip and curl

What it does

Glmv PDF To Ppt is an agent skill from zai-org/GLM-skills. Convert a PDF (research paper, report, or any document) into a polished multi-slide HTML presentation with a structured outline JSON and summary markdown. Trigger this skill when the user mentions making slides or a PPT from a PDF — in Chinese or English.

Its SKILL.md is about 3.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts (for example `scripts/crop.py`, `scripts/generate_slide.py` and `scripts/pdf_to_images.py`).

It sits in Documents & Office, covering Slides and decks and PDF. The repository describes itself as: Official skills for the GLM family of models. The licence is Apache-2.0.

When your agent uses it

  • This skill when the user mentions making slides
  • A PPT from a PDF — in Chinese

Example prompts

  • “/glmv-pdf-to-ppt”

Requirements

  • Python 3

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Create Output Directory
  2. Convert PDF Pages to Images (DPI 120)
  3. Read All Pages in Order
  4. Plan Outline & Save outline.json
  5. Crop Required Images (Grounding + Subagent)
  6. Measure Cropped Image Dimensions
  7. Generate Slides One by One
  8. Generate summary.md

What it can do on your machine

Read from SKILL.md and the folder at commit 2ecd31c. 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

    Ships 3 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python
    • pip
    • curl
    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pip and curl, 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

Glmv PDF To Ppt loads about 3.5k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 1,281 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~68
When it runs · the whole SKILL.md, loaded when a task matches
~3.5k

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); the scripts in this folder are not scanned.

SKILL.md

The full file from zai-org/GLM-skills at commit 2ecd31c, republished under its Apache-2.0 licence (© zai-org). 1,281 words, ~3,469 tokens.

Download SKILL.mdSave it as .claude/skills/glmv-pdf-to-ppt/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
glmv-pdf-to-ppt
description
Convert a PDF (research paper, report, or any document) into a polished multi-slide HTML presentation with a structured outline JSON and summary markdown. Trigger this skill when the user mentions making slides or a PPT from a PDF — in Chinese or English.

PDF → HTML PPT Skill

Convert any PDF into a multi-slide HTML presentation. Pages are converted to images at DPI 120, read sequentially to understand the content, then a structured outline.json is saved, images are cropped locally (no cloud upload), slides are rendered one by one, and finally a summary.md is generated.

Scripts are in: {SKILL_DIR}/scripts/

Dependencies

Python packages (install once):

bash
pip install pymupdf pillow

System tools: curl (pre-installed on macOS/Linux).

When to Use

Trigger when the user asks to make slides or a presentation from a PDF — phrases like: "make a PPT from a PDF", "convert PDF to slides", "create a presentation from this paper", "根据pdf做ppt", "根据论文做幻灯片", "做PPT", "做幻灯片", "生成演示文稿", "把这个pdf转成ppt", or any similar intent in Chinese or English.

Output Directory Convention

All output goes under {WORKSPACE}/ppt/<pdf_stem>_<timestamp>/:

ppt/
└── <pdf_stem>_<timestamp>/
    ├── outline.json        ← structured slide plan (SlidesPlan schema)
    ├── crops/              ← locally-saved cropped images
    │   ├── slide3_method_crop.png
    │   └── slide5_results_crop.png
    ├── slide_01.html
    ├── slide_02.html
    ├── ...
    └── summary.md          ← final summary document
  • <pdf_stem> = PDF filename without extension
  • <timestamp> = format YYYYMMDD_HHMMSS (e.g. 20240119_143022)
  • Cropped images go in crops/ subfolder
  • Each slide HTML references images via relative path crops/<name>.png

Input

$ARGUMENTS is the path to the PDF file (local) or an HTTP/HTTPS URL.

  • If user provides a URL: download with curl first, then convert
  • If user provides a local PDF path: convert directly

Workflow

Phase 0 — Create Output Directory

Compute the output path:

python
import os, datetime
pdf_stem = os.path.splitext(os.path.basename(pdf_path))[0]
timestamp = datetime.datetime.now().strftime("%Y%m%d_%H%M%S")
out_dir = os.path.join(workspace, "ppt", f"{pdf_stem}_{timestamp}")

Create it immediately:

bash
mkdir -p "<out_dir>/crops"

Record out_dir — use it for all subsequent phases.


Phase 1 — Convert PDF Pages to Images (DPI 120)

If the input is a URL, download it first:

bash
pdf_stem=$(basename "$ARGUMENTS" .pdf)
curl -L -o "/tmp/${pdf_stem}.pdf" "$ARGUMENTS"

Then convert (pass either the downloaded path or the original local path):

bash
python {SKILL_DIR}/scripts/pdf_to_images.py "<pdf_path>" --dpi 120

Outputs JSON to stdout:

json
[{"page": 1, "path": "/abs/path/page_001.png"}, ...]

Parse and store the full page → path map. These local paths are used for viewing pages and as --path input to crop.py.


Phase 2 — Read All Pages in Order

View all page images sequentially before planning anything. Your goal here is pure understanding — absorb the full structure, content, figures, and arguments of the document.

While reading, note:

  • What figures, charts, or tables appear on which pages
  • The overall arc (intro → method → results → conclusion for papers; or logical structure for other doc types)
  • Candidate visuals worth cropping for slides (page number + rough region)

Do NOT plan or write slides yet — just read and understand all pages first.


Phase 3 — Plan Outline & Save outline.json

After reading all pages, plan 8–15 slides (adapt freely for non-academic documents).

SlideTypical purpose
1Title, authors, affiliation, venue/year
2Motivation / Problem statement
3Related Work (brief)
4–N-2Method / Core contributions (one concept per slide)
N-1Results & Experiments
NConclusion & Future Work

For each slide that needs a visual, identify:

  • Which page it comes from (the local page path from Phase 1)
  • A description of what the visual shows and why it belongs on this slide

Save the outline as <out_dir>/outline.json using exactly this schema:

json
{
  "presentation_title": "Paper Title Here",
  "lang": "Chinese",
  "total_slides": 10,
  "slides_plan": [
    {
      "slide_index": 1,
      "title": "Slide Title",
      "main_content": "Key points and text content for this slide",
      "template_id": null,
      "required_crops": [
        {
          "url": "<page_image_url_from_phase1>",
          "visual_description": "Figure 3: architecture diagram showing encoder-decoder",
          "usage_reason": "Illustrates the core model structure for slide 4"
        }
      ]
    }
  ]
}

Field notes:

  • lang: "Chinese" or "English" — match the PDF language

  • template_id: always null

  • required_crops: empty array [] if this slide needs no images

  • url in each crop: the local file path of the source page image (from Phase 1 path field) — this is what crop.py will open and crop from

  • visual_description: what the visual shows, including figure/table number if available

  • usage_reason: why this visual belongs on this particular slide

  • For images that need cropping, note the approximate region — exact crop boxes are determined in Phase 4

Write outline.json using the Write tool to <out_dir>/outline.json.


Phase 4 — Crop Required Images (Grounding + Subagent)

IMPORTANT: You MUST delegate ALL cropping to a clean subagent using the Agent tool. By this phase your context is very long (all page images + outline), which degrades visual coordinate accuracy. A fresh subagent with only the target image produces much more precise coordinates.

IMPORTANT: You MUST use the provided {SKILL_DIR}/scripts/crop.py script for ALL image cropping. Do NOT write your own cropping code, do NOT use PIL/Pillow directly, do NOT use any other method.

Read outline.json. Collect all crops needed, then launch one subagent per source page (or one per crop if pages differ). The subagent uses grounding-style localization — it views the image, locates the target element, and outputs a precise bounding box in normalized 0–999 coordinates.

Use the Agent tool like this:

Agent tool call:
  description: "Grounding crop page N"
  prompt: |
    You are a visual grounding and cropping assistant. Your task is to precisely
    locate specified visual elements in a page image and crop them out.

    ## Grounding method

    Use visual grounding to locate each target:
    1. Read the source image using the Read tool to view it
    2. Identify the target element described below
    3. Determine its bounding box as normalized coordinates in the 0–999 range:
       - 0 = left/top edge of the image
       - 999 = right/bottom edge of the image
       - These are thousandths, NOT pixels, NOT percentages (0–100)
       - Format: [x1, y1, x2, y2] where (x1,y1) is top-left, (x2,y2) is bottom-right
       - Example: [0, 0, 500, 500] = top-left quarter of the image
    4. Be precise: tightly bound the target element with a small margin (~10–20 units)
       around it. Do NOT crop too wide or too narrow.

    ## Source image
    <page_image_path>

    ## Crops needed

    For each crop below, first do grounding (locate the element), then crop:

    1. Name: "slide<N>_<descriptive_name>"
       Target: "<visual_description from outline.json>"
       Context: "<usage_reason from outline.json>"

    ## Crop command

    After determining the bounding box [X1, Y1, X2, Y2] for each target, run:
    ```bash
    python <SKILL_DIR>/scripts/crop.py \
        --path "<page_image_path>" \
        --box X1 Y1 X2 Y2 \
        --name "<crop_name>" \
        --out-dir "<out_dir>/crops"
    ```

    ## Verification

    After each crop, READ the output image to visually verify the correct region
    was captured. If the crop missed the target or is too wide/narrow, adjust the
    coordinates and re-run crop.py.

    ## Output

    Report the final results as a list:
    - crop_name: <name>, file: <output_filename>, box: [X1, Y1, X2, Y2]

Replace <page_image_path>, <SKILL_DIR>, <out_dir>, and crop details with actual values from your context.

The crop.py script outputs JSON: {"path": "/abs/path/slide3_method_crop.png"}

Collect results from all subagents and build the mapping: slide_index → [crop filename, ...] to reference in HTML. The filename will be <name>_crop.png.

Launch subagents for independent pages in parallel when possible. Wait for all to complete before proceeding.


Phase 5 — Measure Cropped Image Dimensions

After cropping, get pixel dimensions:

bash
python3 -c "
from PIL import Image; import os, json
d = '<out_dir>/crops'
sizes = {}
for f in sorted(os.listdir(d)):
    if f.endswith('.png'):
        w, h = Image.open(os.path.join(d, f)).size
        sizes[f] = {'width': w, 'height': h, 'aspect': round(w/h, 2)}
print(json.dumps(sizes, indent=2))
"

Use aspect ratios to pick each slide's layout:

Aspect ratioLayout recommendation
< 0.7 (tall/narrow)text + image side-by-side — max-height: 600px on image
0.7 – 1.3 (square-ish)text + image — image takes ~50% width
> 1.3 (wide)Image on top or bottom, text above/below
> 2.0 (very wide, e.g. tables)full-image — spans full 1280px width, caption below

Show full SKILL.md (504 more words)Show less
Phase 6 — Generate Slides One by One

For each slide, write the HTML, save it to a temp file, then call generate_slide.py.

Step A — Write HTML to /tmp/slide_N.html

  • All <img src="..."> must use relative paths: crops/<name>_crop.png
  • Do NOT use absolute paths or URLs for cropped images
  • Navigation is click-area based — no buttons needed:
    • Clicking the left half of the slide navigates to the previous slide
    • Clicking the right half of the slide navigates to the next slide
    • On slide 1, left click does nothing; on the last slide, right click does nothing
    • Keyboard ← / → arrows also navigate
    • Implement with two transparent <div> overlays covering each half, positioned absolute over the slide canvas

Step B — Save slide:

bash
python {SKILL_DIR}/scripts/generate_slide.py \
    --html-file /tmp/slide_N.html \
    --index N \
    --total <total> \
    --title "<presentation title>" \
    --out-dir "<out_dir>/"

Repeat until all slides are saved.


Phase 7 — Generate summary.md

Write <out_dir>/summary.md in the same language as the slides (lang from outline.json).

Include:

  • Document title and basic info (authors, venue, year if applicable)
  • Brief abstract/overview (2–3 sentences)
  • Per-slide breakdown table: slide number, title, 1–2 sentence summary
  • Main contributions or takeaways (bullet list)
  • Link to slide_01.html to open the first slide

Example structure:

markdown
# [Presentation Title]

> **来源 / Source:** [PDF filename] | **语言 / Language:** Chinese | **幻灯片数 / Slides:** 10

## 摘要
[2-3 sentence overview]

## 幻灯片概览
| # | 标题 | 主要内容 |
|---|------|---------|
| 1 | 标题页 | ... |
...

## 主要贡献
- ...

## 📂 打开演示文稿
[▶ 开始播放](slide_01.html)

HTML Slide Spec

Each slide is a standalone HTML file — full <html>…</html> with embedded CSS only.

Canvas: fixed 1280 × 720 px, overflow: hidden — nothing scrolls.

Consistent design across all slides:

  • Choose a visual style that fits the document's domain and tone — no fixed palette or font required
  • If the user specifies a style, follow it exactly; otherwise infer from the content (e.g. a ML paper → clean modern; a historical report → editorial serif; a product pitch → bold and branded)
  • Same fonts, colors, and spacing system applied uniformly to every slide
  • Every slide shows: slide title, page counter (bottom-right corner), presentation title (subtle footer)

Navigation on each slide:

  • Two transparent click areas cover the full slide height: left 50% → previous slide, right 50% → next slide
  • On slide 1 the left area is inert; on the last slide the right area is inert
  • Keyboard ← / → arrows also navigate
  • No visible buttons needed — optionally show a subtle ‹ / › hint at the edges that fades in on hover

Layout patterns:

  • title-card — centered hero, large title, authors/venue below
  • text-only — structured bullet points, max 5–6 items, generous whitespace
  • text + image — image right or left, text opposite
  • full-image — image fills canvas, minimal text overlay
  • grid — 2×2 or 3-column figures with captions

Images:

  • Use relative paths: crops/<name>_crop.png
  • Add style="object-fit: contain; max-width: 100%; max-height: 100%;"
  • Add captions below in small italic text

Do NOT:

  • Use external JS frameworks or icon CDNs
  • Use placeholder/stock images — only the cropped PDFs
  • Generate generic purple-gradient-on-white slides
  • Let content overflow the 720px height

Quality Checklist

  • Output directory named <pdf_stem>_<timestamp>/
  • outline.json saved with valid SlidesPlan schema
  • All crops saved to crops/ (local only, no cloud upload)
  • Each slide fits within 1280×720, nothing overflows
  • Consistent theme across all slides
  • Crop images referenced via relative path crops/<name>_crop.png
  • Slide number and presentation title visible on every slide
  • Left/right click-area navigation works, keyboard arrows work
  • summary.md written in the correct language, links to slide_01.html

Language

Match the PDF language. Chinese PDF → Chinese slides and summary. English → English. No mixing.

© zai-org, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (scripts) in skills/glmv-pdf-to-ppt of zai-org/GLM-skills.

  • SKILL.md
  • .DS_Store
  • scripts/crop.py
  • scripts/generate_slide.py
  • scripts/pdf_to_images.py

Open the folder on GitHubat commit 2ecd31c

Compare with similar skills

Glmv PDF To Ppt 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.

Glmv PDF To Ppt compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Glmv PDF To Ppt this skillzai-org/GLM-skills476—~3.5kAutomated safety check: PassApache-2.0
Paper Deckzsyggg/paper-craft-skills1.3k—~1.4kAutomated safety check: PassNone
Paper2slidesQuZhan51496/paper2anything450—~3.8kAutomated safety check: NotesApache-2.0
Li CarouselJakeschincariol/linkedin-agent-skill1.7k—~715Automated safety check: PassMIT
Ky Markdown RebuilderKyrieCheungYep/ky-markdown-rebuilder117—~5.7kAutomated safety check: PassNone
PDF ReadingWide-Moat/open-computer-use1261 repos~2.7kAutomated safety check: PassProprietary

Similar skills

  • Paper Deck

    zsyggg/paper-craft-skills

    将论文、技术文章或知识内容制作成高真实感的 AIGC 幻灯片。先做叙事结构和逐页视觉导演,再调用生图模型生成每一页 16:9 slide image,最后合成为 PPTX/PDF。适合论文汇报、组会、公开课、技术分享、商业化研究展示;当用户提到“论文PPT”“AI生成PPT”“不像AI的PPT”“高质感幻灯片”“逐页生图PPT”时使用。

    1.3k GitHub stars~1.4k tokensUpdated 4 mo ago
    Documents & OfficeAuto-check passed
  • Paper2slides

    QuZhan51496/paper2anything

    Turn an academic paper PDF into a presentation deck (.pptx) end-to-end.

    450 GitHub stars~3.8k tokensUpdated 2 mo ago
    Documents & OfficeAuto-check: notes
  • Li Carousel

    Jakeschincariol/linkedin-agent-skill

    Build a LinkedIn document post (carousel) - slide-by-slide copy, the cover that earns the swipe, and the PDF to upload.

    1.7k GitHub stars~715 tokensUpdated 23 days ago
    Documents & OfficeAuto-check passed
  • Ky Markdown Rebuilder

    KyrieCheungYep/ky-markdown-rebuilder

    Rebuild visual documents into reliable Markdown by combining text extraction with page or screenshot alignment.

    117 GitHub stars~5.7k tokensUpdated 3 mo ago
    Documents & OfficeAuto-check passed
  • PDF Reading

    Wide-Moat/open-computer-use

    A skill your agent uses when you need to read, inspect, or extract content from PDF files — especially when file content is NOT in your context and you need to read it from disk.

    126 GitHub starsUsed in 1 repo~2.7k tokens
    Documents & OfficeAuto-check passed
  • Sci HTML

    ShZhao27208/Aut_Sci_Write

    Generate academic presentation-style HTML slide decks and browser reports from PDFs, structured text, Markdown, paper summaries, outlines, or research notes.

    209 GitHub stars~1.4k tokensUpdated 1 mo ago
    Documents & OfficeAuto-check: notes

More from zai-org/GLM-skills

All 16 skills in this repo
  • Glmocr

    zai-org/GLM-skills

    Extract text from images using GLM-OCR API. An agent skill from zai-org/GLM-skills.

    476 GitHub stars~1.1k tokensUpdated 5 mo ago
    Auto-check passed
  • Glm Image Gen

    zai-org/GLM-skills

    Official skill for generating high-quality images from text prompts using ZhiPu GLM-Image API.

    476 GitHub stars~2.9k tokensUpdated 5 mo ago
    Auto-check passed
  • Glmocr Formula

    zai-org/GLM-skills

    Official skill for recognizing and extracting mathematical formulas from images and PDFs into LaTeX format using ZhiPu GLM-OCR API.

    476 GitHub stars~2.2k tokensUpdated 5 mo ago
    Auto-check passed
  • Glmocr Handwriting

    zai-org/GLM-skills

    Official skill for recognizing handwritten text from images using ZhiPu GLM-OCR API.

    476 GitHub stars~1.7k tokensUpdated 5 mo ago
    Auto-check passed
  • Glmocr Table

    zai-org/GLM-skills

    Official skill for recognizing and extracting tables from images and PDFs into Markdown format using ZhiPu GLM-OCR API.

    476 GitHub stars~1.7k tokensUpdated 5 mo ago
    Auto-check passed
  • Glmv Caption

    zai-org/GLM-skills

    Generate captions (descriptions) for images, videos, and documents using ZhiPu GLM-V multimodal model series.

    476 GitHub stars~2k tokensUpdated 5 mo ago
    Auto-check: notes

Questions about Glmv PDF To Ppt

What does Glmv PDF To Ppt do?

Convert a PDF (research paper, report, or any document) into a polished multi-slide HTML presentation with a structured outline JSON and summary markdown. Glmv PDF To Ppt is an agent skill from zai-org/GLM-skills. Convert a PDF (research paper, report, or any document) into a polished multi-slide HTML presentation with a structured outline JSON and summary markdown.

When should I use Glmv PDF To Ppt?

Glmv PDF To Ppt fits situations like: this skill when the user mentions making slides; A PPT from a PDF — in Chinese.

How do I install Glmv PDF To Ppt in Claude Code?

Run `npx skills add zai-org/GLM-skills --skill glmv-pdf-to-ppt -a claude-code`. Or copy the skill folder (skills/glmv-pdf-to-ppt in zai-org/GLM-skills) into .claude/skills/glmv-pdf-to-ppt in your project. Claude Code loads it when a task matches its description.

How do I install Glmv PDF To Ppt in Codex?

Run `npx skills add zai-org/GLM-skills --skill glmv-pdf-to-ppt -a codex`. Or copy the skill folder (skills/glmv-pdf-to-ppt in zai-org/GLM-skills) into .agents/skills/glmv-pdf-to-ppt in your project. Codex loads it when a task matches its description.

Can I use Glmv PDF To Ppt 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 zai-org/GLM-skills --skill glmv-pdf-to-ppt -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/glmv-pdf-to-ppt, .gemini/skills/glmv-pdf-to-ppt, .github/skills/glmv-pdf-to-ppt and .opencode/skills/glmv-pdf-to-ppt in your project.

What does Glmv PDF To Ppt need to run?

Going by SKILL.md and its folder, Glmv PDF To Ppt needs Python for the scripts in its folder and the command-line tools its instructions call (python, pip, curl and python3). Our summary lists: Python 3.

Does Glmv PDF To Ppt access the network?

SKILL.md contains no URLs. Its commands use pip and curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Glmv PDF To Ppt 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Glmv PDF To Ppt use?

Glmv PDF To Ppt is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Glmv PDF To Ppt use?

About 3.5k tokens (SKILL.md is roughly 14k 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 Glmv PDF To Ppt?

Skills that share tags, products or a category with Glmv PDF To Ppt: Paper Deck (zsyggg/paper-craft-skills, 1.3k stars), Paper2slides (QuZhan51496/paper2anything, 450 stars), Li Carousel (Jakeschincariol/linkedin-agent-skill, 1.7k stars) and Ky Markdown Rebuilder (KyrieCheungYep/ky-markdown-rebuilder, 117 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Glmv PDF To Ppt?

zai-org (a GitHub organization) maintains it in zai-org/GLM-skills, which has 476 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on April 15, 2026.

Source: zai-org/GLM-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.