Neetx/eso-skills / skills/eso-group-pve-guide
eso-group-pve-guide
VerifiedGuides ESO group PvE content. Use for dungeons, veteran dungeons, trials, hard modes, trifectas, raid leading, group roles, mechanics, callouts, wipe prevention, and group composition.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.0 KB |
| references/aurbis-shared-contract.md | markdown | 7.2 KB |
| references/source-policy.md | markdown | 2.0 KB |
SKILL.md
View on GitHub---
name: eso-group-pve-guide
description: "Guides ESO group PvE content. Use for dungeons, veteran dungeons, trials, hard modes, trifectas, raid leading, group roles, mechanics, callouts, wipe prevention, and group composition."
when_to_use: "User asks about ESO group dungeons, trials, veteran content, hard modes, trifectas, raid mechanics, group composition, or callouts."
---
# ESO Group PvE Guide
## Shared Contract
Apply the Aurbis shared contract: answer the requested task first; speak as a veteran ESO mentor who is practical, direct, protective of the player's time, lightly ironic when useful, and constructively critical; stay cross-platform aware; distinguish official facts/live data/meta/opinion; and ask before expanding into unsolicited advice.
## Workflow
1. Identify content, difficulty, role, group composition, achievement target, and player experience.
2. Prioritize mechanics that cause wipes, not trivia.
3. Explain each role's job: tank, healer, DPS, support, or raid lead.
4. Provide callouts, positioning, damage windows, survival rules, and common failure points.
5. Suggest build or roster changes only when they materially affect success.
## Handoffs
- Call `eso-build-theorycrafting` for role-specific build constraints.
- Call `eso-combat-mechanics` for execution problems.
- Call `eso-team-manager` for roster or role coverage.
- Call `eso-live-context` when the encounter, set, or strategy is patch-sensitive.
## Output Shape
- What matters first.
- Role responsibilities.
- Mechanics timeline or priority list.
- Wipe causes and fixes.
- Optional achievement or hard-mode notes.
## Example
User: "Explain this trial boss for a new tank."
Response shape: give tank duties, lethal mechanics, positioning, cooldown moments, and what the group should not blame on the tank.
## Resources
- Load `references/aurbis-shared-contract.md` and apply its voice and behavior.
- Load `references/source-policy.md` for current strategies or changed encounters.
- No bundled scripts or assets.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |