Loading...
Loading...
Found 854 Skills
Nitro is the framework-agnostic server toolkit (powering Nuxt) for building and deploying web servers anywhere. Use when working with nitro.config, server routes/event handlers, route rules, caching, storage, tasks, websockets, or deploying to Node/Bun/Deno/Cloudflare/Vercel.
Capture ideas, tasks, notes, and seeds to their destination
Meta-router for the tmux-agent-tools plugin. Invoke BEFORE choosing a wrapper or delegating any tmux-agent work — it decides inline vs worker, picks the right script, and points at the canonical capability table. Even a 1% chance this applies means invoke it.
Top-level map of the skill fleet, for "which skill does this need?" when the answer is not obvious. Invoke when a task's ownership is UNCLEAR or it spans MULTIPLE domains. It routes intent → the right router / skill / recipe and names how to invoke each. When the primary goal already names a domain, enter that domain router or member directly instead. Curates the ADOPTED surface only; the full installed roster lives in the skill manifest.
Route run.cloud work to the focused mobile-session or sandbox skill. Use when a request mentions run.cloud generally, spans both products, or does not yet distinguish remote iOS and Android sessions from microVM sandboxes.
Primary entry point for topic audience identification in Eva Audience Finder 2.2.8. Only use this when the user explicitly calls /eva-audience-finder, mentions "Topic Audience Identifier", or clearly asks questions like "Who is the audience behind this topic, who does it really resonate with, who is this topic for, who cares about it". Break down topics, buzzwords, titles, phenomena or comments into specific audiences, cognitive gaps, user problems and subsequent content entry points. Do not take over general topic discussion requests such as "I have an idea for a topic", "Help me look at this topic", "Want to chat"; these should still be handled by eva-think. Do not directly generate complete title proposals or full drafts.
Lightweight PRIMARY for multi-type orchestration of CTF / AWD / security labs. Hand over control to the sidecar CTF-Sandbox-Orchestrator. Use this when the user mentions CTF, AWD, security labs, or competition questions, and no more specific pwn/APK/IDA route has been activated.
Read at the start of every session, before any other skill, and again after any compaction, model change, resume, or handoff. Routes the work to the right skill in this collection and holds one person's decisions rather than a recommendation: where generated files go, which skill wins when two match, which borrowed collections are trusted, where the ceremony is not wanted, and what the portable skills deliberately leave open. Machine-specific on purpose. Not a summary of the other skills, and not a substitute for reading the one that matched.
Meta-router and multi-agent conductor for design work that needs skill selection or a multi-stage pipeline — visual frontend (web pages, landing pages, product UI, mobile screens), data visualization, HTML deliverables (reports/diagrams/plans), artifacts, motion polish, and module/API interface design. The STABLE unified entry point — member skills churn underneath, this router discovers them live, picks one direction authority, delegates image-generation stages to Codex workers, and closes every pipeline with an evidence-first anti-slop quality loop. Do NOT invoke for a one-line CSS/copy tweak, for backend-only work, or when the user explicitly names a single member skill for a single-skill-sized task — those go direct.
Manage GSD workspaces — create, list, or remove isolated workspace environments
Recommend the right trading workflow, skillset, API profile, and setup path from a natural-language goal. Use this as the on-ramp when a user expresses a trading or investing goal and needs to know which skill/workflow to use, where to start, or whether something works without paid API keys — e.g. "where do I start", "which skill should I use", "I want to swing trade only when the market is favorable", "what works without API keys", "どれを使えばいい", "API キー無しで 使えるものは". Routes and explains only; it never executes trades or auto-runs other skills, and it is honest when no workflow has shipped yet.
Dynamic path segments ($paramName), splat routes ($ / _splat), optional params ({-$paramName}), prefix/suffix patterns ({$param}.ext), useParams, params.parse/stringify, pathParamsAllowedCharacters, i18n locale patterns.