openclaw-daily-tips

Original source / Raw SKILL.md

---
name: openclaw-daily-tips
slug: openclaw-daily-tips
version: 1.0.1
description: |
  Daily AI agent optimization tips, tricks and self-improvement strategies. Learn cost-saving, speed, memory and automation best practices from the OpenClaw community.
  
  Use when: you want daily tips to optimize your AI agent, reduce costs, improve performance, or learn automation workflows.
  
  Don't use when: you need immediate config changes - use openclaw-agent-optimize for deep audits.
triggers:
  - openclaw tips
  - openclaw daily
  - openclaw tricks
  - ai agent tips
  - agent optimization
  - openclaw improve
  - ai automation tips
  - openclaw cost optimization
  - openclaw memory tips
  - cron optimization
  - daily ai agent
  - agent self improvement
metadata:
  openclaw:
    emoji: "📈"
    requires:
      bins: ["node"]
      env: []
---

# openclaw-daily-tips

Daily AI agent optimization tips and self-improvement strategies for OpenClaw users.

## What This Skill Does

- Fetches daily optimization tips from community sources
- Tracks your preferences and learns what works for you
- Provides actionable advice with impact scores
- Helps reduce costs and improve agent performance

## Quick Start

```bash
# Get today's tip
node ~/.openclaw/workspace/skills/openclaw-daily-tips/scripts/openclaw-daily-tips.mjs tips

# Search for specific topic
node ~/.openclaw/workspace/skills/openclaw-daily-tips/scripts/openclaw-daily-tips.mjs search "cost"

# Weekly report
node ~/.openclaw/workspace/skills/openclaw-daily-tips/scripts/openclaw-daily-tips.mjs weekly

# List all available tips
node ~/.openclaw/workspace/skills/openclaw-daily-tips/scripts/openclaw-daily-tips.mjs all
```

## Features

### Categories
- **Cost**: Save money on API calls, model routing
- **Speed**: Faster responses, reduced latency
- **Memory**: Context optimization, memory patterns
- **Skills**: New skill recommendations
- **Automation**: Cron, heartbeat, workflow optimization

### Impact Score
- 🟢 Low effort / High reward
- 🟡 Medium effort / Medium reward  
- 🔴 High effort / Experimental

### Self-Learning
The skill remembers your preferences:
- Saved tips are tracked
- Skipped topics won't reappear
- Adapts to your needs over time

## Cron Integration

Schedule daily tips at 9 AM:

```json
{
  "id": "openclaw-daily-tips",
  "schedule": { "kind": "cron", "expr": "0 9 * * *" }
}
```

## Output Example

```
📈 OPENCLAW-DAILY-TIPS - Your Agent Smarter Every Day

💡 TIP OF THE DAY (High Impact)
Title: Use tiered model routing

🟢 Low Effort | 📈 High Impact

What:
- Route simple tasks to cheap models
- Route complex tasks to premium models
- Save significant API costs

How:
1. Add model routing in cron jobs
2. Use cheap model for routine tasks
3. Reserve premium for complex reasoning

🔗 docs.openclaw.ai/models

━━━━━━━━━━━━━━
👍 Save this | 👎 Skip | ➕ More tips
```

## Categories Explained

| Category | What You'll Learn |
|----------|------------------|
| Cost | Model routing, token optimization, batching |
| Speed | Caching, lazy loading, parallel execution |
| Memory | Context discipline, progressive disclosure |
| Skills | Skill best practices, modular design |
| Automation | Cron optimization, alert patterns |

## Tips Database

Current tips cover:
- Tiered model selection
- Script-first cron patterns
- Alert-only delivery
- Semantic memory search
- Batch similar jobs
- Isolated sub-agents
- Context discipline
- Idempotent cron jobs
- Heartbeat optimization
- Modular skill design

## Requirements

- Node.js 18+
- OpenClaw workspace
- Optional: reddit-readonly skill for community feeds

## Related Skills

- **openclaw-agent-optimize** - Deep optimization audit
- **openclaw-token-optimizer** - Token cost optimization  
- **memory-setup** - Memory configuration
- **daily-digest** - General daily briefing
- **compound-engineering** - Agent self-improvement

## Credits

Inspired by openclaw-agent-optimize and the OpenClaw community.

---

## Install

```bash
clawhub install openclaw-daily-tips
```

