Agent Skills
› opensquilla/opensquilla
› meta-meeting-to-workflow
meta-meeting-to-workflow
GitHub将会议笔记、录音或讨论草稿转化为结构化决策、责任人、后续行动及可共享的会议纪要,通过多技能编排实现从混乱信息到可执行工作流的转换。
Trigger Scenarios
用户拥有会议笔记或转录文本需要整理
需要将会议讨论内容转化为具体任务和负责人
生成会议纪要和决策清单
Install
npx skills add opensquilla/opensquilla --skill meta-meeting-to-workflow -g -y
SKILL.md
Frontmatter
{
"kind": "meta",
"name": "meta-meeting-to-workflow",
"always": false,
"metadata": {
"opensquilla": {
"risk": "medium",
"capabilities": [
"filesystem-write",
"network"
]
}
},
"triggers": [
"meeting to tasks",
"meeting notes",
"会议纪要",
"会议转任务",
"把会议整理成",
"整理录音",
"action items"
],
"provenance": {
"origin": "opensquilla-original",
"license": "Apache-2.0"
},
"composition": {
"steps": [
{
"id": "intake",
"kind": "llm_chat",
"with": {
"task": "Extract the meeting workflow contract.\n\nRequest and material:\n{{ inputs.user_message | xml_escape | truncate(5000) }}\n\nReturn exactly:\nMATERIAL_TYPE: <transcript|notes|recording_path|mixed|none>\nMEETING_TOPIC: <topic or unknown>\nATTENDEES:\n - <person or unknown>\nTARGET_SYSTEMS:\n - <github|trello|notion|slack|email|docx|none>\nNEEDS_CLARIFICATION: <yes|no>\nMISSING_FIELDS:\n - <material|desired_targets|none>\nOUTPUT_LANGUAGE: <language>\n",
"system": "You classify meeting material and output needs without inventing attendees."
}
},
{
"id": "clarify",
"kind": "user_input",
"when": "'NEEDS_CLARIFICATION: yes' in outputs.intake",
"clarify": {
"mode": "form",
"intro": "会议转执行流还缺少材料或目标系统。请补齐最小信息。",
"fields": [
{
"name": "meeting_material",
"type": "string",
"prompt": "会议文字、录音路径或摘要 \/ Meeting material",
"required": true,
"max_chars": 3000
},
{
"name": "target_systems",
"type": "string",
"prompt": "要生成到哪些系统 \/ Target systems",
"max_chars": 200
}
],
"nl_extract": true,
"timeout_hours": 24,
"cancel_keywords": [
"取消",
"算了",
"cancel",
"stop"
]
},
"depends_on": [
"intake"
]
},
{
"id": "transcript_digest",
"kind": "skill_exec",
"with": {
"text": "{{ inputs.user_message | xml_escape | truncate(8000) }}\n\nClarification:\n{{ inputs.get('collected', {}).get('clarify', {}) | tojson }}",
"style": "meeting_minutes",
"max_words": 2200
},
"skill": "summarize",
"depends_on": [
"intake",
"clarify"
]
},
{
"id": "decision_map",
"kind": "llm_chat",
"with": {
"task": "Build a structured map:\n- decisions\n- action items with owner, due date, dependency, confidence\n- unresolved questions\n- follow-up messages\n- items unsafe to assign because owner\/due date is missing\n\nDigest:\n{{ outputs.transcript_digest | truncate(5000) }}\n",
"system": "You extract meeting decisions and action items with owner confidence."
},
"depends_on": [
"transcript_digest"
]
},
{
"id": "repo_or_issue_context",
"kind": "skill_exec",
"when": "'github' in (outputs.intake | lower) or 'issue' in (inputs.user_message | lower) or 'pr' in (inputs.user_message | lower)",
"with": {
"task": "Inspect relevant GitHub issue\/PR context mentioned in this meeting request and return only directly supported links and statuses."
},
"skill": "github",
"depends_on": [
"decision_map"
]
},
{
"id": "artifact_plan",
"kind": "agent",
"with": {
"task": "Convert the decision map into target-system payload drafts. Do not\nactually create external tasks unless the user explicitly asked for\nexecution; produce copy-paste-ready GitHub issue bodies, Trello card\ntitles, Slack follow-ups, or Notion sections as appropriate.\n\nDecision map:\n{{ outputs.decision_map | truncate(6000) }}\n\nGitHub context:\n{{ outputs.repo_or_issue_context | truncate(3000) }}\n"
},
"skill": "sub-agent",
"depends_on": [
"decision_map",
"repo_or_issue_context"
]
},
{
"id": "workflow_pack",
"kind": "llm_chat",
"with": {
"task": "Return the final package:\n- executive minutes\n- confirmed decisions\n- action table\n- ready-to-send follow-ups\n- task\/issue\/card drafts\n- missing owner\/date questions\n- source limits\n\nTranscript digest:\n{{ outputs.transcript_digest | truncate(3500) }}\nDecision map:\n{{ outputs.decision_map | truncate(4500) }}\nArtifact plan:\n{{ outputs.artifact_plan | truncate(4500) }}",
"system": "You assemble meeting-to-workflow deliverables with clear ownership and uncertainty labels."
},
"depends_on": [
"transcript_digest",
"decision_map",
"artifact_plan"
]
}
]
},
"description": "Use this meta-skill instead of answering directly when the user has meeting notes, transcripts, recordings, or rough discussion notes and wants them converted into decisions, owners, follow-ups, tasks, issues, or shareable minutes through multi-skill orchestration.",
"meta_priority": 66,
"final_text_mode": "step:workflow_pack"
}
Meeting To Workflow
Turns messy meeting material into minutes, decisions, action ownership, and execution-ready task drafts.
Version History
- 7f72a32 Current 2026-07-05 18:41


