# Self Assess

> Analyze your own source code and capabilities to find bugs, gaps, and improvement opportunities

- Skill: `yologdev/self-assess` (Agent Skill)
- Install (CLI): `npx skillmds@latest add yologdev/self-assess`
- Raw SKILL.md: https://api.skillmd.com/api/skills/yologdev/self-assess/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: yologdev (https://skillmd.com/u/yologdev)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/yologdev/self-assess

---


# Self-Assessment

You are assessing yourself. Your source code is your body. Read it critically.

## Process

1. **Survey your source code** — use `list_files` to map the modules, then read the entry points and the areas that matter (`wc -l` for sizes). `src/` is large; you don't need to read every file.
2. **Read memory/active_learnings.md.** Check your accumulated lessons — patterns that worked, mistakes to avoid, insights from past sessions. Build on what you already know.
3. **Try using yourself.** Pick a small real task and attempt it:
   - Edit a file and check the result
   - Run a shell command that might fail
   - Try an edge case (empty input, long input, special characters)
4. **Note what went wrong.** Be specific:
   - Did you crash? Where?
   - Did you give a bad error message? What should it say?
   - Was something slow or clunky?
   - Is there a feature you needed but didn't have?
5. **Check journals/JOURNAL.md.** Have you tried something before that failed? Don't repeat the same mistake.

## What to look for

- `unwrap()` calls — these are potential panics. Every one is a bug waiting to happen.
- Missing error messages — if something fails silently, that's a problem.
- Hard-coded values — magic numbers, hard-coded paths, assumptions about the environment.
- Missing edge cases — what happens with empty input? Unicode? Very long strings?
- User experience gaps — is anything confusing, unclear, or annoying?
- Verification gaps — tests that pass but don't actually exercise the changed behavior.

## Output

Write your findings as a prioritized list. The most impactful issue goes first. Ground
each finding in evidence — the file:line, command output, or test result that shows it,
not a hunch or something you half-remember. Format:

```
SELF-ASSESSMENT Day [N]:
1. [CRITICAL/HIGH/MEDIUM/LOW] Description of issue — evidence: file:line / command / test result
2. ...
```

Then prioritize which ones to tackle this session. Fix as many as you can.