Loading...
Loading...
Found 197 Skills
Subscribe to Binance Spot public market streams through UXC raw WebSocket support for trades, book ticker, depth, and ticker events with stream-specific guardrails.
Operate DefiLlama public price APIs through UXC with a curated OpenAPI schema and read-first guardrails.
Operate MEXC Spot REST APIs through UXC with a curated OpenAPI schema, HMAC query signing, and separate public/signed workflow guardrails.
Operate X API v2 through UXC with the official OpenAPI schema, OAuth2 PKCE user-context auth, app-only bearer guidance, and read-first guardrails for timeline/bookmark/post workflows.
Processes and guardrails for recruiting, scheduling, consent, and incentive fulfillment.
Kotlin language guardrails, patterns, and best practices for AI-assisted development. Use when working with Kotlin files (.kt, .kts), build.gradle.kts, or when the user mentions Kotlin. Provides null safety patterns, coroutine guidelines, data class conventions, and testing standards specific to this project's coding standards.
OKR trees, KPI dashboards, North Star Metric, leading/lagging indicators, and experiment design. Use when setting team goals, defining success metrics, building measurement frameworks, or designing A/B experiment guardrails.
Operate Slack Web API through UXC with a curated OpenAPI schema, bearer-token auth, and messaging-core guardrails.
Convert a local AGENT.md into a Claude Code optimized agent. Audits one agent against Claude Code runtime behavior, creates a per-agent DAG rewrite plan with source-backed guardrails, and optionally rewrites the frontmatter and system-prompt body so the agent is thinner, more role-specific, and better aligned with Claude's agent runtime. Use when the user says "convert this agent to Claude", "normalize this AGENT.md", "thin this agent", or "rewrite this persona for Claude Code".
Find, compare, adapt, and design repeatable AI-agent loops with explicit triggers, actions, verification, stopping conditions, guardrails, and handoffs. Use when a user asks for a loop, recurring agent workflow, automation cadence, iterative improvement process, an existing Loop Library recommendation, or help turning an outcome into a bounded copy-ready loop through a short question-led design session.
Design the standing organizing team of a recurring technical event - the structure that persists between editions. Covers legal-entity posture (none, fiscal sponsorship, own non-profit), decision-rights shape (board-plus-organizers split, domain-lead federation, consensus committee), the role taxonomy, succession and bus-factor planning, burnout guardrails, and the volunteer-to-paid-staff hiring gate. Use whenever the user mentions structuring or governing an organizing team, forming an association or non-profit for an event, splitting decision rights, organizer succession or rotation, organizer burnout, or hiring the first paid staff - even if they never say "team structure". Do NOT use for day-of staffing - use samber/dev-event-organizer-skills@event-volunteers instead.
Use when asked to "run an A/B test", "design an experiment", "check statistical significance", "trust our results", "avoid false positives", or "experiment guardrails". Helps design, run, and interpret controlled experiments correctly. Based on Ronny Kohavi's framework from "Trustworthy Online Controlled Experiments".