Skip to content

best practices for installing skills from skills.sh with Claude Code? #437

@mturquette

Description

@mturquette

Hi! I apologize if this is a novice question. I've searched the web and asked AI already but with no success ...

I like agent-deck's skill pool. It's the perfect blend of globally storing skills while also retaining per-project control over which skills are activated for a given project.

I use Claude Code from the terminal. I also install skills via Vercel Lab's agent-skills package. E.g: npx skills add vercel-labs/agent-skills

What is the best practice to get these skills to land in ~/.agent-deck/skills/pool/ instead? I'm manually migrating the skills (either from ~/.claude/skills/ or ~/.agents/skills) to ~/.agent-deck/skills/pool and then using agent-deck to interactively add them to specific projects.

I tried to modify where the skills package installs them, but it doesn't seem to support agent-deck as a first-order choice. Should agent-deck be added to the list of agents that are supported by vercel-labs/agent-skills? (effectively this means that agent-skills would know about the ~/.agent-deck/skills/pool path, whereas currently it does not)

I also manually symlinked ~/.agent-deck/skills/pool/agent-deck to ~/.claude/skills/agent-deck since I plan to use that skill globally I guess. To be honest I haven't really figured out what the agent-deck skill even does ... using the agent-deck application without the skill installed seemed to work fine for me and I am pretty new to this so I'm probably missing some power user stuff the skill provides.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions