When the number of tools grows: • Agents burn tokens loading raw schemas • Tool discovery becomes noisy • Different agents need different subsets of tools • Orchestration logic leaks into prompts
Skills are curated, structured sets of MCP tools with documentation. Agents load only the skills they need instead of full tool schemas.
Skills are generated by discovering tools from MCP servers and auto-categorizing them.
Example: generate skills from a Playwright MCP server:
polymcp skills generate --servers "npx @playwright/mcp@latest"
HTTP MCP servers:
polymcp skills generate \ --servers "http://localhost:8000/mcp" \ --output ./mcp_skills
Stdio MCP servers:
polymcp skills generate \ --stdio \ --servers "npx -y @playwright/mcp@latest" \ --output ./mcp_skills
Enable skills in an agent:
agent = UnifiedPolyAgent( llm_provider=llm, skills_enabled=True, skills_dir="./mcp_skills", )
Benefits: • Smaller agent context • Scales to large tool sets • Reusable capabilities across agents • Tool access control without prompt changes • Works with HTTP and stdio MCP servers