Hexdocs Fetcher
CheckedThis tool fetches documentation from HexDocs, streamlining access to project resources and improving developer workflow efficiency.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add oliver-kriska/claude-elixir-phoenix --skill hexdocs-fetcher -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
oliver-kriska
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned oliver-kriska/claude-elixir-phoenix at 19791bb7dc.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 19791bb7dc
- Scanned
- 3 files, 330 lines
- Copies in repo
- 3 — all of them scanned
About this skill
What it does
The hexdocs-fetcher skill retrieves and parses documentation from Elixir HexDocs. It allows AI agents to access information about Elixir modules, functions, and types directly from the official documentation source. This enables agents to understand and explain Elixir code more effectively.
When to use it
- Understanding Elixir Code: When an agent needs to comprehend what a specific function or module does within an Elixir project.
- Explaining Error Messages: To provide context for Elixir error messages by fetching relevant documentation about the functions involved.
- Code Generation Assistance: When generating Elixir code, the skill can be used to ensure that generated code aligns with documented APIs and best practices.
- Learning Elixir: For agents assisting users learning Elixir, providing direct access to HexDocs is a valuable resource.
Key capabilities
- Fetches documentation from Elixir HexDocs.
- Parses the fetched content for structured information.
- Provides access to module, function, and type definitions.
Example prompts
- "What does the
String.length/1function do?" - "Show me the documentation for the
Ecto.Repomodule." - "Explain how to use the
Phoenix.PubSubAPI."
Tips & gotchas
The skill relies on a stable HexDocs structure; changes in Elixir's documentation format may require updates to the skill. Ensure the agent has network access to reach the HexDocs servers.