ethan-agent-skills 0.1.0 → 0.1.1

package/README.md

@@ -25,6 +25,9 @@ npx -y ethan-agent-skills@latest update --target /tmp/test-skills
 npx -y ethan-agent-skills@latest list
 ```
 
+Current common bundled skills include `pdf-extract`, `skill-evolution`, and
+`fix-my-life`, plus the client-specific OpenSpec OPSX skills.
+
 The updater writes `.skills-lock.json` in each target skill root and only
 rewrites skills managed by this package. If a destination skill directory exists
 but is not recorded in the lock file, the updater reports a conflict and leaves
@@ -88,8 +91,14 @@ npm login
 npm publish --access public
 ```
 
+### Automated Release Workflow
+
 This repo includes `.github/workflows/publish.yml` for automated publishing
-with npm Trusted Publishing. To enable it:
+with npm Trusted Publishing. The package `ethan-agent-skills@0.1.0` has already
+been published manually, so do not create or push a `v0.1.0` tag now. That tag
+would try to publish the same version again and fail.
+
+One-time setup:
 
 1. Push this repository to GitHub.
 2. On npmjs.com, open the package settings for `ethan-agent-skills`.
@@ -98,16 +107,67 @@ with npm Trusted Publishing. To enable it:
    - Organization or user: `EthenZhang`
    - Repository: `my_agent_skill`
    - Workflow filename: `publish.yml`
-4. Push a semver tag:
+Trusted Publishing uses GitHub OIDC, so no long-lived `NPM_TOKEN` secret is
+required.
+
+Normal release flow:
 
 ```bash
+npm run test:local
+npm run pack:check
 npm version patch
 git push --follow-tags
 ```
 
