project-experience-distillation

Extract reusable workflow patterns from completed project work and formalize them as SKILL.md updates.

6|1|Updated May 11, 2026
One-click install
npx skills add https://github.com/yakeworld/Synthos --skill project-experience-distillation-yakeworld
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-experience-distillation
Source: https://github.com/yakeworld/Synthos/tree/main/skills/private/extended/meta/project-experience-distillation
Command: npx skills add https://github.com/yakeworld/Synthos --skill project-experience-distillation-yakeworld

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Completed project work contains valuable lessons that are usually lost or recorded only as raw step logs. This Skill turns project practice records into generalized, cross-project reusable patterns by enforcing reflection ("why did it work") and abstraction up to the constraint-type level, then routes the results into existing skills as SKILL.md updates. ## Core Features & Use Cases - Reflection-enforced distillation: Rejects records that only list steps without answering "why it worked", ensuring causal insight is captured. - Constraint-type abstraction: Strips project names, paths, and dates, then elevates findings to constraint types (e.g., "coupling must be additive and baseline-anchored") rather than project-specific templates. - Skill update governance: Prefers extending existing skills over creating new ones, and requires new skills to pass at least the L1 format quality gate. - Use Case: After tuning an ODE simulation and discovering that multiplicative positive feedback causes variable blow-up, submit the practice record and receive generalized patterns plus a diff extending the ode-simulation-tuning skill's Pitfalls section. ## Quick Start Distill my project practice record about fixing DOI coverage for 88 papers into reusable patterns and update the relevant existing skill.

Frequently Asked Questions about project-experience-distillation

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

FAQPage Schema
How do I turn project experience into a reusable skill?

Submit a project practice record containing the steps taken plus a reflection answering why they worked. The distillation process removes project names, paths, and dates, abstracts findings to constraint types, and produces a SKILL.md diff that extends an existing skill rather than creating a new one.

What is the difference between internal reflection and external absorption?

Internal reflection learns from your own completed project practice and is handled by this distillation process. External absorption learns from outside projects and is handled by the separate project-absorption skill. Confusing the two mixes the learning sources and is explicitly rejected.

Why was my practice record rejected during distillation?

Records are rejected when they only list operational steps without answering why the approach worked, or when the extracted patterns still contain project-specific names instead of constraint-type abstractions. Add causal reflection and re-abstract before resubmitting.

When should I create a new skill instead of extending an existing one?

Prefer extending an existing skill whenever the pattern is a general rule. Create a new skill only for highly personalized rules, and any new skill must pass at least the L1 format quality gate before being accepted.

How do I avoid documentation degradation when updating skills?

Avoid accumulating incremental patches, which cause duplicated sections over time. When a major restructuring is needed, rewrite the entire file in one pass instead of layering patches on top of previous edits.