Skill invoked via slash command (e.g. /pds-test) triggers 'API Error: Rate Limit Reached', but keyword trigger works fine

Bug Description

When invoking a custom skill using the slash command syntax (e.g., /pds-test), it immediately fails with:

API Error: Rate Limit Reached

However, when the same skill is triggered by typing the keyword without the slash (e.g., just pds-test), it works correctly and the skill executes as expected.

Steps to Reproduce

1. Define a custom skill in .claude/skills/pds-test/SKILL.md with triggers:

```yaml
triggers:

• pds-test
• pds test

```

1. Type /pds-test in the prompt → Rate Limit error
2. Type pds-test (no slash) in the prompt → Works correctly

Expected Behavior

Both /pds-test (slash command) and pds-test (keyword trigger) should invoke the skill identically without rate limit errors.

Actual Behavior

• /pds-test → API Error: Rate Limit Reached (fails immediately, not actually hitting real rate limits)
• pds-test → Skill loads and executes normally

Environment

• OS: Windows 11 Pro
• Shell: bash (Git Bash)
• Claude Code: latest
• Skill model: sonnet (effort: high)

Additional Context

This appears to be a difference in how the Skill tool processes slash-command invocations vs. keyword-triggered invocations. The rate limit error seems spurious — it happens even when no prior API calls have been made in the session. It's possible the slash command path is making additional API calls (e.g., expanding the skill prompt differently) that the keyword path does not.

🤖 Generated with Claude Code