Feature/Forge-Self-Improvement-System/SKILL.md
Auto-triggers when AI detects a repeated pattern handled ad-hoc 3+ times, when AI makes a mistake that a permanent rule would prevent, when AI identifies a workflow that should be automated as a skill, or when user says 'create skill', 'new skill', 'forge this', 'level up', 'upgrade skill', 'self improve', 'improve skill'. Also triggers when AI wants to propose a level-up to an existing skill based on conversation patterns.
npx skillsauth add kiyoraka/project-ai-memorycore forge-skillInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
The AI that improves its own abilities through experience.
Forge is the meta-skill -- the skill that creates and improves other skills. When your AI detects patterns, mistakes, or opportunities for improvement during conversation, Forge activates to propose new skills or level-ups to existing ones. It uses a human-in-the-loop model: AI drafts, user approves.
When this skill activates, output:
"Forge detected an opportunity for improvement..."
Then present the proposal to the user.
| Context | Status | |---------|--------| | AI detects repeated ad-hoc pattern (3+ times) | ACTIVE -- propose new skill | | AI makes preventable mistake | ACTIVE -- propose new rule or skill | | User says "create skill", "new skill", "forge this" | ACTIVE -- manual trigger | | User says "level up [skill]", "upgrade [skill]" | ACTIVE -- level-up existing | | User says "self improve", "improve skill" | ACTIVE -- review and propose | | Casual conversation (no improvement context) | DORMANT |
Identify the improvement opportunity. Forge recognizes these patterns:
Automatic Detection (AI-initiated):
Manual Trigger (User-initiated):
Before proposing, gather evidence:
TYPE: [New Skill / Level-Up / New Rule]
TARGET: [Skill name if level-up, or proposed name if new]
TRIGGER: [What pattern/mistake/workflow was detected]
EVIDENCE: [At least 2 concrete examples from conversation or session history]
IMPACT: [What improves if this is implemented]
Present to user in this format:
Forge Detected an Opportunity
==============================
Type: [New Skill / Level-Up]
Name: [proposed-name]
Purpose: [what it would do]
Trigger: [what activates it]
Evidence:
1. [First concrete example]
2. [Second concrete example]
Impact: [what improves]
Draft ready -- approve to forge?
CRITICAL: NEVER create or modify skill files without explicit user approval.
For NEW skill:
plugins/[plugin-name]/skills/[skill-name]/SKILL.md following the standard skill format:
For LEVEL-UP:
SKILL.mdAfter forging, update relevant system files:
master-memory.md -- add new skill command or update existingForge Complete!
================
[New Skill / Level-Up]: [name] Lv.[X]
Location: skills/[name]/SKILL.md
Capability: [what was added]
Origin: [the moment that triggered this]
Your AI evolved!
When Forge creates a new skill, use this structure:
---
name: [skill-name]
description: "[When this skill should auto-trigger -- include trigger phrases
and context descriptions]"
---
# [Skill Name] -- [One-line description]
*[Thematic tagline]*
## Activation
When this skill activates, output:
"[Activation message]"
## Context Guard
| Context | Status |
|---------|--------|
| **[Trigger condition 1]** | ACTIVE -- [action] |
| **[Trigger condition 2]** | ACTIVE -- [action] |
| **[Non-trigger context]** | DORMANT |
## Protocol
### Step 1: [First action]
- [ ] [Substep]
- [ ] [Substep]
### Step 2: [Second action]
- [ ] [Substep]
## Mandatory Rules
1. [Rule 1]
2. [Rule 2]
## Level History
- **Lv.1** -- Base: [description of initial capabilities]. (Origin: [what triggered creation])
Before forging, evaluate against these criteria:
| Criteria | Question | |----------|----------| | Repeatable | Will this trigger more than once in future sessions? | | Specific | Is the trigger condition clear and unambiguous? | | Valuable | Does automating this save meaningful time or prevent real errors? | | Independent | Can this skill work without requiring other skills? | | Testable | Can the user verify it works by triggering it? |
If 4 out of 5 criteria are met, the skill is worth forging.
Skills evolve through levels as they gain capabilities:
| Level | Meaning | Typical Addition | |-------|---------|-----------------| | Lv.1 | Base skill | Core functionality, basic triggers, simple protocol | | Lv.2 | Enhanced | Additional trigger conditions, edge case handling | | Lv.3 | Proactive | Auto-detection without explicit commands | | Lv.4 | Integrated | Synergy with other skills, cross-referencing | | Lv.5+ | Mastered | Context-aware, domain-specific intelligence |
Each level should add one meaningful capability -- not multiple changes bundled together.
| Situation | Behavior | |-----------|----------| | No Skill Plugin System installed | Inform user that forged skills work best with the plugin; offer to create as standalone protocol | | Proposed skill overlaps existing | Suggest level-up to existing skill instead of creating duplicate | | User rejects proposal | Note rejection reason, do not re-propose same skill in current session | | Insufficient evidence (< 2 examples) | Wait for more evidence before proposing -- don't force it | | Skill file already exists at target | Treat as level-up, not overwrite |
| Feature | Integration | |---------|-------------| | Skill Plugin System | Forge creates skills in the plugin's skill folder structure | | Auto-Commit System | After forging, commit the new/updated skill file | | Decision Log System | Log the decision to create/level-up a skill with rationale | | Save Diary System | Document the forge event in the session diary |
development
MUST use when user says 'copy plan', 'append plan', 'resume plan', 'load plan', 'start the plan', 'continue the plan', 'execute plan', 'run the plan', 'pick up where we left off', or when the AI exits plan mode and needs to transfer the plan into execution format. This skill manages the full lifecycle of project plans — from plan output to tracked checkbox execution with per-todo commits.
data-ai
MUST use when user says 'save topic', 'save to topic diary', 'remember this under', 'review topic', 'list topics', or when a generic 'save' request needs routing between session memory, daily diary, topic diary, or all targets.
documentation
Auto-triggers when user says 'create songs', 'new album', 'create album', 'make music', 'muse this', 'write a song', 'create a song', 'compose', 'song from image', 'album from image', 'generate album', 'write songs', or when user shares an image and wants to create music from it.
tools
# 📋 Session Briefing — Skill Plugin ## Skill Name Session Briefing ## Trigger Words - Session start (automatic — fires before first response) - `"brief"` - `"session brief"` - `"what did we do last time"` - `"where did we leave off"` ## Suppress Trigger - `"skip brief"` — suppresses for this session only ## Activation Condition Fires automatically at the start of every new conversation session, before processing the user's first message. ## Behavior 1. Read `main/current-session.md` — extr