opción
HogarHogar Skill Herramientas MCP mcp-create-adaptive-cards

mcp-create-adaptive-cards

github/awesome-copilot github/awesome-copilot

Habilidad convertida desde mcp-create-adaptive-cards.prompt.md

...Expandir todo
64
Tiempo actualizado 29 de junio de 2026

Acerca de mcp-create-adaptive-cards

La habilidad « mcp-create-adaptive-cards » está diseñada para mejorar la presentación visual de los datos en los complementos de API basados en MCP mediante la integración de plantillas de respuesta de Adaptive Card. Esta habilidad responde a la necesidad de mejorar la visualización de datos en Microsoft 365 Copilot, lo que permite a los desarrolladores crear experiencias de usuario más atractivas e informativas. Mediante el uso de Adaptive Cards, los desarrolladores pueden presentar datos complejos de forma estructurada y visualmente atractiva, lo que facilita a los usuarios la comprensión y la interacción con la información proporcionada por la API.

Preguntas frecuentes

¿Cómo se implementan las plantillas de respuesta estáticas?

Las plantillas de respuesta estáticas se pueden definir en el archivo ai-plugin.json, en la sección response_semantics.static_template.

¿Puedo utilizar plantillas de respuesta dinámicas para distintos tipos de datos?

Sí, las plantillas de respuesta dinámicas son adecuadas cuando la API devuelve varios tipos de datos, cada uno de los cuales requiere una plantilla diferente.

¿Qué versión de Adaptive Cards es compatible?

La skill es compatible con la versión 1.5 de Adaptive Cards.

¿Hay algún límite en el número de plantillas que puedo definir?

La documentación no especifica ningún límite, pero pueden aplicarse restricciones prácticas en función de la API y del rendimiento.

¿Qué herramientas se necesitan para utilizar esta skill?

La skill utiliza herramientas como «changes», «search/codebase», «edit/editFiles» y «problems».

