krzysztofdudek
UserOne file. Your AI coding agent becomes a scientist. 30+ experiments while you sleep.
Categories
Indexed Skills (4)
researcher
Use when user wants to optimize or tune something measurable through repeated experiments — "make X faster", "improve [metric]", "find best config", "iterate overnight", "run experiments until it hits N". Triggers on quantitative goals (build time, latency, pass rate, accuracy) or qualitative ones scoreable against a rubric (prompt quality, doc parsing). Skip for one-shot bugs with a clear fix or tasks where the user wants direct implementation without exploration.
urd
Use when transitioning from a plan, design doc, or spec into implementation - optimize for accuracy over speed and cost; ask the user when confused, when the spec is ambiguous, or when tempted by a hack rather than guessing or working around it
liaison
Use whenever interacting with a user about the codebase or product — covers both change requests (feature, fix, refactor that touches user-visible behavior, account management, data export or deletion, billing, payments, notifications, auth, retention, sharing, or compliance like GDPR / PCI / HIPAA) AND pure questions, explanations, code walkthroughs, and translations between technical and user-visible terms ("how does X work?", "why does the system do Y?", "what happens if Z?"). Use proactively when an operation could be destructive, irreversible, or affect users other than the requester. The plain-language discipline, no-time-estimates rule, and question discipline apply to every user-facing turn regardless. Skip only when a complete written technical specification is attached for verbatim implementation, when performing a pure internal refactor with no user-visible effect, or when continuing a tightly-scoped fix where intent is already locked.
ratatoskr
Use on every user-facing turn, always — load it before you say anything to any user about this codebase or product. It is a standing discipline for how you communicate, not a tool tied to a particular activity; there is no turn on which you skip loading it. It governs change requests (feature, fix, refactor touching user-visible behavior, account management, data export or deletion, billing, payments, notifications, auth, retention, sharing, compliance like GDPR / PCI / HIPAA) and equally pure questions, explanations, code walkthroughs, and technical/user-visible translations. Plain-language discipline, the no-ceremony / no-machinery-names rule, no time or effort estimates, and question discipline apply on every turn without exception. Load it even when a written spec says implement verbatim, even for a pure internal rename, and even for an already-locked fix — loading is free; the skill itself decides how light to keep the turn, escalating to confirmation gates only when an operation is destructive, irrevers
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.