memory-reflect
unknown-studio-dev/hoangsaThis skill should be used at the end of a coding session, after a bug fix, a finished feature, a deployment, or whenever the user says "we're done", "wrap…
Scores out of 100 · grade B+
2026-08-17Works
40% of the score100/100
- Loads cleanly: valid frontmatter, required fields present, no dangling references.
Maintained
25% of the score92/100
- no commits in the last 12 weeks
Adopted
20% of the score19/100
- 24 stars on the source repo.
Documented
15% of the score81/100
- 869 words with worked examples.
Install
npx skills add unknown-studio-dev/hoangsa/memory-reflectWhat it says it does
This skill should be used at the end of a coding session, after a bug fix, a finished feature, a deployment, or whenever the user says "we're done", "wrap up", "summarize the session", "what did we learn", or "save what you learned". It drives a structured self-reflection pass that decides whether to persist new preferences, facts, lessons, or skills to hoangsa-memory's long-term memory. Also triggers on phrases like "reflect", "postmortem", or "retrospective" applied to the current session.
Also in unknown-studio-dev/hoangsa
| Artifact | Score | What the check found | Type | Reach | Last commit |
|---|---|---|---|---|---|
| fe-testingunknown-studio-dev/hoangsa | clean | Skill | 24 stars | 21 days ago | |
| git-flowunknown-studio-dev/hoangsa | clean | Skill | 24 stars | 21 days ago | |
| memory-cliunknown-studio-dev/hoangsa | clean | Skill | 24 stars | 21 days ago | |
| memory-refactoringunknown-studio-dev/hoangsa | clean | Skill | 24 stars | 21 days ago | |
| memory-debuggingunknown-studio-dev/hoangsa | clean | Skill | 24 stars | 21 days ago | |
| memory-disciplineunknown-studio-dev/hoangsa | clean | Skill | 24 stars | 21 days ago |
Other debugging skills
Browse all| Artifact | Score | What the check found | Category | Reach | Last commit |
|---|---|---|---|---|---|
| azure-diagnosticsmicrosoft/azure-skills | clean | Debugging | 538,931 installs | today | |
| diagnosing-bugsmattpocock/skills | clean | Debugging | 446,167 installs | today | |
| draft-responseanthropics/knowledge-work-plugins | clean | Debugging | 2,281 installs | today | |
| debuganthropics/knowledge-work-plugins | clean | Debugging | 5,114 installs | today | |
| fix-ci-failuresmicrosoft/vscode | clean | Debugging | 189k stars | today | |
| sweeper-fixmicrosoft/vscode | clean | Debugging | 189k stars | today |
Put this measurement in your README
A badge carrying how many listings this index holds from the repository and how many pass every static structural check. It reads from this index every time somebody loads your page, so it changes when the measurement changes and there is nothing to keep up to date. Free, no account, and the value is not something you or we can set by hand.
[](https://skillworks.kynth.studio/?q=unknown-studio-dev%2Fhoangsa)Would rather not hotlink us? Every badge is also served in shields.io’s endpoint schema, so shields renders the image and your readers never talk to our domain:
Published by Toolproof, the masthead over this index and eight others. The method behind the number is at toolproof.kynth.studio/methodology, and the whole thing is readable as JSON with no key at /api.
