「execution」の検索結果

Resolve file access failures by changing to the correct working directory before command execution

日本語の概要は準備中です。原文の説明を表示しています。

Use direct Python execution for reliable document creation including spreadsheets, PDFs, and structured reports

日本語の概要は準備中です。原文の説明を表示しています。

Use direct Python execution for reliable spreadsheet operations instead of shell_agent

日本語の概要は準備中です。原文の説明を表示しています。

Delegate complex tasks to shell_agent when direct tool execution fails, leveraging autonomous error recovery and library selection

日本語の概要は準備中です。原文の説明を表示しています。

Debug Python script execution failures by capturing full output with exit codes and verifying working directory before file operations

日本語の概要は準備中です。原文の説明を表示しています。

Fallback to shell execution when sandbox fails for library-dependent Python code

日本語の概要は準備中です。原文の説明を表示しています。

Fallback pattern for when execute_code_sandbox fails - write script to file and execute directly with run_shell

日本語の概要は準備中です。原文の説明を表示しています。

Execute Python scripts reliably using file-first approach instead of heredoc

日本語の概要は準備中です。原文の説明を表示しています。

Fallback method for executing Python when execute_code_sandbox fails with unknown errors

日本語の概要は準備中です。原文の説明を表示しています。

Debug Python scripts with proper error surfacing and working directory verification

日本語の概要は準備中です。原文の説明を表示しています。

Reliable PDF generation using shell-based Python execution when sandbox fails

日本語の概要は準備中です。原文の説明を表示しています。

Identify and handle pre-execution agent failures occurring before any iterations or tool usage

日本語の概要は準備中です。原文の説明を表示しています。

Fallback workflow for reliable code execution when sandbox fails repeatedly

日本語の概要は準備中です。原文の説明を表示しています。

Fallback pattern for reliable file creation when code execution tools fail

日本語の概要は準備中です。原文の説明を表示しています。

Create Excel files with openpyxl by falling back to shell-based Python heredoc when sandbox execution fails

日本語の概要は準備中です。原文の説明を表示しています。

Fallback workflow for executing Python code when execute_code_sandbox fails repeatedly

日本語の概要は準備中です。原文の説明を表示しています。

Document generation with direct pandoc/ReportLab execution (lightweight default) and optional shell_agent fallback for complex scenarios

日本語の概要は準備中です。原文の説明を表示しています。

Identify and classify agent failures occurring before execution starts

日本語の概要は準備中です。原文の説明を表示しています。

Trigger: bench, journey, journeys, driven mode, gentle-ai-bench, journey corpus, j-numbers, bench axis. Author and verify gentle-ai bench journeys; go test ./bench never proves driven execution.

日本語の概要は準備中です。原文の説明を表示しています。

Generate candidate fixes for verified security findings. Consumes TRIAGE.json (preferred), VULN-FINDINGS.json, INCIDENTS.json, or a vuln-pipeline results directory. Pipeline input is delegated to the execution-verified `vuln-pipeline patch` ladder; static-analysis input gets a per-finding patch subagent + independent reviewer and is written as inert diffs for human review. Writes PATCHES/bug_NN/{patch.diff,patch_result.json}, PATCHES.md, and PATCHES.json. Use when asked to "fix the findings", "patch these vulns", "generate fixes", or "close the loop on triage".

日本語の概要は準備中です。原文の説明を表示しています。

Static source-code vulnerability scan. Reads a target directory (and THREAT_MODEL.md if present), spawns parallel review subagents per focus area, and writes VULN-FINDINGS.json + .md for /triage to consume. Read-only — no building, running, or network. For execution-verified crashes, use vuln-pipeline instead. Use when asked to "scan for vulns", "review this code for security issues", "find bugs in <dir>", or as the step between /threat-model and /triage.

日本語の概要は準備中です。原文の説明を表示しています。

Base skill for Refly ecosystem: creates, discovers, and runs domain-specific skills bound to workflows. Routes user intent to matching domain skills via symlinks, delegates execution to Refly backend. Use when user asks to: create skills, run workflows, automate multi-step tasks, or manage pipelines. Triggers: refly, skill, workflow, run skill, create skill, automation, pipeline. Requires: @refly/cli installed and authenticated.

日本語の概要は準備中です。原文の説明を表示しています。

Audits a project's dependencies for supply-chain risk: version-matched advisories for direct dependencies and the full lockfile tree, abandoned or archived upstreams, npm publisher concentration, and install-time script execution. Use when asked to audit dependencies, assess supply-chain or third-party package risk, or review a dependency tree before an engagement.

日本語の概要は準備中です。原文の説明を表示しています。

Social engineering attack techniques beyond email phishing for authorized red team and physical penetration testing engagements. Covers pretexting methodology (persona creation, authority and urgency psychological triggers, rapport building), vishing (voice phishing via caller ID spoofing, IVR system exploitation, VoIP infrastructure setup with Twilio/Asterisk), smishing (SMS-based phishing, carrier gateway abuse, short code impersonation), physical social engineering (tailgating and piggybacking, RFID badge cloning with Proxmark3, lock picking and bypass, dumpster diving for sensitive documents), USB drop attacks (Rubber Ducky keystroke injection, Bash Bunny multi-vector payloads, O.MG cable covert implants, BadUSB firmware attacks), watering hole attack planning and execution, and OSINT-driven targeting (LinkedIn harvesting, organizational chart reconstruction, employee pattern analysis). Integrates with the Social Engineering Toolkit for attack automation, Proxmark3 for RFID/NFC cloning, USB Rubber Ducky and Bash Bunny for physical payload delivery, and BeEF for browser exploitation. Maps to MITRE ATT&CK T1598 (Phishing for Information), T1566 (Phishing), T1091 (Replication Through Removable Media), and T1189 (Drive-by Compromise). All techniques require explicit written authorization and defined rules of engagement.

日本語の概要は準備中です。原文の説明を表示しています。