skill_rsi

Records skill improvement proposals in an inbox and applies them only after user review.

5|1|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/WissingChen/my_code_config --skill skill-rsi-wissingchen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill_rsi
Source: https://github.com/WissingChen/my_code_config/tree/main/my_skills/skill_rsi
Command: npx skills add https://github.com/WissingChen/my_code_config --skill skill-rsi-wissingchen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When using a family of skills, friction points, user corrections, and inconsistencies surface during real work but usually vanish with the conversation. This Skill captures those observations as structured improvement proposals so the skill set evolves through use, while guaranteeing that no skill file is ever edited silently. ## Core Features & Use Cases - Improvement Inbox: Appends dated, structured proposals (source, evidence, suggestion, type, impact, status) to my_skills/INBOX.md whenever friction, corrections, missing references, or cross-skill inconsistencies appear. - Review-Gated Changes: Notifies the user of pending proposals immediately and modifies skill files only after explicit approval, then runs my_skills/check_skills.sh to validate consistency. - Decision Tracking: Marks proposals as applied or rejected with reasons, keeping rejected records to prevent duplicate suggestions. - Use Case: While writing a report, a user corrects a banned jargon term for the second time. The Skill logs a proposal to add that term to the style rules, tells the user a proposal is pending, and only edits the skill file after the user approves. ## Quick Start When you notice a recurring correction or a missing scenario while using any skill, ask the assistant to record it as an improvement proposal in the skill inbox for later review.

Frequently Asked Questions about skill_rsi

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track improvement ideas for a set of AI skills?▼

Append each idea as a dated block to a central INBOX.md file with fields for source, evidence, suggestion, type, impact, and status. Review pending proposals periodically and mark them applied or rejected so nothing is lost between sessions.

When should a skill improvement proposal be recorded?▼

Record one when a user correction is likely to recur, a rule is bypassed or proves ceremonial, a scenario or reference is missing, cross-skill inconsistencies appear, or the same manual fix happens more than twice.

Can the skill modify other skill files automatically?▼

No. It only proposes changes and notifies the user of pending proposals. Editing any skill file requires explicit user approval for that specific proposal, and silent or opportunistic edits are explicitly forbidden.

What happens to rejected improvement proposals?▼

Rejected proposals are marked with the rejection reason and kept in the inbox rather than deleted. This prevents the same suggestion from being raised again in future sessions.

What are the limitations of an inbox-based improvement workflow?▼

It does not track research project artifacts or decisions, which belong to the research management skills. It also cannot reorder delegation semantics between skills or remove rules; it only proposes changes for human review.