refine-skills

Convert recurring skill.feedback.md patterns into permanent SKILL.md instructions.

Updated Nov 26, 2025
One-click install
npx skills add https://github.com/Aias/dotfiles --skill refine-skills-aias
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refine-skills
Source: https://github.com/Aias/dotfiles/tree/main/agents/skills/refine-skills
Command: npx skills add https://github.com/Aias/dotfiles --skill refine-skills-aias

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Distill accumulated skill.feedback.md entries into permanent skill instructions, turning raw session corrections into crafted rules and keeping feedback as a staging area rather than a permanent store.

Core Features & Use Cases

  • Survey feedback files and identify recurring patterns across multiple skills.
  • Read and analyze each skill's SKILL.md to map patterns to concrete instructions.
  • Propose, review, and promote stable instructions into SKILL.md; leave one-offs in feedback for future review.
  • After promotions, run make compile to refresh builds and make link to deploy changes.

Quick Start

Distill feedback into permanent SKILL.md rules by running the refine-skills workflow.

Frequently Asked Questions about refine-skills

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

FAQPage Schema
How do I convert feedback entries into permanent skill rules?

To convert feedback entries into permanent skill rules, you identify recurring patterns in skill.feedback.md files and promote them into SKILL.md instructions, leaving one-off entries in the feedback file for future review.

What is the best way to manage skill version control and documentation updates?

Managing skill version control involves promoting stable feedback patterns into SKILL.md, running make compile to refresh GLOBAL.md, and executing make link to deploy the documentation changes.

How do I identify recurring patterns across multiple skill feedback files?

To identify recurring patterns, survey skill.feedback.md entries across multiple skills and analyze them to find consistent corrections that can be mapped to concrete instructions in SKILL.md.

What happens to one-off feedback entries when promoting skill instructions?

One-off feedback entries remain in the skill.feedback.md file for future review, ensuring only consistent, stable patterns are promoted to permanent SKILL.md instructions.

Can I use this workflow to automate documentation updates for all skills with feedback?

Yes, this workflow applies to all skills that have accumulated feedback, surveying their feedback files and proposing promotions to ensure consistent patterns are captured in documentation.

Why should I run make compile and make link after promoting feedback to SKILL.md?

Running make compile refreshes GLOBAL.md builds and make link deploys changes, ensuring the newly promoted skill instructions are fully integrated and active across the environment.