IgorWarzocha/merchant
.agents/skills/merchant/SKILL.md
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`.
$ install --global
skillsauthnpx skillsauth add IgorWarzocha/AI-plays-Slay-The-Spire-2 merchantInstall 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:53 AM18.7s3 files scanned
SKILL.md
- name:
- merchant
- description:
- 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`.
Merchant
Use this as the shop decision workflow for STS2 runs.
View Mode Rule
Shops are hard.
- Prefer
--hardfor merchant reads by default. - Do not rely on
--easyfor shop decisions unless you are only confirming a single already-settled follow-through. - Use
--fullonly if the shop surface looks inconsistent or a state/export bug is suspected.
Interpret the modes like this:
--easyis the execution surface for an already-settled shop line.--hardis the planning surface for actually deciding what to buy, skip, remove, or leave behind.
Reason: merchant choices are dense and expensive. They combine gold, path pressure, deck shape, relic text, potion slots, and opportunity cost, so the compact view is usually too lossy for real shop decisions.
Required Reading
Read these before acting:
/home/igorw/Work/STS2/.agents/skills/merchant/references/heuristics.md/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- the current run log under
/home/igorw/Work/STS2/vault/runs
If the next node is an elite or boss, also read:
/home/igorw/Work/STS2/.agents/skills/boss-and-elite-fights/SKILL.md
Workflow
- Read the full merchant state:
- gold
- HP
- deck snapshot
- owned relics
- potion slots, including empties
- all merchant entries with real descriptions
- Classify the shop before choosing anything:
- damage-control shop
- survival shop
- forced-elite prep shop
- boss-prep shop
- value shop
- Identify the run's current bottleneck:
- weak opening hand
- no block smoothing
- no scaling
- no AoE
- bloated deck
- empty potion slots before hard fights
- Spend to solve the real bottleneck, not to maximize raw quantity.
- After every buy, re-read the merchant state before the next buy if prices, inventory, or route pressure matter.
- default to re-reading with
--hard
- default to re-reading with
- Before leaving, confirm:
- gold spent matches the intended line
- potion slots are used correctly
- no better remove or potion line was skipped accidentally
Priorities
- Forced hard fight next:
- value relics that improve setup or consistency immediately
- removes that sharpen the next shuffle
- potions if slots are open
- only buy cards that clearly improve the next fight
- Damage-control shop:
- assume the route already made a mistake or imposed a tax
- spend to survive the next few floors, not to preserve gold efficiency
- fill potion slots aggressively
- prefer consistency and bailout tools over greedy scaling
- Low-HP shop:
- prioritize survival and consistency over speculative scaling
- Comfortable shop:
- prefer one excellent purchase over multiple medium ones
Guardrails
- Do not leave a shop with empty potion slots if the next hard fight can justify filling them.
- Do not buy filler just because gold is available.
- Do not assume a familiar STS1 card or relic is equally strong in STS2; read the live text.
- Respect skip-equivalents in shops too: holding gold can be correct.
- Treat the merchant as a hard-decision surface unless you are only executing an already-settled line.
- If merchant state or post-buy settlement looks inconsistent, stop and fix the exporter or command flow before continuing.
Maintenance
Keep this skill short and practical. Move durable shopping heuristics into the owned references, then tighten this workflow when better shop patterns are discovered.
Related Skills
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/events
development
VerifiedTrustedCommunity
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.
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