2,458 件 ・ 関連度順
概要と使いどころ
Use shell tools safely in sandboxed environments by discovering files from real workspace roots instead of assumed user folders, then explicitly verifying output artifacts after generation.
日本語の概要は準備中です。原文の説明を表示しています。
Safely update Excel workbooks by first locating candidate files, verifying workbook structure before editing, and running post-write validation against required sheets, populated columns, and sample counts.
日本語の概要は準備中です。原文の説明を表示しています。
Create or edit Excel workbooks with openpyxl-specific pitfall handling, anchored preflight audit, and deterministic post-write proof that every criterion is satisfied
日本語の概要は準備中です。原文の説明を表示しています。
Debug Python script execution failures by capturing full output with exit codes and verifying working directory before file operations
日本語の概要は準備中です。原文の説明を表示しています。
Verify PDF page counts and file integrity programmatically using PyPDF2 after generation
日本語の概要は準備中です。原文の説明を表示しています。
Verify generated PDF files using PyPDF2 to check page counts and integrity
日本語の概要は準備中です。原文の説明を表示しています。
Debug Python script execution failures by capturing full tracebacks and verifying working directory
日本語の概要は準備中です。原文の説明を表示しています。
Verify PDF page count and content using command-line tools when Python libraries unavailable
日本語の概要は準備中です。原文の説明を表示しています。
Complete PDF workflow: verify, extract content, assemble reports, and generate output PDFs using command-line tools
日本語の概要は準備中です。原文の説明を表示しています。
Verify generated PDFs for integrity and page count using PyPDF2 before task completion.
日本語の概要は準備中です。原文の説明を表示しています。
Iterative workflow to verify PDF page counts and adjust layout parameters until requirements are met
日本語の概要は準備中です。原文の説明を表示しています。
Verify delegated file-edit results directly in the target workspace before accepting success, and rerun with absolute paths if the delegate's report conflicts with reality.
日本語の概要は準備中です。原文の説明を表示しています。
Debug Python code execution failures by capturing partial traces, isolating failing functions, and incrementally verifying outputs
日本語の概要は準備中です。原文の説明を表示しています。
Triage a batch of raw security findings. Verify each is real, collapse duplicates, re-rank by derived exploitability, and tag with an owner. Takes a directory or file of scanner output and writes TRIAGE.json + TRIAGE.md sorted by what actually needs engineering attention. Use when asked to "triage findings", "validate scanner output", "prioritize vulns", or "review the backlog". Runs interactively by default; pass --auto to skip the interview.
日本語の概要は準備中です。原文の説明を表示しています。
Systematically verifies suspected security bugs to eliminate false positives, producing a TRUE POSITIVE or FALSE POSITIVE verdict with documented evidence for each. Use when asked whether a specific finding is real, exploitable, or a false positive, or to verify or validate a suspected vulnerability — not for hunting or discovering new bugs.
日本語の概要は準備中です。原文の説明を表示しています。
Use when an agent is preparing or performing an OpenRig CLI/daemon upgrade and must preserve live seats, verify each mutation, or reconcile managed plugin and skill files without overwriting local work.
日本語の概要は準備中です。原文の説明を表示しています。
Coordinate the end-to-end CAD/source-asset to SimReady workflow. Use for broad requests such as CAD to SimReady, source asset to simulation-ready USD, or prop packaging that require conversion, material/physics assignment, SimReady conformance, validation, and optional package creation; deploy or verify Content Agents services first when property assignment is enabled; route single-stage work through nested references.
日本語の概要は準備中です。原文の説明を表示しています。
Prompt- and template-complete Google Docs creation and editing with explicit-instruction-authoritative structural preservation, including semantic roles, relationships, comparison dimensions, and instructed extensions; full-topology native-copy routing; source-grounded per-tab adaptation for past/example references; style-preserving hyperlink and table edits; canonical smart-chip-first authoring for dates and relevant supported people or Google resources; a file-backed advisory trusted read before existing-document writes; automatic protected-control awareness; direct connector APIs by default; DOCX-first import only when no supplied Google Doc template/reference constrains the output; and checked-in code mode only for exact native dropdown mutation. Use when Codex must create, edit, fill, adapt, redesign, or verify Google Docs without overriding explicit user/template instructions, adding unrequested document scope, or carrying stale reference facts into a new deliverable.
日本語の概要は準備中です。原文の説明を表示しています。
Use only when the user explicitly asks to fix and verify a validated or plausible security vulnerability. Do not use for ordinary bug fixes, correctness or design review findings, general validation, or full PR, commit, branch, patch, or repository scans.
日本語の概要は準備中です。原文の説明を表示しています。
Use only when the user explicitly requests verification that a security fix remediates a reported vulnerability. Do not invoke automatically while implementing fixes, reviewing ordinary code changes, or running tests. Do not use for non-security fixes, candidate finding validation, or full repository scans.
日本語の概要は準備中です。原文の説明を表示しています。
Add and verify lightweight macOS runtime telemetry. Use when wiring Logger events or inspecting logs for windows, sidebars, menus, and actions.
日本語の概要は準備中です。原文の説明を表示しています。
Boltz CLI setup and auth. Use when installing, updating, verifying, or authenticating `boltz-api`, or fixing missing CLI, PATH, sandbox, browser login, or auth errors.
日本語の概要は準備中です。原文の説明を表示しています。
Feature planning and implementation with 4 adaptive phases (Specify, Design, Tasks, Execute). Auto-sizes depth by complexity. Writes testable requirements in EARS notation, atomic tasks, atomic Conventional Commits, and requirement traceability. Ships deterministic Python validation scripts so structural gates are enforced by code, not memory. Features an independent Verifier (author != verifier, evidence-or-zero), a discrimination sensor, a decision log (STATE.md), a test-coverage matrix, and a self-improving lessons layer. Stack-agnostic and tool-agnostic. Use when (1) planning features, (2) implementing with verification and atomic commits, (3) validating an implementation against a spec. Triggers on "specify feature", "discuss feature", "design", "tasks", "implement", "validate", "verify work", "UAT", "record decision", "pause work", "resume work". Do NOT use for pure architecture decomposition analysis or standalone technical design documents.
日本語の概要は準備中です。原文の説明を表示しています。
Spec-driven feature work that freezes obligations instead of the plan: one human-reviewed plan with EARS criteria, path, entities, interface and one-way doors, then proof-backed checks, then build, then an independent Verifier. Use when the user says "tlc-spec-lean", "plan feature", "specify feature", "write the checks", "build this plan", or "verify work". Do NOT use for standalone design documents unattached to a feature, architecture decomposition analysis, or work that already has a task list or checklist to execute.
日本語の概要は準備中です。原文の説明を表示しています。