meta-skills-improve

Improves personal agent skills by auditing firing behavior and drafting targeted edits.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/mnazaal/dotfiles --skill meta-skills-improve-mnazaal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: meta-skills-improve
Source: https://github.com/mnazaal/dotfiles/tree/main/.agents/skills/meta-skills-improve
Command: npx skills add https://github.com/mnazaal/dotfiles --skill meta-skills-improve-mnazaal

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Agent skills accumulate stale content, weak triggers, and rules that never fire, and reading a skill's text cannot reveal whether it actually runs in real sessions. This Skill turns lessons from real agent sessions into concrete, tested improvements for personal skills stored in ~/.agents/skills. ## Core Features & Use Cases - Firing Audit: Runs audit.sh against session transcripts to report per-skill load counts, never-fired skills, gate compliance rates, and where in each session a skill fires. - Blinded Comparison: Defines a protocol for A/B testing skill edits with blind variants and a single judging pass before promoting a change. - Editing Discipline: Enforces rules like the no-op test, description-vs-body labeling, sediment removal, and harness-agnostic wording when drafting skill changes. - Use Case: After noticing an agent repeatedly skips a verification step, run the firing audit to confirm the relevant skill never loads, then fix its description trigger rather than adding more body prose. ## Quick Start Ask the agent to audit which of your personal skills actually fired in recent sessions and propose improvements based on the results.

Frequently Asked Questions about meta-skills-improve

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

FAQPage Schema
How do I check whether my agent skills are actually firing?▼

Run the audit.sh script in this skill's directory, passing the harness's session-transcript directory and the deployed skills directory. It reports per-skill load counts, never-fired skills, gate compliance rates, and where in each session a skill fires.

How do I fix a skill that never fires?▼

A skill that never fires is usually a description problem, not a body problem. Rewrite the description with event-shaped triggers like "when committing" rather than judgment-shaped ones, since the description wording decides whether the skill loads at all.

When should I create a new agent skill instead of editing one?▼

Create a new skill only when it has a distinct trigger, a repeatable workflow, does not duplicate an existing skill, and will be used often enough to matter. Prefer updating the narrowest existing skill that fits the lesson.

Can a skill guarantee a behavior like asking before acting?▼

No. Gates fire on events the agent emits, so absence-triggered behaviors have no event to hook. Reword the description once if misleading, then accept partial compliance or use a hook or injection channel instead of more prose.

Why does the audit script exclude subagent transcripts?▼

Subagent transcripts are delegate sessions that legitimately do not load the parent's gating skills, so counting them inflates denominators and understates compliance. The script filters paths containing /subagents/ in gate compliance, cost, and prompt sections.