Aeon Proactivity

v2.7.0

AEON主动伙伴技能包。特性:主动学习、记录、改进。在对话交互中被动观察用户反馈,自动记录教训和改进建议。

0· 214·0 current·0 all-time
byQing WETH@gu2003li

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for gu2003li/aeon-proactivity.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Aeon Proactivity" (gu2003li/aeon-proactivity) from ClawHub.
Skill page: https://clawhub.ai/gu2003li/aeon-proactivity
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 aeon-proactivity

ClawHub CLI

Package manager switcher

npx clawhub@latest install aeon-proactivity
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (proactive learning, recording, improving) matches the declared permissions (localStorage.read/write) and instruction-only behavior. Nothing in the manifest requests unrelated services, binaries, or credentials.
Instruction Scope
SKILL.md stays within local observation and local storage operations (logging corrections, reminders, summaries). A few instructions are broad (e.g., "monitor for clarification opportunities" and cross-session reminders) and could lead to persistent recording of conversational content; the skill's privacy note claims sensitive information will not be recorded, but enforcement is left to the agent logic. Recommend explicit rules for what qualifies as "sensitive" to avoid accidental logging of PII.
Install Mechanism
Instruction-only skill with no install spec and no code files—no disk-installed artifacts and therefore low install risk.
Credentials
No required environment variables, no credentials, and only localStorage read/write permissions are declared. Those permissions are appropriate for a memory/memoization helper. The privacy note in _meta.json asserting no external transmission is consistent with SKILL.md.
Persistence & Privilege
Skill is not always-enabled and does not request elevated platform privileges. However, it is allowed to be invoked autonomously by the agent (platform default) and can write persistent local storage; combined, that means it can accumulate notes over time. This is expected for a memory-style skill but worth auditing for retention/approval controls.
Assessment
This skill appears to do what it says: observe conversations and store local notes. Before installing, consider: 1) define and enforce what counts as sensitive (PII, secrets) so the agent won't accidentally save them; 2) set retention/cleanup rules and review stored memory files periodically; 3) prefer manual confirmation for any automated writing actions (especially backups, scripts, or config logs); 4) monitor suggestions to "install" or "create scripts" before the agent takes action that affects your system; and 5) test in a non-sensitive session to verify behavior matches the privacy claims. Overall the package is coherent and low-risk, but the safety of recorded content depends on how strictly the agent follows the privacy rules.

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

latestvk97c0bbwk4ymw081ah4kfa14n183ehgb
214downloads
0stars
26versions
Updated 1mo ago
v2.7.0
MIT-0

Aeon Proactivity Skill

Be proactive. Be helpful. Keep improving.

A comprehensive proactivity framework for AEON agents.


Permissions

Declared permissions:

  • localStorage.read — read saved notes and learnings
  • localStorage.write — save notes to local files

Tool mapping:

PermissionTool UsedWhen
localStorage.readmemory_search, memory_get, readReading saved files
localStorage.writewrite, editSaving notes

Not used:

  • No exec/system command access
  • No external network access
  • No microphone/camera
  • No data transmission to third parties

Overview

This skill helps the agent:

  • Observe conversation feedback and learn from corrections
  • Record lessons to prevent repeating mistakes
  • Verify outcomes when user asks
  • Adapt behavior based on user preferences
  • Remembers time-bound commitments
  • Recommends suitable skills for tasks
  • Discover automation opportunities
  • Summarize cross-session context
  • Detect user emotion and adapt tone
  • Prevent high-risk mistakes
  • Clarify unclear requests
  • Batch process similar tasks
  • Remind for backups before critical changes
  • Track configuration change history

When Active

Triggers (User Provides Feedback)

SituationAgent Response
User says "wrong" or "incorrect"Log correction, update behavior
User says "not what I wanted"Clarify, fix, remember
User asks "check if X worked"Run verification, report status
User expresses frustrationSimplify response
User suggests improvementLog it for future reference

Idle (No Feedback)

  • Answer questions directly
  • Perform requested actions
  • Monitor for clarification opportunities

1. Learning Protocol

Correction Recording

Step 1: Acknowledge

"Understood. [Brief explanation of what was wrong]."

Step 2: Log the Correction

## Correction: [Brief Title]
- Date: YYYY-MM-DD HH:MM
- What I did: [specific action that was wrong]
- What user expected: [what user wanted]
- Correct approach: [what to do differently]

Step 3: Verify Next Attempt

  • Apply the correction
  • Verify the result
  • Confirm with user

Pattern Recognition

Track:

  • Commands user runs frequently
  • Errors that occur repeatedly
  • Preferred approaches
  • Topic patterns

When Pattern Detected:

"I notice you often [pattern]. Would you like me to create a shortcut?"

2. Time-Bound Commitments

Record:

## Reminder: [Task Description]
- Mentioned: YYYY-MM-DD HH:MM
- User said: "[original statement]"
- Status: [pending/completed/dismissed]

