skills/project-summary/SKILL.md
Creates an LLM-friendly project summary
npx skillsauth add abogoyavlensky/agents project-summaryInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
I'd like you to create an LLM-friendly project summary for this codebase.
First try to read_file the docs/PROJECT_SUMMARY.md
IF there is no docs/PROJECT_SUMMARY.md THEN
Please analyze the key files, dependencies, and structure, then generate a docs/PROJECT_SUMMARY.md in the root dir of the project that includes:
A brief overview of what the project does Key file paths with descriptions of their purpose Important dependencies with versions and their roles Available tools/functions/APIs with examples of how to use them The overall architecture and how components interact Implementation patterns and conventions used throughout the code Development workflow recommendations Extension points for future development
Structure this summary to help an LLM coding assistant quickly understand the project and provide effective assistance with minimal additional context.
ELSE IF a docs/PROJECT_SUMMARY.md already exists THEN
Please read it and then update it with any new information that we have learned in this current chat.
development
Review, edit, or draft technical articles, blog posts, tutorials, README-style walkthroughs, and documentation in Andrey Bogoyavlensky's practical technical writing voice. Use when asked to review or improve an article end to end (grammar, fluency, factual correctness, readability) and apply the fixes; improve grammar, fluency, structure, or style of technical prose; align a draft with "my style"; or write/rewrite articles for bogoyavlensky.com while preserving the author's voice.
documentation
Use when writing prose humans will read - documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.
tools
Run a second-opinion code review using the Codex CLI (`codex exec review`) in the background and surface the findings when it finishes. Use when the user says "review with codex", "second-opinion review", "what does codex think", or wants an outside model to look at local changes (uncommitted, current branch vs main, or a named commit). Also used as the review checkpoint inside the `executing-plans` skill.
documentation
Create structured implementation plan in docs/plans/