Or manually copy to your skills directory.


---

## Skill Companion Files

> Additional files collected from the skill directory layout.

### README.md

```markdown
# openclaw-daily-tips

> Daily AI agent optimization tips, tricks and self-improvement strategies for OpenClaw users.

[![OpenClaw Skill](https://img.shields.io/badge/OpenClaw-Skill-blue)](https://clawhub.ai)
[![Version](https://img.shields.io/badge/version-1.0.1-green)]()
[![Node.js](https://img.shields.io/badge/Node.js-18+-yellow)]()

Daily AI agent optimization tips to make your OpenClaw smarter, faster, and cheaper.

## What You'll Get

- 📈 **Daily Tips** - One actionable optimization per day
- 💰 **Cost Savings** - Reduce API costs with model routing
- ⚡ **Speed Improvements** - Faster responses and execution
- 🧠 **Memory Optimization** - Better context management
- 🤖 **Automation** - Cron and workflow best practices

## Installation

### Via ClawHub (Recommended)

```bash
npx clawhub install openclaw-daily-tips
```

### Manual

```bash
# Clone or copy to your skills folder
cp -r openclaw-daily-tips ~/.openclaw/workspace/skills/
```

## Usage

```bash
# Get today's optimization tip
node ~/.openclaw/workspace/skills/openclaw-daily-tips/scripts/openclaw-daily-tips.mjs tips

# Search for specific topic
node ~/.openclaw/workspace/skills/openclaw-daily-tips/scripts/openclaw-daily-tips.mjs search "cost"

# Weekly report
node ~/.openclaw/workspace/skills/openclaw-daily-tips/scripts/openclaw-daily-tips.mjs weekly

# List all tips
node ~/.openclaw/workspace/skills/openclaw-daily-tips/scripts/openclaw-daily-tips.mjs all
```

## Features

### Categories
| Category | Description |
|----------|-------------|
| Cost | Save money on API calls |
| Speed | Faster execution |
| Memory | Better context management |
| Skills | Skill development tips |
| Automation | Cron and workflow optimization |

### Impact Scores
- 🟢 Low Effort / High Reward
- 🟡 Medium Effort / Medium Reward
- 🔴 High Effort / Experimental

### Self-Learning
The skill tracks your preferences and improves over time:
- Save tips you find useful
- Skip topics you don't need
- Adapts to your workflow

## Tips Database

Current tips cover essential optimizations:

1. **Tiered Model Routing** - Use cheapest capable model
2. **Script-First Cron** - Move logic to scripts
3. **Alert-Only Delivery** - Return NO_REPLY on success
4. **Semantic Memory** - Better context recall
5. **Batch Jobs** - Combine similar tasks
6. **Isolated Sub-Agents** - Reduce context bloat
7. **Context Discipline** - Keep prompts lean
8. **Idempotent Cron** - Safe to re-run
9. **Heartbeat Optimization** - Background checks
10. **Modular Skills** - Keep SKILL.md short

## Cron Schedule

Add to your cron jobs for daily tips:

```json
{
  "id": "openclaw-daily-tips",
  "schedule": { "kind": "cron", "expr": "0 9 * * *" }
}
```

## SEO Keywords

openclaw tips, openclaw daily, openclaw optimization, ai agent tips, agent optimization, openclaw cost, openclaw memory, cron optimization, ai automation, openclaw tricks, daily ai tips, openclaw improve

## Related Skills

- [openclaw-agent-optimize](https://clawhub.ai/phenomenoner/openclaw-agent-optimize) - Deep optimization audit
- [openclaw-token-optimizer](https://clawhub.ai/phenomenoner/openclaw-token-optimizer) - Token cost optimization
- [memory-setup](https://clawhub.ai/phenomenoner/memory-setup) - Memory configuration
- [compound-engineering](https://clawhub.ai/phenomenoner/compound-engineering) - Agent self-improvement

## Contributing

Tips are curated from:
- Reddit communities (r/openclaw, r/LocalLLaMA)
- GitHub issues and discussions
- OpenClaw documentation
- Community feedback

## License

MIT

---

**Star ⭐ if this helps your OpenClaw!**

```

### _meta.json

