elixir-docs-reviewReviews Elixir documentation for completeness, quality, and ExDoc best practices. Use when auditing @moduledoc, @doc, @spec coverage, doctest correctness, an...
Install via ClawdBot CLI:
clawdbot install anderskev/elixir-docs-reviewGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated Apr 22, 2026
A development team maintaining an open-source Elixir library uses this skill to audit documentation before new releases. It ensures all public APIs are well-documented with @moduledoc, @doc, and @spec, improving usability for external contributors and reducing support requests.
A large enterprise with legacy Elixir applications employs this skill to review documentation coverage across modules. It helps identify gaps in @spec and @typedoc, ensuring code maintainability and facilitating onboarding for new developers by enforcing ExDoc best practices.
An online learning platform creating Elixir tutorials uses this skill to validate example code snippets in documentation. It checks for correct doctest implementation and cross-references, ensuring educational materials are accurate and follow community standards for clarity.
A software consultancy firm applies this skill during client engagements to assess Elixir project documentation quality. It flags issues like missing @since annotations or generic @doc, providing actionable reports to improve codebase health and compliance with internal guidelines.
Integrate this skill into a SaaS platform offering code quality analysis for Elixir projects. Revenue is generated through subscription tiers based on usage volume, such as number of files reviewed per month, targeting teams needing automated documentation audits.
Freelancers use this skill to offer specialized Elixir documentation review services to clients. Revenue comes from hourly or project-based fees for auditing and improving @moduledoc, @doc, and doctest coverage, helping businesses enhance their codebase maintainability.
Sell enterprise licenses for this skill as part of a larger developer tools suite. Revenue is generated through one-time purchases or annual licenses, targeting large organizations that require on-premise integration and custom support for documentation compliance checks.
💬 Integration Tip
Integrate this skill into CI/CD pipelines to automatically flag documentation issues during pull requests, ensuring consistent quality without manual intervention.
Scored Apr 19, 2026
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Systematic code review patterns covering security, performance, maintainability, correctness, and testing — with severity levels, structured feedback guidance, review process, and anti-patterns to avoid. Use when reviewing PRs, establishing review standards, or improving review quality.
Coding style memory that adapts to your preferences, conventions, and patterns for consistent coding.
Provides a 7-step debugging protocol plus language-specific commands to systematically identify, verify, and fix software bugs across multiple environments.
Control and operate Opencode via slash commands. Use this skill to manage sessions, select models, switch agents (plan/build), and coordinate coding through Opencode.
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions