refine

Mines completed session trajectories for friction and applies evidence-backed edits to harness files.

Updated Aug 30, 2026
One-click install
npx skills add https://github.com/ryanportfolio/threejs-interview-test --skill refine-ryanportfolio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: refine
Source: https://github.com/ryanportfolio/threejs-interview-test/tree/main/.claude/skills/refine
Command: npx skills add https://github.com/ryanportfolio/threejs-interview-test --skill refine-ryanportfolio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a task ends, recurring friction—rediscovered facts, misfired skills, repeated user corrections—goes unrecorded, so the next session repeats the same mistakes. This Skill turns each finished session into a concrete, reversible improvement to the harness (skills, reference notes, memory, kernel instructions). ## Core Features & Use Cases - Trajectory mining: Re-reads actual session events through judgment, tooling, and divergent lenses to classify friction as rediscovery, skill misfire, correction, or stale state. - Smallest-edit discipline: Maps each friction to one minimal edit and one commit, quoting trajectory evidence, with structural enforcement (lints, hooks, scripts, permissions) preferred over prose rules. - Skill description repair: Treats misfired skills as description bugs and verifies fixes by testing routing with a fresh subagent. - Use Case: After a session where the user corrected your git workflow twice, invoke this Skill to locate the friction, add the missing rule to the correct instruction file, and commit it with quoted evidence. ## Quick Start Say "wrap up and refine this session" to mine the trajectory and apply the smallest evidence-backed harness edits.

Frequently Asked Questions about refine

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

FAQPage Schema
How do I improve AI agent behavior after a session ends?▼

Run a post-task refine pass that re-reads the session trajectory, classifies each friction event, and applies the smallest edit to the relevant harness file. Each edit is committed separately with quoted evidence so it can be rolled back.

How to fix a skill that triggers at the wrong time?▼

Treat a misfired skill as a description bug, not a one-off judgment error. Edit the skill's description line, then verify by handing a fresh subagent the descriptions plus the misfire scenario and confirming correct routing without over-firing on neighboring scenarios.

When should a workflow rule be a script instead of documentation?▼

Prefer structural enforcement whenever a lint, hook, script, or permission entry can enforce the rule. Prose rules are the fallback only when the structural encoding is too large for the current pass, in which case it is noted as a follow-up.

What happens if a session had no friction to fix?▼

Zero edits is a valid outcome and the Skill says so and stops. A correction whose rule already exists also produces no edit, since duplicating an existing rule weakens the kernel instructions.

Can refine edits be reversed if they cause problems?▼

Yes, each edit lands as its own commit quoting the trajectory evidence, which serves as the rollback snapshot. Edits outside a git repo, such as global skills or memory files, are named explicitly so they can be reversed by hand.