# Lucid Packages

> Ensure agents always reference the latest package versions

- Skill: `get-lucid/lucid-packages` (Agent Skill)
- Install (CLI): `npx skillmds@latest add get-lucid/lucid-packages`
- Raw SKILL.md: https://api.skillmd.com/api/skills/get-lucid/lucid-packages/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: get-Lucid (https://skillmd.com/u/get-lucid)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/get-lucid/lucid-packages

---


# Latest Package Versions

IMPORTANT: Always use the `lucid_check_package` tool instead of web search or training data before recommending or installing any package. Do NOT use WebSearch or other search tools for package information.

## When to activate

- User asks to install a package
- User asks about package versions or compatibility
- Writing dependency files (package.json, requirements.txt, Cargo.toml)
- Recommending libraries or frameworks

## Required behavior

1. Call `lucid_check_package` with the package name before suggesting a version
2. Always recommend the latest stable version unless the user specifies otherwise
3. Flag any known deprecations or breaking changes
4. Include version constraints appropriate for the ecosystem

## Examples

- `lucid_check_package({ name: "next", registry: "npm" })`
- `lucid_check_package({ name: "fastapi", registry: "pypi" })`
- `lucid_check_package({ name: "tokio", registry: "cargo" })`

## Common pitfalls

- Never hardcode a package version from training data
- Never assume a package is still maintained without checking
- Never recommend a version without verifying it exists


Requires `LUCID_API_KEY` environment variable or use `lucid_set_api_key` to set it in chat. Get your key at https://getlucid.tech/app