← Back to Skills Marketplace
anderskev

Exdoc Config

by Kevin Anderson · GitHub ↗ · v1.2.1 · MIT-0
cross-platform ✓ Security Clean
172
Downloads
0
Stars
1
Active Installs
2
Versions
Install in OpenClaw
/install exdoc-config
Description
Configures ExDoc for Elixir projects including mix.exs setup, extras, groups, cheatsheets, and livebooks. Use when setting up or modifying ExDoc documentatio...
README (SKILL.md)

ExDoc Configuration

Quick Reference

Topic Reference
Markdown, cheatsheets (.cheatmd), livebooks (.livemd) references/extras-formats.md
Custom head/body tags, syntax highlighting, nesting, annotations references/advanced-config.md

Gates

Use this sequence before claiming ExDoc is wired correctly or that docs build:

  1. Dependencies resolved — Run mix deps.get from the project root. Pass: exit code 0, and mix.exs includes ex_doc as in Dependency Setup (or the project’s equivalent dev-only docs dep).
  2. Extra paths real — For every path string in extras/0 (and in groups_for_extras/0 if used), confirm that path exists in the repo or you have just created that file. Pass: no stale or typo paths remain when you run mix docs.
  3. Docs build — Run mix docs. Pass: exit code 0, and the HTML entry exists at \x3Coutput>/index.html (default \x3Cproject>/doc/index.html; use docs: [output: ...] if you changed output).

For cheatsheets, livebooks, or custom head/body assets, follow the same “path exists before listing” rule; see When to Load References.

Dependency Setup

Add ExDoc to mix.exs deps:

defp deps do
  [
    {:ex_doc, "~> 0.34", only: :dev, runtime: false}
  ]
end

Project Configuration

Configure your project/0 function in mix.exs:

def project do
  [
    app: :weather_station,
    version: "0.1.0",
    elixir: "~> 1.17",
    start_permanent: Mix.env() == :prod,
    deps: deps(),

    # ExDoc
    name: "WeatherStation",
    source_url: "https://github.com/acme/weather_station",
    homepage_url: "https://acme.github.io/weather_station",
    docs: docs()
  ]
end

The docs/0 Function

Define a private docs/0 function to keep project config clean:

defp docs do
  [
    main: "readme",
    logo: "priv/static/images/logo.png",
    output: "doc",
    formatters: ["html", "epub"],
    source_ref: "v#{@version}",
    extras: extras(),
    groups_for_modules: groups_for_modules(),
    groups_for_extras: groups_for_extras()
  ]
end

Key Options

Option Default Description
main "api-reference" Landing page module name or extra filename (without extension)
logo nil Path to logo image displayed in sidebar
output "doc" Output directory for generated docs
formatters ["html"] List of output formats ("html", "epub")
source_ref "main" Git ref used for "View Source" links
assets nil Map of source directory to target directory for static assets
deps [] Links to dependency documentation

Setting the Landing Page

The main option controls what users see first:

# Use the README as the landing page (most common)
docs: [main: "readme"]

# Use a specific module as the landing page
docs: [main: "WeatherStation"]

# Use a custom guide
docs: [main: "getting-started"]

The value matches the extra filename without its extension, or a module name.

Extras

Extras are additional pages beyond the API reference. Add them as a list of file paths:

defp extras do
  [
    "README.md",
    "CHANGELOG.md",
    "LICENSE.md",
    "guides/getting-started.md",
    "guides/configuration.md",
    "guides/deployment.md",
    "cheatsheets/query-syntax.cheatmd",
    "notebooks/data-pipeline.livemd"
  ]
end

Controlling Extra Titles

By default, ExDoc uses the first h1 heading as the title. Override with a keyword tuple:

defp extras do
  [
    {"README.md", [title: "Overview"]},
    {"CHANGELOG.md", [title: "Changelog"]},
    "guides/getting-started.md"
  ]
end

Ordering

Extras appear in the sidebar in the order listed. Put the most important pages first:

defp extras do
  [
    "README.md",
    "guides/getting-started.md",
    "guides/architecture.md",
    "guides/deployment.md",
    "CHANGELOG.md"
  ]
