cloudthinker-ai/CloudSkills / skills/connections/managing-hex-pm
managing-hex-pm
VerifiedUse when working with Hex Pm — hex.pm Elixir/Erlang package registry management. Covers package publishing, dependency resolution, Mix configuration, Hex organization management, and package metadata. Use when managing Hex packages, publishing Elixir/Erlang libraries, resolving Mix dependency conflicts, or auditing package security.
Hex.pm Registry Management Skill
Manage and analyze Elixir/Erlang packages, Hex publishing, and Mix dependencies.
MANDATORY: Discovery-First Pattern
Always check current mix.exs configuration before modifying packages.
Phase 1: Discovery
#!/bin/bash
echo "=== Mix Project ==="
cat mix.exs 2>/dev/null | head -25
echo ""
echo "=== Hex Info ==="
mix hex.info 2>/dev/null | head -10
echo ""
echo "=== Elixir/Erlang Version ==="
elixir --version 2>/dev/null | head -3
Phase 2: Analysis
#!/bin/bash
echo "=== Dependencies ==="
mix deps 2>/dev/null | head -15
echo ""
echo "=== Outdated Deps ==="
mix hex.outdated 2>/dev/null | head -15
echo ""
echo "=== Dependency Tree ==="
mix deps.tree --depth=1 2>/dev/null | head -20
echo ""
echo "=== Security Audit ==="
mix hex.audit 2>/dev/null | head -10
Output Rules
- TOKEN EFFICIENCY: Target <=50 lines per output
- List dependencies with version constraints
- Report outdated packages with available versions
- Never expose Hex API keys in output
Common Operations
Package Lookup
#!/bin/bash
PACKAGE="${1:?Package name required}"
echo "=== Hex Package: $PACKAGE ==="
curl -s "https://hex.pm/api/packages/${PACKAGE}" | jq '{
name: .name,
latest: .releases[0].version,
downloads: .downloads.all,
description: .meta.description,
licenses: .meta.licenses
}' 2>/dev/null
Publish Preview
#!/bin/bash
echo "=== Publish Preview ==="
mix hex.publish --dry-run 2>&1 | tail -15
Safety Rules
- Use
mix hex.publish --dry-runbefore publishing - Run
mix hex.auditto check for retired packages - Lock dependency versions with mix.lock for reproducible builds
- Never commit Hex API keys to version control
Output Format
Present results as a structured report:
Managing Hex Pm Report
══════════════════════
Resources discovered: [count]
Resource Status Key Metric Issues
──────────────────────────────────────────────
[name] [ok/warn] [value] [findings]
Summary: [total] resources | [ok] healthy | [warn] warnings | [crit] critical
Action Items: [list of prioritized findings]
Target ≤50 lines of output. Use tables for multi-resource comparisons.
Anti-Hallucination Rules
- NEVER assume resource names — always discover via CLI/API in Phase 1 before referencing in Phase 2.
- NEVER fabricate metric names or dimensions — verify against the service documentation or
--helpoutput. - NEVER mix CLI commands between service versions — confirm which version/API you are targeting.
- ALWAYS use the discovery → verify → analyze chain — every resource referenced must have been discovered first.
- ALWAYS handle empty results gracefully — an empty response is valid data, not an error to retry.
Counter-Rationalizations
| Shortcut | Counter | Why |
|---|---|---|
| "I'll skip discovery and check known resources" | Always run Phase 1 discovery first | Resource names change, new resources appear — assumed names cause errors |
| "The user only asked for a quick check" | Follow the full discovery → analysis flow | Quick checks miss critical issues; structured analysis catches silent failures |
| "Default configuration is probably fine" | Audit configuration explicitly | Defaults often leave logging, security, and optimization features disabled |
| "Metrics aren't needed for this" | Always check relevant metrics when available | API/CLI responses show current state; metrics reveal trends and intermittent issues |
| "I don't have access to that" | Try the command and report the actual error | Assumed permission failures prevent useful investigation; actual errors are informative |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 465k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 465k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 465k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |