skill-upgrader

parcadei/continuous-claude-v3 · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/parcadei/continuous-claude-v3 --skill skill-upgrader
0 commentsdiscussion
summary

Meta-skill that upgrades any SKILL.md to Decision Theory v5 Hybrid format using 4 parallel Ragie-backed agents.

skill.md

Skill Upgrader

Meta-skill that upgrades any SKILL.md to Decision Theory v5 Hybrid format using 4 parallel Ragie-backed agents.

When to Use

  • "Upgrade this skill to v5"
  • "Formalize this skill with decision theory"
  • "Add MDP structure to this skill"
  • "Apply the skill-upgrader to X"

Prerequisites

Ragie RAG with indexed books:

  • decision-theory partition: LaValle Planning Algorithms, Sutton & Barto RL
  • modal-logic partition: Blackburn Modal Logic, Huth & Ryan Logic in CS

Workflow

Step 1: Setup Session

SESSION=$(date +%Y%m%d-%H%M%S)-upgrade-{skill_name}
mkdir -p thoughts/skill-builds/${SESSION}

Step 2: Initialize Blackboard

Create thoughts/skill-builds/{session}/00-blackboard.md:

# Skill Upgrade: {skill_name}
Started: {timestamp}

## Input Skill
{path_to_skill}

## Target Format
Decision Theory v5 Hybrid

## Agent Findings
(Agents append below)

---

Step 3: Launch 4 Agents in Parallel

Use Task tool to spawn all 4 agents simultaneously. Each agent:

  1. Reads the input skill
  2. Queries Ragie for their specific book
  3. Appends findings to the blackboard

Agent 1: LaValle Planner

Book: LaValle's "Planning Algorithms" (decision-theory partition) Focus: States, Actions, Transitions

Task(
  subagent_type="general-purpose",
  prompt="""
INPUT SKILL: {path}
BLACKBOARD: thoughts/skill-builds/{session}/00-blackboard.md

YOUR BOOK: LaValle's "Planning Algorithms" in Ragie partition 'decision-theory'

TASK: Identify MDP structure in the skill.

Query Ragie:
```bash
uv run python scripts/ragie_query.py -q "MDP state space definition" -p decision-theory
uv run python scripts/ragie_query.py -q "action space sequential decisions" -p decision-theory
uv run python scripts/ragie_query.py -q "POMDP partial observability" -p decision-theory

Read the input skill and answer:

  1. What are the STATES? (phases, modes, tracked info)
  2. What are the ACTIONS? (what can agent do in each state)
  3. How do TRANSITIONS work? (deterministic or stochastic)
  4. Is this POMDP or fully observable?

WRITE to blackboard section: ## Agent 1: States, Actions & Transitions

Format as plain English with LaValle chapter citations. """ )


---

## Agent 2: Sutton & Barto Optimizer

**Book:** Sutton & Barto's "Reinforcement Learning" (decision-theory partition)
**Focus:** Policy, Termination, Value
**Depends on:** Agent 1

Task( subagent_type="general-purpose", prompt=""" INPUT SKILL: {path} BLACKBOARD: thoughts/skill-builds/{session}/00-blackboard.md

YOUR BOOK: Sutton & Barto's "Reinforcement Learning" in Ragie partition 'decision-theory'

WAIT: Read Agent 1's findings from blackboard first.

TASK: Design policy and termination conditions.

Query Ragie:

uv run python scripts/ragie_query.py -q "policy deterministic stochastic" -p decision-theory
uv run python scripts/ragie_query.py -q "episodic termination conditions" -p decision-theory
uv run python scripts/ragie_query.py -q "reward function design" -p decision-theory

Using Agent 1's states and actions, answer:

  1. What's the POLICY? (state → action rules)
  2. When does it END? (terminal states, success/failure)
  3. What are REWARDS? (goals +, costs -)
  4. Which states are HIGH/LOW value?

WRITE to blackboard section: ## Agent 2: Policy & Values

Format as plain English with Sutton & Barto section citations. """ )


---

## Agent 3: Blackburn Modal Logician

**Book:** Blackburn's "Modal Logic" (modal-logic partition)
**Focus:** Constraints (temporal, epistemic, deontic)

Task( subagent_type="general-purpose", prompt=""" INPUT SKILL: {path} BLACKBOARD: thoughts/skill-builds/{session}/00-blackboard.md

YOUR BOOK: Blackburn's "Modal Logic" in Ragie partition 'modal-logic'

TASK: Extract constraints from the skill.

Query Ragie:

uv run python scripts/ragie_query.py -q "temporal logic LTL operators" -p modal-logic
uv run python scripts/ragie_query.py -q "epistemic logic knowledge" -p modal-logic
uv run python scripts/ragie_query.py -q "deontic logic obligations" -p modal-logic

Read the input skill and identify:

  1. TEMPORAL: "must do X before Y" → □, ◇, U
  2. EPISTEMIC: "must know X" → K operator
  3. DEONTIC: "must/forbidden/may" → O, F, P
  4. DYNAMIC: "action causes effect" → [action]

WRITE to blackboard section: ## Agent 3: Constraints

For each constraint:

  • Plain English description
  • Modal logic notation
  • Why it matters
  • Blackburn chapter citation """ )

