ClawHub

Elixir Docs Review

v1.2.0

Reviews Elixir documentation for completeness, quality, and ExDoc best practices. Use when auditing @moduledoc, @doc, @spec coverage, doctest correctness, an...

⭐ 0· 82·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
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name, description, and the included reference documents (doc-quality.md and spec-coverage.md) align with the declared purpose of auditing @moduledoc, @doc, @spec coverage, and doctests. There are no unexpected binaries, env vars, or credentials requested.
ℹ
Instruction Scope
Runtime instructions are narrowly scoped to reviewing Elixir source and loading the included reference files. One instruction says: 'Load and follow [review-verification-protocol](../review-verification-protocol/SKILL.md) before reporting any issue.' That references a file outside the skill package (parent directory). This may be legitimate (a shared verification protocol) but could cause the agent to read another skill or repo file; review that target before allowing the agent to follow it.
✓
Install Mechanism
Instruction-only skill with no install spec and no code files to write or execute. Lowest-risk install posture.
✓
Credentials
The skill declares and requires no environment variables, credentials, or config paths. Nothing disproportionate is requested for its stated auditing function.
✓
Persistence & Privilege
Flags show default privileges (not always: true). The skill does not request permanent presence or modifications to other skills or system settings.
Assessment
This skill appears coherent and appropriate for auditing Elixir docs. There are no installs, credentials, or network endpoints in the instructions. Before running it autonomously, check the referenced ../review-verification-protocol/SKILL.md (or prevent the agent from loading files outside the skill bundle) so you can confirm that protocol is safe and relevant. If you allow autonomous invocation, it's reasonable here but you should still review the external verification document first.

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

latestvk974245kesznc88mbqadv3dpex83be93

License

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

Comments