「operations」の検索結果

Google Slides operations through gog.

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

Workspace Admin operations through gog.

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

Google People operations through gog.

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

Google Groups operations through gog.

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

Google Docs operations through gog.

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

Google Maps operations through gog.

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

Google AdSense operations through gog.

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

Convert frontend code (Vite, React, Angular, Vue, etc.) to a Stitch Design by chaining static HTML extraction, design system extraction, and file upload. **ALWAYS** use this skill when the user's intent is to move existing web apps or React/Angular/Vue components into Stitch (e.g., requests to "save", "migrate", or "upload"). You must use this skill even for simple "save" operations, as it is the only way to ensure the design system is extracted and assets are properly linked.

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

CCPM - spec-driven project management: PRD → Epic → GitHub Issues → parallel agents → shipped code. Use this skill for anything in the software delivery lifecycle: writing a PRD ('write a PRD for X', 'let's plan X', 'scope this out'), parsing a PRD into an epic, decomposing an epic into tasks, syncing to GitHub ('sync the X epic', 'push tasks to github'), starting work on an issue ('start working on issue N', 'let's work on issue N'), analyzing parallel work streams, running standups ('standup', 'run the standup'), checking status ('what's next', 'what's blocked', 'what are we working on'), closing issues, or merging an epic. Use ccpm any time the user is talking about shipping a feature, managing work, or tracking progress — even if they don't say 'ccpm' or 'PRD'. Do NOT use for: debugging code, writing tests, reviewing PRs, or raw GitHub issue/PR operations with no delivery context.

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

Workspace file I/O expert. ALWAYS invoke this skill when you need to list workspaces, read or write files in a workspace on a remote node, or browse workspace directories. Use this for cross-node file operations — for local sandbox files, use standard filesystem tools instead.

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

Verify a file's first N lines and total line count in one shell call using head and wc -l with an echo separator, minimizing read operations and shell iterations.

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

Execute Python scripts from files for reliable spreadsheet operations, avoiding heredoc issues with shell_agent

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

Execute Python scripts for spreadsheet operations with mandatory source data validation and fallback protocols

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

Use direct Python execution for reliable spreadsheet operations instead of shell_agent

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

Use direct Python execution for reliable spreadsheet and document/PDF generation operations

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

Use direct Python execution for reliable spreadsheet and document/PDF generation operations

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

Use run_shell with cd and heredoc syntax for complex Excel operations when read_file fails on XLSX or execute_code_sandbox fails on multi-step workbook creation

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

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

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

Fallback to run_shell and write_file when execute_code_sandbox or shell_agent fail on filesystem operations

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

Use run_shell with inline Python as a fallback when execute_code_sandbox fails for openpyxl/spreadsheet operations

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

Use run_shell as fallback when execute_code_sandbox or shell_agent fail on filesystem operations

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

Use shell_agent as fallback when execute_code_sandbox fails for Excel file operations

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

Analyzes smart contract codebases to identify state-changing entry points for security auditing. Detects externally callable functions that modify state, categorizes them by access level (public, admin, role-restricted, contract-only), and generates structured audit reports. Excludes view/pure/read-only functions. Use when auditing smart contracts (Solidity, Vyper, Solana/Rust, Move, TON, CosmWasm) or when asked to find entry points, audit flows, external functions, access control patterns, or privileged operations.

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

Systematic methodology for identifying and exploiting cryptographic implementation weaknesses in real-world applications. Covers padding oracle attacks against CBC-mode ciphers with PKCS7 padding (Vaudenay's original attack through modern padbuster automation), ECB mode exploitation including block cut-and-paste and byte-at-a-time decryption, hash length extension attacks against SHA1/SHA256/MD5-based MACs using HashPump, RSA vulnerabilities including small public exponent, common modulus, Bleichenbacher PKCS1v1.5 padding oracle, and Coppersmith's method for partial key recovery. Addresses weak PRNG exploitation targeting time-seeded generators and Mersenne Twister MT19937 state recovery from observed outputs, timing side-channel attacks against comparison operations, nonce reuse in AES-GCM leading to authentication key recovery, and key derivation weaknesses including insufficient iteration counts and missing salts. Primary tooling includes padbuster, RsaCtfTool, hashpump, and PyCryptodome for building custom exploit payloads. Maps to CWE-327 (Use of a Broken or Risky Cryptographic Algorithm), CWE-328 (Use of Weak Hash), and CWE-330 (Use of Insufficiently Random Values). Emphasizes black-box identification of vulnerable implementations before transitioning to targeted exploitation.

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