AGENT SKILLS
Teach agents expert workflows
Import from catalogs, AI-generate from text, or upload manually. Portable skill packages following the agentskills.io spec.

Agent Skills catalog — browse and import skills from Anthropic, OpenAI, and Skills.sh
HOW IT WORKS
From intent to expert agent in minutes
Three Ways to Create
Import skills from the Anthropic catalog or skills.sh community registry. AI-generate a skill from a natural language description. Or upload a SKILL.md file directly. Every skill follows the agentskills.io open spec.

Progressive Loading
Level 1: skill metadata loads at startup — just 50 tokens. Level 2: the full SKILL.md loads when relevant — up to 5K tokens. Level 3: additional files and scripts load on demand. This keeps agent context windows lean while having deep knowledge available when needed.
AI Skill Generation
Describe what you want in plain English. The Deep Agent generates a complete SKILL.md with metadata, instructions, workflow steps, and tool references. Streamed via SSE so you see progress in real time.
Install on Sandboxes
Skills are portable ZIP packages containing a SKILL.md plus optional scripts and resources. Install them directly into sandboxes where agents can reference the instructions and execute the bundled scripts.
SDK ACCESS
Skills that call tools programmatically
Skills can use mcpgateway-sdk to call MCP tools, search tools, and cache data. The gateway injects a scoped token at runtime — script authors write zero authentication code.
Call any MCP tool from Python
The gateway SDK gives scripts full access to the tool graph. Call tools by name, search semantically, cache results for follow-up questions. The gateway injects a scoped token at runtime — no API keys in your code.
From 51 tool calls to 1
Without SDK access, an agent calling raw tools gets 200KB responses per call. With a skill script using the SDK, the same workflow returns 800 bytes. The agent sees a normal tool — zero awareness that scripts are involved.
SCRIPT TOOLS
Declare tools the gateway enforces
Script tools are MCP Gateway's proposal to solve the token bloat problem. Package Python scripts in a tools/ folder with a workflow.json manifest. When attached to a server, the gateway registers them as first-class MCP tools — with schema validation, response budgets, scoped tokens, and exposure mode control.
Skill packages with script tools
A skill package contains SKILL.md guidance, a workflow.json manifest declaring tool schemas, and Python scripts in tools/. When attached to a server, the gateway registers each script as an MCP tool — the agent never sees the raw APIs behind them.
Skill Package
▼ salesforce-workflows/
SKILL.md
workflow.json
▼ tools/
summarize_pipeline.py
Gateway registers tools/ as MCP tools on attach
tools/summarize_pipeline.py
from mcpgateway_sdk import MCPGateway
gw = MCPGateway() # auto-auth from env
# 1. Fetch opportunities via SDK
opps = await gw.tools.execute(
"salesforce_opportunities_list",
{"quarter": "Q1-2026"}
)
# 2. Filter and join
return {"total_deals": len(opps), ...} # 800 bytesFrom prototype to production
Agent-Mediated
scripts/ folder
Agent reads SKILL.md, decides when to run. Wildcard SDK token scope. No schema validation. Best for prototyping.
- Agent reads SKILL.md, decides when to run
- Wildcard SDK token scope
- No schema validation
- Best for: prototyping
Gateway-Enforced
tools/ + workflow.json
Gateway dispatches on tool call. Scoped token, schema validation, response budgets. Best for production.
- Gateway dispatches on tool call
- Scoped token (allowed_tools only)
- Schema validation + response budgets
- Best for: production
Upgrade path: Start with scripts/ to iterate quickly. Move to tools/ when ready for production guardrails. Both live in the same skill package.
SDK REFERENCE
Python SDK
Import, generate, manage, and distribute skills programmatically.
Ready to teach your agents?
Import skills from the community or generate your own. Give every agent expert-level workflows.