934 skills · sorted by relevance
Process Excel workbooks and generate PDF or Word documents by running Python scripts directly through run_shell. The skill covers multi-sheet edits, formatting, data transformations, document layout, and error handling for complex tasks that can exceed agent step limits.
Create documents when several research or execution tools fail. Delegate PDFs and complex layouts to shell_agent, a separate agent, or save Markdown directly, while distinguishing verified facts from general guidance and checking the output.
Generate documents through shell scripts when standard tools fail, then locate files saved in nested folders. Covers finding PowerPoint or PDF outputs, copying them to the delivery location, and checking that the resulting files exist and are usable.
Run Python through shell commands when sandbox execution fails because required packages are unavailable. The skill explains short commands, multiline scripts, package checks, and output verification, with examples for creating Excel and Word files.
Recover failed Python tasks by saving the code as a script and running it through the shell. Provides steps to inspect errors and confirm generated files for spreadsheet creation, data processing, and calculations.
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.
Recover Python file-generation tasks when sandbox execution fails by saving a script and running it through the shell, a command interface. Use the workflow for PDFs, document file operations, dependency checks, and output verification.
Create PowerPoint presentations with shell_agent, then switch to Python and python-pptx if generation fails. The workflow captures error details, locates output files, and checks that the presentation opens and contains the expected slides.
Create PowerPoint presentations with specified slide content and structure. If generation through shell_agent fails, the workflow switches to Python, captures error details, locates the output, and checks the file format, size, and slide count.
Recover from repeated code execution tool failures by writing a script through the shell and running it with an absolute path. Check output files and investigate syntax, permissions, disk space, or execution errors when needed.
Generate PDF documents when sandbox execution fails with unclear errors. Check available Python libraries, switch to direct shell execution, and verify the resulting file while collecting error details to help diagnose problems.
Use shell heredocs, which pass multiline text directly to a command, when write_file fails on complex code. Save TypeScript, JSX, JSON, or shell scripts with literal quotes and formatting, then verify the file and its contents.
Recover PDF or DOCX generation when execute_code_sandbox fails with unclear errors. Use run_shell to execute Python directly, check required libraries, report specific failures, and verify that the output file was created.
Extract text, tables, and headings from Word documents when standard file reading tools fail. The workflow uses Python and python-docx through run_shell to recover document content for further review or analysis.
Convert Markdown into Word, PDF, and HTML using a workflow suited to the document. Simple files use direct delegation, while documents with special characters use separate conversion steps, character replacement, and output checks.
Recover document generation tasks by separating Markdown content creation, format conversion, and output checks. Uses pandoc to produce Word, PDF, or HTML files, making it easier to identify which conversion step failed.
Run Python code through a saved script and shell when repeated sandbox failures point to environment problems. Captures execution output and checks exit codes and expected files to verify whether the task completed.
Create formatted Excel files when sandbox code execution fails by running Python through the shell. Uses openpyxl to add styled headers, alternating row colors, borders, alignment, and adjusted column widths.
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.
Capture MSBuild execution records as binary logs during .NET builds, tests, packaging, publishing, or restores. It explains unique filenames, PowerShell quoting, and file checks so logs remain available for later failure or performance analysis.
Review and implement gh-aw workflows and Go code with security checks for untrusted input, shell commands, dependency versions, and permissions. The skill also covers event-specific conditions and tools that inspect workflows for errors and security risks without running them.
Assess file upload and import features for weaknesses in file checks and processing. The skill covers extension and content-type bypasses, unsafe image and document handling, archive extraction flaws, and evidence needed to confirm execution or browser-side impact.
[omh] Shell command or test-suite execution: policy overlay for terminal commands - add cwd, environment, safety, and result-evidence gates after preferring native shell tools for ordinary CLI, package-manager, and test runs. Use when the user says: command-operator, command operator, terminal command, terminal task, shell command, shell task, cli command, command execution.
The English summary is being prepared. Showing the original description.
Terminal security analysis for shell environments. This skill should be used when checking commands for supply-chain attacks before execution, scanning repositories for hidden content or config poisoning, scoring URLs for homograph attacks, setting up AI tool protection, inspecting Python package artifacts, governing untrusted tasks or Web3 commands, auditing browser extensions, creating provenance receipts, downloading and executing scripts safely, investigating why tirith blocked a command, managing trusted patterns, running security audits, configuring MCP gateway proxies, or working with threat intelligence databases. Also use when the user mentions "tirith", "pipe-to-shell", "homograph", "ANSI injection", "zero-width", "punycode", "terminal security", "shell hook", "cloaking detection", "supply chain attack", "bidi override", "invisible unicode", or "config poisoning". Even if the user does not explicitly name tirith, use this skill when they ask about protecting shell environments, intercepting dangerous commands, or hardening AI agent tool execution.
The English summary is being prepared. Showing the original description.