ClawHub

Exdoc Config

v1.2.0

Configures ExDoc for Elixir projects including mix.exs setup, extras, groups, cheatsheets, and livebooks. Use when setting up or modifying ExDoc documentatio...

⭐ 0· 85·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
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The name and description (ExDoc configuration) match the SKILL.md and reference files. All instructions and examples are about mix.exs, docs/0, extras, grouping, assets, and ExDoc hooks — nothing asks for unrelated services, binaries, or credentials.
ℹ
Instruction Scope
The runtime instructions stay within documentation configuration, but they explicitly show ExDoc hooks (before_closing_head_tag, before_closing_body_tag) that allow arbitrary HTML/JS injection and linking to external assets or analytics. That capability is expected for documentation customization, but it means generated docs can include third-party scripts or external endpoints — review any injected code or asset URLs before publishing.
✓
Install Mechanism
No install spec or code files that would be written to disk; this is instruction-only and therefore has minimal installation risk.
✓
Credentials
The skill declares no environment variables, no credentials, and no config paths. The examples reference only project-local files (mix.exs, extras, assets), which is proportionate to the stated purpose.
✓
Persistence & Privilege
The skill is not always-enabled and does not request elevated persistence or modify other skills; autonomous invocation is allowed by default but not combined with any other red flags.
Assessment
This skill is coherent and low-risk in structure: it only provides examples and instructions for configuring ExDoc. Before using the snippets in your project, audit any injected HTML/JS (before_closing_body_tag/head_tag) and external asset URLs — those can introduce trackers or exfiltrate data when the docs are hosted. Ensure assets referenced are from trusted sources and do not embed secrets in documentation files. If you publish docs publicly, double-check that examples linking to external services (analytics, CDN-hosted scripts) are intentional.

Like a lobster shell, security has layers — review code before you run it.

latestvk976ajcvx6kz06zg14cm87g6f983ah8a

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments