doc-validate-markdown
Validate markdown files for formatting, links, and style compliance using markdownlint. Use before committing documentation changes.
Browse published AI skills maintained by mvillmow. Compare skill descriptions and follow each source repository for setup instructions.
Indexed skills
85Repository stars across indexed skills
1,105Repository forks
340Average repository stars per indexed skill
13Repository stars may repeat across skills from the same repository.
Validate markdown files for formatting, links, and style compliance using markdownlint. Use before committing documentation changes.
Reply to PR review comments using the correct GitHub API endpoint. Use when responding to inline code review feedback (not gh pr comment).
Analyze imports and identify all module dependencies. Use when mapping project structure.
Parse and analyze CI failure logs to identify root causes and error patterns. Use when CI builds fail to understand what broke.
Parse and document algorithm pseudocode from research papers. Use when preparing for implementation.
Post structured documentation to GitHub issue as a comment. Use when starting work on an issue to document approach and track progress.
Check function inputs for correctness and safety. Use when implementing defensive programming.
Check code for style and quality issues. Use when validating code before commits.
Create distributable packages including .mojopkg files and archives. Use during package phase to prepare components for distribution.
Execute test suites and report results. Use when validating code functionality.
Run Mojo tests using mojo test command. Use when executing tests or verifying test coverage.
Automatically fix code formatting issues using mojo format, markdownlint, and pre-commit hooks. Use when formatting checks fail or before committing code.
End-to-end implementation workflow for a GitHub issue from planning through PR creation. Use when starting work on an issue from scratch.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.