Loading...
Loading...
Found 44 Skills
Use when the user asks to design multi-agent systems, create agent architectures, define agent communication patterns, or build autonomous agent workflows.
Technical documentation writer specializing in creating clear, well-structured markdown documents for algorithms, system design, interview preparation, and code documentation. Use when writing README files, algorithm explanations, system design docs, or technical guides.
Design high-level functional and technical specifications by defining scope, modules, contracts, boundaries, responsibilities, architecture models, constraints, and verification criteria.
Use for latency-sensitive systems such as realtime dashboards, market data, streaming agents, execution gateways, queues, caches, or HFT-like infrastructure where freshness and p95 latency matter.
The orchestrator and entry point for the engineering skills suite. Use this skill whenever the task involves doing engineering work to a high bar — reviewing code or a design, designing a new system or component, debugging a hard problem or running an incident, implementing a substantive change, writing documentation, or sanity-checking an approach. Use it when the user phrases things casually ("rip into this", "be brutal", "is this approach right", "what am I missing", "what would you change", "look at this") or formally ("review this PR", "audit this design"). Use it proactively for any non-trivial engineering work, before declaring something done. The skill triages the work, dispatches to the right specialty skill(s), enforces verification, and produces an evidence-backed result. The goal is to ensure no AI shortcut, sycophantic agreement, or stylistic distraction gets in the way of work that holds up to senior-engineer scrutiny.
Use this skill when designing structured interviews, creating rubrics, building coding challenges, or assessing culture fit. Triggers on interview design, rubrics, scoring criteria, coding challenges, behavioral interviews, system design interviews, culture fit assessment, and any task requiring interview process design or evaluation criteria.
Write technical reports — experiment reports, system design documents, code documentation, and internal research memos. Use when documenting technical work that doesn't fit paper format.
Choose system boundaries, architectural patterns, and tradeoffs. USE when deciding overall software shape, domain boundaries, or major technical direction.