opencode-scheduler
Advanced tools
+1
-1
| { | ||
| "name": "opencode-scheduler", | ||
| "version": "1.0.2", | ||
| "version": "1.0.3", | ||
| "description": "OpenCode plugin for scheduling recurring jobs using launchd (Mac) or systemd (Linux)", | ||
@@ -5,0 +5,0 @@ "main": "dist/index.js", |
+16
-5
@@ -45,3 +45,3 @@ # opencode-scheduler | ||
| | Get version | `Show scheduler version` | | ||
| | Get skill template | `Get the scheduled job best practices skill` | | ||
| | Install skill template | `Install the scheduled job best practices skill` | | ||
| | Get job | `Show details for standing-desk` | | ||
@@ -97,2 +97,3 @@ | Update job | `Update standing-desk to run at 10am` | | ||
| | `get_skill` | Get built-in skill templates (best practices) | | ||
| | `install_skill` | Install a built-in skill into your repo | | ||
| | `get_job` | Fetch job details and metadata | | ||
@@ -102,3 +103,3 @@ | `update_job` | Update an existing job | | ||
| | `run_job` | Execute a job immediately (fire-and-forget) | | ||
| | `job_logs` | View logs from a job | | ||
| | `job_logs` | View the latest logs from a job | | ||
@@ -137,4 +138,2 @@ Tools accept an optional `format: "json"` argument to return structured output with `success`, `output`, `shouldContinue`, and `data`. | ||
| - This plugin is intentionally a thin wrapper: it schedules `opencode run` via launchd (Mac) or systemd (Linux). | ||
| - We avoid prompt “injection” as a feature. If a job needs dynamic values (dates, paths, etc.), the prompt should compute them at runtime using tools. | ||
| - Prefer non-interactive dependencies for scheduled runs (e.g., Telegram Bot API over `web.telegram.org`). | ||
| - Logs are the source of truth for scheduled runs: `~/.config/opencode/logs/*.log`. | ||
@@ -145,4 +144,16 @@ - Resiliency/reporting roadmap (not implemented): `PRD-resilient-execution.md`. | ||
| Use `get_skill` to fetch `scheduled-job-best-practices`, copy it into your repo, then add `@scheduled-job-best-practices` at the top of scheduled job prompts. | ||
| To install the built-in skill into your project (no copy/paste), open OpenCode in your repo and run: | ||
| ``` | ||
| Install the scheduled job best practices skill | ||
| ``` | ||
| This calls the plugin’s `install_skill` tool and writes `.opencode/skill/scheduled-job-best-practices/SKILL.md`. | ||
| (If you prefer, you can also say: `Get skill from opencode-scheduler and add it to my skills`.) | ||
| Then add `@scheduled-job-best-practices` at the top of scheduled job prompts. | ||
| (Manual option: use `get_skill` to fetch `scheduled-job-best-practices` and copy it into `.opencode/skill/scheduled-job-best-practices/SKILL.md`.) | ||
| ## Troubleshooting | ||
@@ -149,0 +160,0 @@ |
Sorry, the diff of this file is too big to display
Shell access
Supply chain riskThis module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.
Found 1 instance in 1 package
Environment variable access
Supply chain riskPackage accesses environment variables, which may be a sign of credential stuffing or data theft.
Found 2 instances in 1 package
Filesystem access
Supply chain riskAccesses the file system, and could potentially read sensitive data.
Found 1 instance in 1 package
Long strings
Supply chain riskContains long string literals, which may be a sign of obfuscated or packed code.
Found 1 instance in 1 package
Shell access
Supply chain riskThis module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.
Found 1 instance in 1 package
Environment variable access
Supply chain riskPackage accesses environment variables, which may be a sign of credential stuffing or data theft.
Found 2 instances in 1 package
Filesystem access
Supply chain riskAccesses the file system, and could potentially read sensitive data.
Found 1 instance in 1 package
Long strings
Supply chain riskContains long string literals, which may be a sign of obfuscated or packed code.
Found 1 instance in 1 package
493529
0.85%13453
0.61%173
6.79%30
-6.25%