Skip to main content ホーム クリエイター jeremylongshore tons-of-skills-marketplace miro-core-workflow-b
miro-core-workflow-b Manage Miro connectors, images, embeds, app cards, and document items via REST API v2.
Use for visual workflows, embedding content, and building rich board layouts.
Trigger with phrases like "miro connectors", "miro embed",
"miro app card", "miro image upload", "connect miro items".
インストールへ移動 Skills Marketplace コミュニティが作成したAIスキルを発見・探索
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace --skill miro-core-workflow-bコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Zipをダウンロード ダウンロード中... このリポジトリの他の Skills langchain-deploy-integration Deploy a LangChain 1.0 / LangGraph 1.0 app to Cloud Run, Vercel, or LangServe correctly — with timeouts sized for chain length, cold-start mitigation, SSE anti-buffering headers, and Secret Manager over .env. Use when prepping a first production deploy, debugging a stream that hangs behind a proxy, or diagnosing p99 latency spikes. Trigger with "langchain deploy", "langchain cloud run", "langchain vercel python", "langchain langserve", or "langchain docker".
langchain-langgraph-agents Build a correct LangGraph 1.0 ReAct agent with create_react_agent — typed tools, error propagation, recursion caps, and stop conditions that actually stop. Use when writing a first tool-calling agent, migrating from AgentExecutor or initialize_agent, or diagnosing an agent that loops on vague prompts. Trigger with "langgraph agent", "create_react_agent", "langgraph tool calling", "AgentExecutor migration", or "agent loop cost".
langchain-langgraph-human-in-loop Build LangGraph 1.0 human-in-the-loop approval flows with interrupt_before /
interrupt_after and Command(resume=...) — JSON-serializable state, clean
resume semantics, and UI wiring for approval decisions. Use when adding an
approval gate before an expensive tool call, wiring a Slack/web UI for agent
approvals, or debugging a graph that crashes on interrupt.
Trigger with "langgraph human in loop", "langgraph interrupt_before",
"langgraph approval flow", "Command resume", "langgraph HITL".
name miro-core-workflow-b description Manage Miro connectors, images, embeds, app cards, and document items via REST API v2.
Use for visual workflows, embedding content, and building rich board layouts.
Trigger with phrases like "miro connectors", "miro embed",
"miro app card", "miro image upload", "connect miro items".
allowed-tools Read, Write, Edit, Bash(npm:*), Bash(curl:*), Grep version 1.7.0 license MIT author Jeremy Longshore <jeremy@intentsolutions.io> tags ["saas","miro","connectors","embeds","app-cards"] compatibility Designed for Claude Code
Miro Core Workflow B — Connectors, Embeds & Rich Items
Overview
Advanced item operations: connectors between items, image uploads, embedded content, app cards for custom integrations, and document items — all via the Miro REST API v2.
Prerequisites
Completed miro-core-workflow-a (boards and basic items)
Access token with boards:read and boards:write scopes
Connectors
Connectors are lines that visually link two items on a board. They replaced "lines" from the v1 API.
Create a Connector
const connector = await miroFetch (`/v2/boards/${boardId} /connectors` , 'POST' , {
startItem : {
id : startItemId,
position : {
x : 1.0 ,
y : 0.5 ,
},
},
endItem : {
id : endItemId,
snapTo : 'left' ,
},
captions : [
{
content : 'depends on' ,
position : 0.5 ,
textAlignVertical : 'top' ,
},
],
shape : 'curved' ,
style : {
color : '#1a1a2e'
fontSize
12
strokeColor
'#1a1a2e'
strokeWidth
2
strokeStyle
'normal'
startStrokeCap
'none'
endStrokeCap
'stealth'
console
log
`Connector ${connector.id} : ${startItemId} → ${endItemId} `
List All Connectors on a Board
const connectors = await miroFetch (`/v2/boards/${boardId} /connectors?limit=50` );
for (const c of connectors.data ) {
console .log (`${c.startItem.id} --[${c.captions?.[0 ]?.content ?? '' } ]--> ${c.endItem.id} ` );
}
Update a Connector
await miroFetch (`/v2/boards/${boardId} /connectors/${connectorId} ` , 'PATCH' , {
captions : [{ content : 'blocks' , position : 0.5 }],
style : { strokeColor : '#ff0000' , endStrokeCap : 'filled_triangle' },
});
Delete a Connector
await miroFetch (`/v2/boards/${boardId} /connectors/${connectorId} ` , 'DELETE' );
Images
Upload Image from URL
const image = await miroFetch (`/v2/boards/${boardId} /images` , 'POST' , {
data : {
url : 'https://example.com/architecture-diagram.png' ,
title : 'System Architecture' ,
},
position : { x : 500 , y : 0 },
geometry : { width : 400 },
});
Upload Image from Base64 Data URL import fs from 'fs' ;
const imageBuffer = fs.readFileSync ('diagram.png' );
const base64 = imageBuffer.toString ('base64' );
const dataUrl = `data:image/png;base64,${base64} ` ;
const image = await miroFetch (`/v2/boards/${boardId} /images` , 'POST' , {
data : { url : dataUrl, title : 'Local Diagram' },
position : { x : 0 , y : 400 },
});
Embed Items Embed external content (URLs rendered as previews).
const embed = await miroFetch (`/v2/boards/${boardId} /embeds` , 'POST' , {
data : {
url : 'https://www.youtube.com/watch?v=dQw4w9WgXcQ' ,
mode : 'inline' ,
previewUrl : '' ,
},
position : { x : -400 , y : 400 },
geometry : { width : 480 , height : 270 },
});
App Cards App cards display custom data from your integration, with structured fields and status indicators.
const appCard = await miroFetch (`/v2/boards/${boardId} /app_cards` , 'POST' , {
data : {
title : 'JIRA-1234: Fix login bug' ,
description : 'Users unable to log in after password reset' ,
status : 'connected' ,
fields : [
{ value : 'High' , iconUrl : '' , fillColor : '#ff0000' , iconShape : 'round' , tooltip : 'Priority' },
{ value : 'In Progress' , fillColor : '#ffd700' , iconShape : 'square' , tooltip : 'Status' },
{ value : 'John Doe' , tooltip : 'Assignee' },
],
},
style : { cardTheme : '#2d9bf0' },
position : { x : 600 , y : 200 },
});
Update App Card Status
await miroFetch (`/v2/boards/${boardId} /app_cards/${appCardId} ` , 'PATCH' , {
data : {
status : 'connected' ,
fields : [
{ value : 'Done' , fillColor : '#00c853' , tooltip : 'Status' },
],
},
});
Document Items
const doc = await miroFetch (`/v2/boards/${boardId} /documents` , 'POST' , {
data : {
url : 'https://example.com/spec.pdf' ,
title : 'Technical Specification v2' ,
},
position : { x : -600 , y : 0 },
});
Building a Visual Workflow Complete example: Kanban-style board with frames, cards, and connectors.
async function buildKanbanBoard (boardId : string const todoFrame = await miroFetch (`/v2/boards/${boardId} /frames` , 'POST' , {
data : { title : 'To Do' , format : 'custom' },
position : { x : 0 , y : 0 },
geometry : { width : 400 , height : 800 },
});
const doingFrame = await miroFetch (`/v2/boards/${boardId} /frames` , 'POST' , {
data : { title : 'In Progress' , format : 'custom' },
position : { x : 500 , y : 0 },
geometry : { width : 400 , height : 800 },
});
const doneFrame = await miroFetch (`/v2/boards/${boardId} /frames` , 'POST' , {
data : { title : 'Done' , format : 'custom' },
position : { x : 1000 , y : 0 },
geometry : { width : 400 , height : 800 },
});
const card1 = await miroFetch (`/v2/boards/${boardId} /cards` , 'POST' , {
data : { title : 'Design API schema' , description : 'OpenAPI 3.1 spec' },
position : { x : 0 , y : -200 },
parent : { id : todoFrame.id },
});
const card2 = await miroFetch (`/v2/boards/${boardId} /cards` , 'POST' , {
data : { title : 'Implement auth' , description : 'OAuth 2.0 flow' },
position : { x : 500 , y : -200 },
parent : { id : doingFrame.id },
});
await miroFetch (`/v2/boards/${boardId} /connectors` , 'POST' , {
startItem : { id : card1.id , snapTo : 'right' },
endItem : { id : card2.id , snapTo : 'left' },
captions : [{ content : 'blocks' }],
style : { endStrokeCap : 'stealth' , strokeStyle : 'dashed' },
});
}
Instructions Use the ordered procedures and code samples in this guide as a sequence: begin with the prerequisites, apply the configuration or operational step for the target environment, then perform the documented validation or cleanup before proceeding. Keep credentials in the documented secret store; never hard-code them in source.
Output Following this guide produces the Miro integration outcome for its topic—configuration, validation evidence, operational recovery, or a documented migration result. Record command output and relevant identifiers so a failed step is traceable.
Examples Start with the smallest applicable command or code example in the relevant section, using a dedicated test board and non-production credentials. Confirm the expected response or validation result before applying the pattern to production.
Error Handling Error Status Cause Solution connectorStartItemNotFound404 Start item deleted Verify both items exist connectorEndItemNotFound404 End item deleted Verify both items exist invalidImageUrl400 URL inaccessible Check URL is publicly reachable imageTooLarge400 File exceeds size limit Resize image before upload embedUrlNotSupported400 URL cannot be embedded Check Miro's supported embed providers
Resources
Next Steps For common errors and troubleshooting, see miro-common-errors.
