'agent' 검색 결과

Create an agent user in Microsoft Entra ID so an AI agent can access services requiring a user identity. Covers validating the parent agent identity, creating the account, assigning a manager and licenses, and troubleshooting setup errors.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create a user identity linked to an existing agent identity
• Prepare an agent account for a mailbox and Teams
• Assign a manager for organizational chart visibility

Manage multiple AI agents through the AI Maestro command-line tool. Create agents, inspect their status, pause and resume work, rename them, export or import configurations, and manage plugins from one interface.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating an agent for a specific project
• Checking agent status and assigned tasks
• Hibernating agents and resuming them later

Create specialized Agent Zero profiles by defining their roles, working methods, and delegation criteria. The skill prepares configuration files and instructions, with optional custom tools, extensions, and model preset selection when needed.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create a specialist agent for data analysis
• Define when to delegate work to an agent
• Customize an agent's workflow and response format

Automate Agenty tasks through Rube MCP, a connection to external tools. The skill discovers available operations and their required inputs, checks the Agenty connection, and executes tasks using the tools it finds.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding available Agenty operations
• Running Agenty tasks through an agent
• Processing multiple Agenty operations together

Build Java applications with cooperating AI agents using AgentScope Java. Guides asynchronous processing, where waiting tasks do not block execution, plus language model connections, external tools, workflow coordination, error handling, and tests.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Building a Java agent connected to a language model
• Coordinating agents in sequential or parallel workflows
• Connecting external tools through MCP

Generate VeADK-Go Agent code from a description of the required functionality, or convert existing Enio Agent code using the supplied framework documentation, examples, and feature mapping rules.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Generating Agent code from functional requirements
• Converting existing Enio code to VeADK-Go
• Developing Agents with framework reference examples

Build VeADK Agent code from functional requirements, including agent structure and prompt refinement. Convert existing Langchain or Langgraph code, or a Dify workflow, into VeADK Agent code and save the generated Python files.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Generating a VeADK Agent from functional requirements
• Converting Langchain code to VeADK Agent code
• Converting Langgraph code to VeADK Agent code

Build Python agents with Agentica SDK using function decorators or agent instances. Examples cover conversation memory, external tools, MCP connections for tool access, multi-agent coordination, typed results, and logging to help implement and debug agent behavior.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add agent behavior to existing Python functions
• Build a chatbot that remembers conversation history
• Connect agents to external tools through MCP

Builds Agent2Agent (A2A) servers and clients, the open protocol (originally from Google, now under the Linux Foundation) that lets AI agents from different frameworks call each other. Use when the user wants to create an A2A-compliant agent, build an Agent Card, implement task management, connect agents across frameworks, set up agent discovery, handle streaming responses, implement push notifications, or orchestrate multi-agent workflows. Trigger words: a2a, agent to agent, agent2agent, a2a protocol, a2a server, a2a client, agent card, agent interoperability, agent collaboration, multi-agent, agent discovery, a2a sdk, a2a task.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when: AI teammate / AIチームメイト / AI チームメイト / Agent Template / Foundry Autopilot / Agent 365 / 同僚エージェントの開発・公開。既定は Foundry hosted agent を Agent template として発行する経路。publish_foundry_autopilot.py が必須で、汎用 scripts/deploy.py や SDK agents.create_version だけで完了にしない。明示的な Agent Template / Autopilot 要求の前提が不足したら停止し、通常 Agent・自己ホストへの自動フォールバックは禁止。明示選択の自己ホストは別経路として対応する。M365 Requests の Type=Agent template と Teams Agents for your team での hire を手動確認するまで未完了。初回 scaffold で評価Hub（Code Apps）・Python EvaluationWorker・回帰テスト、publish 時に Foundry Monitor/Evaluations を構成する。CI/CD・レビューゲートは alm に委譲する。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when deploying an Agentforce agent to a channel surface: Embedded Service web chat, Slack, Experience Cloud, Agent REST API, or Salesforce Mobile. Triggers: 'deploy agent to website', 'add Agentforce to Slack', 'enable agent for mobile app', 'configure embedded service for agent', 'agent API for custom integration', 'multi-channel agent deployment'. NOT for agent logic design — use agentforce/agent-topic-design or agentforce/agent-actions for topics, instructions, and action contracts.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Architecture and systems design for building always-on AI agents with episodic memory. Covers the memory hierarchy (core/recall/archival), persistence layers, agent server infrastructure, vector stores, and framework selection. Provides concrete deployment patterns for agents that maintain identity and learn across sessions. Activate on: "always-on agent", "persistent agent architecture", "episodic memory system", "agent memory design", "long-running agent", "stateful agent", "agent that remembers", "MemGPT architecture", "Letta deployment", "/always-on-agent-architecture". NOT for: choosing what data to feed the agent (use always-on-agent-inputs), brainstorming applications (use always-on-agent-applications), safety and privacy concerns (use always-on-agent-safety), general agentic patterns (use agentic-patterns).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Cryptographic security for agentic systems — zero-trust agent networking, signed message envelopes (JWS/JWE), capability-based security (ocaps), Merkle tree audit trails, WASM sandboxing, and formal verification. Covers CLI dev tool security, mTLS between agents, permission boundaries (least privilege for AI agents), and supply chain security for skills/plugins. Activate on: "agent security", "zero trust agents", "secure agent communication", "capability-based security", "ocap", "signed messages between agents", "agent audit trail", "sandbox agent execution", "agent permissions", "mTLS agents", "cryptographic verification", "agent supply chain", "OWASP agentic", "prove agent did X", "tamper-proof agent logs". NOT for: application-level SAST scanning (use security-auditor), network firewall rules (use infrastructure), SOC2/HIPAA compliance (organizational), or prompt injection defense (use prompt-engineer).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Improve agent reliability over time — diagnose why agents fail and fix the setup. Triggers on: agent keeps failing, same mistake again, agent not improving, make agent smarter, agent quality plateau, agents ignore skills, agent skips tests, fix agent behavior, agent unreliable, improve agent setup, self-improving harness, agents worse over time, tune agent instructions, agent going in circles, agent ignores AGENTS.md, repeated agent errors. Requires harness v0 and eval harness. AUTO-ROUTED from harness-engineering on symptoms. Not first setup — harness-generation first.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Cryptographic security for agentic systems — zero-trust agent networking, signed message envelopes (JWS/JWE), capability-based security (ocaps), Merkle tree audit trails, WASM sandboxing, and formal verification. Covers CLI dev tool security, mTLS between agents, permission boundaries (least privilege for AI agents), and supply chain security for skills/plugins. Activate on: "agent security", "zero trust agents", "secure agent communication", "capability-based security", "ocap", "signed messages between agents", "agent audit trail", "sandbox agent execution", "agent permissions", "mTLS agents", "cryptographic verification", "agent supply chain", "OWASP agentic", "prove agent did X", "tamper-proof agent logs". NOT for: application-level SAST scanning (use security-auditor), network firewall rules (use infrastructure), SOC2/HIPAA compliance (organizational), or prompt injection defense (use prompt-engineer).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

