# Skill Identifier

> When to trigger this skill - be specific about the scenarios where Claude should use it

- Skill: `viperjuice/skill-identifier` (Agent Skill)
- Install (CLI): `npx skillmds@latest add viperjuice/skill-identifier`
- Raw SKILL.md: https://api.skillmd.com/api/skills/viperjuice/skill-identifier/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: ViperJuice (https://skillmd.com/u/viperjuice)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/viperjuice/skill-identifier

---


# Skill Name

Brief overview of what this skill provides.

## When to Use

Specific triggers that should activate this skill:
- User asks to [do X]
- User mentions [keyword Y]
- User wants to [accomplish Z]

## Instructions

Clear, concise instructions for Claude to follow when using this skill.

### Step 1: [Action]

Detailed guidance on the first step.

### Step 2: [Action]

Detailed guidance on the second step.

## Examples

```bash
# Example command or code snippet
```

## Notes

- **references/**: Place detailed documentation here (loaded only when needed)
- **scripts/**: Place reusable scripts here for deterministic operations
- **assets/**: Place templates, config files, or other resources here

## Important Principles

1. **Directive-only** — no narratives, war stories, anecdotes, or stats (e.g. "47% of sessions…", "we got burned last quarter…"). Rules only, in imperative form. If a rule needs a reason, state it in one clause, not a paragraph.
2. **Description is for triggering** — describe *when* the skill fires and *what* it does. Never cite metrics, session counts, or incident rates.
3. **Keep SKILL.md concise** — you share the context window with the conversation. Target <300 lines; move long rationales to `references/`.
4. **Use references/ for details** — link to them rather than duplicating content.
5. **Scripts for consistency** — Python/Bash for operations that need exact behavior.