IgorWarzocha/events
.agents/skills/events/SKILL.md
Use this when the current screen is an event or when planning an event line from the real run state. Trigger it before choosing any event option, especially when the event offers generated cards, relics, gold-for-HP trades, removes, transforms, or branch-defining risk/value choices.
$ install --global
skillsauthnpx skillsauth add IgorWarzocha/AI-plays-Slay-The-Spire-2 eventsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 12:52 AM24.9s4 files scanned
SKILL.md
- name:
- events
- description:
- Use this when the current screen is an event or when planning an event line from the real run state. Trigger it before choosing any event option, especially when the event offers generated cards, relics, gold-for-HP trades, removes, transforms, or branch-defining risk/value choices.
Events
Use this as the event decision workflow for STS2 runs.
Required Reading
Read these before acting:
/home/igorw/Work/STS2/.agents/skills/act-start/references/planning.md/home/igorw/Work/STS2/.agents/skills/act-start/references/rewards-and-deck-shape.md/home/igorw/Work/STS2/.agents/skills/events/references/heuristics.md/home/igorw/Work/STS2/.agents/skills/events/references/known-events.mdif the current event is already documented there- the current character skill for the run
- the current run log under
/home/igorw/Work/STS2/vault/runs
If the event is immediately upstream of an elite or boss, also read:
/home/igorw/Work/STS2/.agents/skills/boss-and-elite-fights/SKILL.md
Workflow
- Read the full event state before choosing:
- title
- event text
- every option with concrete payload text
- trust the live option payload text first; only fall back to local references if the event state is still not concrete enough to choose
- Reconstruct the live run context:
- HP and max HP
- gold
- deck shape and current bloat
- relics and potion slots
- map pressure after the event
- the run's current bottleneck
- Classify the event before choosing:
- damage-control event
- value event
- deck-quality event
- pathing enabler
- hard-fight prep
- trap disguised as value
- Judge each option by this run, not by generic familiarity:
- what it fixes right now
- what it worsens
- what relics, potions, or deck payoffs it synergizes with
- whether it changes the next hard-fight plan
- If any option payload is not concrete, stop and fix the exporter before choosing.
- After choosing, re-read the resulting state if the event changes deck, relics, potions, HP, gold, or pathing permission.
Guardrails
- Do not evaluate an event in isolation from the route.
- Do not take short-term value and then path like a high-roll deck unless the event actually earned that pivot.
- Do not ignore current relic context. Generated cards and event rewards must be judged against the relic stack already in play.
- Do not assume STS1 event instincts are enough; use them as heuristics only.
- If a new repeatable event heuristic appears, tighten this skill or its references instead of leaving it buried in a run log.
Maintenance
Keep this skill short and operational. Durable event-specific lessons belong in the owned references; this skill should stay focused on how to think before choosing.
Related Skills
IgorWarzocha/merchant
development
VerifiedTrustedCommunity
Use this when the current screen is a merchant or when planning a shop line from map pressure, gold, deck state, relics, and potions. Trigger it before buying, before leaving a shop, and when a forced elite or boss makes the shop an immediate survival checkpoint. Shops are hard decisions, so prefer reading them with `--hard`.
1SKILL.mdUpdated Apr 16, 2026
IgorWarzocha/learning-loop
testing
VerifiedTrustedCommunity
Use this when playing in this repo and you need to keep the run log, reference notes, mechanic notes, and strategy notes updated as durable learning. Trigger it during live runs, immediately after meaningful floors, immediately after elite or boss fights and boss rewards, when a new boss/elite/event/mechanic appears, when a fight needs STS1 parallels to understand what it is testing, and when ending a run so the post mortem can be reconciled against Compendium -> Run History before the final rewrite.
1SKILL.mdUpdated Apr 16, 2026
IgorWarzocha/ironclad
testing
VerifiedTrustedCommunity
Use this when the current run is Ironclad. Trigger it on new runs, after automated compaction summaries, and for Ironclad card, route, shop, reward, and combat decisions.
1SKILL.mdUpdated Apr 16, 2026
IgorWarzocha/combat
testing
VerifiedTrustedCommunity
Use this for combat turn planning and execution. Trigger it before taking combat turns, when deciding whether a turn is easy or hard, when a fight presents setup vs tempo tension, when cost changes or free-card effects appear, and whenever you need general combat heuristics that are not boss-or-elite specific.
1SKILL.mdUpdated Apr 16, 2026