Loading...
Loading...
Found 9,859 Skills
Research and compare destinations with source-backed Gezgin data, and coordinate connected Gezgin workflows for shortlists, profile context, member discovery, follows, presence, and casual meetups. Use when a user asks for destination research, personalized travel planning, Gezgin community discovery, or meetup creation and management.
Autonomous execution workflow for complex long-running tasks. This applies to scenarios where users have a complex or vague task (e.g., "Help me figure out X / Help me evaluate Y / Help me organize this pile of stuff / Help me compare N solutions / Help me run a research"), and expect the AI to decompose, execute, and verify the task on its own, only reaching out to the user at critical moments. It enables unattended autonomous execution for 1-2 hours through the process of "Task Confirmation → Task Queue → Batch Execution → Periodic Queue Verification → Triggered Reporting". It is triggered when users say phrases like "Help me figure out / Evaluate / Organize / Compare / Run a research / Run it on your own don't bother me / Long-running task / Run autonomously". **Not applicable to**: UI design (use design-exploration), to-do priority judgment (use priority-judge), article writing (use writing-assistant), backlog management (use backlog-manager), vision exploration (use vision-exploration), naming (use product-naming), implementation coding tasks with clear specs (code directly).
Integrated Collaboration for PRD + Executable Test Cases (Development Paradigm v2 Definition Section). Input is a finalized split task/requirement; outputs 4 files: PRD-MD and Test Case-MD (fact sources for AI) + two template-based review HTMLs (for human review, strictly 1:1 with MD). Co-write and iterate with users: autonomously read code after understanding requirements before writing; story-driven + phased single-point confirmation; UI stories include ASCII wireframes + Mermaid capabilities. Triggers: organizing/writing/refining PRDs, requirement documents, user stories, acceptance criteria, test cases, test benchmarks, test plans. Not applicable to: ambiguous requirements not split into tasks (use issue-pool first), unexplored interface solutions (use design-exploration first, whose output requirement-summary.md is exactly the input for this skill), small requirements for modifying an already launched feature (use req-change-workflow), long HTML articles/retrospectives/reports for human reading (use readable-output), project-level framework plans and version roadmaps (use issue-pool), writing code or running tests (this skill only produces documents, does not implement or execute cases).
Eva Link standalone local workflow entry point. Handles existing Link calls, integrating prompts/SOPs/private methodologies into Eva, customizing Links, and checking Links. Triggers: /eva-link, /eva-link-builder, /eva-link-diy, /eva-link-doctor, custom Eva-skill, create my own Link, integrate prompts into Eva, check local Links, use one of my Links.
Backend architecture guidance. Use when planning, building, or migrating an API or backend; choosing between Functions, Services, containers, Workflow, Queues, and Marketplace databases; or selecting a supported backend framework or runtime.
Use when the user needs to search or navigate code with Sourcegraph MCP tools. Provides disciplined search workflows for finding implementations, understanding systems, debugging issues, fixing bugs, and reviewing code.
Coordinate Codex sub-agents for substantial multi-step work. Requires Codex collaboration tools and the listed Luna, Terra, and Sol model families. Use proactively when a request involves two or more separable workstreams; repository exploration plus implementation or verification; production diagnosis across logs, code, and live systems; PR or release review; multi-source analytics or research; or long-running tests, transfers, workflows, and monitors that should not block user communication. Assign bounded leaf work to Luna and collaborative or high-stakes work to Terra or Sol. Skip only trivial single-step or tightly sequential tasks.
Generate images and videos through the currently installed Media.io CLI. Use for text-to-image, image-to-image, text-to-video, image-to-video, reference-to-video and published workflows that appear in the live `mediaio model list` or `mediaio workflow list`. Effects may be used only when their parameters have been independently verified because the current CLI exposes `effect list` but not `effect get`. Always discover the exact job type and schema before submission. Use the human-readable discovery output, upload local files before generation, submit with `generate create`, and wait with the separate `generate wait` command. On hosts that sandbox local command networking, the first networked `mediaio` or `curl` Shell/Bash tool call must request host approval before process launch. Never probe network availability by running it in the default sandbox.
Gate 0 research phase for pre-dev workflow. Dispatches 4 parallel research agents to gather codebase patterns, external best practices, framework documentation, and UX/product research BEFORE creating PRD/TRD. Outputs research.md with file:line references and user research findings.
Branch completion workflow - guides merge/PR/cleanup decisions after implementation is verified complete.
Mandatory orchestrator protocol - establishes ORCHESTRATOR principle (dispatch agents, don't operate directly) and skill discovery workflow for every conversation.
12 pre-dev workflow skills + 4 research agents organized into Small Track (4 gates, <2 days) and Large Track (9 gates, 2+ days) for systematic feature planning with research-first approach.