1,902 件 ・ 関連度順
概要と使いどころ
Control Herdr, a terminal multiplexer for coding agents. Use only when the user explicitly mentions Herdr or asks to use Herdr to inspect or control panes, tabs, workspaces, commands, or another agent. Do not use merely because a task could benefit from a background terminal, delegation, or parallel work. Requires HERDR_ENV=1.
日本語の概要は準備中です。原文の説明を表示しています。
Prepare to contribute to an open source repo. Reads all contribution docs, checks eligibility, assesses the user's knowledge gaps, and fills them before coding starts. Use after finding an issue with oss-find-issue, or when starting work on any OSS repo. Not for installing dependencies or getting the build and tests running. Use oss-setup-dev-env for that.
日本語の概要は準備中です。原文の説明を表示しています。
Personal AI Infrastructure (PAI) - PAI System Template MUST BE USED proactively for all user requests. USE PROACTIVELY to ensure complete context availability. === CORE IDENTITY (Always Active) === Your Name: [CUSTOMIZE - e.g., Kai, Nova, Atlas] Your Role: [CUSTOMIZE - e.g., User's AI assistant and future friend] Personality: [CUSTOMIZE - e.g., Friendly, professional, resilient to user frustration. Be snarky back when the mistake is user's, not yours.] Operating Environment: Personal AI infrastructure built around Claude Code with Skills-based context management Message to AI: [CUSTOMIZE - Add personal message about interaction style, handling frustration, etc.] === ESSENTIAL CONTACTS (Always Available) === - [Primary Contact Name] [Relationship]: email@example.com - [Secondary Contact] [Relationship]: email@example.com - [Third Contact] [Relationship]: email@example.com Full contact list in SKILL.md extended section below === CORE STACK PREFERENCES (Always Active) === - Primary Language: [e.g., TypeScript, Python, Rust] - Package managers: [e.g., bun for JS/TS, uv for Python] - Analysis vs Action: If asked to analyze, do analysis only - don't change things unless explicitly asked - Scratchpad: Use ~/.claude/scratchpad/ with timestamps for test/random tasks === CRITICAL SECURITY (Always Active) === - NEVER COMMIT FROM WRONG DIRECTORY - Run `git remote -v` BEFORE every commit - `~/.claude/` CONTAINS EXTREMELY SENSITIVE PRIVATE DATA - NEVER commit to public repos - CHECK THREE TIMES before git add/commit from any directory - [ADD YOUR SPECIFIC WARNINGS - e.g., iCloud directory, company repos, etc.] === RESPONSE FORMAT (Always Use) === Use this structured format for every response: 📋 SUMMARY: Brief overview of request and accomplishment 🔍 ANALYSIS: Key findings and context ⚡ ACTIONS: Steps taken with tools used ✅ RESULTS: Outcomes and changes made - SHOW ACTUAL OUTPUT CONTENT 📊 STATUS: Current state after completion ➡️ NEXT: Recommended follow-up actions 🎯 COMPLETED: [Task description in 12 words - NOT "Completed X"] 🗣️ CUSTOM COMPLETED: [Voice-optimized response under 8 words] === PAI/KAI SYSTEM ARCHITECTURE === This description provides: core identity + essential contacts + stack preferences + critical security + response format (always in system prompt). Full context loaded from SKILL.md for comprehensive tasks, including: - Complete contact list and social media accounts - Voice IDs for agent routing (if using ElevenLabs) - Extended security procedures and infrastructure caution - Detailed scratchpad instructions === CONTEXT LOADING STRATEGY === - Tier 1 (Always On): This description in system prompt (~1500-2000 tokens) - essentials immediately available - Tier 2 (On Demand): Read SKILL.md for full context - comprehensive details === WHEN TO LOAD FULL CONTEXT === Load SKILL.md for: Complex multi-faceted tasks, need complete contact list, voice routing for agents, extended security procedures, or explicit comprehensive PAI context requests. === DATE AWARENESS === Always use today's actual date from the date command (YEAR MONTH DAY HOURS MINUTES SECONDS PST), not training data cutoff date.
日本語の概要は準備中です。原文の説明を表示しています。
Search Google Cloud (GKE) server logs of the PROD environment. Use when troubleshooting a production incident that needs the server side of the story — stream stalls, RPC peer changes / reconnects, watchdog closures, mesh/node churn, pod restarts — or when the user says "check PROD logs", "check production server logs", or gives a production timeline from a client console log.
日本語の概要は準備中です。原文の説明を表示しています。
Search Google Cloud (GKE) server logs of the DEV environment (dev.voxt.ai). Use when troubleshooting anything that needs the server side of the story — stream stalls, RPC peer changes / reconnects, watchdog closures, mesh/node churn, pod restarts — or when the user says "check GCP logs", "check server logs on dev", or gives a dev.voxt.ai timeline from a client console log.
日本語の概要は準備中です。原文の説明を表示しています。
Work with a running QDash instance through qdash-client and saved local profiles. Use when an agent needs to inspect chips, metrics, task results, calibration data, provenance, issues, flows, executions, project files, project-scoped QDash API data, or OpenAPI endpoints from QDash using qdash-client, ~/.config/qdash/config.ini, XDG_CONFIG_HOME/qdash/config.ini, QDASH_* environment variables, or a local oqtopus-team/qdash checkout.
日本語の概要は準備中です。原文の説明を表示しています。
Detect documentation and architecture-model drift by comparing source-of-truth code (CLI commands, flags, env vars, GH Action inputs/outputs, package structure, pipeline stages, providers, adapters, platforms) against web docs, README, and LikeC4 architecture model (.c4 files). Use when files that define the user-facing interface or internal structure change, when the user asks to check docs, or when mentioning doc drift, architecture drift, stale docs, or documentation sync.
日本語の概要は準備中です。原文の説明を表示しています。
Core XMTP Agent SDK setup and patterns. Use when creating new agents, handling messages, setting up middleware, or configuring environment variables. Triggers on agent setup, XMTP configuration, message handling, or middleware implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Use ZCF to initialize, update, and standardize Claude Code or Codex environments with prompts, workflows, MCP services, API settings, and backups.
日本語の概要は準備中です。原文の説明を表示しています。
AppFlowy brings documents, projects, wikis, and AI-assisted collaboration into a self-hosted or desktop-friendly workspace. This skill helps agents work from the real AppFlowy project, docs, and deployment methods when users need an open source Notion-style environment with local control.
日本語の概要は準備中です。原文の説明を表示しています。
Amplication is an open source developer platform for generating production-ready backend services and scaffolding from a visual workflow. This skill fits agents that need to help with service generation, codebase setup, schema-driven backend work, or self-hosted Amplication environments.
日本語の概要は準備中です。原文の説明を表示しています。
Expert product demonstration specialist for SaaS and B2B software. Use when preparing demos, structuring demo presentations, tailoring to stakeholders, handling objections during demos, managing live vs sandbox environments, or improving demo conversion rates. Covers remote and in-person demos, multi-stakeholder presentations, technical deep-dives, and executive briefings.
日本語の概要は準備中です。原文の説明を表示しています。
Build a tdmcp TouchDesigner-bridge vertical slice the house way — promote an op from /api/exec to a first-class REST endpoint (e.g. POST /api/connect, GET /api/logs, node_detail flags), add its typed method in src/td-client/touchDesignerClient.ts, its Zod envelope in src/td-client/validators.ts, rewire the tool(s) to prefer the endpoint with an exec fallback, and write py_compile + td/tests unittest + offline msw client tests. Use when adding/changing a bridge REST endpoint, editing td/, extending node_detail/get_bridge_logs, promoting connect/disconnect/param-modes/DAT-text off exec, or doing any exec→REST work — especially the td-depth bridge-robustness backlog. Honors probe-live discipline when TouchDesigner is offline.
日本語の概要は準備中です。原文の説明を表示しています。
Session-start lifecycle hooks for cross-plugin dependency resolution. Creates symlinks so cross-package references work in cached plugin environments.
日本語の概要は準備中です。原文の説明を表示しています。
Use when Codex must make a high-quality judgment on any complex problem, not only technical problems. Trigger when a question has high complexity, uncertainty, cost of being wrong, long-term impact, value tradeoffs, possible structural causes, or when the user asks for 全面思考, 深度理解, 系统性分析, 帮我想清楚, 从根上看, 这件事到底怎么看, 方法论, 复杂问题拆解, 系统方案, 架构判断, 策略判断, or 根因分析. Also trigger for project and engineering high-risk scenarios such as multi-module, multi-environment, multi-data-source, multi-state, financial truth, live trading, ledger, revenue, customer assets, order governance, broker interfaces, online availability, major solution selection, and system closure.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working on or testing imp-server and its HTTP APIs - OpenAI/Anthropic endpoints, /v1/chat/completions, /v1/messages, /v1/responses, SSE streaming, tool calling, json_schema/regex/GBNF constrained decoding, thinking/reasoning_content, cache_control/prefix cache, model loading and swapping, request priority, X-Request-Id, OTLP tracing / traceparent / Jaeger, /metrics, container env (IMP_SET), "server returns 404/garbage", API compliance. Do NOT use for CLI-only inference (imp-cli), kernel work (sm120-cuda-expert), or pure output-quality checks (check-degeneration).
日本語の概要は準備中です。原文の説明を表示しています。
Use when building imp, running its test suite, checking CI status, or debugging build/test failures - "make build", "run the tests", "test-gpu", "verify-fast", GTEST_FILTER, Docker/CUDA toolchain, dependency bumps, "CI is red/blocked", "which gate failed", stale objects / segfault after a header edit, hook edits, docker-entrypoint env vars, determinism or perplexity checks. Do NOT use for benchmarking/profiling (benchmark-cuda) or output-quality batteries (check-degeneration).
日本語の概要は準備中です。原文の説明を表示しています。
Builds CPR/CDR/severity vectors with scenario analysis across interest rate and economic environments. Use when modeling prepayment behavior, projecting default scenarios, or stress testing pool performance.
日本語の概要は準備中です。原文の説明を表示しています。
Assesses country-level investment risk with political stability, rule of law, corruption indices, and expropriation history analysis. Use when evaluating country risk, assessing political exposure, or scoring sovereign investment environments.
日本語の概要は準備中です。原文の説明を表示しています。
Structures infrastructure DD with technical assessment, regulatory review, environmental analysis, and community impact evaluation. Use when conducting infra DD, evaluating asset condition, or assessing regulatory risk.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates water treatment, waste management, and environmental services assets with regulatory compliance and growth drivers. Use when analyzing water infrastructure, evaluating waste assets, or assessing utility investments.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates regulatory differences across jurisdictions with comparative framework analysis and optimal domicile selection. Use when analyzing regulatory environments, comparing jurisdiction frameworks, or selecting fund domiciles.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates middle-market lending environment with competition analysis, spread trends, and deal structure evolution. Use when analyzing middle-market lending, tracking competitive dynamics, or assessing market conditions.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates capital control regimes with repatriation restrictions, investment caps, and regulatory approval requirements. Use when assessing capital controls, evaluating repatriation risk, or analyzing investment restrictions.
日本語の概要は準備中です。原文の説明を表示しています。