4,147 件 ・ 関連度順
概要と使いどころ
Browser Use is an open source browser automation framework for AI agents that turns websites into controllable interfaces for multi-step tasks. It combines a Python SDK, browser orchestration, and model integrations so agents can navigate, extract data, and complete workflows in real browsers.
日本語の概要は準備中です。原文の説明を表示しています。
broot is a Rust-based terminal tool that provides a new way to see and navigate directory trees. It offers fuzzy search, file preview, git status integration, and an interactive tree view that adapts to your terminal size.
日本語の概要は準備中です。原文の説明を表示しています。
Investigates anomalous patterns in AWS CloudWatch Logs using the CloudWatch Logs Insights API and CloudWatch Anomaly Detection. Correlates log spikes with deployment events via AWS CodeDeploy API.
日本語の概要は準備中です。原文の説明を表示しています。
This skill uses OpenClaw's healthcheck workflow to inspect the host running the assistant, surface risky exposure, and turn the findings into a staged hardening plan. It is for operator-style audits with explicit approval gates, not a generic software listing or a replacement for OS administration.
日本語の概要は準備中です。原文の説明を表示しています。
Runs CloudWatch Logs Insights queries via AWS SDK for JavaScript v3. Analyzes Lambda cold starts, API Gateway latency, and ECS container logs. Generates anomaly detection alarms with math expressions.
日本語の概要は準備中です。原文の説明を表示しています。
Investigates CloudWatch metric anomalies using the AWS SDK CloudWatch.getMetricData and Logs.filterLogEvents APIs. Correlates metric spikes with log patterns and deployment events from CodeDeploy.
日本語の概要は準備中です。原文の説明を表示しています。
Monitors ArgoCD applications for configuration drift using the ArgoCD REST API and grpc-gateway. Compares live Kubernetes manifests against Git-declared state and generates remediation playbooks via kubectl diff.
日本語の概要は準備中です。原文の説明を表示しています。
Manages ArgoCD application sync waves and hooks using the ArgoCD API and argocd CLI. Coordinates multi-application deployment ordering with sync-wave annotations, health checks, and progressive rollout gates.
日本語の概要は準備中です。原文の説明を表示しています。
Monitors ArgoCD application sync status via the ArgoCD REST API and gRPC gateway. Detects drift between desired and live Kubernetes manifests and triggers Slack notifications through the Slack Bolt SDK.
日本語の概要は準備中です。原文の説明を表示しています。
AI browser automation via CDP. Use when you need to control a browser, navigate pages, click elements, fill forms, extract content, or take screenshots.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrates translation of motion designer video specifications into working Remotion code by coordinating specialized agents. Acts as pipeline coordinator that delegates to remotion-scaffold, remotion-animation, remotion-composition, and remotion-component-gen. Use when you have a complete VIDEO_SPEC.md and need full Remotion implementation.
日本語の概要は準備中です。原文の説明を表示しています。
The Mileva Method (CRISP) — Phase 1: Clarify. Problem definition, eliciting, painkiller test, buy vs build, AI justification gate, Go/No-Go. Use at the start of any AI implementation project. Triggers on "clarify", "phase 1", "start discovery", "define the problem", "what problem are we solving", or at the beginning of a new client engagement.
日本語の概要は準備中です。原文の説明を表示しています。
The Mileva Method (CRISP) — Phase 4: Spec. Full implementation readiness package including solution design, UX direction, tech stack, backlog, MVP prioritization, risk assessment, and AI architecture for Claude Code projects — CLAUDE.md, skill mapping, AI specs, sprint planning, quality gates. Triggers on "spec", "phase 4", "build ready", "implementation plan", "CLAUDE.md", "sprint planning", "backlog", "AI spec", or after Phase I exit checklist is complete.
日本語の概要は準備中です。原文の説明を表示しています。
Review, harden, and test the safety policy for AI-Controlled Party mixer/Soundcraft Ui24R scene arming. Use for approval gates, blocked mixer operations, hazardous request handling, venue validation, bypass attempts, QA, risk review, or follow-up safety changes.
日本語の概要は準備中です。原文の説明を表示しています。
Run or maintain the full tdmcp repo quality-audit team: command sweeps, all package/Makefile/CI gates, security review, usability/flow review, refactor/test-gap analysis, coverage hardening, QA, and follow-up fix waves. Use whenever the user asks for a complete audit, improve repo/code quality, test all commands, find security/usability failures, refactor debt, add missing tests, re-run the audit, continue a previous quality wave, or verify the repo is ready.
日本語の概要は準備中です。原文の説明を表示しています。
Authoritative reference for submitting tdmcp to the Anthropic Connectors Directory as a Codex Desktop Extension (MCPB). Use whenever drafting, checking, or fixing the submission — it defines the two submission paths, why tdmcp is a Desktop Extension (never a remote connector), every form field, the rejection-causing gates, and the local-only compliance story. Read this before writing any submission deliverable.
日本語の概要は準備中です。原文の説明を表示しています。
Design the Soundcraft Ui24R adapter boundary for AI-Controlled Party: dry-run, Bitfocus Companion, direct Node bridge, connection health, config, failure handling, and live-validation gates. Use whenever a task mentions Soundcraft, Ui24R, snapshots, cues, Companion, soundcraft-ui-connection, mixer bridge, or revising the adapter design.
日本語の概要は準備中です。原文の説明を表示しています。
Release tdmcp: write the Keep-a-Changelog entry, bump the SemVer version across every manifest, then (autonomously, per project policy) commit, tag, and push — gated on a td-qa PASS, with hard git safety rails. Use when releasing/shipping/cutting a tdmcp version, writing the CHANGELOG, bumping the version, or tagging a release.
日本語の概要は準備中です。原文の説明を表示しています。
Authoritative reference for submitting tdmcp to the Anthropic Connectors Directory as a Claude Desktop Extension (MCPB). Use whenever drafting, checking, or fixing the submission — it defines the two submission paths, why tdmcp is a Desktop Extension (never a remote connector), every form field, the rejection-causing gates, and the local-only compliance story. Read this before writing any submission deliverable.
日本語の概要は準備中です。原文の説明を表示しています。
Verification methodology and gate checklist for the tdmcp Connectors Directory submission — run the docs build, build and inspect the .mcpb bundle, sweep for stale .dxt references, and cross-check the form-answer draft against the real requirements. Use to validate the submission package before a human submits, by executing commands and quoting evidence, not by trusting that work was done.
日本語の概要は準備中です。原文の説明を表示しています。
Restructure and enrich the tdmcp documentation site for artists — categorized/collapsible sidebar (EN+PT), interactive goal-based guide home, new step-by-step tutorials, copy-prompt/level-badge components. Use whenever the user asks to make the docs more interactive, easier to navigate, better organized, add categories/subcategories, add tutorials, improve docs UX/IA, or for follow-ups: re-run, continue, fix QA findings, add one more tutorial, re-organize a section, or update the docs structure. NOT for syncing docs with a release (tdmcp-docs-roadmap-update) or cookbook entries (tdmcp-cookbook-examples).
日本語の概要は準備中です。原文の説明を表示しています。
Quality-assure integrated tdmcp features: run the four PR gates + recipe/bridge tests, cross-boundary coherence checks (tool schema↔CLI↔docs↔registry, operator↔createable, bridge↔client), and live TouchDesigner validation (preview + post-cook error check) when the bridge is reachable. Use when validating/QA-ing/testing tdmcp tools, checking a feature actually cooks in TD, verifying CLI matches a tool, or gating a release.
日本語の概要は準備中です。原文の説明を表示しています。
How to author one new tdmcp MCP tool the house way — the file shape (XImpl + registerX), the Python-bridge pattern (buildPayloadScript/parsePythonReport over executePythonScript), the result helpers (errorResult/guardTd/jsonResult/structuredResult), fail-forward error handling, ESM/.js + Biome style, and the offline msw unit test that proves it. Load this whenever building, extending, reviewing, or testing a tdmcp tool file under src/tools/** (and its test under tests/unit/**). Use it for every Phase-13 / v0.5.0 feature-build tool and any re-run after a gate failure.
日本語の概要は準備中です。原文の説明を表示しています。
Track validated Codex Security findings in Linear, Jira, GitHub issues, or draft GitHub security advisories. Use it for one finding or an explicitly selected batch of up to 25 findings tracked as Linear, Jira, or GitHub issues. Includes duplicate checks, exact previews, approval-gated writes, and readback. Do not use it for scans or fixes.
日本語の概要は準備中です。原文の説明を表示しています。