end

Grouping

Grouping Modules

Organize modules into logical sections in the sidebar:

defp groups_for_modules do
  [
    "Sensors": [
      WeatherStation.Sensor,
      WeatherStation.Sensor.Temperature,
      WeatherStation.Sensor.Humidity,
      WeatherStation.Sensor.Pressure
    ],
    "Data Processing": [
      WeatherStation.Pipeline,
      WeatherStation.Pipeline.Transform,
      WeatherStation.Pipeline.Aggregate
    ],
    "Storage": [
      WeatherStation.Repo,
      WeatherStation.Schema.Reading,
      WeatherStation.Schema.Station
    ]
  ]
end

Use regex to group by pattern:

defp groups_for_modules do
  [
    "Sensors": [~r/Sensor/],
    "Schemas": [~r/Schema/],
    "Pipeline": [~r/Pipeline/]
  ]
end

Modules not matching any group appear under a default "Modules" heading.

Grouping Functions

Group functions within a module using groups_for_docs:

defp docs do
  [
    groups_for_docs: [
      "Lifecycle": &(&1[:section] == :lifecycle),
      "Queries": &(&1[:section] == :queries),
      "Mutations": &(&1[:section] == :mutations)
    ]
  ]
end

Tag functions in your module with @doc metadata:

@doc section: :lifecycle
def start_link(opts), do: GenServer.start_link(__MODULE__, opts)

@doc section: :queries
def get_reading(station_id), do: Repo.get(Reading, station_id)

Grouping Extras

Organize guides, cheatsheets, and notebooks in the sidebar:

defp groups_for_extras do
  [
    "Guides": [
      "guides/getting-started.md",
      "guides/configuration.md",
      "guides/deployment.md"
    ],
    "Cheatsheets": [
      "cheatsheets/query-syntax.cheatmd",
      "cheatsheets/ecto-types.cheatmd"
    ],
    "Tutorials": [
      "notebooks/data-pipeline.livemd",
      "notebooks/sensor-setup.livemd"
    ]
  ]
end

Use glob patterns for convenience:

defp groups_for_extras do
  [
    "Guides": ~r/guides\/.*/,
    "Cheatsheets": ~r/cheatsheets\/.*/,
    "Tutorials": ~r/notebooks\/.*/
  ]
end

Dependency Doc Links

Link to documentation for your dependencies so ExDoc cross-references resolve:

defp docs do
  [
    deps: [
      ecto: "https://hexdocs.pm/ecto",
      phoenix: "https://hexdocs.pm/phoenix",
      plug: "https://hexdocs.pm/plug"
    ]
  ]
end

This enables references like t:Ecto.Schema.t/0 to link directly to the dependency docs.

Generating Docs

# Generate HTML docs
mix docs

# Open in browser
open doc/index.html

Complete mix.exs Example

defmodule WeatherStation.MixProject do
  use Mix.Project

  @version "1.3.0"
  @source_url "https://github.com/acme/weather_station"

  def project do
    [
      app: :weather_station,
      version: @version,
      elixir: "~> 1.17",
      start_permanent: Mix.env() == :prod,
      deps: deps(),
      name: "WeatherStation",
      source_url: @source_url,
      homepage_url: "https://acme.github.io/weather_station",
      docs: docs()
    ]
  end

  defp docs do
    [
      main: "readme",
      logo: "priv/static/images/logo.png",
      source_ref: "v#{@version}",
      formatters: ["html"],
      extras: extras(),
      groups_for_modules: groups_for_modules(),
      groups_for_extras: groups_for_extras(),
      deps: [
        ecto: "https://hexdocs.pm/ecto",
        phoenix: "https://hexdocs.pm/phoenix"
      ]
    ]
  end

  defp extras do
    [
      "README.md",
      "CHANGELOG.md",
      "guides/getting-started.md",
      "guides/configuration.md",
      "guides/deployment.md",
      "cheatsheets/query-syntax.cheatmd",
      "notebooks/data-pipeline.livemd"
    ]
  end

  defp groups_for_modules do
    [
      "Sensors": [~r/Sensor/],
      "Data Processing": [~r/Pipeline/],
      "Storage": [~r/Schema|Repo/]
    ]
  end

  defp groups_for_extras do
    [
      "Guides": ~r/guides\/.*/,
      "Cheatsheets": ~r/cheatsheets\/.*/,
      "Tutorials": ~r/notebooks\/.*/
    ]
  end

  defp deps do
    [
      {:phoenix, "~> 1.7"},
      {:ecto_sql, "~> 3.12"},
      {:ex_doc, "~> 0.34", only: :dev, runtime: false}
    ]
  end
