Loading...
Loading...
Found 6,199 Skills
Load PROACTIVELY when task involves database design, schemas, or data access. Use when user says "set up the database", "create a schema", "add a migration", "write a query", or "set up Prisma". Covers schema design and normalization, ORM setup (Prisma, Drizzle), migration workflows, connection pooling, query optimization, indexing strategies, seeding, and transaction patterns for PostgreSQL, MySQL, SQLite, and MongoDB.
Use this skill when managing git branches, releases, or hotfixes according to the Gitflow workflow. It enforces naming conventions and synchronization policies.
Deep travel research workflow for museums and ancient architecture. Input a city name to automatically generate a structured knowledge document (org-mode) and portable reference cards (PNG). It covers historical background, museum highlights, archaeological significance, and architectural heritage. This workflow is activated when users say '旅行研究', '博物馆功课', '古建功课', 'travel research', '出发前功课', or provide a city name with the intention of conducting in-depth cultural travel preparation.
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for reverse proxies, Host headers, forwarded headers, vhost routing, websocket upgrades, path-prefix rewriting, base-URL derivation, and multi-node route resolution. Use when the user asks which host or container serves a route, why a public-looking domain still belongs to the sandbox, how headers or proxies change behavior, or how a route resolves across proxy, container, and worker boundaries. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.
Zixflow integration. Manage data, records, and automate workflows. Use when the user wants to interact with Zixflow data.
Platform9 integration. Manage data, records, and automate workflows. Use when the user wants to interact with Platform9 data.
Points agents to the public Phalcon Compliance documentation portal for compliance-oriented blockchain investigation and monitoring workflows. Use when the user asks about Phalcon Compliance docs, transaction-monitoring-style tooling references, or where to read product documentation alongside crypto-investigation-compliance—not for legal advice or unsubstantiated vendor claims.
This skill guides development of full-stack features on EdgeOne Pages — Edge Functions, Cloud Functions (Node.js / Go / Python runtimes), Middleware, KV Storage, and local dev workflows. It should be used when the user wants to create APIs, serverless functions, middleware, WebSocket endpoints, or full-stack features specifically on EdgeOne Pages — e.g. "create an API", "add a serverless function", "write middleware", "build a full-stack app", "add WebSocket support", "set up edge functions", "use KV storage", "create a Go API", "build a Python backend", "use Flask/FastAPI/Gin on EdgeOne Pages". Do NOT trigger for framework-native features (Next.js API routes, Next.js middleware, Nuxt server routes) or generic Express/Koa development outside an EdgeOne Pages project. Do NOT trigger for deployment — use edgeone-pages-deploy instead. Do NOT trigger for other platforms (Cloudflare Workers, Vercel Functions, AWS Lambda).
Standard workflow for pulling updates from main or other branches on multi-contributor projects (including Dune apps) without silently discarding work. Guides fetching/merging, requires listing merge conflicts explicitly, analyzing ours vs theirs using conversation history and repo context, presenting prioritized recommendations, and obtaining user answers before editing conflict markers or completing the merge. Triggers: pull main, merge main, merge origin, rebase, merge conflict, unmerged paths, both modified, integrate branch, sync with main, git merge abort, resolve conflicts, UU status, theirs vs ours, feat branch update.
Interactive workflow to create Commerce B2B Stores and retrieve storefront metadata. Use when users want to: create B2B Commerce stores, build Commerce storefronts, set up B2B stores from Vibes, retrieve Commerce metadata, deploy Commerce experiences, work with DigitalExperienceBundle for Commerce.
Guides deal operations administration—quote-to-cash coordination, deal desk intake and routing, CRM opportunity hygiene, order form and SOW assembly, approval workflows, signature tracking, and handoffs to legal, finance, and provisioning after customer signature. Use when processing a sales deal, preparing order paperwork, running deal desk checklist, fixing CRM stage/fields, coordinating signatures, or closing the loop post-signature—not for contract legal redlines (commercial-counsel), board or equity approvals (corporate-counsel), ASC 606 accounting (senior-revenue-accountant), support tickets after go-live (customer-ops-specialist), or M&A/financing closing (transaction-manager).
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.