← Back to Skills Marketplace
110
Downloads
0
Stars
1
Active Installs
5
Versions
Install in OpenClaw
/install calendar-guard
Description
Standard Operating Procedure (SOP) that autonomously defends your schedule using TS atomic plugins.
README (SKILL.md)
Lean Philosophy (Principles)
- Kaizen (改善): This workflow relies entirely on discrete, single-responsibility TS tools rather than a monolithic loop.
- Standardized Work (Hyojun Sagyo): This node represents a strict, step-by-step Standard Operating Procedure (SOP) for scheduling recovery blocks.
- Jidoka (自働化): Includes autonomous self-healing loops with hard verification stops between every step.
Calendar Guard SOP
This procedure evaluates schedule density and automatically injects recovery blocks into your Google Calendar when needed to prevent burnout.
Cognitive Directives
WHEN [Requested to check calendar for burnout risks OR running on a daily schedule] THEN [ Follow this strict Standard Operating Procedure:
Step 1: Event Retrieval
- Execute
gog calendar events primary --from "..." --to "..." --jsonfor the target timeframe. - Jidoka Stop: Verify JSON output. IF fails, retry 3 times. IF still fails, STOP.
Step 2: High Load Detection
- Execute the
workflow_detect_high_load_periodsatomic TS tool with the retrieved events. - Jidoka Stop: Verify the tool returns structured load periods. IF it returns an error, correct input and retry.
Step 3: Recovery Injection
- For each detected high-load period, execute
Google Calendar Create Eventto inject a "Recovery Block". - Jidoka Stop: Verify creation. IF it fails, log the failure and continue to the next. ]
Expected Output
A JSON log of any recovery blocks injected.
Usage Guidance
Before installing or enabling this skill, ask the publisher to clarify exactly how it authenticates to Google Calendar: which executable provides the write operation (gog or a plugin), where credentials/tokens live (env vars or config paths), and which OAuth scopes are required. Verify the provenance of the 'gog' binary and the 'autonomous-workflows-plugin' (source, integrity, and least-privilege scopes). If you proceed, use a dedicated/calendar account or restricted service account with only the minimal calendar scopes (create/read limited range), enable audit logging, and test on a non-production calendar to ensure it doesn't spam or expose sensitive events. If the skill will run autonomously, require explicit user confirmation or rate limits for event creation and insist the SKILL.md be updated to list required credentials/config paths and the exact commands used to create events.
Capability Analysis
Type: OpenClaw Skill
Name: calendar-guard
Version: 1.0.4
The skill bundle defines a 'Calendar Guard' Standard Operating Procedure (SOP) for managing schedule density and injecting recovery blocks into Google Calendar. It utilizes the 'gog' CLI tool and an autonomous workflow plugin to retrieve events, detect high-load periods, and create new calendar entries. The logic is transparent, follows its stated purpose, and contains no indicators of malicious behavior, data exfiltration, or unauthorized access in SKILL.md or _meta.json.
Capability Assessment
Purpose & Capability
The skill's purpose (detect busy periods and create 'Recovery Block' events in Google Calendar) is plausible given the required 'gog' binary, but the skill does not declare any credentials, OAuth scopes, or config paths needed to access Google Calendar. That omission is inconsistent with the stated capability: creating calendar events normally requires authenticated access.
Instruction Scope
SKILL.md instructs the agent to run 'gog calendar events ...' and to run an atomic TS tool 'workflow_detect_high_load_periods', then 'execute `Google Calendar Create Event`' — these steps stay within the calendar domain but are vague about the concrete command/CLI/plugin used to create events and about where auth comes from. The instructions do not reference other files or env vars, but their ambiguity grants broad implementation discretion (which could hide unwanted behavior).
Install Mechanism
This is instruction-only (no install spec and no code files), so nothing is written to disk by the skill itself. That minimizes install-time risk.
Credentials
No environment variables, credentials, or config paths are declared, yet the skill intends to read and create Google Calendar events. The required 'gog' binary likely needs stored credentials or access tokens; the skill should explicitly declare how credentials are supplied (env vars or config paths) and what OAuth scopes are required. Lack of declared credentials is disproportionate to the write operations described.
Persistence & Privilege
The skill does not request 'always: true' and is user-invocable only; it does not declare modifications to other skills or system-wide settings. Autonomous invocation is allowed (platform default) but not combined with other privilege red flags here.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install calendar-guard - After installation, invoke the skill by name or use
/calendar-guard - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.4
- Updated description to emphasize use of SOP and TS atomic plugins.
- Introduced dependency on the autonomous-workflows-plugin.
- Replaced monolithic loop with step-by-step SOP, detailing discrete steps for event retrieval, high load detection, and recovery block injection.
- Added explicit Jidoka verification stops and retry logic at each step.
- Clarified that the workflow uses atomic TS tools for each individual process phase.
v1.0.3
- Enhanced workflow with step-by-step Jidoka (autonomous validation) checks to improve reliability.
- Added verification and retry logic for each core action: event retrieval, conflict detection, and recovery block creation.
- Improved error handling: failures now trigger retries or are logged per block rather than stopping the entire process.
- Updated Cognitive Directives section for greater clarity and robustness.
v1.0.2
calendar-guard 1.0.2 Changelog
- Added `gog` as a required binary in the skill requirements.
- Updated workflow steps to use native terminal `gog` calendar commands for retrieving events and creating recovery blocks.
- Clarified usage of commands and parameters in the cognitive directives section.
v1.0.1
- Expanded OS support from Windows-only to all operating systems in the skill metadata.
- No changes to logic or workflow.
v1.0.0
Initial release of calendar-guard skill:
- Evaluates Google Calendar for signs of schedule overload or burnout risk.
- Automatically inserts "Recovery Block" events when high cognitive load is detected.
- Follows Lean principles: kaizen, standardized work, and autonomous defect detection.
- Outputs a JSON log detailing any recovery blocks added.
Metadata
Frequently Asked Questions
What is Calendar Guard?
Standard Operating Procedure (SOP) that autonomously defends your schedule using TS atomic plugins. It is an AI Agent Skill for Claude Code / OpenClaw, with 110 downloads so far.
How do I install Calendar Guard?
Run "/install calendar-guard" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Calendar Guard free?
Yes, Calendar Guard is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Calendar Guard support?
Calendar Guard is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Calendar Guard?
It is built and maintained by zvirb (@zvirb); the current version is v1.0.4.
More Skills