improve-skill

Collect conversation signals and draft PR-ready edits to skills/*/SKILL.md.

27|2|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/maragudk/fabrik --skill improve-skill-maragudk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: improve-skill
Source: https://github.com/maragudk/fabrik/tree/main/skills/improve-skill
Command: npx skills add https://github.com/maragudk/fabrik --skill improve-skill-maragudk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill collects signals from a conversation to identify improvements for fabrik skills and ships those improvements back to the fabrik repo as PRs (concrete fixes) or issues (design observations). It enables continuous quality enhancement of the skill catalog based on real session feedback.

Core Features & Use Cases

  • Collects corrections, friction reports, and missed triggers from the current session.
  • Generates PR-ready edits to skills/*/SKILL.md and related references, with a clear rationale and scope.
  • Supports cross-skill improvements by aggregating signals across multiple conversations and sessions.

Quick Start

Invite the improve-skill process after a chat to begin collecting signals and drafting concrete edits.

Frequently Asked Questions about improve-skill

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

FAQPage Schema
How do I collect conversation feedback to improve skill documentation?

Collect conversation feedback to improve skill documentation by applying this process after sessions to aggregate signals like corrections and missed triggers, generating structured plans for SKILL.md edits.

Can I prepare PR-ready edits to SKILL.md files from chat signals?

Yes, you can prepare PR-ready edits to SKILL.md files from chat signals by identifying concrete fixes and design changes during a session, then outputting a structured plan suitable for pull requests and issues.

What is the best way to aggregate cross-skill improvements from multiple sessions?

The best way to aggregate cross-skill improvements from multiple sessions is to collect friction reports and corrections across conversations, applying the process to prepare PR-ready edits for multiple skills.

When should I trigger a skill improvement workflow for documentation updates?

You should trigger a skill improvement workflow for documentation updates after sessions with concrete triggers like corrections, missed triggers, or explicit improvement requests to ensure quality enhancements are captured.

Does this process support generating issues for design observations?

Yes, this process supports generating issues for design observations by collecting conversation signals and shipping improvements back to the repository as concrete fixes or detailed design observation issues.