topics/mcp/SKILL.md
# MCP TOPIC SKILL ## Purpose Implement Model Context Protocol (MCP) servers and clients with the official MCP Python SDK (`mcp`) using deterministic, transport-explicit patterns. ## When to Use - Building MCP servers over `stdio` for local process integration - Building MCP servers over Streamable HTTP for remote/networked access - Building MCP clients that connect to local (`stdio`) or online (`streamable-http`) servers - Defining reusable MCP templates and transport-specific implementation p
npx skillsauth add azadehtavassoli/agent-skills-toolkit topics/mcpInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Implement Model Context Protocol (MCP) servers and clients with the official MCP Python SDK (mcp) using deterministic, transport-explicit patterns.
stdio for local process integrationstdio) or online (streamable-http) serversmcp package.stdio vs streamable-http) instead of implicit defaults in production code.stateless_http=True, json_response=True) unless there is a documented reason not to.stdio and/or streamable-http).stdio usage template includeddevelopment
# Demo Pipeline — SKILL ## What this skill is for Use this skill to implement a long-term, maintainable demo pipeline for product demos. The aim is to create a reusable machine for demos, not a one-off screen recording. ## Canonical design A good demo pipeline has these responsibilities: ### 1. Scenario definition A scenario defines: - objective - audience - core message - preconditions - interaction steps - hero moment - output profiles Use: - `brief.md` for human-readable story and intent
development
# UI TOPIC SKILL ## Purpose Define deterministic UI implementation patterns with accessibility, component decomposition, and reproducible behavior. ## Framework Adapters - `topics/ui/frameworks/streamlit/` - `topics/ui/frameworks/gradio/` ## Hard MUST Rules - Component contracts must be explicit. - Accessibility checks are mandatory. - UI state transitions must be predictable and testable. - Framework-specific UI logic MUST remain inside adapter folders.
testing
# RAG TOPIC SKILL ## Purpose Define deterministic retrieval-augmented generation pipelines with grounded outputs and measurable evaluation. ## Hard MUST Rules 1. Retrieval, ranking, and generation stages MUST be explicit and logged. 2. Groundedness and citation integrity MUST be validated in tests. 3. Evaluation outputs MUST be structured and reproducible. 4. No real LLM/provider calls in automated tests. 5. Structured output models are mandatory.
tools
# LangGraph Skill ## Capability You can design and build stateful, long-running agents using LangGraph's low-level orchestration primitives and integrate observability via LangSmith for development and debugging. ## Key Abilities ### 1. Design Agents with LangGraph - **Graph-based state machines**: Design agents as directed acyclic graphs (DAGs) using nodes (computation steps) and edges (transitions between them). - **Explicit control flow**: Define precisely what happens at each step—no hid