AgentDB의 데이터 압축, 검색 인덱스, 캐시, 일괄 처리 설정과 성능 측정을 지원하여 메모리 사용량과 검색 속도의 균형을 조정합니다.

• AgentDB 메모리 사용량 줄이기
• 정확도를 유지하며 검색 속도 높이기
• 수백만 벡터에 맞는 설정 검토하기

Design autonomous agents for Claude Code plugins, including when they should run, what they should do, and which tools they may use. Provides file templates and guidance for validating configuration and testing behavior.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create a code review agent
• Clarify when an agent should run
• Limit the tools an agent can access

Plan a Claude Managed Agent around one clear job, then route work through setup, launch preparation, evaluation, and scheduling. Produce execution plans and curl commands that users run with their own Anthropic API key.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Defining one clear job for a managed agent
• Preparing launch commands for an Anthropic account
• Planning evaluation and revision with an iteration limit

Guide AI agent development from requirements and project setup through implementation, behavior evaluation, deployment, and monitoring. Provides coding rules, debugging steps, and links to specialized skills so each phase follows a defined process.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning an agent's requirements and architecture
• Running and debugging an agent locally
• Evaluating responses and tool use before deployment

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use to extend an existing agent project with memory, app integration, VPC, multi-agent, migration, model, browser, code interpreter, payments, or resource removal. Triggers: "add memory", "remember across sessions", "call agent from app", "invoke agent from code", "agent auth", "streaming", "VPC", "VPC connectivity", "can't reach from VPC", "multi-agent", "A2A", "A2A auth", "orchestrator not delegating", "specialist not called", "migrate Bedrock Agent", "migration issue", "change model", "browser tool", "code interpreter", "delete agent", "tear down", "agentcore remove", "cross-account memory", "add payments capability to my agent", "wire payments plugin", "integrate x402 payments with the agent I'm building", "add MPP payments", "Machine Payments Protocol". External APIs via Gateway: use agents-connect. New project: use agents-get-started. CLI/dev-server errors: use agents-debug. Runtime x402/MPP payments: use agents-pay. Migration-specific Strands vs LangGraph routes here.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Single entry point for every Agentlas command: /agentlas network, /agentlas build, /agentlas storm, /agentlas graph, /agentlas one, /agentlas upload, /agentlas cloud, /agentlas hub, /agentlas local, /agentlas browser, /agentlas call, /agentlas search, /agentlas connect.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Claude Code の SubAgent（agents/*.md）を正しく定義するためのベストプラクティスガイド。 YAML frontmatter、ツール選択、3-Phase 構造、コンテキスト受け渡し、アンチパターンを網羅。 Use when: agents/*.md を書く、SubAgent 定義を改善する、エージェントの動作が想定外、 コンテキストが渡らない、ツール選択に迷う。 Triggers: "subagent", "agent definition", "agents/*.md", "エージェント定義", "サブエージェント", "3-Phase", "context passing", "コンテキスト渡し", "tool selection", "ツール選択", "subagent_type", "bypassPermissions"

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create AI agents and workflows using Microsoft Agent Framework SDK. Supports single-agent and multi-agent workflow patterns. USE FOR: create agent, build agent, scaffold agent, new agent, agent framework, workflow pattern, multi-agent, MCP tools, create workflow. DO NOT USE FOR: deploying agents (use agent/deploy), evaluating agents (use agent/evaluate), Azure AI Foundry agents without Agent Framework SDK.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.