---

## Agent 4: Huth & Ryan Verifier

**Book:** Huth & Ryan's "Logic in Computer Science" (modal-logic partition)
**Focus:** Validation, Safety, Liveness
**Depends on:** Agents 1-3

Task( subagent_type="general-purpose", prompt=""" INPUT SKILL: {path} BLACKBOARD: thoughts/skill-builds/{session}/00-blackboard.md

YOUR BOOK: Huth & Ryan's "Logic in Computer Science" in Ragie partition 'modal-logic'

WAIT: Read Agents 1-3 findings from blackboard first.

TASK: Verify consistency and completeness.

Query Ragie:

uv run python scripts/ragie_query.py -q "safety properties verification" -p modal-logic
uv run python scripts/ragie_query.py -q "liveness properties eventually" -p modal-logic
uv run python scripts/ragie_query.py -q "model checking CTL" -p modal-logic

Check:

  1. SAFETY: What bad things never happen? □¬(bad)
  2. LIVENESS: What good things eventually happen? ◇(good)
  3. CONSISTENCY: Any contradictions between agents?
  4. COMPLETENESS: Any gaps in coverage?

WRITE to blackboard section: ## Agent 4: Verification

Report with ✓/✗ for each property. Overall verdict: PASS or NEEDS_WORK Huth & Ryan section citations. """ )


---

## Step 4: Synthesize Final Skill

After all agents complete, read the blackboard and create:

**Output:** `thoughts/skill-builds/{session}/SKILL-upgraded.md`

Use v5 Hybrid template:

```yaml
---
name: {original_name}
description: {original_description}
version: 5.1-hybrid
---

# Option: {name}

## Initiation (I)
[From original + Agent 1 state analysis]

## Observation Space (Y)
[From Agent 1 POMDP analysis]

## Action Space (U)
[From Agent 1 actions]

## Policy (pi)
[From Agent 2 state→action rules]

## Termination (beta)
[From Agent 2 episode structure]

## Q-Heuristics
[From Agent 2 value guidance]

## Constraints
[From Agent 3 modal logic]

## Verification
[From Agent 4 safety/liveness]

Example Usage

User: "Upgrade .claude/skills/implement_plan/SKILL.md to v5 Hybrid"

Claude:
1. Creates session directory
2. Initializes blackboard
3. Launches 4 agents in parallel (Task tool)
4. Waits for completion
5. Reads blackboard
6. Synthesizes upgraded skill
7. Reports: "Upgraded skill at thoughts/skill-builds/.../SKILL-upgraded.md"

Ragie Query Reference

# Decision theory partition
uv run python scripts/ragie_query.py -q "your question" -p decision-theory

# Modal logic partition
uv run python scripts/ragie_query.py -q "your question" -p modal-logic

# With reranking for better results
uv run python scripts/ragie_query.py -q "your question" -p decision-theory --rerank

Files Created

After upgrade:

thoughts/skill-builds/{session}/
├── 00-blackboard.md      # Agent collaboration
├── SKILL-upgraded.md     # Final v5 Hybrid skill
└── validation-report.md  # Agent 4 verification
how to use skill-upgrader

How to use skill-upgrader on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add skill-upgrader
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/parcadei/continuous-claude-v3 --skill skill-upgrader

The skills CLI fetches skill-upgrader from GitHub repository parcadei/continuous-claude-v3 and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/skill-upgrader

Reload or restart Cursor to activate skill-upgrader. Access the skill through slash commands (e.g., /skill-upgrader) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.852 reviews
  • Shikha Mishra· Dec 28, 2024

    skill-upgrader is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Isabella Rahman· Dec 28, 2024

    skill-upgrader reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Arya Liu· Dec 20, 2024

    skill-upgrader fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Aanya Gill· Dec 20, 2024

    skill-upgrader is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Evelyn Srinivasan· Dec 8, 2024

    We added skill-upgrader from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Aanya Gupta· Nov 27, 2024

    Useful defaults in skill-upgrader — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Yash Thakker· Nov 19, 2024

    Keeps context tight: skill-upgrader is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Tariq Sethi· Nov 11, 2024

    Registry listing for skill-upgrader matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Michael Harris· Nov 11, 2024

    Keeps context tight: skill-upgrader is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Aarav Brown· Nov 7, 2024

    I recommend skill-upgrader for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

showing 1-10 of 52

1 / 6