skills/learn/SKILL.md
Update local AGENTS.md with strategic knowledge discovered during this session. Use when user says "learn", "save knowledge", "update AGENTS.md", "capture learnings", or at end of significant work sessions. Also used by commit skill for pre-commit knowledge capture.
npx skillsauth add abogoyavlensky/agents learnInstall 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.
Review the current conversation history and identify strategic, reusable project knowledge that should be captured in the local AGENTS.md file.
Review Session History
Extract Strategic Knowledge
Categorize Findings
INCLUDE - Strategic discoveries from this session:
EXCLUDE - Session-specific tactical work:
Ask yourself for each discovery:
First, check if local AGENTS.md exists and read its current content to avoid duplication.
If no new strategic knowledge was discovered during this session:
Present discovered knowledge formatted for local AGENTS.md:
## [Section Name]
- Discovery 1
- Discovery 2
CRITICAL: Use AskUserQuestion tool for granular selection of what to save.
Build options dynamically based on discoveries:
Example with 3 discoveries:
question: "Which knowledge should I save to local AGENTS.md?"
options:
- label: "All (3 items)"
description: "Save all discovered patterns"
- label: "Testing pattern"
description: "Table-driven tests with shared fixtures"
- label: "Config approach"
description: "Environment-based configuration loading"
- label: "None"
description: "Skip saving, nothing worth keeping"
Example with 1 discovery:
question: "Save this knowledge to local AGENTS.md?"
options:
- label: "Yes"
description: "Save: [brief description of the discovery]"
- label: "No"
description: "Skip saving"
After user selection:
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/