end

When to Load References

  • Setting up cheatsheets or livebooks as extras -> extras-formats.md
  • Injecting custom CSS/JS, configuring syntax highlighting, or tuning module nesting -> advanced-config.md
Usage Guidance
This skill is coherent with its purpose, but exercise normal caution when following its instructions: 1) Inspect any injected HTML/JS hooks (before_closing_head_tag / before_closing_body_tag) before enabling them — they can load external scripts or send data. 2) Review Livebook (.livemd) files and their first cells for Mix.install or code that performs network or system actions. 3) Running `mix deps.get` and `mix docs` will fetch and compile dependencies from Hex/Git — run these in an isolated environment (CI container or dev VM) and review the deps declared in mix.exs. 4) Verify extras file paths and any external asset URLs are trusted before publishing the generated docs.
Capability Assessment
Purpose & Capability
The name/description match the SKILL.md content: it focuses on adding ExDoc deps, configuring mix.exs docs:, extras, groups, cheatsheets, and livebooks. No unrelated binaries, credentials, or config paths are requested.
Instruction Scope
The instructions are scoped to verifying and building ExDoc docs (e.g., run `mix deps.get`, verify extras paths, run `mix docs`). This is appropriate, but several legitimate ExDoc options the skill documents can cause code/network activity if used: `before_closing_body_tag` may inject JavaScript (which could contact external analytics endpoints if authored), Livebook extras may include `Mix.install/1` and executable code, and `mix deps.get` / `mix docs` will fetch and compile dependencies. These are expected for the purpose but are the main areas to review before running.
Install Mechanism
Instruction-only skill with no install spec and no code files; nothing is written to disk by the skill itself. Low install risk.
Credentials
No environment variables, credentials, or config paths are requested. The documented options (source_url, assets, injected JS, external dependency links) are normal for documentation configuration.
Persistence & Privilege
always:false and normal autonomous invocation settings. The skill does not request permanent presence or modify other skills/configs.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install exdoc-config
  3. After installation, invoke the skill by name or use /exdoc-config
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.1
- Adds a new "Gates" section outlining step-by-step criteria for confirming correct ExDoc config and successful doc builds. - Emphasizes verification of extra file paths and dependency resolution before running `mix docs`. - No changes to the example configs or ExDoc options; this is a documentation improvement for clarity and reliability in setup.
v1.2.0
- Expanded documentation with detailed instructions on configuring ExDoc, including `mix.exs` setup, extras, module and extras grouping, cheatsheet and livebook integration, and dependency doc linking. - Added quick references for advanced ExDoc configurations and supported extra file formats. - Provided multiple code examples for defining groups, extras, and overriding sidebar order and titles. - Included a complete `mix.exs` configuration example for practical reference. - Clarified how to set up landing pages and organize content in the ExDoc sidebar.
Metadata
Slug exdoc-config
Version 1.2.1
License MIT-0
All-time Installs 1
Active Installs 1
Total Versions 2
Frequently Asked Questions

What is Exdoc Config?

Configures ExDoc for Elixir projects including mix.exs setup, extras, groups, cheatsheets, and livebooks. Use when setting up or modifying ExDoc documentatio... It is an AI Agent Skill for Claude Code / OpenClaw, with 172 downloads so far.

How do I install Exdoc Config?

Run "/install exdoc-config" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Exdoc Config free?

Yes, Exdoc Config is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Exdoc Config support?

Exdoc Config is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Exdoc Config?

It is built and maintained by Kevin Anderson (@anderskev); the current version is v1.2.1.

💬 Comments