86 Learning & Documentation agent skills on Mcprush — 74 free, 1229k of context between them.
Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to…
Generates or updates an index.md to reference all docs in the folder.
Comprehensive markdown and Mermaid diagram writing skill.
Use this skill any time a .pptx file is involved in any way — as input, output, or both.
Writing examples for the tldraw SDK examples app.
Writing SDK documentation for tldraw. Use when creating new documentation articles, updating existing docs, or when documentation writing…
Use when the user wants more human-like AI responses — less robotic, less listy, more authentic.
Translate "The Interactive Book of Prompting" chapters and UI strings to a new language
Document a recently solved problem to compound your team's knowledge
Refresh stale or drifting learnings and pattern docs in docs/solutions/ by reviewing, updating, consolidating, replacing, or deleting them…
Use Context7 to fetch up-to-date library documentation.
Use when creating code examples for documentation pages - JavaScript, TypeScript, React, Angular, and Vue variants with proper imports…
Create EmDash CMS plugins with hooks, storage, settings, admin UI, API routes, and Portable Text block types.
../../../agents/engineering/cs-wiki-librarian.md
Overcome LLM knowledge cutoffs with real-time developer content. daily.dev aggregates articles from thousands of sources, validated by…
Create a new screen in the Multi-site Dashboard with automatic route registration
Universal deep research agent team. 13-agent pipeline for rigorous academic research on any topic. 8 modes: full research, quick brief…
Guide users through a structured workflow for co-authoring documentation.
Analyze main branch implementation and configuration to find missing, incorrect, or outdated documentation in docs/.
This skill should be used to refine brainstorm or plan documents before proceeding to the next workflow step.
This skill should be used when the user asks about libraries, frameworks, API references, or needs code examples.