Audit or fix sensitive-data exposure in JS SDK diagnostics, exceptions, logging, and telemetry.
日本語の概要は準備中です。原文の説明を表示しています。
1,541 件 ・ 関連度順
概要と使いどころ
Audit or fix sensitive-data exposure in JS SDK diagnostics, exceptions, logging, and telemetry.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze logs and source from a completed repository example run. Never execute or control examples.
日本語の概要は準備中です。原文の説明を表示しています。
Measure JS SDK coverage or address measured coverage gaps. Use for coverage audits and metric regressions, not routine test additions.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and, after explicit approval, execute runtime-behavior probes for local or live integrations. Use only when explicitly invoked to verify behavior that code review and normal tests cannot settle; define a controlled validation matrix, keep disposable JS probes outside tracked paths, and report observed evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Prepare a local PR title, description, and branch suggestion when requested or after eligible implementation work.
日本語の概要は準備中です。原文の説明を表示しています。
Review completed implementation changes before final verification. Use when repository policy requires independent review or the user explicitly requests it.
日本語の概要は準備中です。原文の説明を表示しています。
Use when fixing invoice total calculations in the sandbox quickstart repository.
日本語の概要は準備中です。原文の説明を表示しています。
Choose supported scope and compatibility boundaries for SDK behavior changes; revisit when feedback changes the design.
日本語の概要は準備中です。原文の説明を表示しています。
Fix the tiny credit-note formatting bug and rerun the exact targeted test command.
日本語の概要は準備中です。原文の説明を表示しています。
Audit or update authored English SDK documentation within a requested topic or diff using implementation evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Assess a JS SDK release candidate or release plan against the previous release and recommend ship or block.
日本語の概要は準備中です。原文の説明を表示しています。
Assess a GitHub issue or PR for demonstrated need, supported alternatives, correctness, and maintainer action. Desk review only.
日本語の概要は準備中です。原文の説明を表示しています。
Keep pnpm current: preflight the published package and pnpm/action-setup self-installer, update pnpm locally, align packageManager in package.json, and refresh CI pins. Use this when refreshing the pnpm toolchain manually or in automation.
日本語の概要は準備中です。原文の説明を表示しています。
Run the required final install, build, type, lint, test, and format checks after eligible SDK changes pass review.
日本語の概要は準備中です。原文の説明を表示しています。
Route generic agent-history ingestion requests to the appropriate specialized history-ingest skill. Use when the user asks to ingest AI-agent history without directly selecting the underlying agent-specific skill.
日本語の概要は準備中です。原文の説明を表示しています。
[omh] AI agent progress for managers: help managers inspect AI-agent progress, blockers, quality gates, and throughput levers. Use when the user says: agent-ops-review, agent ops review, agent productivity, operator productivity, manager view, quality dashboard, throughput review, agent work quality.
日本語の概要は準備中です。原文の説明を表示しています。
Discover, find, compare, audit, repair, adapt, craft, run, debrief, save, and prepare repeatable AI-agent loops for publication. Use when a user asks to analyze code or coding threads for recurring work, find a published loop, interview them to turn a goal into a bounded loop, review a loop for weak checks or unsafe authority, execute a loop with an evidence receipt, learn from completed runs, save or reuse a project loop, or validate and submit a loop to Loop Library.
日本語の概要は準備中です。原文の説明を表示しています。
Build AI applications using the Azure AI Projects Python SDK (azure-ai-projects). Use when working with Foundry project clients, creating versioned agents with PromptAgentDefinition, running evaluations, managing connections/deployments/datasets/indexes, or using OpenAI-compatible clients. This is the high-level Foundry SDK - for low-level agent operations, use azure-ai-agents-python skill.
日本語の概要は準備中です。原文の説明を表示しています。
Azure AI Agents Persistent SDK for Java. Low-level SDK for creating and managing AI agents with threads, messages, runs, and tools. Triggers: "PersistentAgentsClient", "persistent agents java", "agent threads java", "agent runs java", "streaming agents java".
日本語の概要は準備中です。原文の説明を表示しています。
Azure AI Agents Persistent SDK for .NET. Low-level SDK for creating and managing AI agents with threads, messages, runs, and tools. Use for agent CRUD, conversation threads, streaming responses, function calling, file search, and code interpreter. Triggers: "PersistentAgentsClient", "persistent agents", "agent threads", "agent runs", "streaming agents", "function calling agents .NET".
日本語の概要は準備中です。原文の説明を表示しています。
Entry point for AI-agent work on AWS: pick a runtime, plan a migration for existing workloads, and build an executable POC — one phased flow. Triggers on: which runtime for my agent, AgentCore vs ECS vs EKS vs Lambda, AgentCore vs Lambda MicroVMs, deploy an AI agent on AWS, agent architecture on AWS, I have an agent idea what do I build, move/migrate my agents to AWS, agent migration plan, add AgentCore services (memory, gateway, identity, policy, observability) to an agent already on AWS, Temporal on AWS (migrate/run Temporal workers on AWS, a service orchestrated by Temporal, Temporal Cloud vs self-hosted). Temporal Workflow code is never rewritten into Step Functions. Requires at least one agentic component — a purely non-agent system (plain services, batch jobs, HTTP endpoints, non-agent Temporal Activities) is out of scope, redirected to gcp-to-aws / heroku-to-aws / llm-to-bedrock. Not for: compute/data migration with no AI agent; pure LLM SDK rewrite (use llm-to-bedrock); per-model pricing.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a local repository risk receipt before Claude Code or other AI-agent edits. Use when the user asks to prepare a repository for agent changes, check for risky hooks or credential-writing automation, or run the /agent-preflight command. Trigger with "run agent preflight", "check this repo before agent edits", or "/agent-preflight".
日本語の概要は準備中です。原文の説明を表示しています。
Grida AI agent system work: `@grida/daemon` (DaemonServer, loopback HTTP perimeter, files/workspaces, secrets store, daemon discovery) and `@grida/agent` (the agent tenant: sessions, providers/BYOK, runtime/tool execution, skills discovery, prompts, tiers, sandbox hosts). Use for `packages/grida-daemon/**`, `packages/grida-ai-agent/**`, desktop sidecar protocol changes, agent chat transport, and bugs in agent state or streams. For pure Electron window, preload, menu, deep-link, or CDP work, use `desktop`.
日本語の概要は準備中です。原文の説明を表示しています。
Build safe, local, defensive reproductions of ALREADY-PATCHED, publicly disclosed security vulnerabilities (CVEs, vendor advisories, AI-agent incidents) for whitepapers, control testing, and education. Use this skill whenever the user wants to reproduce, demonstrate, or write up a known vulnerability or security incident — phrases like "reproduce this CVE", "build a repro for", "demonstrate the EchoLeak/Cursor/postmark-mcp issue", "show how this exploit worked", "add a reproducibility guide", or "pull the NVD/CVE details for". It fetches advisory metadata from NVD and CVE.org, confirms the issue is fixed, and produces a vulnerable-vs-patched harness that is offline, loopback-only, and uses synthetic markers. It NEVER discovers, develops, or weaponizes new zero-days and refuses any unpatched or live-target request.
日本語の概要は準備中です。原文の説明を表示しています。