Elixir Writing Docs
v1.2.0Guides writing Elixir documentation with @moduledoc, @doc, @typedoc, doctests, cross-references, and metadata. Use when adding or improving documentation in...
⭐ 0· 99·0 current·0 all-time
byKevin Anderson@anderskev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name and description (Elixir documentation guidance) match the contents: a detailed SKILL.md and three reference markdown files about doctests, cross-references, and formatting. There are no unexpected requirements (no binaries, env vars, or config paths).
Instruction Scope
The runtime instructions are purely editorial: examples, formatting rules, and advice for ExDoc and doctests. They do not instruct the agent to read arbitrary files, access credentials, call external endpoints, or perform system-level operations beyond authoring documentation in .ex files.
Install Mechanism
No install spec and no code files beyond documentation. Nothing is downloaded or written to disk by the skill itself, so install risk is minimal.
Credentials
The skill requests no environment variables, credentials, or config paths. The advice references common Elixir tooling (ExDoc, mix) but does not require access to them or to any secrets.
Persistence & Privilege
always is false and the skill is user-invocable. It does not attempt to modify other skills or system settings. Autonomous invocation is allowed by platform default but is not combined with any privileged access.
Assessment
This skill is instruction-only documentation for writing Elixir @moduledoc/@doc/@typedoc and doctests; it contains no code, no installs, and requests no credentials—so installation risk is low. As with any third-party guidance, verify recommendations against your project's policies (e.g., whether to include runnable doctests for your codebase) and be mindful that the skill itself cannot run tests or change your repository—it's a writing aid. If you need the agent to modify source files or run mix/test commands, those actions would require separate tooling or explicit commands and additional review.Like a lobster shell, security has layers — review code before you run it.
latestvk97amd8yc0xw7aak68pbprzqq983bwez
License
MIT-0
Free to use, modify, and redistribute. No attribution required.