skill-review

Original：🇺🇸 English

Translated

Skills retrospective and improvement. Use when: - User asks to "review", "retrospect", "summarize" or "复盘" skills - User wants to analyze skills issues from the conversation - User requests skills optimization or improvement - End of conversation or after significant skill usage

6installs

Sourceoldwinter/skills

Added on2026-02-28

NPX Install

npx skill4agent add oldwinter/skills skill-review

SKILL.md Content

View Translation Comparison →

Skills Retrospective

Review and improve skills based on conversation experience.

When to Trigger

This skill activates when user asks for:

"复盘 skills" / "review skills" / "总结 skills"
"Skills 有什么问题" / "What issues with skills"
"Improve skills" / "优化 skills"
"Skills 需要改进的地方"

Retrospective Workflow

Step 1: Identify Skills Used

List all skills loaded in this conversation:

```
tasknotes-skill
```
- TaskNotes CLI integration
```
skill-creator
```
- Base skill creation guidance

Step 2: Analyze Issues

For each skill, identify:

Command failures - What commands failed and why
Missing content - What should have been documented but wasn't
Incorrect guidance - What advice was wrong or misleading
Edge cases - What scenarios weren't covered
User confusion - Where user got confused

Step 3: Prioritize Improvements

Priority	Issue Type	Action
Critical	Wrong/misleading info	Fix immediately
High	Missing critical info	Add to SKILL.md
Medium	Edge case not covered	Add to troubleshooting
Low	Clarity improvement	Refine wording

Step 4: Document Findings

Create a summary in this format:

markdown

## Skills Review - [Date]

### [Skill Name]
**Issues Found:**
1. [Issue description] - [Root cause]
2. ...

**Improvements Made:**
1. [Change] - [Location]
2. ...

**Still Missing:**
1. [What's still needed]

Common Issues to Watch For

Command Option Mismatches

Check
```
tn --help
```
for actual options
```
create
```
doesn't support
```
--priority
```
,
```
--tags
```
, etc.
```
update --add-projects
```
may silently fail

Path Handling

Chinese punctuation in paths (。) requires exact matching
```
.md
```
extension may or may not be required
Use
```
tn list --json
```
to get exact IDs

Natural Language Parsing

```
∑
```
symbol causes parsing issues → use
```
_
```
instead
Project names with
```
-
```
may be misinterpreted
Test with simple cases first

Actionable Improvements

Immediate Actions

Update SKILL.md with workaround for
```
update --add-projects
```
Document project naming convention (underscore vs sum symbol)
Add exact ID extraction patterns

Documentation Updates

Add "Gotchas" section for known issues
Include command output examples
Document batch operation risks

Output Format

When presenting improvements: