agents-connect

Use when connecting your agent to external APIs, tools, or services via Gateway, or restricting tool access with Cedar policies. Handles gateway setup, target types, outbound auth (OAuth, API key, IAM), credentials, and Cedar policy authoring. Triggers on: "connect to API", "add gateway", "connect to MCP server", "Lambda tools", "OpenAPI", "gateway target", "Cedar policy", "restrict tools", "policy engine", "gateway auth error", "store API key", "outbound credential", "env var API key", "API key None after deploy", "credential not available after deploy", "should this be a gateway target", "give my agent tools", "add tools to agent". Not for inbound auth (who can call your agent) — use agents-harden. Not for debugging agent behavior — use agents-debug. Not for VPC networking errors (agent can't reach APIs due to VPC) — use agents-build. Not for creating or hosting a new MCP server project — use agents-get-started.

Agent Skill from aws/agent-toolkit-for-aws

Copilot Studio

Passes documented load rules

No documented load rule failed.

Microsoft 365 Copilot Preview, Frontier tenants only

Needs changes

Fails: Instructions are under 20,000 characters (M365-INSTRUCTIONS)
instructions are 28,293 characters
rule · Microsoft 365 Copilot: What is a skill

Warnings (don't change the verdict):

Warning: No sign of network access, package installs or authenticated calls (M365-SANDBOX)
SKILL.md mentions Python HTTP client, sockets
rule · Microsoft 365 Copilot: Script execution sandbox

An agent can have at most 8 skills. Custom skills aren't available in tenants that use Microsoft Purview Information Barriers.

Agent Skills spec notes

Warning: No experimental allowed-tools field (SPEC-ALLOWED-TOOLS)
uses allowed-tools
rule · Agent Skills specification

Compatible isn't the same as safe. These verdicts only say whether a skill's files follow Microsoft's documented load rules. The checker reads files and never runs them, and it doesn't review what a skill or its scripts actually do. Read a skill's instructions and scripts before you add it to an agent.

Standards signals

Meets the agentskills.io required fields.

Frontmatter	Present and parsed Spec: frontmatter
name	Meets the spec (1-64 chars, a-z 0-9 hyphens) Spec: name
description	Present, 1-1,024 characters Spec: description
compatibility	Absent or under 500 characters Spec: compatibility
Name matches folder	Yes (`agents-connect`) Spec: name
allowed-tools	Used Note: experimental in the spec; support varies by agent. Spec: allowed-tools

Observed from the public SKILL.md at the commit above on 2026-10-23. Not a certification: AAIF and the Agent Skills project don't certify skills. Validate your own skill with skills-ref validate.

Source repo	aws/agent-toolkit-for-aws
Path	plugins/aws-agents/skills/agents-connect/SKILL.md
Commit checked	`9ab50636d125`
Repo license	Apache-2.0
Files	2
Scripts	None
Instructions	28,293 characters
Deepest folder	1 below the skill folder
Rules version	2026-10-22

Re-check the latest version How skill checks work

Is this wrong or out of date? Email us. Skills data built 2026-10-23; rules as of 2026-10-22.

Rule-based checks of public files against Microsoft's documented load rules, not tested in Copilot Studio or Microsoft 365 Copilot. Independent project, not affiliated with Microsoft.