Skip to content
Back to skills

Self Improvement

ASecurity

**Purpose:** The meta-skill. Makes every other skill better. Forces daily compound growth across website, products, capabilities, revenue, and autonomy. This is not a weekly nice-to-have — it's the engine that prevents Acrid from plateauing. **Trigger:** - `/improve` — full weekly consolidation (Sundays or when learnings feel scattered) - Daily: The Level-Up Tracker gets updated every session as part of `/kaizen` - On-demand: When the operator says "level up" or "improve" ---

  • 5 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added October 10, 2026
ai-agentsgogit

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned October 10, 2026

npx -y skills add acrid-auto/acrid-brain --skill self-improvement --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Self Improvement?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Self Improvement
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/acrid-auto-self-improvement/badge)](https://www.skillsdirectory.com/skills/acrid-auto-self-improvement)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
# Self-Improvement Skill — `/improve`

**Purpose:** The meta-skill. Makes every other skill better. Forces daily compound growth across website, products, capabilities, revenue, and autonomy. This is not a weekly nice-to-have — it's the engine that prevents Acrid from plateauing.

**Trigger:**
- `/improve` — full weekly consolidation (Sundays or when learnings feel scattered)
- Daily: The Level-Up Tracker gets updated every session as part of `/kaizen`
- On-demand: When the operator says "level up" or "improve"

---

## The Compound Growth Model

Acrid improves on 5 axes. Every day, at least ONE must move forward:

| Axis | What It Means | Example |
|------|--------------|---------|
| **Website** | acridautomation.com gets better | New section, better copy, faster load, new page |
| **Products** | New digital products or existing ones improve | New micro-product, better landing page, new format |
| **Capabilities** | Acrid can do something new | New skill, new automation, new tool integration |
| **Revenue** | Money experiments running | New channel, new pricing, new funnel, new distribution |
| **Autonomy** | Less human needed | New automation, self-triggering workflow, removed bottleneck |

**Rule: No day passes without at least one axis advancing.**

---

## Daily Level-Up Protocol

Every session, before `/kaizen` and `/ops`:

1. **Check the Level-Up Tracker** — read `skills/self-improvement/LEVEL-UP-TRACKER.md`
2. **Pick one axis** — what's the highest-leverage improvement today?
3. **Execute it** — ship something real, not a plan
4. **Log it** — add entry to Level-Up Tracker with what shipped and what axis it served
5. **Queue tomorrow** — identify the next improvement for each axis

---

## Weekly `/improve` Consolidation

Run every Sunday (or when triggered). This is the deep clean.

### Phase 1: Harvest Learnings
1. Read ALL `LEARNINGS.md` files across `skills/` and `products/`
2. Read `soul/MEMORY.md`
3. Read the Level-Up Tracker for the past week
4. Read the Revenue Experiments log
5. Read the Product Factory pipeline

### Phase 2: Graduate Lessons
For each learning found:
- **Pattern detected 3+ times?** → Promote to a RULE in the relevant SKILL.md
- **Durable fact about Acrid's world?** → Promote to `soul/MEMORY.md`
- **One-off observation?** → Leave in LEARNINGS.md, mark as processed
- **Contradicts existing rule?** → Update the rule, document why

### Phase 3: Skill Upgrades
For each skill:
- What's the weakest dimension in its rubric scores?
- What rule would fix it?
- Add the rule. Make it specific and testable.

### Phase 4: System Upgrades
- Any new automation possible this week?
- Any manual step that happened 3+ times that should be automated?
- Any new tool or integration worth exploring?
- Any website improvement that's been queued too long?

### Phase 5: Product & Revenue Review
- Check Product Factory pipeline — what's ready to ship?
- Check Revenue Experiments — what worked, what didn't?
- Propose 1 new experiment for next week
- Propose 1 new micro-product idea

### Phase 6: Write the Improvement Report
Output to Notion Kaizen Log as a weekly consolidation entry:
- Learnings graduated (count + list)
- Skills upgraded (which ones, what changed)
- Axes advanced this week (which ones, how)
- Revenue experiments status
- Product pipeline status
- Next week's improvement targets

### Phase 7: Update LEARNINGS.md
Add entry to `skills/self-improvement/LEARNINGS.md` with what this consolidation found.

---

## Supporting Files

| File | Purpose |
|------|---------|
| `LEVEL-UP-TRACKER.md` | Daily log of what improved and on which axis |
| `PRODUCT-FACTORY.md` | Pipeline of digital product ideas with status |
| `SITE-IMPROVEMENTS.md` | Queued website improvements with priority |
| `REVENUE-EXPERIMENTS.md` | Active and completed money experiments |
| `LEARNINGS.md` | What this skill learned about self-improvement |

---

## Digital Product Factory Rules

Acrid should be shipping micro-products regularly. Not everything needs to be a $17 flagship.

**Product tiers:**
- **Free lead magnets** ($0, email capture) — checklists, templates, one-pagers
- **Micro-products** ($1-5) — single tools, mini-guides, prompt packs
- **Core products** ($7-17) — full guides, apps, frameworks
- **Premium** ($27+) — courses, communities, comprehensive systems

**Daily product thinking:** Every day, observe what Acrid built or learned. Ask: "Could someone pay for this?" If yes, package it.

**Shipping cadence target:** 1 new product or product improvement per week.

---

## Website Improvement Rules

The website is Acrid's storefront. It should get better every week.

**Categories:**
- **Content** — new sections, better copy, new pages
- **Conversion** — better CTAs, email capture, product placement
- **Technical** — speed, SEO, mobile, accessibility
- **Brand** — visuals, consistency, polish
- **New pages** — tools, resources, blog index, product pages

**Rule:** Never let the site go 7 days without an improvement.

---

## Revenue Experiment Rules

Revenue doesn't come from hoping. It comes from running experiments.

**Experiment format:**
- Hypothesis: "If I do X, Y will happen"
- Action: What specifically to do
- Metric: How to measure success
- Timeline: When to evaluate
- Result: What actually happened

**Rule:** Always have at least 1 active revenue experiment running.

**Experiment categories:**
- Distribution (where to post/share products)
- Pricing (test different price points)
- Packaging (bundle, unbundle, reformat)
- Channels (new platforms, partnerships, affiliates)
- Products (new offerings)

---

## Failure Conditions

This skill has FAILED if:
- 3 consecutive days pass with no axis advancing
- Weekly consolidation doesn't run for 2 weeks
- Learnings accumulate but never graduate to rules
- Product Factory has 0 items in pipeline
- Revenue Experiments has 0 active experiments
- Website hasn't improved in 7+ days

---

## Pre-Execution Checklist

Before running `/improve`:
- [ ] Read ALL LEARNINGS.md files
- [ ] Read Level-Up Tracker for the period
- [ ] Read Product Factory pipeline
- [ ] Read Revenue Experiments log
- [ ] Read Site Improvements queue
- [ ] Read soul/MEMORY.md

**Never run this skill without reading the inputs. The whole point is synthesis.**

---

*The worst version of Acrid is right now. This skill is how that changes every single day.*

Files in this skill

  • LEARNINGS.md1.9 KB
  • LEVEL-UP-TRACKER.md3.4 KB
  • SITE-IMPROVEMENTS.md3.3 KB
  • SKILL.md6.3 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.