Skip to content
cccskills
FreePublished on GitHub

ppt-workflow-location

Create PowerPoint presentations through shell_agent with specified slide counts and content, then locate the resulting files in nested workspace folders. Copy the presentation to the working directory and check that it exists and is not empty.

OriginalShow the original description

Generate PowerPoint files using shell_agent and locate them in nested workspace directories

Works withPowerPoint
See how to install

Good for

  • Creating slides with specified content and structure
  • Generating presentations when document tools fail
  • Locating presentations in nested folders
  • Checking whether a generated presentation is empty

Files included (2)

  • SKILL.md3.0 KB
  • .skill_id35 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

PowerPoint Generation and Location Workflow

When to Use This Skill

Use this workflow when:

  • Direct document generation tools fail or are unavailable
  • You need to create PowerPoint presentations with specific slide content and structure
  • Output files may be created in unexpected nested directories within the workspace

Step 1: Generate PowerPoint via shell_agent

Delegate the PowerPoint creation task to shell_agent with clear specifications:

Use shell_agent to create a PowerPoint presentation with:
- Specify the exact number of slides needed
- Define the content/topic for each slide
- Request the file be saved with a clear filename (e.g., presentation.pptx)
- Ask the agent to confirm the file path after creation

Example task description:

Create a PowerPoint presentation with 10 slides covering [topic]. Each slide should have a title and bullet points. Save it as presentation.pptx and tell me the full file path.

Step 2: Locate the Output File

PowerPoint files created by shell_agent may be in nested workspace directories. Use the find command to locate them:

# Find all .pptx files in the workspace
find . -name "*.pptx" -type f

# Or search for a specific filename
find . -name "presentation.pptx" -type f

Step 3: Copy to Working Directory

Once located, copy the file to your working directory:

# Copy the found file to current directory
cp /path/to/found/presentation.pptx .

# Or move it if you prefer
mv /path/to/found/presentation.pptx .

Step 4: Verify the File

Confirm the file exists and is accessible:

# List the file with details
ls -la presentation.pptx

# Check file size to ensure it's not empty
file presentation.pptx

Common Pitfalls

  1. Don't assume the file is in the current directory - shell_agent may create files in subdirectories
  2. Don't skip the find step - always verify the file location before proceeding
  3. Check file size - ensure the PowerPoint file is not empty (0 bytes)
  4. Request confirmation - ask shell_agent to report the file path after creation

Example Workflow

# Step 1: shell_agent creates the presentation (done via task delegation)

# Step 2: Find the created file
find . -name "*.pptx" -type f
# Output: ./workspace/task_123/output/presentation.pptx

# Step 3: Copy to working directory
cp ./workspace/task_123/output/presentation.pptx .

# Step 4: Verify
ls -la presentation.pptx
# Output: -rw-r--r-- 1 user user 45632 Jan 15 10:30 presentation.pptx

Troubleshooting

ProblemSolution
File not found with findSearch broader: find / -name "*.pptx" 2>/dev/null
File is 0 bytesRe-run shell_agent task; ensure it completed successfully
Permission deniedCheck directory permissions with ls -la on parent dirs
Multiple .pptx files foundUse more specific search: find . -name "*presentation*.pptx"

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Prepare audio stems, the separate parts of a track, for mixing by matching their durations with silence, loops, or crossfades. Verify each generated and processed file before moving to the next production step.

  • Match audio parts with different durations
  • Extend drums and melodic parts using suitable methods
  • Check audio specifications before mixing
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

Produce audio in separate stems, meaning individual instrument tracks, and verify each output as you go. Align track lengths with silence, loops, or crossfades, then apply effects, mix a master, and package the files.

  • Align instrument tracks to a reference audio file
  • Choose how to extend tracks that are too short
  • Verify audio properties after generation and effects
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

Build serverless endpoints that relay external API requests for a dashboard while keeping API keys on the server. Includes Vercel examples for input checks, caching, cross-origin access, and consistent JSON responses.

  • Connect a dashboard to external APIs without exposing API keys
  • Create endpoints for stock quotes and news
  • Standardize API responses and error handling
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

Produce a master track and separate audio parts through a structured Python workflow. Apply filters and reverb, export WAV files with consistent settings, package them in a ZIP archive, and check that the deliverables meet the requested specifications.

  • Export a master track with separate audio parts
  • Apply filters and reverb to audio
  • Check duration and format across deliverables
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

Keep document creation moving when web searches and page retrieval repeatedly fail. The skill preserves the original task, uses the model’s existing knowledge, and clearly identifies information that could not be checked against external sources.

  • Continue drafting after repeated web retrieval failures
  • Preserve task requirements during network errors
  • Mark information that could not be externally verified
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

When Python execution repeatedly fails in execute_code_sandbox, use a file-based alternative: save the script, run it through the shell, and capture results or errors. The guidance covers paths, imports, timeouts, structured output, and optional cleanup.

  • Retry Python work through the shell after repeated sandbox failures
  • Run longer tasks with an adjusted timeout
  • Execute Python work that needs multiple files or system utilities
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

See all skills by HKUDS

Report a problem with this skill