← Back to Skills Marketplace
112
Downloads
0
Stars
1
Active Installs
4
Versions
Install in OpenClaw
/install flow-state-monitoring
Description
Workflow-driven skill that infers deep focus and autonomously mutes interruptions.
README (SKILL.md)
\r
Lean Philosophy (Principles)\r
- Kaizen (改善): This skill is an atomic node, broken down into its simplest, smallest component to eliminate waste and ensure perfection.\r
- Standardized Work (Hyojun Sagyo): This node represents the most efficient, standardized path for this specific task before automation.\r
- Jidoka (自働化): This node includes autonomous defect detection. It will stop immediately and report if it cannot achieve the expected outcome.\r \r
Flow State Monitoring\r
\r This skill orchestrates a workflow to analyze focus telemetry and autonomously update your status in Google Workspace to protect your flow state.\r \r
Cognitive Directives\r
WHEN [telemetry from local sensors indicates deep focus] \r THEN [\r Execute the following Jidoka-validated loop:\r
- Execute
llm_classify_intent(Sub-Agent) to classify the activity.\r- Verification Step (Jidoka): Verify the sub-agent returns a valid classification (e.g., "Deep Work"). IF it hallucinates text, retry classification.\r
- IF classified as "Deep Work", Execute the native terminal command
gog calendar create primary --summary "Busy - In Flow"to block interruptions.\r- Verification Step (Jidoka): Check if the calendar event creation returns a successful JSON response. IF it fails, wait 3 seconds and retry (max 3 times). IF it still fails, report the error and STOP.\r ]\r \r
Expected Output\r
A JSON confirmation of the calendar status update.\r
Usage Guidance
Before installing, verify what 'gog' is and where it comes from (official Google tool, third-party, etc.). Ask the skill author to: (1) declare required credentials or config paths (where 'gog' reads OAuth tokens), (2) describe exactly which local sensors or files will be read for telemetry, and (3) add an explicit user confirmation step before creating calendar events or provide an opt-in/opt-out. If you decide to test it, run it with a disposable/low-privilege Google account and inspect the 'gog' configuration files (and any token caches) so you know what will be used. If you cannot get these clarifications, treat the skill as risky because it can autonomously modify your calendar and may access local telemetry without clear limits.
Capability Analysis
Type: OpenClaw Skill
Name: flow-state-monitoring
Version: 1.0.3
The skill defines a workflow for automating Google Calendar status updates based on focus telemetry using the 'gog' CLI tool. The instructions in SKILL.md are well-structured, including error-handling logic (Jidoka) and clear intent classification, with no evidence of malicious behavior, data exfiltration, or unauthorized system access.
Capability Assessment
Purpose & Capability
The skill claims to update Google Workspace calendar status and the SKILL.md runs a calendar-creation command via the 'gog' binary, which is coherent. However, the skill does not declare any required credentials or config paths for Google access (OAuth tokens/config), relying on an assumption that the 'gog' CLI is pre-authenticated. The source/homepage are unknown, which increases uncertainty about that binary's behavior.
Instruction Scope
Instructions refer to "telemetry from local sensors" but do not define what sensors, what data sources, or what commands to run to obtain telemetry; that gives the agent wide latitude to access local system data. It also directs an LLM sub-agent (llm_classify_intent) and the native command `gog calendar create ...` to modify the user's calendar; the destination for error reporting is unspecified. The lack of concrete telemetry access constraints is scope creep and a privacy risk.
Install Mechanism
This is instruction-only (no install spec, no code files), so nothing new is written to disk by the skill itself. It does require the 'gog' binary to be present on PATH; the skill doesn't provide or vet that binary or its origin.
Credentials
The skill lists no required environment variables or config paths but performs calendar writes. That implies it expects an existing authenticated CLI configuration (OAuth tokens or similar) to be present, which is not declared. Because the skill can modify calendar state, it should explicitly declare required credentials/config locations and justify them; the omission is disproportionate to the transparency a user needs.
Persistence & Privilege
always is false (good). The skill allows autonomous model invocation (default), which means the agent could autonomously create calendar events based on telemetry. Autonomous invocation combined with unclear telemetry sources and undeclared credential use increases the potential impact, though autonomous invocation alone is expected behavior.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install flow-state-monitoring - After installation, invoke the skill by name or use
/flow-state-monitoring - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.3
- Improved workflow to include Jidoka-validated loop for greater reliability.
- Added verification steps: sub-agent output and calendar event creation are now checked for validity.
- Implemented retry logic for failed classifications and event creation (up to 3 attempts).
- Enhanced error handling: failures are reported and process stops if retries are exhausted.
v1.0.2
flow-state-monitoring 1.0.2
- Added "gog" to the required binaries list.
- Updated directive to use the native terminal command: gog calendar create primary --summary "Busy - In Flow".
- Clarified cognitive workflow for calendar status updates.
v1.0.1
- Expanded OS support from "windows" to "all".
- No other changes to functionality or workflow.
v1.0.0
- Initial release of the flow-state-monitoring skill.
- Monitors local focus telemetry to detect deep work states.
- Automatically updates Google Workspace calendar status to "Busy - In Flow," muting potential interruptions.
- Follows Lean principles: atomic design, standardized workflow, and built-in defect detection with automated error reporting.
Metadata
Frequently Asked Questions
What is Flow State Monitoring?
Workflow-driven skill that infers deep focus and autonomously mutes interruptions. It is an AI Agent Skill for Claude Code / OpenClaw, with 112 downloads so far.
How do I install Flow State Monitoring?
Run "/install flow-state-monitoring" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Flow State Monitoring free?
Yes, Flow State Monitoring is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Flow State Monitoring support?
Flow State Monitoring is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Flow State Monitoring?
It is built and maintained by zvirb (@zvirb); the current version is v1.0.3.
More Skills