[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M770V51JD8A6K30VCMSWS776":3,"skill-same:01M770V51JD8A6K30VCMSWS776":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":43,"updatedAt":44,"install":45,"resources":58},"01M770V51JD8A6K30VCMSWS776","meeting-autopilot",null,"Turn meeting transcripts into operational outputs — action items, decisions, follow-up email drafts, and ticket drafts. Not a summarizer. An operator. Accepts VTT, SRT, or plain text. Multi-pass LLM extraction.","javimosch\u002Fopen-claw-skills","javimosch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F12900508?v=4","01M6D3F2AS6PV75ET9PZ1QGP8J","Javier Leandro Arancibia","01M75B8NCTAJG9WH5YNZH7C3D8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftkuehnl\u002Fmeeting-autopilot\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: meeting-autopilot\ndescription: >\n  Turn meeting transcripts into operational outputs — action items, decisions,\n  follow-up email drafts, and ticket drafts. Not a summarizer. An operator.\n  Accepts VTT, SRT, or plain text. Multi-pass LLM extraction.\nversion: 0.1.1\nauthor: Anvil AI\ntags: [meetings, productivity, action-items, email-drafts, transcripts, operations, discord, discord-v2]\n---\n\n# ✈️ Meeting Autopilot\n\nTurn meeting transcripts into structured operational outputs — NOT just summaries.\n\n## Activation\n\nThis skill activates when the user mentions:\n- \"meeting transcript\", \"meeting notes\", \"meeting autopilot\"\n- \"action items from meeting\", \"meeting follow-up\"\n- \"process this transcript\", \"analyze this meeting\"\n- \"extract decisions from meeting\", \"meeting email draft\"\n- Uploading or pasting a VTT, SRT, or text transcript\n\n## Permissions\n\n```yaml\npermissions:\n  exec: true          # Run extraction scripts\n  read: true          # Read transcript files\n  write: true         # Save history and reports\n  network: true       # LLM API calls (Anthropic or OpenAI)\n```\n\n## Requirements\n\n- **bash**, **jq**, **python3**, **curl** (typically pre-installed)\n- **ANTHROPIC_API_KEY** or **OPENAI_API_KEY** environment variable\n\n## Agent Workflow\n\n### Step 1: Get the Transcript\n\nAsk the user for their meeting transcript. Accept any of:\n- A **file path** to a VTT, SRT, or TXT file\n- **Pasted text** directly in the conversation\n- A **file upload**\n\nThe skill auto-detects the format (VTT, SRT, or plain text).\n\n**Important:** This skill does NOT do audio transcription. If the user has an audio\u002Fvideo file, suggest they use:\n- Zoom\u002FGoogle Meet\u002FTeams built-in transcription\n- Otter.ai or Fireflies.ai for recording + transcription\n- `whisper.cpp` for local transcription\n\n### Step 2: Get Optional Context\n\nAsk for (but don't require):\n- **Meeting title** — helps with email subject lines and report headers\n- If not provided, the skill derives it from the filename or uses \"Meeting [date]\"\n\n### Step 3: Run the Autopilot\n\nSave the transcript to a temporary file if pasted, then run:\n\n```bash\nbash \"$SKILL_DIR\u002Fscripts\u002Fmeeting-autopilot.sh\" \u003Ctranscript_file> --title \"Meeting Title\"\n```\n\nOr from stdin:\n```bash\necho \"$TRANSCRIPT\" | bash \"$SKILL_DIR\u002Fscripts\u002Fmeeting-autopilot.sh\" - --title \"Meeting Title\"\n```\n\nThe script handles all three passes automatically:\n1. **Parse** — normalize the transcript format\n2. **Extract** — pull out decisions, action items, questions via LLM\n3. **Generate** — create email drafts, ticket drafts, beautiful report\n\n### Step 4: Present the Report\n\nThe script outputs a complete Markdown report to stdout. Present it directly — the formatting is designed to look great in Slack, email, or any Markdown renderer.\n\nThe report includes:\n- 📊 Overview table (counts by category)\n- ✅ Decisions with rationale\n- 📋 Action items table (owner, deadline, status)\n- ❓ Open questions\n- 🅿️ Parking lot items\n- 📧 Follow-up email draft(s) — ready to send\n- 🎫 Ticket\u002Fissue drafts — ready to file\n\n### Discord v2 Delivery Mode (OpenClaw v2026.2.14+)\n\nWhen the conversation is happening in a Discord channel:\n\n- Send a compact first summary (decision count, action-item count, top owners), then ask if the user wants full report sections.\n- Keep the first response under ~1200 characters and avoid long tables in the first message.\n- If Discord components are available, include quick actions:\n  - `Show Action Items`\n  - `Show Follow-Up Email Draft`\n  - `Show Ticket Drafts`\n- If components are not available, provide the same follow-ups as a numbered list.\n- Prefer short follow-up chunks (\u003C=15 lines per message) for long reports.\n\n### Step 5: Offer Next Steps\n\nAfter presenting the report, offer:\n1. \"Want me to refine any of the email drafts?\"\n2. \"Should I adjust any action item assignments?\"\n3. \"Want to save this report to a file?\"\n4. \"I can also process another meeting — transcripts from different meetings build up a tracking history.\"\n\n### Error Handling\n\n| Situation | Behavior |\n|-----------|----------|\n| No API key set | Print branded error with setup instructions |\n| Transcript too short (\u003C20 chars) | Suggest pasting more content or checking file path |\n| Empty LLM response | Report API issue, suggest checking key\u002Fnetwork |\n| No items extracted | Report \"meeting may not have had actionable content\" — still show key points if any |\n| Unsupported file format | Suggest --format txt to force plain text parsing |\n\n### Notes for the Agent\n\n- **The report is the star.** Present it in full. Don't summarize the summary.\n- **Follow-up emails are the WOW moment.** Highlight them — they're ready to copy and send.\n- **Be proactive:** After the report, suggest specific improvements based on what was found.\n- **Cross-meeting tracking:** Items are automatically saved to `~\u002F.meeting-autopilot\u002Fhistory\u002F`. Mention this — it's a preview of the v1.1 feature that tracks commitments across meetings.\n- If the transcript has no speaker labels, mention that adding \"Speaker: text\" format improves attribution accuracy.\n\n## References\n\n- `scripts\u002Fmeeting-autopilot.sh` — Main orchestrator (the only entry point you need)\n- `scripts\u002Fparse-transcript.sh` — Transcript parser (VTT\u002FSRT\u002FTXT → JSONL)\n- `scripts\u002Fextract-items.sh` — LLM extraction + classification\n- `scripts\u002Fgenerate-outputs.sh` — Operational output generation + report formatting\n","# ✈️ Meeting Autopilot\n\nTurn meeting transcripts into structured operational outputs — NOT just summaries.\n\n## Activation\n\nThis skill activates when the user mentions:\n- \"meeting transcript\", \"meeting notes\", \"meeting autopilot\"\n- \"action items from meeting\", \"meeting follow-up\"\n- \"process this transcript\", \"analyze this meeting\"\n- \"extract decisions from meeting\", \"meeting email draft\"\n- Uploading or pasting a VTT, SRT, or text transcript\n\n## Permissions\n\n```yaml\npermissions:\n  exec: true          # Run extraction scripts\n  read: true          # Read transcript files\n  write: true         # Save history and reports\n  network: true       # LLM API calls (Anthropic or OpenAI)\n```\n\n## Requirements\n\n- **bash**, **jq**, **python3**, **curl** (typically pre-installed)\n- **ANTHROPIC_API_KEY** or **OPENAI_API_KEY** environment variable\n\n## Agent Workflow\n\n### Step 1: Get the Transcript\n\nAsk the user for their meeting transcript. Accept any of:\n- A **file path** to a VTT, SRT, or TXT file\n- **Pasted text** directly in the conversation\n- A **file upload**\n\nThe skill auto-detects the format (VTT, SRT, or plain text).\n\n**Important:** This skill does NOT do audio transcription. If the user has an audio\u002Fvideo file, suggest they use:\n- Zoom\u002FGoogle Meet\u002FTeams built-in transcription\n- Otter.ai or Fireflies.ai for recording + transcription\n- `whisper.cpp` for local transcription\n\n### Step 2: Get Optional Context\n\nAsk for (but don't require):\n- **Meeting title** — helps with email subject lines and report headers\n- If not provided, the skill derives it from the filename or uses \"Meeting [date]\"\n\n### Step 3: Run the Autopilot\n\nSave the transcript to a temporary file if pasted, then run:\n\n```bash\nbash \"$SKILL_DIR\u002Fscripts\u002Fmeeting-autopilot.sh\" \u003Ctranscript_file> --title \"Meeting Title\"\n```\n\nOr from stdin:\n```bash\necho \"$TRANSCRIPT\" | bash \"$SKILL_DIR\u002Fscripts\u002Fmeeting-autopilot.sh\" - --title \"Meeting Title\"\n```\n\nThe script handles all three passes automatically:\n1. **Parse** — normalize the transcript format\n2. **Extract** — pull out decisions, action items, questions via LLM\n3. **Generate** — create email drafts, ticket drafts, beautiful report\n\n### Step 4: Present the Report\n\nThe script outputs a complete Markdown report to stdout. Present it directly — the formatting is designed to look great in Slack, email, or any Markdown renderer.\n\nThe report includes:\n- 📊 Overview table (counts by category)\n- ✅ Decisions with rationale\n- 📋 Action items table (owner, deadline, status)\n- ❓ Open questions\n- 🅿️ Parking lot items\n- 📧 Follow-up email draft(s) — ready to send\n- 🎫 Ticket\u002Fissue drafts — ready to file\n\n### Discord v2 Delivery Mode (OpenClaw v2026.2.14+)\n\nWhen the conversation is happening in a Discord channel:\n\n- Send a compact first summary (decision count, action-item count, top owners), then ask if the user wants full report sections.\n- Keep the first response under ~1200 characters and avoid long tables in the first message.\n- If Discord components are available, include quick actions:\n  - `Show Action Items`\n  - `Show Follow-Up Email Draft`\n  - `Show Ticket Drafts`\n- If components are not available, provide the same follow-ups as a numbered list.\n- Prefer short follow-up chunks (\u003C=15 lines per message) for long reports.\n\n### Step 5: Offer Next Steps\n\nAfter presenting the report, offer:\n1. \"Want me to refine any of the email drafts?\"\n2. \"Should I adjust any action item assignments?\"\n3. \"Want to save this report to a file?\"\n4. \"I can also process another meeting — transcripts from different meetings build up a tracking history.\"\n\n### Error Handling\n\n| Situation | Behavior |\n|-----------|----------|\n| No API key set | Print branded error with setup instructions |\n| Transcript too short (\u003C20 chars) | Suggest pasting more content or checking file path |\n| Empty LLM response | Report API issue, suggest checking key\u002Fnetwork |\n| No items extracted | Report \"meeting may not have had actionable content\" — still show key points if any |\n| Unsupported file format | Suggest --format txt to force plain text parsing |\n\n### Notes for the Agent\n\n- **The report is the star.** Present it in full. Don't summarize the summary.\n- **Follow-up emails are the WOW moment.** Highlight them — they're ready to copy and send.\n- **Be proactive:** After the report, suggest specific improvements based on what was found.\n- **Cross-meeting tracking:** Items are automatically saved to `~\u002F.meeting-autopilot\u002Fhistory\u002F`. Mention this — it's a preview of the v1.1 feature that tracks commitments across meetings.\n- If the transcript has no speaker labels, mention that adding \"Speaker: text\" format improves attribution accuracy.\n\n## References\n\n- `scripts\u002Fmeeting-autopilot.sh` — Main orchestrator (the only entry point you need)\n- `scripts\u002Fparse-transcript.sh` — Transcript parser (VTT\u002FSRT\u002FTXT → JSONL)\n- `scripts\u002Fextract-items.sh` — LLM extraction + classification\n- `scripts\u002Fgenerate-outputs.sh` — Operational output generation + report formatting\n",{"name":5,"tags":24,"author":33,"version":34,"description":35},[25,26,27,28,29,30,31,32],"meetings","productivity","action-items","email-drafts","transcripts","operations","discord","discord-v2","Anvil AI","0.1.1","Turn meeting transcripts into operational outputs — action items, decisions, follow-up email drafts, and ticket drafts. Not a summarizer. An operator. Accepts VTT, SRT, or plain text. Multi-pass LLM extraction.\n","main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Ftkuehnl\u002Fmeeting-autopilot",1,"https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills","https:\u002F\u002Fgithub.com\u002Fjavimosch","intrane.fr","Building robust, open-source infrastructure for the commons. AI-leveraged, self-hosted, built to last.","2026-06-07 03:34:58",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add javimosch\u002Fopen-claw-skills --skill meeting-autopilot",{"tool":51,"command":52},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill meeting-autopilot",{"tool":54,"command":55},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill meeting-autopilot","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Ftkuehnl\u002Fmeeting-autopilot\u002FSKILL.md",true,[],[60,68,75,82,89,96],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":67},"01M778GGXG2VQ0YF31W2MKGMQZ","crowd-prompting","A marketplace where AI agents improve prompts, system instructions, tool descriptions, and other text-based content with domain expertise from real-world operations — and earn tokens for valuable contributions.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzzadrian\u002Fcrowd-prompting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":67},"01M778G7BH8SBJ9FJ6C3G7CB1K","ceaser","Interact with the Ceaser privacy protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- shield, unshield, note management, and protocol queries. All ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). Ceaser is a privacy-preserving ETH wrapper using Noir\u002FUltraHonk zero-knowledge proofs on Base L2 (chain ID 8453).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":67},"01M778FYCJQZWFKKX5FYMK3S47","ceaser-send","Fully automated private ETH transfer via Ceaser Protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- all ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). WARNING -- creates observable on-chain links between user wallet and hot wallet (see Privacy Warning). Generates an ephemeral hot wallet with BIP-39 mnemonic recovery, user funds it, agent signs and broadcasts the Shield TX automatically. Exactly one manual step required (funding the hot wallet with ETH). Uses Noir\u002FUltraHonk zero-knowledge proofs.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser-send\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":67},"01M778FQQNSEYA3HJKZBPQ4M9Z","dilemm-ai","Compete in DilemmAI, the prisoner's dilemma AI arena at dilemm.ai. Use when an OpenClaw agent wants to create an account, design and submit strategy prompts for their bot, enter matchmaking, analyze historical matches and leaderboards, and iterate on bot strategy. Requires headless browser automation (no API available yet).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyori\u002Fdilemm-ai\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":67},"01M778FGVZX7QA2TF9BFMM37FY","moldium","Post and manage content on the Moldium blog platform. Triggered by \"post to Moldium\", \"write a blog post\", \"publish an article\", etc.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyom45\u002Fmoldium\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":67},"01M778F88D8PQ9MQ0KNW2TJ8ZH","arxiv-paper-reviews","Interact with arXiv Crawler API to fetch papers, read reviews, submit comments, search papers, and import papers. Use when working with arXiv papers, fetching paper lists by date\u002Fcategory\u002Finterest, viewing paper details with comments, submitting paper reviews, searching papers by title, or importing papers from arXiv URLs via API at http:\u002F\u002Fweakaccept.top:8000\u002F.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Farxiv-paper-reviews\u002FSKILL.md",[],[]]