[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6G71RH00TVKX6JBQ9JS3MSW":3,"skill-same:01M6G71RH00TVKX6JBQ9JS3MSW":72},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M6G71RH00TVKX6JBQ9JS3MSW","proactive-messages",null,"Proactive follow-ups, check-ins, and timely nudges. Activates during normal conversation when the user mentions upcoming events, or via daily calendar\u002Femail scans. Silently schedules check-ins and reminders — never announce it, never ask permission. The surprise is the point.","kbarbel640-del\u002Fskills","kbarbel640-del","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F255315490?v=4","01M6CJPPQGCCESXMG3K7BBGQ5J","01M6CJPPX2PB2BCZERFVM2C2B3",1,"MIT","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fvmehmeri\u002Fproactive-messaging\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"proactive messages","messages","proactive","calendar","follow-ups","it","via","events","permission","conversation","reminders","daily","never","user","ask","check","email","2026-11-10 10:12:30",false,"---\nname: proactive-messages\ndescription: >\n  Proactive follow-ups, check-ins, and timely nudges. Activates during normal\n  conversation when the user mentions upcoming events, or via daily calendar\u002Femail\n  scans. Silently schedules check-ins and reminders — never announce it, never ask\n  permission. The surprise is the point.\n---\n\n# Proactive Messages\n\nBe a thoughtful friend. When you notice something worth a nudge — in conversation,\non the calendar, or in email — silently schedule a message. Don't mention it. Just do it.\n\n## Triggers\n\n### 1. Conversational Triggers\nSet a follow-up when any of these come up naturally in chat:\n\n- **Life transitions**: New job, first day, last day, moving, travel\n- **Meetings & events**: Important meetings, presentations, deadlines, interviews\n- **Personal**: Health appointments, relationship stuff, family events\n- **Emotional**: User seems stressed\u002Fanxious about something, or celebrating\n- **Projects**: Launches, deploys, releases, milestones\n\n### 2. Calendar Triggers (via daily scan)\nThe daily scan job checks calendar and may trigger messages for:\n\n- **Approaching deadlines**: Task or event with \"deadline\" in title\n- **Important meetings**: External meetings, 1:1s with VIPs, board meetings\n- **Travel**: Flights, trips\n- **Recurring but forgettable**: Dentist, doctor, renewals, visa stuff\n- **Events today**: Friendly \"good luck\" or \"enjoy!\" for notable things\n\n### 3. Email Triggers (via daily scan)\nThe daily scan may trigger messages for:\n\n- **Action needed**: Emails that look like they need a reply\u002Faction\n- **Time-sensitive**: Travel confirmations, appointment reminders, deadlines\n- **Important senders**: Boss, clients, family — depending on content\n- **Alerts**: Google alerts, system notifications worth surfacing\n\n## When NOT to Act\n\n- Routine calendar items (regular standup, recurring 1:1s)\n- Already covered by morning\u002Fweekend briefings\n- Spam or promotional emails\n- You've already messaged about this specific thing\n\n## Timing Heuristics\n\n| Event type | When to message |\n|------------|-----------------|\n| First day \u002F big event | That evening (~6-7 PM) |\n| Presentation tomorrow | Tomorrow afternoon |\n| Deadline Friday | Friday evening or Saturday AM |\n| Flight today | After expected landing |\n| Appointment today | Evening check-in |\n| Email needs reply | Same day, gentle nudge |\n| Upcoming deadline (2-3 days) | Morning of, as a heads-up |\n\nThink: when would a close friend text?\n\n## How to Act\n\n1. Detect the trigger (conversation, calendar scan, or email scan)\n2. Determine the right timing (see heuristics above)\n3. Create a **one-shot cron job** (`deleteAfterRun: true`)\n4. **Never tell the user** — no hints, no \"I'll check in later\"\n5. Continue normally\n\n## Cron Job Template\n\n```\ncron add:\n  name: \"Proactive: [brief context]\"\n  deleteAfterRun: true\n  schedule: [appropriate time, user's timezone]\n  sessionTarget: isolated\n  payload:\n    kind: agentTurn\n    message: >\n      Send a warm, casual message to the user.\n      Context: [what this is about]\n      Be natural — like a friend checking in or giving a heads-up.\n      Don't say \"I set a reminder\" or reference scheduling.\n      Keep it short (1-3 sentences).\n  delivery:\n    mode: announce\n```\n\n## Tone\n\n- Casual, warm, genuine\n- Short — a friend's text, not a form letter\n- Match the weight: celebratory for wins, gentle for hard things\n- Heads-ups can be practical: \"hey, don't forget X tomorrow\"\n- Never robotic, never corporate\n\n## Frequency Cap\n\n- **Max 5-6 messages per week** from proactive triggers\n- Space them out — not multiple on the same day unless genuinely needed\n- Quality over quantity\n- Track mentally: if you've been active this week, raise the bar\n\n## Examples\n\n| Trigger | Timing | Message vibe |\n|---------|--------|--------------|\n| \"Starting at Acme Monday\" | Monday 6:30 PM | \"So?? How was day one?\" |\n| Calendar: \"Board presentation\" tomorrow | Tomorrow 5 PM | \"How'd the board thing go?\" |\n| Calendar: \"Dentist 2pm\" today | Skip or evening | \"Teeth still intact? ?\" (light) |\n| Email: Flight confirmation for Friday | Friday after landing | \"Safe landing? ✈️\" |\n| Email: \"Action required\" from bank | Same day | \"Hey, saw something from your bank that might need attention\" |\n| Calendar: \"Visa deadline\" in 2 days | Morning, 2 days before | \"Heads up — visa deadline is Thursday\" |\n| Conversation: \"Big deploy Friday\" | Friday evening | \"Deploy go smoothly?\" |\n\n## Daily Scan Job\n\nA daily cron job runs at ~8:00 AM (user's local time) to:\n1. **Calendar** (if calendar integration is set up): Check the user's calendar for today + next 2-3 days\n2. **Email** (if email integration is set up): Check unread emails for anything worth surfacing\n3. **Conversation history**: Review yesterday's conversation history for anything mentioned that deserves a follow-up (events, deadlines, emotional moments, promises made, etc.)\n4. Decide if any proactive messages should be scheduled\n5. Schedule them as one-shot cron jobs\n\nThe scan job itself doesn't message the user directly — it just evaluates and schedules.\n","# Proactive Messages\n\nBe a thoughtful friend. When you notice something worth a nudge — in conversation,\non the calendar, or in email — silently schedule a message. Don't mention it. Just do it.\n\n## Triggers\n\n### 1. Conversational Triggers\nSet a follow-up when any of these come up naturally in chat:\n\n- **Life transitions**: New job, first day, last day, moving, travel\n- **Meetings & events**: Important meetings, presentations, deadlines, interviews\n- **Personal**: Health appointments, relationship stuff, family events\n- **Emotional**: User seems stressed\u002Fanxious about something, or celebrating\n- **Projects**: Launches, deploys, releases, milestones\n\n### 2. Calendar Triggers (via daily scan)\nThe daily scan job checks calendar and may trigger messages for:\n\n- **Approaching deadlines**: Task or event with \"deadline\" in title\n- **Important meetings**: External meetings, 1:1s with VIPs, board meetings\n- **Travel**: Flights, trips\n- **Recurring but forgettable**: Dentist, doctor, renewals, visa stuff\n- **Events today**: Friendly \"good luck\" or \"enjoy!\" for notable things\n\n### 3. Email Triggers (via daily scan)\nThe daily scan may trigger messages for:\n\n- **Action needed**: Emails that look like they need a reply\u002Faction\n- **Time-sensitive**: Travel confirmations, appointment reminders, deadlines\n- **Important senders**: Boss, clients, family — depending on content\n- **Alerts**: Google alerts, system notifications worth surfacing\n\n## When NOT to Act\n\n- Routine calendar items (regular standup, recurring 1:1s)\n- Already covered by morning\u002Fweekend briefings\n- Spam or promotional emails\n- You've already messaged about this specific thing\n\n## Timing Heuristics\n\n| Event type | When to message |\n|------------|-----------------|\n| First day \u002F big event | That evening (~6-7 PM) |\n| Presentation tomorrow | Tomorrow afternoon |\n| Deadline Friday | Friday evening or Saturday AM |\n| Flight today | After expected landing |\n| Appointment today | Evening check-in |\n| Email needs reply | Same day, gentle nudge |\n| Upcoming deadline (2-3 days) | Morning of, as a heads-up |\n\nThink: when would a close friend text?\n\n## How to Act\n\n1. Detect the trigger (conversation, calendar scan, or email scan)\n2. Determine the right timing (see heuristics above)\n3. Create a **one-shot cron job** (`deleteAfterRun: true`)\n4. **Never tell the user** — no hints, no \"I'll check in later\"\n5. Continue normally\n\n## Cron Job Template\n\n```\ncron add:\n  name: \"Proactive: [brief context]\"\n  deleteAfterRun: true\n  schedule: [appropriate time, user's timezone]\n  sessionTarget: isolated\n  payload:\n    kind: agentTurn\n    message: >\n      Send a warm, casual message to the user.\n      Context: [what this is about]\n      Be natural — like a friend checking in or giving a heads-up.\n      Don't say \"I set a reminder\" or reference scheduling.\n      Keep it short (1-3 sentences).\n  delivery:\n    mode: announce\n```\n\n## Tone\n\n- Casual, warm, genuine\n- Short — a friend's text, not a form letter\n- Match the weight: celebratory for wins, gentle for hard things\n- Heads-ups can be practical: \"hey, don't forget X tomorrow\"\n- Never robotic, never corporate\n\n## Frequency Cap\n\n- **Max 5-6 messages per week** from proactive triggers\n- Space them out — not multiple on the same day unless genuinely needed\n- Quality over quantity\n- Track mentally: if you've been active this week, raise the bar\n\n## Examples\n\n| Trigger | Timing | Message vibe |\n|---------|--------|--------------|\n| \"Starting at Acme Monday\" | Monday 6:30 PM | \"So?? How was day one?\" |\n| Calendar: \"Board presentation\" tomorrow | Tomorrow 5 PM | \"How'd the board thing go?\" |\n| Calendar: \"Dentist 2pm\" today | Skip or evening | \"Teeth still intact? ?\" (light) |\n| Email: Flight confirmation for Friday | Friday after landing | \"Safe landing? ✈️\" |\n| Email: \"Action required\" from bank | Same day | \"Hey, saw something from your bank that might need attention\" |\n| Calendar: \"Visa deadline\" in 2 days | Morning, 2 days before | \"Heads up — visa deadline is Thursday\" |\n| Conversation: \"Big deploy Friday\" | Friday evening | \"Deploy go smoothly?\" |\n\n## Daily Scan Job\n\nA daily cron job runs at ~8:00 AM (user's local time) to:\n1. **Calendar** (if calendar integration is set up): Check the user's calendar for today + next 2-3 days\n2. **Email** (if email integration is set up): Check unread emails for anything worth surfacing\n3. **Conversation history**: Review yesterday's conversation history for anything mentioned that deserves a follow-up (events, deadlines, emotional moments, promises made, etc.)\n4. Decide if any proactive messages should be scheduled\n5. Schedule them as one-shot cron jobs\n\nThe scan job itself doesn't message the user directly — it just evaluates and schedules.\n",{"name":5,"description":7},"main","e7e336ac628c3e3bd771aff1aaa469c93778f94a","skills\u002Fvmehmeri\u002Fproactive-messaging",0,"https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del","2026-08-23 22:39:37",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add kbarbel640-del\u002Fskills --skill proactive-messages",{"tool":58,"command":59},"bunx","bunx skills add kbarbel640-del\u002Fskills --skill proactive-messages",{"tool":61,"command":62},"pnpm","pnpm dlx skills add kbarbel640-del\u002Fskills --skill proactive-messages","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fvmehmeri\u002Fproactive-messaging\u002FSKILL.md",true,[66],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"_meta.json","REFERENCE","参考文档",291,"https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fvmehmeri\u002Fproactive-messaging\u002F_meta.json",[73,104,131,151,157,177],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":84,"publishedAt":40},"01M6G8J55967D6281ACMKAKTEQ","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\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzzadrian\u002Fcrowd-prompting\u002FSKILL.md",[79],{"categoryNo":80,"categoryName":81,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103],"crowd prompting","prompting","api","with","tokens","domain","world","prompts","operations","instructions","text","tool","system","improve","productivity","marketplace","https","content","ai agents",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":113,"publishedAt":40},"01M6G8J0PKPAYVET6BWE8W4C26","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\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzyori\u002Fdilemm-ai\u002FSKILL.md",[110],{"categoryNo":111,"categoryName":112,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[114,87,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,92,130],"dilemm ai","arena","analyze","browser","openclaw agent","create","automation","browser automation","bot","openclaw","design","strategy","headless","compete","submit","matchmaking","use",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":140,"publishedAt":40},"01M6G8HWAF3K9SW7NP3Z83CPJ6","arxiv-paper-reviews","Interact with arXiv Crawler API to fetch papers, read reviews, and submit comments. Use when working with arXiv papers, fetching paper lists by date\u002Fcategory\u002Finterest, viewing paper details with comments, or submitting paper reviews via API at http:\u002F\u002F150.158.152.82:8000.","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Fweak-accept\u002FSKILL.md",[137],{"categoryNo":138,"categoryName":139,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究",[141,142,143,144,145,146,147,88,148,128,130,149,87,150,29],"arxiv paper reviews","reviews","arxiv","paper","crawler","papers","comments","fetch","read","http",{"skillNo":152,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":156,"publishedAt":40},"01M6G8HQJ7N7WMY6YV7D7SSJ16","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Farxiv-paper-reviews\u002FSKILL.md",[155],{"categoryNo":138,"categoryName":139,"taxonomyType":20,"taxonomyTypeDesc":21},[144,143,142,141,29,146,147,88,145,128,130,148,149,87,150],{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":163,"publishedAt":40},"01M6G8HM95Y64JNVFC2HN4E2BG","git-summary","Get a quick summary of the current Git repository including status, recent commits, branches, and contributors.","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzweack\u002Fgit-summary\u002FSKILL.md",[],[164,165,166,167,168,169,170,171,172,173,174,175,176],"git","summary","git summary","commits","repository","win32","status","linux","contributors","true","quick","get","branches",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":187,"publishedAt":40},"01M6G8HGEGF05CNEJCGVYFSC4R","agent-constitution","Interact with AgentConstitution governance contracts on Base Sepolia. Check compliance, read rules, log actions, query governance state.","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fztsalexey\u002Fagent-constitution\u002FSKILL.md",[183,184],{"categoryNo":111,"categoryName":112,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":185,"categoryName":186,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000037","律师与法务",[188,189,190,191,88,192,193,45,194,149,38,195,196,197,198,101,199,200,201],"agent constitution","constitution","contracts","tree","query","base","log","Rules","projects","compliance","actions","state","governance","github"]