Automation Suggestion

Suggest automations only when they make sense, based on objective triggers.

Security Scan

The skill's requests and instructions are coherent with its stated purpose (suggesting automations based on simple triggers) and it does not ask for extra credentials, installs, or unrelated system access.

Purpose & Capability

Name/description match the instructions: the skill inspects recent task history, applies simple repetition/time/sentiment triggers, and proposes automation. It does not require unrelated credentials, binaries, or system access.

Instruction Scope

Instructions are limited to reading task history from memory, running simple keyword-based sentiment checks on user messages, and tracking suggestion outcomes in memory. This is appropriate for the stated purpose, but the SKILL.md is vague about how long 'memory' persists and whether stored suggestion data is tied to a single user/session.

Install Mechanism

Instruction-only skill with no install steps, no downloads, and no code files — minimal risk from installation.

Credentials

Skill declares no environment variables, credentials, or config paths. The data it needs (task history and user messages) is expected and proportionate to the feature.

Persistence & Privilege

Skill does not request always:true and is user-invocable. It requests in-memory tracking of suggestions/outcomes; the policy around persistence, retention period, and multi-user isolation is unspecified and should be clarified to avoid unintended data retention or cross-user leakage.

Assessment

This skill appears to do what it says and asks for no extra permissions. Before installing, confirm how 'memory' is implemented: is suggestion/outcome data stored only for the current user/session, how long is it retained, and where is it stored? If you care about privacy, ensure there is an opt-out or a way to clear stored suggestion history, and verify that sentiment checks are local keyword matches (not sent to external services). Also review cooldown and suppression rules to ensure they match your preferences.

Automation Suggestion Skill

Purpose

Suggest automations only when they make sense, based on objective triggers. Avoid nagging; only propose when clear value exists.

Triggers (any one qualifies)

1. Repetition: Same task executed manually >= 2 times within 7 days
2. Time saving: Estimated weekly manual effort >= 10 minutes
3. User frustration: Detected via negative sentiment or explicit statement ("znowu to muszę robić", "to jest męczące")

Suggestion Format

After a task completes (when trigger detected):

[Automation idea]
I noticed you've done X 3 times this week (~15 min total).
Would you like me to automate it? I can set up a scheduled run or a quick command.
Reply: "yes" to configure, "no" to dismiss.

Rules

• Never suggest before first manual completion
• Max 1 suggestion per user per day
• If user says "no", suppress similar suggestions for 30 days
• Track suggestions and outcomes in memory for learning

Configuration (optional)

• minRepetitions: 2
• minWeeklyMinutes: 10
• cooldownDaysAfterNo: 30

Integration

• Hook: after task completion (via interaction-pipeline)
• Reads task history from memory
• Uses sentiment analysis on user messages (simple keyword-based)

Related Skills

• interaction-pipeline (post-action hook)
• satisfaction-learning (capture user response)