Create a SKILL.md entry summarizing debugging sessions and root causes.
npx skills add https://github.com/Project-N-E-K-O/N.E.K.O --skill -project-n-e-k-o
Please help me install this Agent Skill. Skill: 📝 任务完成后归档 Source: https://github.com/Project-N-E-K-O/N.E.K.O/tree/main/.agent/skills/post-work-analysis Command: npx skills add https://github.com/Project-N-E-K-O/N.E.K.O --skill -project-n-e-k-o
This Skill helps teams systematically capture insights from complex debugging or development tasks and reuse them as a formal Skill entry, avoiding loss of knowledge.
Create or update the Skill at .agent/skills/post-work-analysis/SKILL.md by filling in the template sections for direct causes, root causes, and knowledge artifacts.
High-intent search queries and answers about installing and using this skill.
You can archive debugging lessons learned by creating a Skill entry that summarizes complex sessions, identifying direct and root causes, and preserving them in a SKILL.md template for future knowledge reuse.
The best way to document root cause analysis is using structured post-work archival to capture direct causes, root causes, and learning points in a standardized text template, ensuring insights are preserved for future reference.
No, you do not need external tools for post-work analysis capture. It requires no tooling beyond standard text editing and the conventional SKILL.md template to store debugging summaries and reusable lessons.
Create a shareable knowledge artifact by transforming iterative research and debugging tasks into a formal Skill entry with root-cause summaries and actionable templates, avoiding loss of knowledge across projects.
You should use a structured post-work archival template for project tasks involving complex debugging, research, or iterative work, guiding teams to systematically identify direct and root causes and preserve knowledge for onboarding.
Yes, post-work knowledge capture improves onboarding and debugging consistency by transforming project tasks into shareable Skills with structured root-cause summaries, enabling quick onboarding and consistent practices across projects.
CharlieGreenmanDiagnoses physics calculation discrepancies by orchestrating parallel subagents to isolate root causes.
aslaiiConsolidate milestone artifacts into a structured MILESTONE_SUMMARY report.
sk8metalmeEnforce Change ID-based commits and bookmark usage in Jujutsu workflows.
lihaoze123Analyze fixed bugs to identify root causes and formulate prevention strategies.