-The workflow runs validation and publishes to npm when tags matching `v*.*.*`
-are pushed. It can also be started manually from the GitHub Actions tab. Trusted
-Publishing uses GitHub OIDC, so no long-lived `NPM_TOKEN` secret is required.
+`npm version patch` updates `package.json` and `package-lock.json`, creates a
+commit, and creates a tag like `v0.1.1`. Pushing the tag triggers the workflow,
+which runs validation and publishes the tagged version to npm.
+
+### Publishing Skill Updates
+
+When you change a skill, a normal `git push origin main` only updates GitHub.
+It does not publish a new npm version. To make the change available through
+`npx -y ethan-agent-skills@latest update`, publish a new package version:
+
+```bash
+# Edit skill files first, then:
+npm run test:local
+npm run pack:check
+git add .
+git commit -m "Update <skill-name> skill"
+npm version patch
+git push --follow-tags
+```
+
+Use `patch` for routine skill edits and fixes. Use `minor` when adding a new
+skill or a meaningful new CLI capability. Use `major` only for breaking changes.
+
+After the GitHub Actions publish job succeeds, users can refresh local skills:
+
+```bash
+npx -y ethan-agent-skills@latest update
+```
+
+For minor or major releases, use:
+
+```bash
+npm version minor
+# or
+npm version major
+git push --follow-tags
+```
+
+If the workflow fails:
+
+- Check the GitHub Actions run logs first.
+- If npm says the version already exists, bump to a new version and push a new
+  tag.
+- If npm says trusted publishing is not configured, confirm the npm package
+  settings still point to `EthenZhang/my_agent_skill` and `publish.yml`.
+
+The workflow can also be started manually from the GitHub Actions tab, but tag
+pushes are the preferred release path because they tie npm versions to Git
+history.
 
 ## OpenSpec OPSX Usage
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ethan-agent-skills",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Agent skills published from my_agent_skill",
   "type": "module",
   "bin": {

package/skills/fix-my-life/SKILL.md

@@ -0,0 +1,57 @@
+---
+name: fix-my-life
+description: Interactive life-fixing session. Use when user says "fix my life", "life review", "I'm stuck", "help me change", or "/fix-my-life".
+---
+
+# Fix My Life
+
+An interactive 3-phase session. Concise. Direct. No fluff.
+
+**Inspired by**: Dan Koe's "How to Fix Your Entire Life in 1 Day"
+
+---
+
+## Core Insight
+
+> You don't have bad habits. You have an identity that requires them.
+> Change the identity → behavior follows automatically.
+
+---
+
+## Flow
+
+```
+Phase 1: EXCAVATE   → Understand current state & hidden desires
+Phase 2: DESIGN     → Build the life game (vision + anti-vision)
+Phase 3: COMMIT     → Output the game plan
+```
+
+Each phase: ask → listen → reflect → move forward.
+
+---
+
+## Rules
+
+- Ask **one question at a time**
+- Wait for the answer before proceeding
+- Reflect back key insights in **1-2 sentences**
+- Use **lists** over paragraphs
+- Be direct. Comfort is the enemy here.
+- If answer is vague → ask one follow-up to sharpen it
+- Better utilize the USER.md file
+- Always use the user's language.
+
+---
+
+## Entry Point
+
+When invoked, say exactly:
+
+```
+**Fix My Life** — 3-phase session.
+
+Quick question first:
+What made you do this today? (1-3 words)
+```
+
+Then load and follow `phase-1-excavation.md`.

package/skills/fix-my-life/phase-1-excavation.md

@@ -0,0 +1,98 @@
+# Phase 1: Excavate
+
+**Goal**: Surface what's actually broken and what's actually wanted.
+
+**Time**: ~10 min of honest answers.
+
+---
+
+## Opening
+
+After getting the entry answer, say:
+
+```
+Good. Let's dig.
+
+I'll ask 5 questions. Short answers are fine.
+Honest answers are required.
+```
+
+---
+
+## The 5 Questions
+
+Ask one at a time. After each answer, reflect with 1 line before asking next.
+
+### Q1 — The Complaint Test
+```
+List your top 3 complaints about your life right now.
+(These are clues, not problems.)
+```
+
+*Why*: Complaints reveal what we value but aren't getting.
+
+---
+
+### Q2 — The Behavior Mirror
+```
+What do you spend most of your time on that you're not proud of?
+```
+
+*Why*: Behavior is honest. It shows your real identity.
+
+*If vague*: "Give me a specific example from yesterday."
+
+---
+
+### Q3 — The 5-Year Reel
+```
+If nothing changes — same habits, same identity, same choices —
+where are you in 5 years?
+
+Describe it in 3 bullets.
+```
+
+*Why*: Future-pain is the most honest motivator.
+
+---
+
+### Q4 — The Desire Beneath the Desire
+```
+What do you actually want?
+Not what you think you should want. What you actually want.
+```
+
+*If answer is surface-level* (e.g., "more money"):
+```
+Okay. What would "more money" give you that you don't have now?
+```
+
+Keep drilling until they hit something emotional.
+
+---
+
+### Q5 — The Identity Cost
+```
+If you became the person who achieves that — what would you have to give up?
+(Habits, relationships, beliefs, comfort zones)
+```
+
+*Why*: This is where resistance lives. Name it.
+
+---
+
+## Phase 1 Close
+
+After all 5 answers, summarize:
+
+```
+**What I'm hearing:**
+
+- Biggest gap: [their complaint → their desire, distilled]
+- Hidden fear: [what they'd have to give up]
+- The real problem: identity, not circumstance
+
+Ready for Phase 2?
+```
+
+Load `phase-2-design.md`.

package/skills/fix-my-life/phase-2-design.md

@@ -0,0 +1,141 @@
+# Phase 2: Design the Game
+
+**Goal**: Turn insights into a concrete game structure.
+
+**Framework**: Life is a video game. Structure it like one.
+
+---
+
+## Setup
+
+Say:
+```
+Now we build the game.
+
+Your life already has a win condition.
+You just haven't defined it clearly enough to play.
+```
+
+---
+
+## Step 1 — Anti-Vision (The Stakes)
+
+```
+Describe the life you absolutely refuse to live.
+3 years from now, worst case.
+
+Use "I am..." statements.
+```
+
+*Example output*:
+- I am still in the same job I hate
+- I am heavier, more tired, less alive
+- I am someone my past self would be disappointed by
+
+**After they answer**, reflect:
+```
+Good. That's your "Game Over" screen.
+Keep it visible. It's fuel.
+```
+
+---
+
+## Step 2 — Vision MVP (The Win Condition)
+
+```
+Now the opposite.
+
+3 years from now, if things go right:
+- What does your work look like? (1 line)
+- What does your body/health look like? (1 line)
+- What do your relationships look like? (1 line)
+- How do you feel when you wake up? (1 word)
+```
+
+*Keep it concrete. Not "be happy." "Wake up excited about my work."*
+
+**After they answer**, distill to:
+```
+**Your Win Condition**: [1-sentence synthesis]
+```
+
+---
+
+## Step 3 — Build the Quest Log
+
+### Main Quest (1 Year)
+```
+To move toward that 3-year vision —
+what's the ONE thing you could accomplish this year
+that would make everything else easier?
+```
+
+*Must be specific and measurable.*
+
+---
+
+### Boss Fight (This Month)
+```
+What project, if completed this month,
+would be the biggest step toward that 1-year goal?
+```
+
+---
+
+### Daily Quests (This Week)
+```
+Name 3 daily actions that move the needle.
+
+Format: [action] → [outcome it creates]
+```
+
+*Example*:
+- Write 500 words → builds the book
+- No phone before 9am → protects deep work
+- 30 min walk → clears head, resets energy
+
+---
+
+### Rules (Personal Constraints)
+```
+What are 2-3 rules you need to protect your progress?
+
+Format: "I don't [behavior]" or "I always [behavior]"
+```
+
+*Example*:
+- I don't check messages before 10am
+- I always ship something before consuming content
+
+---
+
+## Phase 2 Close
+
+Compile their full game:
+
+```
+**YOUR LIFE GAME**
+
+🏆 Win Condition: [their 3-year vision]
+💀 Game Over: [their anti-vision]
+
+🗺️ Main Quest (1 year): [their 1-year goal]
+⚔️ Boss Fight (this month): [their monthly project]
+
+📋 Daily Quests:
+- [action 1]
+- [action 2]
+- [action 3]
+
+📜 Rules:
+- [rule 1]
+- [rule 2]
+```
+
+Then say:
+```
+One phase left. The hardest one.
+Ready?
+```
+
+Load `phase-3-commit.md`.

package/skills/fix-my-life/phase-3-commit.md

@@ -0,0 +1,124 @@
+# Phase 3: Commit
+
+**Goal**: Convert the game plan into a saved document + one immediate action.
+
+---
+
+## The Commitment Problem
+
+Most people fail here. Not because of bad plans.
+Because they never commit to the identity behind the plan.
+
+Say:
+```
+The game is designed. Now the real question:
+
+Who do you need to become to win this game?
+
+Name that person in 3 words or less.
+(Example: "focused creator", "disciplined builder", "present father")
+```
+
+---
+
+## Identity Lock
+
+After they answer, say:
+```
+From now on, every decision runs through one filter:
+
+"What would [their 3 words] do here?"
+
+That's it. That's the whole system.
+```
+
+---
+
+## The One Action
+
+```
+What's ONE thing you can do in the next 24 hours
+that signals — to yourself — that you're now playing this game?
+
+Not a big thing. A real thing.
+```
+
+*Must be specific. "Start journaling" is not specific. "Write 3 sentences tonight" is.*
+
+---
+
+## Save the Game
+
+Say:
+```
+I'll save this as your Game Plan.
+Want me to save it to your workspace?
+```
+
+If yes → write to `workspace/outputs/life-game-{YYYY-MM-DD}.md` with this template:
+
+```markdown
+# Life Game — {date}
+
+## Identity
+**I am**: {their 3 words}
+
+## Stakes
+**Win**: {3-year vision}
+**Game Over**: {anti-vision}
+
+## Quest Log
+
+| Quest | Description |
+|-------|-------------|
+| Main Quest (1 year) | {1-year goal} |
+| Boss Fight (this month) | {monthly project} |
+| Daily Quest 1 | {action} → {outcome} |
+| Daily Quest 2 | {action} → {outcome} |
+| Daily Quest 3 | {action} → {outcome} |
+
+## Rules
+{rules as bullet list}
+
+## Next Action (24h)
+- [ ] {their one action}
+
+---
+*Generated by fix-my-life skill*
+```
+
+---
+
+## Closing
+
+After saving (or if they decline), say:
+
+```
+**Session complete.**
+
+What you did today:
+- Named what's broken (most people never do this)
+- Designed a system, not just a goal
+- Committed to an identity
+
+The gap between who you are and who you want to be
+is just a series of daily quests.
+
+Start yours today.
+```
+
+---
+
+## Optional: Weekly Check-in
+
+If they want accountability, say:
+```
+One more thing — set a reminder for 7 days from now.
+
+Ask yourself:
+- Did I run my daily quests?
+- Did I make progress on the boss fight?
+- Did I act like [their identity]?
+
+That's the whole review. Keep it short. Keep playing.
+```

package/skills/fix-my-life/skill.json

@@ -0,0 +1,5 @@
+{
+  "name": "fix-my-life",
+  "version": "0.1.0",
+  "description": "Interactive life-fixing session for life reviews, stuck states, personal change, and /fix-my-life."
+}

package/skills/skill-evolution/.env.example

@@ -0,0 +1,11 @@
+# Skill Evolution — Optional Configuration
+#
+# Everything works out of the box with zero config.
+# This file is ONLY needed if you want to use a private registry.
+
+# --- Private registry (advanced) ---
+# Override to use your own Supabase instance instead of the public registry.
+#
+# SUPABASE_URL=
+# SUPABASE_ANON_KEY=
+# SUPABASE_SERVICE_KEY=

package/skills/skill-evolution/CONTRIBUTING.md

@@ -0,0 +1,53 @@
+# Contributing to Skill Evolution
+
+## Publishing a Skill
+
+The easiest way to contribute is to publish a skill you've built:
+
+1. Create a skill following the structure in `references/structure.md`
+2. Test it in your own project
+3. Run `publish.py --skill-name <name>` to preview (default behavior, no upload)
+4. Fix any sanitize warnings (secrets, hardcoded paths)
+5. Publish with `publish.py --skill-name <name> --yes`
+
+Your skill will be immediately searchable by any agent using the registry.
+
+## Improving an Existing Skill
+
+When you fork and improve someone else's skill:
+
+1. Install the skill: `install.py --name <name>`
+2. Modify it locally for your use case
+3. Publish as your variant: `publish.py --skill-name <name> --variant <your-name> --yes`
+
+The system automatically tracks lineage via `parent_id`.
+
+## Skill Quality Guidelines
+
+Good skills share these traits:
+
+- **SKILL.md ≤ 300 lines** — routing layer only, details in references/
+- **Clear triggers** — description says exactly when the skill should activate
+- **Scripts work standalone** — `--help` works, exits with proper codes
+- **No hardcoded secrets** — use `requires_env` to declare needed variables
+- **Tested in production** — at least one real use before publishing
+
+## Code Contributions
+
+For changes to the scripts themselves (publish.py, search.py, install.py, uninstall.py, merge.py, review.py, audit.py):
+
+1. Fork this repo
+2. Make your changes
+3. Test: run `--help` on all modified scripts to verify they load
+4. Submit a PR with what you changed and why
+
+## Bug Reports
+
+Open an issue with:
+- What you tried to do
+- What happened instead
+- The error message (scripts prefix errors with `ERROR:`)
+
+## Registry Setup
+
+Want to run your own registry? See `setup.sql` — it's one file, takes 5 minutes on Supabase free tier.

package/skills/skill-evolution/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 DutyAI
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.