1,490 件 ・ 関連度順
概要と使いどころ
Pull the latest GEO-SEO skill updates from the upstream repository. Compares installed files against the latest release, shows what changed, and updates all skills, agents, scripts, and schema templates in place.
日本語の概要は準備中です。原文の説明を表示しています。
Verify the Omnigent CLI's setup/onboarding flow, terminal UI/UX, and critical user journeys in a completely isolated, reproducible loop. Drives the real `omnigent` binary through a PTY (pexpect) inside a throwaway OMNIGENT_CONFIG_HOME / OMNIGENT_DATA_DIR sandbox that never touches the user's real ~/.omnigent, captures ANSI-stripped frames for UX inspection, and proves a change is verifiable via a before→fix→after baseline diff. Load when developing or reviewing a CLI setup/onboarding/REPL/picker change (omnigent/cli.py, omnigent/onboarding/*, omnigent/repl/*, scripts/install_oss.sh), reproducing a cold-start/first-run UX bug, or confirming a fix actually lands. Several agents can run it concurrently on separate worktrees.
日本語の概要は準備中です。原文の説明を表示しています。
Runs metrics queries against Axiom MetricsDB via scripts. Discovers available metrics, tags, and tag values. Use when asked to query metrics, explore metric datasets, check metric values, or investigate OTel metrics data.
日本語の概要は準備中です。原文の説明を表示しています。
Add regression test cases to the Bifrost provider harness (the Postman collection run via `make run-provider-harness-test`) based on a merged PR or a GitHub issue. Fetches the PR/issue, traces the affected wire path in the codebase, checks existing harness coverage, designs cases following harness conventions, inserts them into tests/e2e/api/collections/provider-harness.json without reformatting the file, and validates via the augment and filter scripts. Invoked with /harness-test-writer <PR# | issue# | URL> or /harness-test-writer (prompts for a reference).
日本語の概要は準備中です。原文の説明を表示しています。
Yao process execution expert. ALWAYS invoke this skill when the user needs to call a Yao process, query data models, run scripts, or check process permissions. Do not call processes without checking this skill first.
日本語の概要は準備中です。原文の説明を表示しています。
自媒体创作者在策划历史名人访谈短视频时，当需要融合古今反差与网络热梗打造爆款，使用本技能可自动生成包含吸睛标题、主持人串词与爆笑问答的完整结构化脚本，轻松产出高传播力的趣味短视频文案。
日本語の概要は準備中です。原文の説明を表示しています。
Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, with mandatory post-write verification via read_file and cleanup of /tmp helper scripts.
日本語の概要は準備中です。原文の説明を表示しています。
Execute Python scripts for spreadsheets with prerequisite data validation and source accessibility checks
日本語の概要は準備中です。原文の説明を表示しています。
Recover from execute_code_sandbox failures by writing Python scripts to files and executing via run_shell
日本語の概要は準備中です。原文の説明を表示しています。
Execute Python scripts for spreadsheet operations with mandatory source data validation and fallback protocols
日本語の概要は準備中です。原文の説明を表示しています。
Fallback pattern for executing Python code when sandbox execution fails by writing scripts to disk and running via shell
日本語の概要は準備中です。原文の説明を表示しています。
Execute Python scripts with prerequisite data validation and fallback strategies for inaccessible sources
日本語の概要は準備中です。原文の説明を表示しています。
Execute Python scripts from files for reliable spreadsheet operations, avoiding heredoc issues with shell_agent
日本語の概要は準備中です。原文の説明を表示しています。
Execute Python scripts reliably using file-first approach instead of heredoc
日本語の概要は準備中です。原文の説明を表示しています。
Resilient multi-step workflow for spreadsheet processing when execute_code_sandbox fails, using shell_agent exploration, file-based scripts, and verification steps
日本語の概要は準備中です。原文の説明を表示しています。
Fallback pattern when primary tools fail - embed known data in scripts and persist to JSON for auditability
日本語の概要は準備中です。原文の説明を表示しています。
Debug Python scripts with proper error surfacing and working directory verification
日本語の概要は準備中です。原文の説明を表示しています。
Check available FFmpeg encoders before writing encoding scripts to avoid library version mismatches
日本語の概要は準備中です。原文の説明を表示しています。
Iteratively debug Excel structure with exploratory scripts before writing extraction logic
日本語の概要は準備中です。原文の説明を表示しています。
Port an existing mod to a newer game version or another mod loader while keeping its behaviour, values and quirks. Typical cases are an old Forge 1.7.10 or 1.12 Minecraft mod moving to modern Fabric or NeoForge, a Skyrim LE plugin moving to SE/AE, or a tModLoader 1.3 mod moving to 1.4. It covers pinning one source version, a private decompiled reference, an adaptation matrix, extracting the mod's data with scripts instead of retyping it, porting unit by unit with tests that catch drift, real-client checks, audits against the original, and keeping a long port resumable across sessions and agents. Use when the user wants to update, port, revive or re-implement a mod that already exists, or to continue such a port.
日本語の概要は準備中です。原文の説明を表示しています。
Research a game, engine or modding technique on the open web with archive-aware, rate-limit-safe searches — Wayback Machine/archive.today for dead forums (XeNTaX, Zenhax, old threads), GitHub code/repo search, Nexus/Steam Workshop/Thunderstore APIs, Reddit JSON, YouTube transcripts, plus archive snapshots as evidence. Use when starting work on a game ("how did people mod X before?"), when a documented tool/link is dead, when forum threads are login-gated (semi-auto handoff to the human), and before writing a field note so claims carry source URLs.
日本語の概要は準備中です。原文の説明を表示しています。
Enrolls a project in OSS-Fuzz, Google's free continuous fuzzing service for open source, and drives it locally. Covers project.yaml, Dockerfile and build.sh setup, the helper scripts, reproducing OSS-Fuzz crash reports, and the acceptance criteria. Use when setting up continuous fuzzing for an open-source project, reproducing an OSS-Fuzz bug report, or testing an OSS-Fuzz build before submitting it.
日本語の概要は準備中です。原文の説明を表示しています。
Configures Python projects with modern tooling (uv, ruff, ty). Use when creating projects, writing standalone scripts, or migrating from pip/Poetry/mypy/black.
日本語の概要は準備中です。原文の説明を表示しています。
Runs a Semgrep security scan over a codebase: detects languages, selects rulesets, presents the plan for explicit approval, then runs every approved ruleset through scripts/run-scans.sh, which batches the semgrep processes and writes scans.json, and merges the output to SARIF. Supports two scan modes, "run all" for full ruleset coverage and "important only" for security findings at medium-to-high confidence and impact. Uses Semgrep Pro for cross-file taint analysis when it is available. Use when asked to scan code for vulnerabilities, run a security audit with Semgrep, find bugs, or perform static analysis. For the same scan without the approval gate, use the /static-analysis:semgrep-scan workflow.
日本語の概要は準備中です。原文の説明を表示しています。