Loading...
Loading...
Found 2,071 Skills
Compact, compress, or minify markdown files to use fewer tokens while preserving all information and meaning. Use this skill whenever the user wants to reduce the size of a markdown file, shrink a README, compress a SKILL.md or CLAUDE.md, minify documentation, or make any markdown more token-efficient. Trigger even if they just say "make this shorter" or "compress this" on a markdown file.
Prepare R packages for CRAN submission by checking for common ad-hoc requirements not caught by devtools::check(). Use when: (1) Preparing a package for first CRAN release, (2) Preparing a package update for CRAN resubmission, (3) Reviewing a package to ensure CRAN compliance, (4) Responding to CRAN reviewer feedback. Covers documentation requirements, DESCRIPTION field standards, URL validation, examples, and administrative requirements.
Guide for creating effective internal technical documentation (READMEs, ADRs, Contribution Guides). Use this skill when the user asks to write, refactor, or improve internal project documentation.
Document capabilities and skills comprehensively. Creates skill documentation with examples, specifications, and usage patterns.
Use the ctx7 CLI to fetch library documentation, manage AI coding skills, and configure Context7 MCP. Activate when the user mentions "ctx7" or "context7", needs current docs for any library, wants to install/search/generate skills, or needs to set up Context7 for their AI coding agent.
Generate or update a README.md in French, oriented Product Owner, with Mermaid diagrams. Reviews and improves technical documentation in docs/. Also generates CLAUDE.md and AGENT.md if missing. Triggers on: create readme, update readme, generate readme, générer le readme, mettre à jour le readme, generate docs, update docs, /docs.
Technical documentation expert for creating clear, comprehensive documentation. Use when user asks to write docs, create README, or document code.
Generate structured documentation templates for components, patterns, or guidelines within a design system.
Quick guide to choosing the right creative writing skill. Use when you need help deciding which creative writing skill to use for a specific task - brainstorming vs documentation, critique vs writing, etc.
Discovers all documentation in a project, analyzes it for redundancy, contradictions, and staleness, proposes a consolidation plan, then executes it. Produces optimized docs for both humans and agents. Use when user says "combine docs", "consolidate documentation", "merge docs", "clean up docs", "fix documentation", "optimize docs", "documentation sprawl", "too many docs", or asks about doc organization.
This skill should be used when the user invokes "/describe" to look up Emacs documentation via emacsclient.
Analyzes code comments for accuracy, completeness, and long-term maintainability. Identifies misleading comments, comment rot, and documentation gaps. Triggers: After adding documentation, before finalizing a PR, when reviewing comments. Examples: - "Check if the comments are accurate" -> verifies comments match code behavior - "Review the documentation I added" -> analyzes new comments for quality - "Analyze comments for technical debt" -> finds outdated or misleading comments - "Are my docstrings correct?" -> validates documentation accuracy