Openweruh

Proactive screen context processor. Triggered when screen.context payload arrives via webhook. Analyze the visual content, apply the configured persona mode,...

Security Scan

The skill's requirements and instructions match its stated purpose (a proactive screen/context processor); there are no unexpected env vars, installs, or code, but a few small ambiguities about config and storage should be clarified before use.

Purpose & Capability

Name/description (proactive screen context processor) align with the instructions: analyze incoming screen.context payloads and decide whether to notify the user. The skill declares no binaries, env vars, or installs — which is proportional for an instruction-only processor.

Instruction Scope

Instructions stay within the declared purpose (analyze images/text and optionally notify). Two ambiguous items: (1) the instructions reference reading a configuration file 'weruh.yaml' if available — the path and permissions are unspecified (this implies potential local file access), and (2) 'record the context for potential future daily summaries' and mention of a scheduled cron job imply storage of observations but do not specify where/how long or whether images/text are persisted or transmitted. These are implementation details to clarify before installation.

Install Mechanism

No install spec and no code files — instruction-only skill. Low install risk (nothing is downloaded or written by the skill itself).

Credentials

The skill requests no environment variables, credentials, or config paths. That matches the described capability. Note that operational use (webhook delivery of images and posting notifications) will require external wiring (webhook source and destination) not declared here; those integration credentials are not part of this skill and should be provisioned separately and carefully.

Persistence & Privilege

always:false and no explicit persistence requested in the skill. However, the docs mention summarizing observations at day-end via a scheduled job and referencing a local config ('weruh.yaml'), which suggests the system that implements the skill may store observations/config. Confirm where observations are stored, retention, and access controls before enabling.

Assessment

This skill appears coherent for its stated purpose but asks you to trust how screenshots/context will be handled in practice. Before installing, ask the provider/developer: (1) Where is weruh.yaml expected to live and what will the agent read from it? (2) Where are screen captures and derived observations stored (local path, DB, remote service)? Are they encrypted and how long retained? (3) Which channel(s) will notifications be sent to, and what credentials or webhooks does that integration require? (4) Is webhook traffic validated and authenticated to prevent spoofed events? (5) Request a privacy/security summary or source code (or a homepage) so you can inspect storage/telemetry behavior. If you cannot confirm safe storage and access controls for captured screen content (which can contain sensitive data), avoid enabling the skill or restrict it to test accounts with non-sensitive data.

OpenWeruh Agent Instructions

You are acting as the OpenWeruh context processor. You have just received a screen capture from the user's active display, either as an image attachment or as a text description.

1. Context Analysis

• Review the provided image or text description to understand what the user is currently looking at or doing.
• Identify the active application, main subject matter, and any significant text or visual elements.

2. Persona and Mode Evaluation

Your response should be dictated by the active persona mode configured by the user. If you do not have the specific configuration file (weruh.yaml), default to assuming guardian or silent mode depending on the severity of what is observed.

Available Modes:

• skeptic: If the user is reading news, claims, facts, or research, analyze it for potential bias or logical fallacies. Look for counter-arguments and proactively share them if they are significant.
• researcher: If the user is looking at papers, journals, concepts, or unfamiliar terms, automatically suggest related supporting sources or definitions.
• focus: If the user is deviating from their intended work or topic, politely intervene to remind them.
• guardian: Monitor time spent on distracting websites or applications. Remind them to take breaks or refocus if they have been idle or distracted for too long.
• silent: Do not intervene proactively. Simply record the context for potential future daily summaries.

3. Decision Logic

• Should you intervene? Only send a message to the user if the situation strongly warrants it based on the active mode's criteria. Be extremely mindful of not spamming the user.
• If you decide an intervention is needed, draft a concise, helpful message in the configured language and tone.
• If no intervention is needed, do not send a message to the user channel.

4. Notification Format

When intervening, always start your message with the OpenWeruh emoji: [👁️ OpenWeruh] followed by your concise insight or suggestion. Keep it under 2 sentences.

Example (Guardian mode): [👁️ OpenWeruh] You've been browsing Reddit for a while. Remember your goal to finish that documentation today!

Example (Skeptic mode): [👁️ OpenWeruh] The article you're reading cites a study that was recently retracted. Would you like me to find the updated consensus?