Claude Code Skills: Full Guide | CampusX

Summary

Nitish Singh (CampusX) provides a comprehensive guide on Claude Code Skills, explaining how to transform general-purpose agents into specialized experts. The guide covers the hierarchy of skills (Global vs. Local), the structural requirements (SKILL.md + YAML), and a practical demonstration of building a profile page using a dedicated skill.

Key Takeaways

1. Skill Hierarchy & Storage

• Global Skills (~/.claude/skills/): Personal skills available across all repositories (e.g., specific coding styles, unit test preferences).
• Project Skills (.claude/skills/): Repository-specific skills used for project standards and team collaboration.
• Nested Skills: Sub-directories can have their own skills for modular expertise.

2. The “Description is Key” Principle

• The YAML description in SKILL.md is the primary metadata used by Claude for Dynamic Discovery.
• Accurate descriptions allow the agent to automatically load the skill when the task matches the intent.

3. Skill Structure & Resources

• SKILL.md: The core logic and instructions.
• Resources Folder: Storing templates, schemas, or design tokens within the skill directory for the agent to reference.
• Just-in-Time Knowledge: Skills are only loaded when needed, maintaining a lean context window.

4. Practical Demonstration: Profile Design

• A skill named profile-design was created to encapsulate Tailwind CSS rules, card structures, and table formatting.
• This approach replaces repetitive prompting and ensures UI consistency across the “Expense Tracker” project.

Synthesis

Skills represent the “long-term specialized memory” of an agent. By move beyond simple chat-based instructions into version-controlled, structured skill folders, teams can encode their “Senior Engineer” knowledge directly into the agent’s toolbox.

References

• Claude Code
• Claude Skills
• Spec-Driven Development