Run any Skill in Manus with one click

skill-improver

Stars338

Forks59

UpdatedMay 9, 2026 at 17:33

Improve skills and workflows by analyzing run artifacts and execution logs (events.jsonl/state.json) under runs/ (or OpenSpec changes/). Use when you want to iterate on skills based on real runs: find failure modes, bottlenecks, unclear prompts, missing I/O contracts, and propose concrete edits.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Heyvhuang

Heyvhuang/ship-faster

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Computer Occupations, All OtherComputer and Mathematical Occupations·SOC 15-1299

SKILL.md

readonly

More from this repository

same repository

review-clean-code

Heyvhuang/ship-faster

Analyze code quality based on "Clean Code" principles. Identify naming, function size, duplication, over-engineering, and magic number issues with severity ratings and refactoring suggestions. Use when the user requests code quality checks, refactoring advice, Clean Code analysis, code smell detection, or mentions terms like code review, code quality, refactoring check.

2026-05-09338

review-doc-consistency

Heyvhuang/ship-faster

Documentation consistency reviewer that checks alignment between code implementation and documentation. Use when user requests reviewing documentation vs code consistency, checking if README/docs are outdated, verifying API documentation accuracy. Applicable for (1) reviewing README vs implementation consistency (2) checking if docs/ directory content is outdated (3) verifying API/config documentation accuracy (4) generating documentation consistency reports. Trigger words include doc review, documentation consistency, check outdated docs, verify docs.

2026-05-09338

review-merge-readiness

Heyvhuang/ship-faster

Request/execute structured code review: use after completing important tasks, at end of each execution batch, or before merge. Based on git diff range, compare against plan and requirements, output issue list by Critical/Important/Minor severity, and provide clear verdict on merge readiness. Trigger words: request code review, PR review, merge readiness, production readiness.

2026-05-09338

workflow-execute-plans

Heyvhuang/ship-faster

Execute written implementation plans: first read and critically review the plan, then implement in small batches (default 3 tasks), produce verification evidence per batch and pause for feedback; must stop immediately and ask for help when blocked/tests fail/plan unclear. Trigger words: execute plan, implement plan, batch execution, follow the plan.

2026-05-09338

workflow-template-extractor

Heyvhuang/ship-faster

Extract a shareable runnable template under templates/NNN-slug/ from a real project: copy + de-brand + remove secrets + add env examples + docs, with minimal refactors. Use when you have a working project and want to turn it into a template.

2026-05-09338

workflow-template-seeder

Heyvhuang/ship-faster

Seed a new runnable template under templates/NNN-slug/ from a short spec by chaining existing skills (intake → ship-faster stages) while keeping it clean and shareable (no secrets, minimal scope). Use when creating a new template quickly.

2026-05-09338

name	skill-improver
description	Improve skills and workflows by analyzing run artifacts and execution logs (events.jsonl/state.json) under runs/ (or OpenSpec changes/). Use when you want to iterate on skills based on real runs: find failure modes, bottlenecks, unclear prompts, missing I/O contracts, and propose concrete edits.

Skill Improver

Retrospect and improve Skills/Workflows based on real execution artifacts, making the skill chain more stable with use.

Input (pass path only)

run_dir: runs/<workflow>/active/<run_id>/ (or openspec/changes/<change-id>/)

Output

improvements.md: Improvement suggestions (can be directly converted to change tasks)
Optional: Minimal patch to relevant SKILL.md (only change what's necessary)

Process

Read logs/state.json and logs/events.jsonl, extract:
- Failure points (error types, frequency, missing context)
- Time bottlenecks (repetitive steps, ineffective searches, excessive context)
- Manual confirmation points (whether too early/too late/missing)
Check artifact contracts:
- Whether each step has persisted output
- Whether only paths are passed instead of content
- Whether there are inconsistent naming/paths
Output improvement suggestions (sorted by benefit):
- Prompt/trigger word optimization
- I/O contract completion (add required fields, fix artifact file names)
- Error handling and rejection strategies
- Suggest new deterministic scripts (only when necessary)

Output Template (recommended)

Overview: Core issues from this run
Top Issues (high → low): Each includes "symptom/root cause/fix suggestion/related skill/suggested change point"
Suggested Minimal Change List: Listed by file