Agent skill

julien-workflow-check-loaded-skills

Check which Claude skills are loaded globally and project-level. Displays loaded skills by category (Hostinger, Anthropic, custom), counts, and helps troubleshoot missing skills.

Stars 163
Forks 31

Install this agent skill to your Project

npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/julien-workflow-check-loaded-skills

Metadata

Additional technical details for this skill

author
Julien
version
1.0.0
category
workflow
keywords
skills debug workflow loaded discovery troubleshoot

SKILL.md

Check Loaded Skills

This skill helps you verify which Claude Code skills are currently loaded in your project.

When to Use This Skill

Observability

First: At the start of execution, display:

πŸ”§ Skill "julien-workflow-check-loaded-skills" activated

Use this skill when you need to:

  • Verify loaded skills before invoking infrastructure or workflow skills
  • Debug missing skills when a skill you expect isn't available
  • Check skill hierarchy between global (~/.claude/skills/) and project-level (.claude/skills/)
  • Discover available skills to understand what's in your environment
  • Troubleshoot skill conflicts when project-level skills override globals

What This Skill Does

The skill runs a comprehensive check of your skill environment:

  1. Lists global skills from ~/.claude/skills/
  2. Lists project-level skills from .claude/skills/ (if any)
  3. Categorizes skills by author/type:
    • Hostinger infrastructure skills (julien-infra-hostinger-*)
    • Anthropic official skills (anthropic-*)
    • Custom/personal skills (julien-, google-services-)
  4. Shows counts for each category
  5. Identifies conflicts if project-level skills override globals

Usage

Via Slash Command (Recommended)

bash
/check-loaded-skills

Via Direct Invocation

Ask Claude to check loaded skills and Claude will invoke this skill automatically.

Examples:

  • "Check which skills are loaded"
  • "Show me available skills"
  • "List Hostinger skills"
  • "Are all my infrastructure skills loaded?"

Output Format

═══════════════════════════════════════════════════════
πŸ” SKILLS CHARGΓ‰S - Current Project
═══════════════════════════════════════════════════════

πŸ“¦ SKILLS GLOBAUX (~/.claude/skills/)
───────────────────────────────────────────────────────
Total: 28 skills

🏒 Skills Hostinger-specific:
  βœ“ julien-infra-hostinger-database
  βœ“ julien-infra-hostinger-deployment
  βœ“ julien-infra-hostinger-docker
  βœ“ julien-infra-hostinger-maintenance
  βœ“ julien-infra-hostinger-nginx
  βœ“ julien-infra-hostinger-space-reclaim
  βœ“ julien-infra-hostinger-ssh

πŸ€– Skills Anthropic: 9
  βœ“ anthropic-design-canvas
  βœ“ anthropic-office-docx
  [...]

πŸ“ SKILLS PROJECT-LEVEL (.claude/skills/)
───────────────────────────────────────────────────────
βœ… Aucun skill project-level
   β†’ Utilise uniquement les skills globaux

═══════════════════════════════════════════════════════
βœ… VΓ©rification terminΓ©e
═══════════════════════════════════════════════════════

Skill Resolution Hierarchy

Claude loads skills in this order:

  1. Global skills (~/.claude/skills/) - Lower priority
  2. Project-level skills (.claude/skills/) - Higher priority (overrides globals)

If a skill exists in both locations, the project-level version takes precedence.

Troubleshooting

Problem: Expected skill not showing up

Solutions:

  1. Check if skill exists in marketplace: ls -1 "path/to/marketplace/skills/"
  2. Verify sync to global: ls -1 ~/.claude/skills/
  3. Re-sync from marketplace: /sync-personal-skills
  4. Check for typos in skill name

Problem: Skill shows in global but not working

Possible causes:

  • Skill has incorrect YAML frontmatter
  • Skill references missing files
  • Permissions issue on script files

Solution: Check skill SKILL.md file for correct format

Skill Chaining

Skills Required Before

  • None (diagnostic skill, entry point)

Input Expected

  • None required
  • Optional: specific skill name to search for

Output Produced

  • Format: Console output with categorized skill list
  • Side effects: None (read-only)
  • Duration: < 5 seconds

Compatible Skills After

RecommandΓ©s:

  • julien-workflow-sync-personal-skills: If skills are missing, sync from marketplace
  • julien-dev-tools-skill-creator-pro: If need to create new skill

Optionnels:

  • julien-dev-tools-skill-reviewer: Review quality of loaded skills

Called By

  • Direct user invocation: "Check loaded skills", "List my skills"
  • Debugging workflows when skills aren't triggering
  • Pre-deployment verification

Tools Used

  • Bash (usage: run check-loaded-skills.sh script)
  • Read (usage: read skill directories)

Visual Workflow

User: "Check which skills are loaded"
    ↓
[THIS SKILL]
    β”œβ”€β–Ί List ~/.claude/skills/
    β”œβ”€β–Ί List .claude/skills/ (if exists)
    β”œβ”€β–Ί Categorize by author
    └─► Show counts + conflicts
    ↓
Skills report displayed
    ↓
[If missing skills]
    └─► sync-personal-skills

Usage Example

Scenario: Verify Hostinger skills are loaded before deployment

Command: "Are my Hostinger skills loaded?"

Result:

  • Lists 7 Hostinger infrastructure skills
  • Confirms all loaded from ~/.claude/skills/
  • No project-level overrides

Technical Details

Script: scripts/check-loaded-skills.sh Requirements: Bash shell (Git Bash on Windows) Permissions: Read-only (no modifications)

Didn't find tool you were looking for?

Be as detailed as possible for better results