SkillHub ClubShip Full StackFull Stack

check-dependencies

Validate and verify dependencies are available and compatible. Use when setting up environments.

Packaged view

This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.

Stars

Hot score

Updated

March 19, 2026

Overall rating

C4.1

Composite score

4.1

Best-practice grade

S96.0

Install command

npx @skill-hub/cli install mvillmow-projectodyssey-check-dependencies

Repository

mvillmow/ProjectOdyssey

Skill path: .claude/skills/tier-2/check-dependencies

Validate and verify dependencies are available and compatible. Use when setting up environments.

Open repository

Best for

Primary workflow: Ship Full Stack.

Technical facets: Full Stack.

Target audience: everyone.

License: Unknown.

Original source

Catalog source: SkillHub Club.

Repository owner: mvillmow.

This is still a mirrored public skill entry. Review the repository before installing into production workflows.

What it helps with

Install check-dependencies into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
Review https://github.com/mvillmow/ProjectOdyssey before adding check-dependencies to shared team environments
Use check-dependencies for development workflows

Works across

Claude CodeCodex CLIGemini CLIOpenCode

Favorites: 0.

Sub-skills: 0.

Aggregator: No.

Original source / Raw SKILL.md

---
name: check-dependencies
description: "Validate and verify dependencies are available and compatible. Use when setting up environments."
mcp_fallback: none
category: analysis
tier: 2
---

# Check Dependencies

Verify that required dependencies are installed and compatible with the project requirements.

## When to Use

- Setting up development environment
- Validating CI/CD environment configuration
- Troubleshooting import errors
- Checking version compatibility

## Quick Reference

```bash
# Check Python dependencies
pip check

# Verify specific package versions
pip show package_name

# Validate pixi environment
pixi info
pixi task list
```

## Workflow

1. **List requirements**: Identify all declared dependencies (pixi.toml, requirements.txt)
2. **Verify installation**: Check that all packages are installed and importable
3. **Check versions**: Confirm version constraints are met
4. **Test imports**: Actually import modules to detect hidden issues
5. **Report status**: Document any missing or incompatible dependencies

## Output Format

Dependency validation report:

- All declared dependencies listed
- Installation status (installed/missing)
- Installed version vs required version
- Compatibility status (compatible/incompatible)
- Issues found (if any)

## References

- See CLAUDE.md > Environment Setup for Pixi configuration
- See `extract-dependencies` skill for dependency extraction
- See pixi.toml in repository root for project dependencies