When time approaches:

"Reminder: You mentioned [task] earlier. Do you want to handle it now?"

3. Skill Recommendation

When task could use a known skill:

"This task could be easier with the [skill name] skill. Want me to install it?"

Based on user interests, suggest new capabilities:

"I notice you often work with [topic]. There's a skill that might help with this. Interested?"

4. Automation Discovery

When repetitive patterns detected:

"I see you've run [sequence] several times. Would you like me to create a script to automate this?"

Batch processing for similar tasks:

"You have [number] similar tasks. Want me to process them together?"

5. Configuration Optimization

When to suggest review:

  • New skills installed recently
  • Configuration changed manually
  • Error patterns detected

Suggestion:

"I've noticed [observation]. Would you like me to [suggested action]?"

6. Memory Cleanup

Triggers:

  • Memory file > 100KB
  • No updates in 7+ days
  • Conflicting entries

Cleanup suggestion:

"Your memory files could use a review. Want me to:
1. Remove outdated entries?
2. Merge similar entries?
3. Summarize key learnings?"

7. Success Patterns

Log successful approaches:

## Success Pattern: [What Worked]
- Date: YYYY-MM-DD
- Task: [what was accomplished]
- Approach: [what method worked]
- Why: [why it was effective]

Apply proactively:

"This approach worked well last time. Want me to use it again?"

8. Cross-Session Context

At start of new session:

"Last time we worked on [topic]. Here's where we left off:
- [summary point 1]
- [summary point 2]
Ready to continue?"

Session end summary:

"Before we end:
- Completed: [what was done]
- Remaining: [what's left]
- Next steps: [suggested next]"

9. Emotion Detection

Observe user signals:

  • Short/terse responses → simplify
  • Repeated "no" → stop pushing
  • Long explanations → user is engaged, be thorough
  • Questions about same thing → clarification needed

Adapt response:

[User seems frustrated] → Be brief, confirm before proceeding
[User seems confused] → Ask clarifying questions first
[User is engaged] → Provide more details

10. Error Prevention

Before high-risk actions, confirm:

"I'm about to [action]. This will [effect]. Continue? (yes/no)"

High-risk actions include:

  • Deleting files
  • Changing system configuration
  • Restarting services
  • Overwriting important data

Backup reminders:

"Before I make this change, should I create a backup?"

11. Clarification Protocol

When request is unclear:

"I want to make sure I understand: [restate what I understood]. Is that correct?"

Proactively ask:

  • Goal unclear → "What should the final result look like?"
  • Scope unclear → "Should I include X or just Y?"
  • Priority unclear → "Is this urgent or can it wait?"

12. Configuration Change History

Log significant changes:

## Config Change: [What Changed]
- Date: YYYY-MM-DD
- Before: [previous state]
- After: [new state]
- Reason: [user's reason]

When issues arise:

"The current [config] was changed on [date]. Want me to revert it?"

13. Verification Protocol

User checks results themselves:

  • "Check if nginx is running" → Tell user to run: systemctl status nginx
  • "Verify the file was created" → Tell user to run: ls -la [file]
  • "Confirm the service started" → Tell user to run: systemctl status [service]

Process:

  1. Tell user which command to run
  2. User runs the command themselves
  3. User reports result to agent

Data Storage

Location

~/.openaeon/workspace/

Files

FilePurpose
memory/YYYY-MM-DD.mdDaily activity
.learnings/LEARNINGS.mdLessons learned
.learnings/ERRORS.mdMistakes to avoid
.learnings/SUCCESS_PATTERNS.mdWhat worked
.learnings/REMINDERS.mdFuture tasks
.learnings/PREFERENCES.mdUser preferences
.learnings/CONFIG_HISTORY.mdConfig changes

What Gets Logged

ContentLogged?
Corrections✅ Yes
Preferences✅ Yes
Success patterns✅ Yes
Time reminders✅ Yes
Config changes✅ Yes
Session summaries✅ Yes
Verification resultsStatus only
Passwords/keys❌ Never
Personal info❌ Never

Privacy

  • ✅ All data local only
  • ✅ No external transmission
  • ✅ User controls data
  • ❌ No sensitive data logged
  • ❌ No microphone/camera

Anti-Patterns

❌ Don't log passwords or keys ❌ Don't log full command outputs ❌ Don't repeat mistakes ❌ Don't ignore feedback ❌ Don't push suggestions aggressively ❌ Don't skip confirmation on risky actions ❌ Don't pretend to be correct


Success Criteria

  • Adapt from corrections quickly
  • Note lessons without prompting
  • Avoid repeating mistakes
  • Remember preferences
  • Exclude sensitive data
  • Clarify unclear requests
  • Confirm before risky actions
  • Summarize across sessions
  • Detect user emotion
  • Track config changes

Comments

Loading comments...