Agent skill
elm-packages
Look up Elm package documentation, list project dependencies, search the Elm package registry, and read module exports. Use when working with Elm projects, elm.json files, or needing information about Elm packages.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/elm-packages
SKILL.md
Capabilities
All capabilities are exposed as bash scripts in the scripts/ directory relative to this skill.
If scripts fail, see ./TROUBLESHOOTING.md for diagnosis and installation help.
# List installed packages (elm.json dependencies)
./scripts/list-installed-packages.sh
# Search the Elm package repository
./scripts/search-packages.sh "search query"
# Get README documentation for a package
./scripts/get-readme.sh {author} {name} {version}
# List package modules or module exports
./scripts/get-exports.sh {author} {name} {version}
./scripts/get-exports.sh {author} {name} {version} {ModuleName}
# Get full docs for a specific export
./scripts/get-export-docs.sh {author} {name} {version} {ModuleName} {exportName}
Common Workflows
Looking up docs for an installed package
- Run
list-installed-packages.shto get author/name/version - Run
get-exports.shto list modules, then exports - Run
get-export-docs.shfor full documentation on a specific export
Discovering new packages
- Run
search-packages.shwith keywords to find packages - Run
get-readme.shfor an overview - Run
get-exports.shto explore the API
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?