My Skill: project-briefing What it does:· I often deal with messy folders (code projects, messy notes, or desktop clutter). I built a skill called project-briefing that scans a directory structure, skips noise directories, flags sensitive files by name only (never touching .env or keys), and writes a condensed _briefing.md summary directly inside the folder with an overview, topic groupings, recent changes, and unfinished files. How to trigger it: - I can trigger it using natural language like "summarize this folder", or via the /project-briefing command followed by the path. - The bug and the optimization I made: I tested it on a real course folder containing just 3 files, the agent successfully read two PDFs, but hit an Outlook .msg email and silently wrote: "couldn't read this format, skipped." It turned out that skipped email was the most important file in the folder—an internal message revealing that the PDFs were recycled from an old year's template, which finally explained a date that made no sense otherwise. Watching the agent quietly give up on the one file that actually mattered taught me a vital lesson. I added a new rule: for common non-native formats (.msg, .eml, .docx, .pptx), it must actually try to extract the content first and only report "unreadable" if it genuinely fails.