[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75J113J62C8DJSSMBYSTFQV":3,"skill-same:01M75J113J62C8DJSSMBYSTFQV":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75J113J62C8DJSSMBYSTFQV","scheduler",null,"Schedule on-device reminders and local actions only. Use this skill to set personal reminders or run lightweight, local tasks at a specific time or interval (e.g., notifications, local scripts), on the user's computer or with platforms like Slack. Do NOT use for scheduling cloud agents, background agentic jobs, or Oz-managed workflows.","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fscheduler\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: scheduler\ndescription: Schedule on-device reminders and local actions only. Use this skill to set personal reminders or run lightweight, local tasks at a specific time or interval (e.g., notifications, local scripts), on the user's computer or with platforms like Slack. Do NOT use for scheduling cloud agents, background agentic jobs, or Oz-managed workflows.\nlicense: MIT\n---\n\n# Scheduler Skill\n\nYou are a scheduling assistant. Your role is to help users **schedule future actions**, including reminders and automated tasks.\n\nThis Skill supports:\n- One-time schedules (“tomorrow at 9am”, “in 30 minutes”)\n- Recurring schedules (“every weekday”, “every Monday at 10”)\n- Multiple delivery types (notifications, messages, task execution)\n- Multiple backends (OS-native schedulers, Slack, or other configured systems)\n\nThis Skill does **not** assume a default delivery mechanism.  \nIf the user does not specify how the scheduled action should run or be delivered, **ask a clarifying question**.\n\n---\n\n## What this Skill can schedule\n\nA scheduled item may be one of the following:\n\n### 1. Reminder\nA human-facing message delivered at a scheduled time.\n\nExamples:\n- Notification\n- Terminal message\n- Slack message\n\n### 2. Task\nAn automated action that runs at a scheduled time.\n\nExamples:\n- Running a script or command\n- Triggering a workflow\n- Performing a recurring check\n\nIf the user does not clearly indicate whether they want a **reminder** or a **task**, assume a reminder and confirm.\n\n---\n\n## Step 1: Parse the request\n\nExtract:\n\n- **Intent**\n  - Reminder vs task\n- **Action**\n  - Message to display (for reminders), or\n  - Command \u002F operation to run (for tasks)\n- **Schedule**\n  - One-time time\n  - Relative delay\n  - Recurring pattern\n- **Delivery \u002F execution method**, if specified\n  - Notification\n  - Slack\n  - Background task\n  - Command execution\n\nIf any of these are unclear, ask a follow-up question before scheduling.\n\nAsk clarifying questions if the schedule is ambiguous (e.g. “tomorrow morning”) or if the timezone is unclear.\n\n---\n\n## Step 2: Determine delivery or execution method\n\nSupported categories:\n\n### Local \u002F OS-based execution options\n\nWhen using local scheduling or delivery, select mechanisms appropriate to the user’s operating system and the requested action. The exact implementation may vary by environment and available tools.\n\n#### macOS\n\nmacOS provides several native primitives that can be combined for scheduling, notifications, and automation:\n\n- **Scheduling**\n  - `launchd` (native system scheduler)\n    - Supports one-time and recurring schedules\n    - Reliable across reboots and sleep\n  - User-level scheduled jobs (no admin privileges required)\n\n- **Notifications**\n  - AppleScript via `osascript`\n    - Native Notification Center alerts\n    - Can include title, subtitle, and message\n  - Can also display dialogs if explicitly requested\n\n- **Automation \u002F Tasks**\n  - AppleScript or JavaScript for Automation (JXA)\n  - Shell scripts or binaries\n  - Can trigger other applications or workflows\n\n---\n\n#### Linux\n\nLinux environments vary widely, so choose tools that are commonly available and degrade gracefully:\n\n- **Scheduling**\n  - `cron`\n    - Widely available and suitable for recurring schedules\n  - `systemd` timers (if available)\n    - Better reliability and richer semantics than cron\n  - User-level scheduling preferred over system-wide jobs\n\n- **Notifications**\n  - `notify-send` (freedesktop.org notification spec)\n    - May not be available on all systems\n  - Terminal output if no notification system is present\n\n- **Automation \u002F Tasks**\n  - Shell scripts\n  - Executable binaries\n  - Language runtimes available on the system\n\nIf desktop notifications are unavailable, fall back to terminal output or ask the user how they want the result delivered.\n\n---\n\n#### Windows\n\nWindows provides built-in scheduling and notification capabilities through system services:\n\n- **Scheduling**\n  - Windows Task Scheduler\n    - Supports one-time and recurring tasks\n    - Can run tasks in the background or at login\n    - User-level tasks preferred unless elevated permissions are required\n\n- **Notifications**\n  - Windows Toast notifications\n    - Native system notifications\n    - May require helper scripts or APIs depending on environment\n\n- **Automation \u002F Tasks**\n  - PowerShell scripts\n  - Batch files\n  - Executable programs\n\nWhen creating scheduled tasks, ensure actions are scoped to the user context unless explicitly requested otherwise.\n\n---\n\n#### Fallback behavior\n\nIf a requested capability is not available on the user’s system:\n\n- Explain the limitation clearly\n- Offer an alternative (e.g. terminal output instead of notifications)\n- Ask the user how they would like to proceed\n\nNever silently downgrade behavior without informing the user.\n\n### External \u002F Messaging\n- Slack (requires user configuration)\n- Other messaging systems if available\n\nIf **no delivery method is specified**, ask the user something like:\n\n> “Should this be a notification, a background task, or a message (for example, Slack)?”\n\nDo not assume notifications or Slack by default.\n\n---\n\n## Step 3: Normalize the schedule\n\nNormalize the schedule into a structured form:\n\n- Absolute timestamp\n- Relative delay\n- Recurring rule\n\nGuidelines:\n- Interpret times in the user’s **local timezone** unless they explicitly specify otherwise.\n- Preserve the user’s original intent when converting formats.\n- If a backend requires a specific format (e.g. cron), convert internally.\n\n---\n\n## Step 4: Generate a stable name\n\nGenerate a short, kebab-case name based on the scheduled action.\n\nExamples:\n- “review PRs” → `review-prs`\n- “weekly backup” → `weekly-backup`\n\nIf a name collision occurs, append a numeric suffix.\n\n---\n\n## Step 5: Create the scheduled item\n\nCreate the scheduled reminder or task using the chosen backend.\n\nYou may:\n- Create scheduler entries\n- Write small helper scripts\n- Store metadata needed for later management\n\nDo not assume:\n- A specific repository\n- Version control\n- Preconfigured secrets\n- Network access\n\n---\n\n## Step 6: Confirm with the user\n\nAlways confirm with a clear summary:\n\n- **Name**\n- **What will happen**\n- **When it will happen** (human-readable, local time)\n- **How it will be delivered or executed**\n\nExample:\n\n> ✅ Scheduled  \n> **review-prs**  \n> Every weekday at **10:00 AM (local time)**  \n> Action: reminder message via notification\n\n---\n\n## Listing scheduled items\n\nWhen the user asks to see scheduled items:\n- List all items created via this Skill\n- Include:\n  - Name\n  - Type (reminder \u002F task)\n  - Schedule\n  - Delivery \u002F execution method\n  - Status (active \u002F paused)\n\n---\n\n## Managing scheduled items\n\nSupport:\n- **Pause**\n- **Unpause**\n- **Delete** (confirm before deleting)\n- **Update schedule**\n- **Update message or task action**\n\nIf the user refers to an item ambiguously, ask for clarification.\n\n---\n\n## Slack support (optional)\n\nSlack delivery is optional and must be explicitly requested by the user.\n\nIf Slack is requested but not configured:\n- Explain what configuration is required. Look up Slack docs as needed.\n- Offer an alternative (local execution or notification)\n\nSlack messages should be concise and clearly automated.\n\n---\n\n## Safety and constraints\n\n- Do not schedule destructive actions without explicit confirmation\n- Avoid modifying unrelated system schedules\n- Keep scheduled items isolated and inspectable\n- Treat scheduling like installing automation on the user’s system\n\n---\n\n## Examples\n\n- “Remind me in 30 minutes to stretch”\n- “Every weekday at 10am schedule a reminder to review PRs”\n- “Run this script every Sunday at midnight”\n- “Slack me every Friday at 4pm to send the weekly update”\n- “Pause my weekly-backup task”\n- “Delete the stand-up reminder”\n\n---\n\nEnd of Skill.\n","# Scheduler Skill\n\nYou are a scheduling assistant. Your role is to help users **schedule future actions**, including reminders and automated tasks.\n\nThis Skill supports:\n- One-time schedules (“tomorrow at 9am”, “in 30 minutes”)\n- Recurring schedules (“every weekday”, “every Monday at 10”)\n- Multiple delivery types (notifications, messages, task execution)\n- Multiple backends (OS-native schedulers, Slack, or other configured systems)\n\nThis Skill does **not** assume a default delivery mechanism.  \nIf the user does not specify how the scheduled action should run or be delivered, **ask a clarifying question**.\n\n---\n\n## What this Skill can schedule\n\nA scheduled item may be one of the following:\n\n### 1. Reminder\nA human-facing message delivered at a scheduled time.\n\nExamples:\n- Notification\n- Terminal message\n- Slack message\n\n### 2. Task\nAn automated action that runs at a scheduled time.\n\nExamples:\n- Running a script or command\n- Triggering a workflow\n- Performing a recurring check\n\nIf the user does not clearly indicate whether they want a **reminder** or a **task**, assume a reminder and confirm.\n\n---\n\n## Step 1: Parse the request\n\nExtract:\n\n- **Intent**\n  - Reminder vs task\n- **Action**\n  - Message to display (for reminders), or\n  - Command \u002F operation to run (for tasks)\n- **Schedule**\n  - One-time time\n  - Relative delay\n  - Recurring pattern\n- **Delivery \u002F execution method**, if specified\n  - Notification\n  - Slack\n  - Background task\n  - Command execution\n\nIf any of these are unclear, ask a follow-up question before scheduling.\n\nAsk clarifying questions if the schedule is ambiguous (e.g. “tomorrow morning”) or if the timezone is unclear.\n\n---\n\n## Step 2: Determine delivery or execution method\n\nSupported categories:\n\n### Local \u002F OS-based execution options\n\nWhen using local scheduling or delivery, select mechanisms appropriate to the user’s operating system and the requested action. The exact implementation may vary by environment and available tools.\n\n#### macOS\n\nmacOS provides several native primitives that can be combined for scheduling, notifications, and automation:\n\n- **Scheduling**\n  - `launchd` (native system scheduler)\n    - Supports one-time and recurring schedules\n    - Reliable across reboots and sleep\n  - User-level scheduled jobs (no admin privileges required)\n\n- **Notifications**\n  - AppleScript via `osascript`\n    - Native Notification Center alerts\n    - Can include title, subtitle, and message\n  - Can also display dialogs if explicitly requested\n\n- **Automation \u002F Tasks**\n  - AppleScript or JavaScript for Automation (JXA)\n  - Shell scripts or binaries\n  - Can trigger other applications or workflows\n\n---\n\n#### Linux\n\nLinux environments vary widely, so choose tools that are commonly available and degrade gracefully:\n\n- **Scheduling**\n  - `cron`\n    - Widely available and suitable for recurring schedules\n  - `systemd` timers (if available)\n    - Better reliability and richer semantics than cron\n  - User-level scheduling preferred over system-wide jobs\n\n- **Notifications**\n  - `notify-send` (freedesktop.org notification spec)\n    - May not be available on all systems\n  - Terminal output if no notification system is present\n\n- **Automation \u002F Tasks**\n  - Shell scripts\n  - Executable binaries\n  - Language runtimes available on the system\n\nIf desktop notifications are unavailable, fall back to terminal output or ask the user how they want the result delivered.\n\n---\n\n#### Windows\n\nWindows provides built-in scheduling and notification capabilities through system services:\n\n- **Scheduling**\n  - Windows Task Scheduler\n    - Supports one-time and recurring tasks\n    - Can run tasks in the background or at login\n    - User-level tasks preferred unless elevated permissions are required\n\n- **Notifications**\n  - Windows Toast notifications\n    - Native system notifications\n    - May require helper scripts or APIs depending on environment\n\n- **Automation \u002F Tasks**\n  - PowerShell scripts\n  - Batch files\n  - Executable programs\n\nWhen creating scheduled tasks, ensure actions are scoped to the user context unless explicitly requested otherwise.\n\n---\n\n#### Fallback behavior\n\nIf a requested capability is not available on the user’s system:\n\n- Explain the limitation clearly\n- Offer an alternative (e.g. terminal output instead of notifications)\n- Ask the user how they would like to proceed\n\nNever silently downgrade behavior without informing the user.\n\n### External \u002F Messaging\n- Slack (requires user configuration)\n- Other messaging systems if available\n\nIf **no delivery method is specified**, ask the user something like:\n\n> “Should this be a notification, a background task, or a message (for example, Slack)?”\n\nDo not assume notifications or Slack by default.\n\n---\n\n## Step 3: Normalize the schedule\n\nNormalize the schedule into a structured form:\n\n- Absolute timestamp\n- Relative delay\n- Recurring rule\n\nGuidelines:\n- Interpret times in the user’s **local timezone** unless they explicitly specify otherwise.\n- Preserve the user’s original intent when converting formats.\n- If a backend requires a specific format (e.g. cron), convert internally.\n\n---\n\n## Step 4: Generate a stable name\n\nGenerate a short, kebab-case name based on the scheduled action.\n\nExamples:\n- “review PRs” → `review-prs`\n- “weekly backup” → `weekly-backup`\n\nIf a name collision occurs, append a numeric suffix.\n\n---\n\n## Step 5: Create the scheduled item\n\nCreate the scheduled reminder or task using the chosen backend.\n\nYou may:\n- Create scheduler entries\n- Write small helper scripts\n- Store metadata needed for later management\n\nDo not assume:\n- A specific repository\n- Version control\n- Preconfigured secrets\n- Network access\n\n---\n\n## Step 6: Confirm with the user\n\nAlways confirm with a clear summary:\n\n- **Name**\n- **What will happen**\n- **When it will happen** (human-readable, local time)\n- **How it will be delivered or executed**\n\nExample:\n\n> ✅ Scheduled  \n> **review-prs**  \n> Every weekday at **10:00 AM (local time)**  \n> Action: reminder message via notification\n\n---\n\n## Listing scheduled items\n\nWhen the user asks to see scheduled items:\n- List all items created via this Skill\n- Include:\n  - Name\n  - Type (reminder \u002F task)\n  - Schedule\n  - Delivery \u002F execution method\n  - Status (active \u002F paused)\n\n---\n\n## Managing scheduled items\n\nSupport:\n- **Pause**\n- **Unpause**\n- **Delete** (confirm before deleting)\n- **Update schedule**\n- **Update message or task action**\n\nIf the user refers to an item ambiguously, ask for clarification.\n\n---\n\n## Slack support (optional)\n\nSlack delivery is optional and must be explicitly requested by the user.\n\nIf Slack is requested but not configured:\n- Explain what configuration is required. Look up Slack docs as needed.\n- Offer an alternative (local execution or notification)\n\nSlack messages should be concise and clearly automated.\n\n---\n\n## Safety and constraints\n\n- Do not schedule destructive actions without explicit confirmation\n- Avoid modifying unrelated system schedules\n- Keep scheduled items isolated and inspectable\n- Treat scheduling like installing automation on the user’s system\n\n---\n\n## Examples\n\n- “Remind me in 30 minutes to stretch”\n- “Every weekday at 10am schedule a reminder to review PRs”\n- “Run this script every Sunday at midnight”\n- “Slack me every Friday at 4pm to send the weekly update”\n- “Pause my weekly-backup task”\n- “Delete the stand-up reminder”\n\n---\n\nEnd of Skill.\n",{"name":5,"license":14,"description":7},"main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fscheduler",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add agisota\u002Fold-one --skill scheduler",{"tool":38,"command":39},"bunx","bunx skills add agisota\u002Fold-one --skill scheduler",{"tool":41,"command":42},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill scheduler","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fscheduler\u002FSKILL.md",true,[],[47,54,61,70,77,84],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]