[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78J6PX6BA94CFZCP2RRB0HS":3,"skill-same:01M78J6PX6BA94CFZCP2RRB0HS":54},{"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":31,"commitSha":32,"skillDirectory":33,"forksCount":34,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":37,"ownerDescription":38,"updatedAt":39,"install":40,"resources":53},"01M78J6PX6BA94CFZCP2RRB0HS","todoist-due-drafts",null,"Check Todoist for tasks due today (and overdue) that involve pinging, emailing, or following up with someone. Auto-draft the emails using meeting context and notify via WhatsApp. Use when running the daily due-drafts cron, or when user asks to process email tasks from Todoist.","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fbusiness-tools--executive-assistant-skills--todoist-due-drafts\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: todoist-due-drafts\ndescription: Check Todoist for tasks due today (and overdue) that involve pinging, emailing, or following up with someone. Auto-draft the emails using meeting context and notify via WhatsApp. Use when running the daily due-drafts cron, or when user asks to process email tasks from Todoist.\nversion: 1.0.0\nlicense: MIT\nauthor: \"Martin Gontovnikas \u003Cmartin@hypergrowthpartners.com>\"\ncompatible-with: claude-code\ntags: [business, todoist-due]\nallowed-tools: Read, Bash(gog:*), Bash(mcporter:*), Bash(todoist-cli:*), Bash(python3:*), Bash(source:*), Glob, Grep, Write\n---\n# Todoist Due-Today Email Drafts\n\n## Config — read before starting\nRead `..\u002Fconfig\u002Fuser.json` (resolves to `~\u002Fexecutive-assistant-skills\u002Fconfig\u002Fuser.json`).\nExtract and use throughout:\n- `primary_email`, `work_email` — Gmail accounts\n- `whatsapp` — for notification delivery\n- `workspace` — absolute path to OpenClaw workspace\n- `signature` — email signature\n\n## Debug Logging (MANDATORY)\nRead `..\u002Fconfig\u002FDEBUG_LOGGING.md` for the full convention. Use `python3 {user.workspace}\u002Fscripts\u002Fskill_log.py todoist-due-drafts \u003Clevel> \"\u003Cmessage>\" ['\u003Cdetails>']` at every key step. Log BEFORE and AFTER every external call (todoist-cli, gog, mcporter). On any error, log the full command and stderr before continuing.\n\n## Steps\n\n### 1. Get today's due tasks from Todoist\n```bash\nsource {user.workspace}\u002F.env\ntodoist-cli today --json\n```\n\nAlso check overdue tasks:\n```bash\ntodoist-cli list --filter \"overdue\" --json\n```\n\n### 2. Identify email\u002Fping tasks\nFilter for tasks whose content matches outreach intent:\n- Keywords: `ping`, `email`, `follow up`, `follow-up`, `send`, `reach out`, `text`, `message`, `intro`, `connect`, `check in`, `nudge`, `reply`, `respond`, `draft`\n- Pattern: any task that implies sending a communication to a specific person\n\nSkip tasks that are clearly NOT outreach (e.g. \"review doc\", \"read report\", \"build proposal\").\n\n### 3. For each outreach task, draft the email\nRead and follow `~\u002Fexecutive-assistant-skills\u002Femail-drafting\u002FSKILL.md` for all drafting rules.\n\nFor each task:\n1. **Identify the recipient**: Extract person\u002Fcompany name from task content + description\n2. **Pull meeting context (if available)**: If the task description references a meeting name, date, or was created by the action-items cron (check for Granola citation links or meeting metadata in description), retrieve the transcript via Granola\u002FGrain. If no meeting reference exists in the task, skip directly to step 3 — draft from email history and task content alone.\n   ```bash\n   # Find the meeting in Granola\n   mcporter call granola list_meetings --args '{\"time_range\": \"custom\", \"custom_start\": \"\u003Cmeeting-date>\", \"custom_end\": \"\u003Cmeeting-date+1>\"}'\n   # Query for what was discussed with this person\n   mcporter call granola query_granola_meetings --args '{\"query\": \"What did {user.name} discuss with \u003Crecipient> and what did he promise or commit to do?\", \"document_ids\": [\"\u003Cmeeting_id>\"]}'\n   ```\n   Then cross-check with Grain for the full transcript:\n   ```bash\n   mcporter call grain.list_attended_meetings --args '{}'\n   # Note: Grain's schema does not support `start_date`\u002F`end_date` filters. Call with empty args and filter the results manually by `start_datetime` to match the meeting date range.\n   mcporter call grain.fetch_meeting_transcript --args '{\"meeting_id\": \"\u003Cgrain_meeting_id>\"}'\n   ```\n   When meeting context is available, the email draft must reflect what was actually said — not just the task title. Look for: specific commitments, timelines discussed, names\u002Fprojects mentioned, tone of the conversation, and any docs\u002Flinks promised.\n3. **Search email history**: Find the latest thread with this person across both Gmail accounts to get context, their email address, and the right account to reply from. If no prior thread exists with this recipient, default to `{user.work_email}` for professional\u002Fbusiness contacts or `{user.primary_email}` for personal contacts. When ambiguous, use `{user.work_email}`.\n4. **Determine email type**: follow-up, ping\u002Fcheck-in, intro, send-doc, etc.\n5. **Draft the email**: Create a Gmail draft on the correct account (the one with the existing thread). If it's a reply, use `--thread-id` to keep it in the same thread.\n6. **Use all context together**: Combine the meeting transcript (what was actually discussed), task description, and email history to write a specific, contextual draft. Never write generic follow-ups — reference concrete topics from the conversation.\n\n#### Draft rules\n- Mirror the language of the existing thread (English or Spanish)\n- Keep it short — these are follow-ups and pings, not essays\n- Sign with `{user.signature}`\n- If the task says \"ping\" or \"check in\" — write a brief, friendly nudge\n- If the task says \"send [thing]\" — draft the email with the attachment reference (or attach if path is known)\n- If the task says \"intro\" — follow intro format from email-drafting skill\n- If recipient email can't be found — report it, don't skip silently\n\n### 4. Notify via WhatsApp\nSend a single WhatsApp message to {user.whatsapp} with:\n\n```\n📬 *Due-today drafts*\n\n\u003CN> email drafts created from today's Todoist tasks:\n\n1. **\u003Crecipient>** — \u003Cone-line intent> (draft in \u003Caccount>)\n2. ...\n\nReview and send when ready.\n```\n\nIf tasks exist but none are outreach-type, report:\n```\n📋 *Due-today tasks (no drafts needed)*\n\n\u003Clist of today's tasks — quick reference>\n```\n\nIf no tasks due today → NO_REPLY (skip notification entirely).\n\n### 5. Infrastructure\n```bash\npython3 {user.workspace}\u002Fscripts\u002Fcron_canary.py ping todoist-due-drafts\n```\n\n## Error handling\n- If `todoist-cli` fails: notify via WhatsApp \"⚠️ Todoist due-drafts failed: \u003Cerror>\", ping canary, exit.\n- If Granola\u002FGrain lookup fails for a task: continue without meeting context — draft from email history + task content only.\n- If Gmail draft creation fails for one task: continue with remaining tasks, report failures in the notification.\n- If no `.env` file or token expired: report \"⚠️ Todoist token unavailable — check agent-secrets lease\" and exit.\n\n## Rules\n- Don't complete the tasks — just draft and notify. User decides when to send.\n- Before drafting, check if user already replied: `gog --account \u003Caccount> --no-input gmail search \"to:\u003Crecipient> in:sent newer_than:14d\" --json`. If recent sent mail exists in the same thread, skip drafting and note \"already replied\" in the notification.\n- Check for existing drafts before creating: `gog --account \u003Caccount> --no-input gmail drafts --json`. If a draft already exists for the same thread (matching thread ID or recipient + subject), skip and note \"draft already exists.\"\n- Overdue outreach tasks get a ⚠️ prefix in the notification.\n\n## Overview\n\nScans Todoist for due and overdue tasks that involve outreach (pinging, emailing, following up), auto-drafts contextual emails using meeting transcripts and email history, and notifies via WhatsApp.\n\n## Prerequisites\n\n- `todoist-cli` installed with valid API token in workspace `.env`\n- `gog` CLI configured with both Gmail accounts\n- `mcporter` with Granola and Grain MCP connections for meeting context lookup\n- WhatsApp delivery endpoint configured in `user.json`\n- OpenClaw workspace with `skill_log.py` and `cron_canary.py` scripts\n\n## Instructions\n\nSee the Steps section above (Steps 1 through 5) for the full execution workflow.\n\n## Output\n\n- Gmail drafts created on the appropriate account for each outreach task\n- A single WhatsApp notification summarizing all drafts created, or a task list if no drafts were needed\n- NO_REPLY if no tasks are due today\n\n## Examples\n\n```bash\n# The skill runs todoist-cli to find due tasks, identifies outreach items,\n# pulls meeting context from Granola\u002FGrain, drafts emails via gog, and notifies.\n# Example WhatsApp output:\n# \"2 email drafts created from today's Todoist tasks:\n#  1. Sarah Chen — follow-up on advisory scope (draft in work account)\n#  2. David Park — intro to Marcos (draft in personal account)\"\n```\n\n## Resources\n\n- [Todoist REST API](https:\u002F\u002Fdeveloper.todoist.com\u002Frest\u002Fv2\u002F)\n- [Gmail API](https:\u002F\u002Fdevelopers.google.com\u002Fgmail\u002Fapi)\n- [Granola API](https:\u002F\u002Fgranola.ai\u002Fdocs)\n- [Grain API](https:\u002F\u002Fgrain.com\u002Fdocs)\n","# Todoist Due-Today Email Drafts\n\n## Config — read before starting\nRead `..\u002Fconfig\u002Fuser.json` (resolves to `~\u002Fexecutive-assistant-skills\u002Fconfig\u002Fuser.json`).\nExtract and use throughout:\n- `primary_email`, `work_email` — Gmail accounts\n- `whatsapp` — for notification delivery\n- `workspace` — absolute path to OpenClaw workspace\n- `signature` — email signature\n\n## Debug Logging (MANDATORY)\nRead `..\u002Fconfig\u002FDEBUG_LOGGING.md` for the full convention. Use `python3 {user.workspace}\u002Fscripts\u002Fskill_log.py todoist-due-drafts \u003Clevel> \"\u003Cmessage>\" ['\u003Cdetails>']` at every key step. Log BEFORE and AFTER every external call (todoist-cli, gog, mcporter). On any error, log the full command and stderr before continuing.\n\n## Steps\n\n### 1. Get today's due tasks from Todoist\n```bash\nsource {user.workspace}\u002F.env\ntodoist-cli today --json\n```\n\nAlso check overdue tasks:\n```bash\ntodoist-cli list --filter \"overdue\" --json\n```\n\n### 2. Identify email\u002Fping tasks\nFilter for tasks whose content matches outreach intent:\n- Keywords: `ping`, `email`, `follow up`, `follow-up`, `send`, `reach out`, `text`, `message`, `intro`, `connect`, `check in`, `nudge`, `reply`, `respond`, `draft`\n- Pattern: any task that implies sending a communication to a specific person\n\nSkip tasks that are clearly NOT outreach (e.g. \"review doc\", \"read report\", \"build proposal\").\n\n### 3. For each outreach task, draft the email\nRead and follow `~\u002Fexecutive-assistant-skills\u002Femail-drafting\u002FSKILL.md` for all drafting rules.\n\nFor each task:\n1. **Identify the recipient**: Extract person\u002Fcompany name from task content + description\n2. **Pull meeting context (if available)**: If the task description references a meeting name, date, or was created by the action-items cron (check for Granola citation links or meeting metadata in description), retrieve the transcript via Granola\u002FGrain. If no meeting reference exists in the task, skip directly to step 3 — draft from email history and task content alone.\n   ```bash\n   # Find the meeting in Granola\n   mcporter call granola list_meetings --args '{\"time_range\": \"custom\", \"custom_start\": \"\u003Cmeeting-date>\", \"custom_end\": \"\u003Cmeeting-date+1>\"}'\n   # Query for what was discussed with this person\n   mcporter call granola query_granola_meetings --args '{\"query\": \"What did {user.name} discuss with \u003Crecipient> and what did he promise or commit to do?\", \"document_ids\": [\"\u003Cmeeting_id>\"]}'\n   ```\n   Then cross-check with Grain for the full transcript:\n   ```bash\n   mcporter call grain.list_attended_meetings --args '{}'\n   # Note: Grain's schema does not support `start_date`\u002F`end_date` filters. Call with empty args and filter the results manually by `start_datetime` to match the meeting date range.\n   mcporter call grain.fetch_meeting_transcript --args '{\"meeting_id\": \"\u003Cgrain_meeting_id>\"}'\n   ```\n   When meeting context is available, the email draft must reflect what was actually said — not just the task title. Look for: specific commitments, timelines discussed, names\u002Fprojects mentioned, tone of the conversation, and any docs\u002Flinks promised.\n3. **Search email history**: Find the latest thread with this person across both Gmail accounts to get context, their email address, and the right account to reply from. If no prior thread exists with this recipient, default to `{user.work_email}` for professional\u002Fbusiness contacts or `{user.primary_email}` for personal contacts. When ambiguous, use `{user.work_email}`.\n4. **Determine email type**: follow-up, ping\u002Fcheck-in, intro, send-doc, etc.\n5. **Draft the email**: Create a Gmail draft on the correct account (the one with the existing thread). If it's a reply, use `--thread-id` to keep it in the same thread.\n6. **Use all context together**: Combine the meeting transcript (what was actually discussed), task description, and email history to write a specific, contextual draft. Never write generic follow-ups — reference concrete topics from the conversation.\n\n#### Draft rules\n- Mirror the language of the existing thread (English or Spanish)\n- Keep it short — these are follow-ups and pings, not essays\n- Sign with `{user.signature}`\n- If the task says \"ping\" or \"check in\" — write a brief, friendly nudge\n- If the task says \"send [thing]\" — draft the email with the attachment reference (or attach if path is known)\n- If the task says \"intro\" — follow intro format from email-drafting skill\n- If recipient email can't be found — report it, don't skip silently\n\n### 4. Notify via WhatsApp\nSend a single WhatsApp message to {user.whatsapp} with:\n\n```\n📬 *Due-today drafts*\n\n\u003CN> email drafts created from today's Todoist tasks:\n\n1. **\u003Crecipient>** — \u003Cone-line intent> (draft in \u003Caccount>)\n2. ...\n\nReview and send when ready.\n```\n\nIf tasks exist but none are outreach-type, report:\n```\n📋 *Due-today tasks (no drafts needed)*\n\n\u003Clist of today's tasks — quick reference>\n```\n\nIf no tasks due today → NO_REPLY (skip notification entirely).\n\n### 5. Infrastructure\n```bash\npython3 {user.workspace}\u002Fscripts\u002Fcron_canary.py ping todoist-due-drafts\n```\n\n## Error handling\n- If `todoist-cli` fails: notify via WhatsApp \"⚠️ Todoist due-drafts failed: \u003Cerror>\", ping canary, exit.\n- If Granola\u002FGrain lookup fails for a task: continue without meeting context — draft from email history + task content only.\n- If Gmail draft creation fails for one task: continue with remaining tasks, report failures in the notification.\n- If no `.env` file or token expired: report \"⚠️ Todoist token unavailable — check agent-secrets lease\" and exit.\n\n## Rules\n- Don't complete the tasks — just draft and notify. User decides when to send.\n- Before drafting, check if user already replied: `gog --account \u003Caccount> --no-input gmail search \"to:\u003Crecipient> in:sent newer_than:14d\" --json`. If recent sent mail exists in the same thread, skip drafting and note \"already replied\" in the notification.\n- Check for existing drafts before creating: `gog --account \u003Caccount> --no-input gmail drafts --json`. If a draft already exists for the same thread (matching thread ID or recipient + subject), skip and note \"draft already exists.\"\n- Overdue outreach tasks get a ⚠️ prefix in the notification.\n\n## Overview\n\nScans Todoist for due and overdue tasks that involve outreach (pinging, emailing, following up), auto-drafts contextual emails using meeting transcripts and email history, and notifies via WhatsApp.\n\n## Prerequisites\n\n- `todoist-cli` installed with valid API token in workspace `.env`\n- `gog` CLI configured with both Gmail accounts\n- `mcporter` with Granola and Grain MCP connections for meeting context lookup\n- WhatsApp delivery endpoint configured in `user.json`\n- OpenClaw workspace with `skill_log.py` and `cron_canary.py` scripts\n\n## Instructions\n\nSee the Steps section above (Steps 1 through 5) for the full execution workflow.\n\n## Output\n\n- Gmail drafts created on the appropriate account for each outreach task\n- A single WhatsApp notification summarizing all drafts created, or a task list if no drafts were needed\n- NO_REPLY if no tasks are due today\n\n## Examples\n\n```bash\n# The skill runs todoist-cli to find due tasks, identifies outreach items,\n# pulls meeting context from Granola\u002FGrain, drafts emails via gog, and notifies.\n# Example WhatsApp output:\n# \"2 email drafts created from today's Todoist tasks:\n#  1. Sarah Chen — follow-up on advisory scope (draft in work account)\n#  2. David Park — intro to Marcos (draft in personal account)\"\n```\n\n## Resources\n\n- [Todoist REST API](https:\u002F\u002Fdeveloper.todoist.com\u002Frest\u002Fv2\u002F)\n- [Gmail API](https:\u002F\u002Fdevelopers.google.com\u002Fgmail\u002Fapi)\n- [Granola API](https:\u002F\u002Fgranola.ai\u002Fdocs)\n- [Grain API](https:\u002F\u002Fgrain.com\u002Fdocs)\n",{"name":5,"tags":24,"author":27,"license":15,"version":28,"description":7,"allowed-tools":29,"compatible-with":30},[25,26],"business","todoist-due","Martin Gontovnikas \u003Cmartin@hypergrowthpartners.com>","1.0.0","Read, Bash(gog:*), Bash(mcporter:*), Bash(todoist-cli:*), Bash(python3:*), Bash(source:*), Glob, Grep, Write","claude-code","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fbusiness-tools--executive-assistant-skills--todoist-due-drafts",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill todoist-due-drafts",{"tool":46,"command":47},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill todoist-due-drafts",{"tool":49,"command":50},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill todoist-due-drafts","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fbusiness-tools--executive-assistant-skills--todoist-due-drafts\u002FSKILL.md",true,[],[55,62,69,76,83,91],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":87,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]