```json
{
  "owner": "adelpro",
  "slug": "openclaw-daily-tips",
  "displayName": "OpenClaw Daily Tips",
  "latest": {
    "version": "1.0.1",
    "publishedAt": 1772005706737,
    "commit": "https://github.com/openclaw/skills/commit/cca1e26a80c430d8694e2e68a906b108deb217dc"
  },
  "history": []
}

```

### references/cron-optimization.md

```markdown
# Cron Optimization (General Patterns)

Cron jobs are best when they are **deterministic, small, and testable**. The biggest recurring costs come from:
- long prompts that re-explain the world every run
- tool calls that return large payloads
- jobs that deliver messages even when nothing changed
- re-running expensive work due to non-idempotent steps

This guide is **model-agnostic**: it avoids naming specific models and focuses on repeatable patterns.

---

## 1) Principle: Cron should be "script-first"

**Goal:** the cron payload should be:
- a short instruction (or one command)
- a single script execution
- a small, bounded output

Prefer:
- `scripts/<job>.py` or `scripts/<job>.mjs`
- inputs/outputs stored in `memory/` or `state/` files

---

## 2) Keep prompts short and stable

Patterns:
- Put long documentation in `references/` files or comments in the script.
- Put configuration knobs in a JSON file (read by script), not in the prompt.
- Avoid embedding large templates unless absolutely necessary.

Rule of thumb:
- If the prompt needs > ~300 tokens of "how to run", convert it into a script.

---

## 3) Prefer "alert-only delivery"

Most scheduled jobs should not message the user every time.

Recommended pattern:
- Job always writes its output to `memory/<artifact>.md` or `memory/<artifact>.json`.
- Job returns:
  - `NO_REPLY` when nothing is new / actionable
  - a short alert message only when something changed (new signal, error, anomaly)

If you need periodic reporting, separate into two jobs:
- **collector** (frequent, deliver=false, script-first)
- **reporter** (less frequent, deliver=true, summarizes recent artifacts)

---

## 4) Throttles and budgets (anti-surprise)

Add explicit throttles to reduce waste:
- **time-based throttle**: only run heavy steps every N runs
- **change-based throttle**: compute a hash of inputs; skip if unchanged
- **result-size cap**: never output more than X lines / X chars

Budget guardrails (recommended when costs matter):
- If cost spikes (or error repeats), downgrade behavior:
  - reduce scan scope
  - reduce frequency
  - disable delivery and log locally
  - fall back to minimal mode and alert once

---

## 5) Model assignment (tiered, not named)

Model-agnostic guidance:
- Default cron jobs should use the **cheapest tier** that reliably completes the task.
- Upgrade to a higher tier only if:
  - the task repeatedly fails, or
  - accuracy materially matters (e.g., financial decisions, complex synthesis)

---

## 6) Idempotency and crash safety

Cron jobs should be safe to re-run.

Patterns:
- Keep a cursor/state file (e.g., `memory/<job>-state.json`).
- Append-only logs (JSONL) for auditability.
- a human explicitly approves.

---

##  Avoid side effects unless7) Guardrails (human control)

- Do not create/edit/remove cron definitions unless explicitly requested.
- Show the exact cron change and rollback plan before applying.
- If optimization requires reducing coverage or frequency, present options and let the user choose.

```

### references/model-selection.md

```markdown
# Model Selection (Tiered, Model-Agnostic)

## Principle
Use the **cheapest capable tier** for the job. Escalate only when:
- the task repeatedly fails at a cheaper tier, or
- correctness materially matters (risk, finance, security), or
- the task requires deep synthesis/architecture.

Avoid naming specific models in guidance. Treat "model" as a **tier**.

---

## Tiers (conceptual)
- **Tier 1 (cheap / frequent):** routine formatting, lightweight summaries, single-script cron runs.
- **Tier 2 (general):** multi-file edits, orchestration, non-trivial debugging.
- **Tier 3 (deep):** architecture, risk analysis, complex planning.

---

## Escalation policy
- Start at Tier 1 for automation.
- Escalate to Tier 2 only after *observed* failure or clear complexity.
- Escalate to Tier 3 only with justification.

If you need user approval to change a global default, ask. Otherwise prefer local overrides per job.

---

## Anti-patterns
- Using Tier 3 for simple cron/heartbeat tasks.
- Re-running the same expensive analysis every schedule tick.
- Asking the user to choose a model for routine tasks (choose the cheapest tier that works).

```