Ver en GitHub
---mode: 'agent'tools: ['changes', 'search/codebase', 'edit/editFiles', 'problems']description: 'Add Adaptive Card response templates to MCP-based API plugins for visual data presentation in Microsoft 365 Copilot'model: 'gpt-4.1'tags: [mcp, adaptive-cards, m365-copilot, api-plugin, response-templates]---# Create Adaptive Cards for MCP PluginsAdd Adaptive Card response templates to MCP-based API plugins to enhance how data is presented visually in Microsoft 365 Copilot.## Adaptive Card Types### Static Response TemplatesUse when API always returns items of the same type and format doesn't change often.Define in `response_semantics.static_template` in ai-plugin.json:```json{  "functions": [    {      "name": "GetBudgets",      "description": "Returns budget details including name and available funds",      "capabilities": {        "response_semantics": {          "data_path": "$",          "properties": {            "title": "$.name",            "subtitle": "$.availableFunds"          },          "static_template": {            "type": "AdaptiveCard",            "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",            "version": "1.5",            "body": [              {                "type": "Container",                "$data": "${$root}",                "items": [                  {                    "type": "TextBlock",                    "text": "Name: ${if(name, name, 'N/A')}",                    "wrap": true                  },                  {                    "type": "TextBlock",                    "text": "Available funds: ${if(availableFunds, formatNumber(availableFunds, 2), 'N/A')}",                    "wrap": true                  }                ]              }            ]          }        }      }    }  ]}```### Dynamic Response TemplatesUse when API returns multiple types and each item needs a different template.**ai-plugin.json configuration:**```json{  "name": "GetTransactions",  "description": "Returns transaction details with dynamic templates",  "capabilities": {    "response_semantics": {      "data_path": "$.transactions",      "properties": {        "template_selector": "$.displayTemplate"      }    }  }}```**API Response with Embedded Templates:**```json{  "transactions": [    {      "budgetName": "Fourth Coffee lobby renovation",      "amount": -2000,      "description": "Property survey for permit application",      "expenseCategory": "permits",      "displayTemplate": "$.templates.debit"    },    {      "budgetName": "Fourth Coffee lobby renovation",      "amount": 5000,      "description": "Additional funds to cover cost overruns",      "expenseCategory": null,      "displayTemplate": "$.templates.credit"    }  ],  "templates": {    "debit": {      "type": "AdaptiveCard",      "version": "1.5",      "body": [        {          "type": "TextBlock",          "size": "medium",          "weight": "bolder",          "color": "attention",          "text": "Debit"        },        {          "type": "FactSet",          "facts": [            {              "title": "Budget",              "value": "${budgetName}"            },            {              "title": "Amount",              "value": "${formatNumber(amount, 2)}"            },            {              "title": "Category",              "value": "${if(expenseCategory, expenseCategory, 'N/A')}"            },            {              "title": "Description",              "value": "${if(description, description, 'N/A')}"            }          ]        }      ],      "$schema": "http://adaptivecards.io/schemas/adaptive-card.json"    },    "credit": {      "type": "AdaptiveCard",      "version": "1.5",      "body": [        {          "type": "TextBlock",          "size": "medium",          "weight": "bolder",          "color": "good",          "text": "Credit"        },        {          "type": "FactSet",          "facts": [            {              "title": "Budget",              "value": "${budgetName}"            },            {              "title": "Amount",              "value": "${formatNumber(amount, 2)}"            },            {              "title": "Description",              "value": "${if(description, description, 'N/A')}"            }          ]        }      ],      "$schema": "http://adaptivecards.io/schemas/adaptive-card.json"    }  }}```### Combined Static and Dynamic TemplatesUse static template as default when item doesn't have template_selector or when value doesn't resolve.```json{  "capabilities": {    "response_semantics": {      "data_path": "$.items",      "properties": {        "title": "$.name",        "template_selector": "$.templateId"      },      "static_template": {        "type": "AdaptiveCard",        "version": "1.5",        "body": [          {            "type": "TextBlock",            "text": "Default: ${name}",            "wrap": true          }        ]      }    }  }}```## Response Semantics Properties### data_pathJSONPath query indicating where data resides in API response:```json"data_path": "$"           // Root of response"data_path": "$.results"   // In results property"data_path": "$.data.items"// Nested path```### propertiesMap response fields for Copilot citations:```json"properties": {  "title": "$.name",            // Citation title  "subtitle": "$.description",  // Citation subtitle  "url": "$.link"               // Citation link}```### template_selectorProperty on each item indicating which template to use:```json"template_selector": "$.displayTemplate"```## Adaptive Card Template Language### Conditional Rendering```json{  "type": "TextBlock",  "text": "${if(field, field, 'N/A')}"  // Show field or 'N/A'}```### Number Formatting```json{  "type": "TextBlock",  "text": "${formatNumber(amount, 2)}"  // Two decimal places}```### Data Binding```json{  "type": "Container",  "$data": "${$root}",  // Break to root context  "items": [ ... ]}```### Conditional Display```json{  "type": "Image",  "url": "${imageUrl}",  "$when": "${imageUrl != null}"  // Only show if imageUrl exists}```## Card Elements### TextBlock```json{  "type": "TextBlock",  "text": "Text content",  "size": "medium",      // small, default, medium, large, extraLarge  "weight": "bolder",    // lighter, default, bolder  "color": "attention",  // default, dark, light, accent, good, warning, attention  "wrap": true}```### FactSet```json{  "type": "FactSet",  "facts": [    {      "title": "Label",      "value": "Value"    }  ]}```### Image```json{  "type": "Image",  "url": "https://example.com/image.png",  "size": "medium",  // auto, stretch, small, medium, large  "style": "default" // default, person}```### Container```json{  "type": "Container",  "$data": "${items}",  // Iterate over array  "items": [    {      "type": "TextBlock",      "text": "${name}"    }  ]}```### ColumnSet```json{  "type": "ColumnSet",  "columns": [    {      "type": "Column",      "width": "auto",      "items": [ ... ]    },    {      "type": "Column",      "width": "stretch",      "items": [ ... ]    }  ]}```### Actions```json{  "type": "Action.OpenUrl",  "title": "View Details",  "url": "https://example.com/item/${id}"}```## Responsive Design Best Practices### Single-Column Layouts- Use single columns for narrow viewports- Avoid multi-column layouts when possible- Ensure cards work at minimum viewport width### Flexible Widths- Don't assign fixed widths to elements- Use "auto" or "stretch" for width properties- Allow elements to resize with viewport- Fixed widths OK for icons/avatars only### Text and Images- Avoid placing text and images in same row- Exception: Small icons or avatars- Use "wrap": true for text content- Test at various viewport widths### Test Across HubsValidate cards in:- Teams (desktop and mobile)- Word- PowerPoint- Various viewport widths (contract/expand UI)## Complete Example**ai-plugin.json:**```json{  "functions": [    {      "name": "SearchProjects",      "description": "Search for projects with status and details",      "capabilities": {        "response_semantics": {          "data_path": "$.projects",          "properties": {            "title": "$.name",            "subtitle": "$.status",            "url": "$.projectUrl"          },          "static_template": {            "type": "AdaptiveCard",            "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",            "version": "1.5",            "body": [              {                "type": "Container",                "$data": "${$root}",                "items": [                  {                    "type": "TextBlock",                    "size": "medium",                    "weight": "bolder",                    "text": "${if(name, name, 'Untitled Project')}",                    "wrap": true                  },                  {                    "type": "FactSet",                    "facts": [                      {                        "title": "Status",                        "value": "${status}"                      },                      {                        "title": "Owner",                        "value": "${if(owner, owner, 'Unassigned')}"                      },                      {                        "title": "Due Date",                        "value": "${if(dueDate, dueDate, 'Not set')}"                      },                      {                        "title": "Budget",                        "value": "${if(budget, formatNumber(budget, 2), 'N/A')}"                      }                    ]                  },                  {                    "type": "TextBlock",                    "text": "${if(description, description, 'No description')}",                    "wrap": true,                    "separator": true                  }                ]              }            ],            "actions": [              {                "type": "Action.OpenUrl",                "title": "View Project",                "url": "${projectUrl}"              }            ]          }        }      }    }  ]}```## WorkflowAsk the user:1. What type of data does the API return?2. Are all items the same type (static) or different types (dynamic)?3. What fields should appear in the card?4. Should there be actions (e.g., "View Details")?5. Are there multiple states or categories requiring different templates?Then generate:- Appropriate response_semantics configuration- Static template, dynamic templates, or both- Proper data binding with conditional rendering- Responsive single-column layout- Test scenarios for validation## Resources- [Adaptive Card Designer](https://adaptivecards.microsoft.com/designer) - Visual design tool- [Adaptive Card Schema](https://adaptivecards.io/schemas/adaptive-card.json) - Full schema reference- [Template Language](https://learn.microsoft.com/en-us/adaptive-cards/templating/language) - Binding syntax guide- [JSONPath](https://www.rfc-editor.org/rfc/rfc9535) - Path query syntax## Common Patterns### List with Images```json{  "type": "Container",  "$data": "${items}",  "items": [    {      "type": "ColumnSet",      "columns": [        {          "type": "Column",          "width": "auto",          "items": [            {              "type": "Image",              "url": "${thumbnailUrl}",              "size": "small",              "$when": "${thumbnailUrl != null}"            }          ]        },        {          "type": "Column",          "width": "stretch",          "items": [            {              "type": "TextBlock",              "text": "${title}",              "weight": "bolder",              "wrap": true            }          ]        }      ]    }  ]}```### Status Indicators```json{  "type": "TextBlock",  "text": "${status}",  "color": "${if(status == 'Completed', 'good', if(status == 'In Progress', 'attention', 'default'))}"}```### Currency Formatting```json{  "type": "TextBlock",  "text": "$${formatNumber(amount, 2)}"}```

Todos los archivos

1 archivos
SKILL.md 12.2k
Ver

Instalar mcp-create-adaptive-cards

Descarga y descomprime los archivos de habilidades en tu directorio .claude/skills/.

Descargar ZIP

Clona el repositorio y copia los archivos de la habilidad a tu proyecto.

git clone https://github.com/github/awesome-copilot/blob/main/skills/mcp-create-adaptive-cards/SKILL.md # Copy SKILL.md to your .claude/skills/ directory

Copiar Copiar
Configuración rápida: Copia la carpeta de la habilidad en .claude/skills/. Claude la detectará automáticamente y la utilizará.

Habilidades relacionadas

office-mcp
Tiempo actualizado 13 de julio de 2026
composio
Tiempo actualizado 29 de junio de 2026
mcpgraph
Tiempo actualizado 29 de junio de 2026
connect-mcp-server
Tiempo actualizado 29 de junio de 2026
OR