skill-presentation
- Repo stars 435
- Author updated Live
- Author repo nvim
- Domain
- Data
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @benbrastmckie · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- Python
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: skill-presentation
description: Presentation extraction and slide generation routing Thin wrapper that routes presentation opera…
category: data
runtime: Python
---
# skill-presentation output preview
## PART A: Task fit
- Use case: Presentation extraction and slide generation routing Thin wrapper that routes presentation operations to the presentation-agent. Reference (do not load eagerly): This skill activates when: When an implementing agent encounters any of these patterns: Do not invoke for: runs entirely locally; runs on Python. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Context Pointers / Trigger Conditions / Direct Invocation” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Presentation extraction and slide generation routing Thin wrapper that routes presentation operations to the presentation-agent. Reference (do not load eagerly): This skill activates when: When an implementing agent encounters any of these patterns: Do not invoke for: runs entirely locally; runs on Python. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Context Pointers / Trigger Conditions / Direct Invocation” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source mentions slash commands such as `/convert`; use them first when your agent supports command triggers.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Start with a small task and check whether the result follows “Context Pointers / Trigger Conditions / Direct Invocation”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: skill-presentation
description: Presentation extraction and slide generation routing Thin wrapper that routes presentation opera…
category: data
source: benbrastmckie/nvim
---
# skill-presentation
## When to use
- Presentation extraction and slide generation routing Thin wrapper that routes presentation operations to the presentat…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Context Pointers / Trigger Conditions / Direct Invocation” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "skill-presentation" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Context Pointers / Trigger Conditions / Direct Invocation
rules -> SKILL.md triggers / order / output contract
runtime -> Python | read files, write/modify files, run shell commands | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} Presentation Skill
Thin wrapper that routes presentation operations to the presentation-agent.
Context Pointers
Reference (do not load eagerly):
- Path:
.claude/context/formats/subagent-return.md - Purpose: Return validation
- Load at: Subagent execution only
Note: This skill is a thin wrapper. Context is loaded by the delegated agent, not this skill.
Trigger Conditions
This skill activates when:
Direct Invocation
- User runs
/convertwith a.pptx/.pptsource and--format beamer|polylux|touying - User requests presentation conversion in conversation
Implicit Invocation (during task implementation)
When an implementing agent encounters any of these patterns:
Plan step language patterns:
- "Convert presentation to Beamer"
- "Extract slides from PowerPoint"
- "Generate Polylux slides"
- "Create Touying presentation"
- "Convert PPTX to LaTeX"
File extension detection:
- Source file has extension:
.pptx,.ppt - Target mentions: "Beamer", "slides", ".tex", "Polylux", "Touying", ".typ"
Task description keywords:
- "presentation conversion"
- "PowerPoint to LaTeX"
- "slide extraction"
- "academic slides"
When NOT to trigger
Do not invoke for:
- Document conversions (use skill-filetypes)
- Spreadsheet conversions (use skill-spreadsheet)
- Simple markdown extraction without slide formatting
Execution
1. Input Validation
Validate required inputs:
source_path- Must be provided and file must existoutput_path- Optional, defaults to source dir with .tex extensionoutput_format- Optional, defaults to "beamer"theme- Optional theme name
# Validate source exists
if [ ! -f "$source_path" ]; then
return error "Source file not found: $source_path"
fi
# Validate source is presentation format
source_ext="${source_path##*.}"
case "$source_ext" in
pptx|ppt|md) ;; # Valid
*) return error "Not a presentation format: .$source_ext" ;;
esac
# Determine output path if not provided
if [ -z "$output_path" ]; then
source_dir=$(dirname "$source_path")
source_base=$(basename "$source_path" | sed 's/\.[^.]*$//')
case "$output_format" in
beamer|latex|tex) output_path="${source_dir}/${source_base}.tex" ;;
polylux|touying|typst|typ) output_path="${source_dir}/${source_base}.typ" ;;
pptx) output_path="${source_dir}/${source_base}_generated.pptx" ;;
*) output_path="${source_dir}/${source_base}.tex" ;;
esac
fi
2. Context Preparation
Prepare delegation context:
{
"source_path": "/absolute/path/to/presentation.pptx",
"output_path": "/absolute/path/to/slides.tex",
"output_format": "beamer",
"theme": "metropolis",
"metadata": {
"session_id": "sess_{timestamp}_{random}",
"delegation_depth": 1,
"delegation_path": ["orchestrator", "convert", "skill-presentation"]
}
}
3. Invoke Agent
CRITICAL: You MUST use the Agent tool to spawn the agent.
Required Tool Invocation:
Tool: Agent (NOT Skill, NOT Plan)
Parameters:
- subagent_type: "presentation-agent"
- prompt: [Include source_path, output_path, output_format, theme, metadata]
- description: "Convert {source_path} to {output_format} slides"
The agent will:
- Detect available tools (python-pptx, pandoc, markitdown)
- Extract presentation content
- Generate formatted slide output
- Extract and preserve speaker notes
- Return standardized JSON result
4. Return Validation
Validate return matches subagent-return.md schema:
- Status is one of: converted, partial, failed
- Summary is non-empty and <100 tokens
- Artifacts array present with output file path
- Metadata contains slide count
5. Return Propagation
Return validated result to caller without modification.
Return Format
Expected successful return:
{
"status": "converted",
"summary": "Successfully converted presentation.pptx to Beamer slides with 15 slides",
"artifacts": [
{
"type": "implementation",
"path": "/absolute/path/to/slides.tex",
"summary": "Beamer presentation with speaker notes"
}
],
"metadata": {
"session_id": "sess_...",
"agent_type": "presentation-agent",
"delegation_depth": 2,
"tool_used": "python-pptx+pandoc",
"slide_count": 15,
"has_speaker_notes": true
},
"next_steps": "Review and compile slides"
}
Error Handling
Input Validation Errors
Return immediately with failed status if source file not found or not a presentation.
Unsupported Format
Return failed status with clear message about supported formats.
Agent Errors
Pass through the agent's error return verbatim.
Tool Not Available
Return failed status with installation instructions.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review