Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Intelligent Scheduler

v1.0.0

Context-aware intelligent scheduler for AI agents — time zone handling, priority queues, conflict resolution, and adaptive scheduling

0· 113·1 current·1 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for sky-lv/intelligent-scheduler.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Intelligent Scheduler" (sky-lv/intelligent-scheduler) from ClawHub.
Skill page: https://clawhub.ai/sky-lv/intelligent-scheduler
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install intelligent-scheduler

ClawHub CLI

Package manager switcher

npx clawhub@latest install intelligent-scheduler
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
!
Purpose & Capability
The SKILL.md describes a full-featured scheduler (time zones, priority queues, conflict resolution) which is coherent with the name. However, the examples call out commands like `node scheduler.js ...` and reference a local `.scheduler/config.json` even though the skill declares no required binaries, no code files, and no install spec. Also there is no mention of how calendar integration would work (no API tokens, endpoints, or sync mechanism). Requiring a local Node script and local config is inconsistent with the registry metadata.
!
Instruction Scope
The instructions tell an agent to run shell/Node commands and show a config path (.scheduler/config.json). Because the skill is instruction-only and includes no code, following those instructions would fail or prompt the agent to obtain/execute code from elsewhere. The SKILL.md does not specify where events are stored or how external calendars are accessed (no declared endpoints or credentials), which grants the agent ambiguous discretion.
!
Install Mechanism
There is no install spec and no code files. Yet the runtime examples assume an executable Node script. This is an incoherence: either the skill is incomplete documentation or it expects the agent/user to fetch and execute external code. That gap increases risk because an agent acting on these instructions might attempt to download/execute artifacts from untrusted sources.
Credentials
The skill declares no required environment variables, credentials, or config paths. This is proportionate in the sense that nothing sensitive is explicitly requested. However, practical calendar integration would typically require API tokens (not declared), so the absence of credential requests further suggests the package is incomplete or only intended for local-only scheduling.
Persistence & Privilege
The skill does not request always:true and allows normal model invocation. It does not claim to modify other skills or system-wide configuration. No elevated persistence privileges are requested.
What to consider before installing
This skill looks like documentation or a usage example rather than a runnable skill: it shows commands that call `node scheduler.js` and a `.scheduler/config.json` but provides no code or install steps. Before installing or allowing the agent to use it, ask the publisher for: (1) the source code or a trustworthy install process (GitHub release or package manager), (2) explicit instructions about calendar integrations and any credentials required, and (3) justification for any network access the skill needs. If you cannot verify the code origin, do not let the agent fetch/execute arbitrary scripts — that is the primary risk here. Providing the missing install artifacts and documented integration points would reduce the concern.

Like a lobster shell, security has layers — review code before you run it.

latestvk97ecrfv4q1244gsc8ddzhh1t585654q
113downloads
0stars
1versions
Updated 1w ago
v1.0.0
MIT-0

intelligent-scheduler

Context-aware intelligent scheduler — handle time zones, prioritize tasks, resolve conflicts, and optimize schedules for AI agents.

Skill Metadata

  • Slug: intelligent-scheduler
  • Version: 1.0.0
  • Description: Context-aware scheduling system for AI agents. Handles multi-timezone scheduling, priority-based task queues, conflict detection and resolution, and adaptive schedule optimization based on agent workload and user preferences.
  • Category: automation
  • Trigger Keywords: scheduler, task scheduling, priority queue, calendar, conflict resolution, timezone, schedule optimization

Capabilities

1. Schedule Tasks

```bash node scheduler.js add "Review PR #42" --time "14:00" --tz "Asia/Shanghai" --priority high node scheduler.js add "Deploy v2.0" --time "2024-03-15 09:00" --tz "America/New_York" --depends "Review PR #42" ```

2. Priority Queue Management

```bash node scheduler.js queue --sort priority node scheduler.js queue --filter today node scheduler.js promote "Urgent hotfix" --to critical ```

Priority levels: critical > high > medium > low > deferred

3. Conflict Detection

```bash node scheduler.js check-conflicts --date 2024-03-15

Output: CONFLICT: "Team standup" (09:00-09:30) overlaps "Client call" (09:15-10:00)

```

4. Timezone Conversion

```bash node scheduler.js convert "14:00 Asia/Shanghai" --to "America/New_York"

Output: 01:00 EDT (next day)

```

5. Smart Rescheduling

```bash node scheduler.js auto-reschedule --fill-gaps --respect-priority ``` Automatically moves tasks to fill schedule gaps while respecting priorities and dependencies.


Configuration

```json // .scheduler/config.json { "timezone": "Asia/Shanghai", "workHours": { "start": "09:00", "end": "18:00" }, "bufferMinutes": 15, "rules": [ "No meetings before 10:00 on Mondays", "Reserve Friday afternoons for deep work", "Critical tasks always scheduled first" ] } ```

Use Cases

  1. Agent Task Management: Schedule and prioritize agent tasks
  2. Meeting Coordination: Handle multi-timezone meeting scheduling
  3. Cron Job Optimization: Space out automated tasks to avoid resource contention
  4. Deadline Management: Track and prioritize tasks by deadline proximity
  5. Work-Life Balance: Enforce work hours and break scheduling

Comments

Loading comments...