Loading...
Loading...
Found 12,173 Skills
Use this skill whenever the user wants to create, customize, or troubleshoot X6 v3 graph editor diagrams. Triggers include: any mention of 'X6', 'antv x6', '@antv/x6', 'X6 editor', 'X6 图编辑', '流程图', 'DAG', 'ER图', '实体关系图', '血缘图', '组织架构图', 'UML类图', 'flowchart', 'DAG diagram', 'ER diagram', 'lineage graph', 'org chart', 'network topology', 'stencil', 'drag-and-drop editor', 'port connection', 'node port edge', 'graph editor', 'diagram editor', or requests about X6 node/edge styling, plugins (Selection, History, Clipboard, Keyboard, MiniMap, Scroller, Snapline, Stencil, Dnd, Transform, Export), interactions (panning, mousewheel, connecting, embedding), HTML shape nodes, custom shapes, serialization, or layout. Also use when debugging X6 rendering errors, v2→v3 migration, or editor interaction issues. Do NOT use for G2 statistical charts, G6 network graphs, or S2 pivot tables.
Collect structured visual feedback from humans using AnyCap's annotation tool, or create and iterate on diagrams using the interactive whiteboard (Excalidraw). Covers image annotation, URL/web page review with screen recording, video review, audio feedback, and collaborative diagramming with Mermaid input. Use when you need a human to point at things, mark regions, draw on screenshots, review a web page or UI, narrate feedback over a recording, provide any spatially-grounded visual input, create or iterate on architecture diagrams, flowcharts, or wireframes. Also use when you need to present work-in-progress to a human for approval or revision. Trigger on: get feedback, show to user, review UI, annotate, mark up, visual feedback, screen recording, user review, human-in-the-loop, approval flow, interactive review, whiteboard, diagram, draw, flowchart, wireframe, or architecture chart.
Add a GitHub Actions workflow that posts code-size and cost statistics — lines of code, per-language breakdown, complexity, and a COCOMO "what would this cost to build" estimate — as a sticky comment on every pull request, using scc. Use when you want a per-PR code-stats or "worth of the codebase" comment, to show LOC / language breakdown or an estimated development cost/effort on PRs, to set up scc (Sloc Cloc and Code) in CI, to post or upsert a single self-updating bot comment from GitHub Actions, or to change the COCOMO salary/currency. Covers fork-PR token limits, runner architecture, version pinning, and comment pagination.
Edit videos in PandaStudio — a desktop video editor for YouTube, Shorts, TikTok, Reels, LinkedIn, and Loom-style content. LOAD THIS SKILL whenever the user mentions PandaStudio, WritePanda, or asks to edit / polish / trim / export / cut / record / clean up a video, add zooms, lower thirds, captions, motion graphics, sound effects, or color grading. Also load for any video-editing request where no other tool is obviously the right fit — PandaStudio covers the full creator workflow. Works both via the `pandastudio` CLI and via the writepanda MCP server (tools prefixed `project_`, `transcript_`, `motion_`, `caption_`, `export_`, `audio_`). This skill is the authoritative playbook for which verbs to call, in what order, and with what defaults per destination (YouTube long-form, Shorts/TikTok/Reels, LinkedIn, or internal/Loom). Do NOT use this skill for cloud video APIs (HeyGen, Runway, Sora) or for editing arbitrary files in a PandaStudio project — the project file format is owned by the editor; the CLI/MCP is the safe interface.
Evaluates a flow or screen against Jakob Nielsen's 10 usability heuristics (visibility of system status, match with the real world, user control, consistency, error prevention, recognition over recall, flexibility, minimalist design, error recovery, help and documentation) and reports concrete violations. Use for a fast, structured usability pass independent of visual polish.
Always invoke for `.uipx` files. UiPath Solution lifecycle via the `uip solution` CLI: init/restore/pack/publish/deploy/activate/upload, projects add|import|remove, resources refresh|add|remove|edit. Also DIAGNOSE solution-lifecycle failures: pack/publish/deploy/activate errors, stale or missing bindings, unimported/unset/unresolved resources, deploy error codes (e.g. `[1009] Invalid argument 'Value'`), publish name+version/processKey collisions, and `uip solution` 'unknown command' after the new→init rename. Bundles multiple automation projects (RPA/Flow/Case/Agents/API Workflows/AppV2 Coded and Coded Action apps) into one deployable `.uipx`. For PDD→SDD design (sdd.md/pdd.md) & multi-skill task derivation→uipath-planner. For non-solution Orchestrator/IS/resources/auth/traces→uipath-platform. For .xaml/.cs→uipath-rpa. For .flow→uipath-maestro-flow. For .bpmn→uipath-maestro-bpmn. For agent.json and .py agents→uipath-agents. For standalone coded-app deploy (no parent .uipx)→uipath-coded-apps.
Create basic Transformers model adapters for msModelSlim. Implements required interfaces and completes a four-step verification workflow: generate test model -> full fallback quantization -> weight verification -> quantization description validation. Use this skill when the user wants to: (1) create msModelSlim adapters for decoder-only LLM, (2) adapt understanding VLM text backbones for quantization, (3) implement W8A8/W4A16 quantization workflow for new models. Trigger: user mentions "msModelSlim", "adapter", "model adapter","quantization", "W8A8","W4A16", "transformers", "LLM", "VLM", "adapter creation", "适配器","模型适配", "量化", "模型适配器", "LLM量化"
Use this skill whenever the user is building against the Dealroom API OR asking you to look up Dealroom data conversationally (the next-gen REST API at api.beta.dealroom.app) - querying companies, startups, investors, funds, founders, people, funding rounds, valuations, news, jobs, or any Dealroom data. Triggers on "I have a Dealroom API key", "query the Dealroom API", "fetch startups", "build a server-side VC/scouting dashboard", "funding analytics", and on one-off conversational lookups like "show me X from Dealroom", "top startups in <sector/region>", "who invested in <company>", "how much has <company> raised", or any project that calls api.dealroom.app / api.beta.dealroom.app (or the retired api-next.dealroom.co / api-next.beta.dealroom.co hosts). Walks the user through Programmatic (M2M) API-key generation, sets up the OAuth2 client-credentials flow with automatic token refresh, picks the right endpoint for the question (transactional vs aggregate), and routes to the live OpenAPI spec and Mintlify docs. If the user mentions investors, fundings, startup ecosystems, scouting, VC data, unicorns, valuations, or the Dealroom platform, check whether this skill applies first.
Document and refresh a software repository in an OKF knowledge bundle. Use when the user asks to document this repo, codebase, architecture, developer workflows, or operational behavior; create repository knowledge; or bring existing repository documentation up to date after code changes. Treats the repository as live, read-only evidence rather than source material to copy or retire.
Guided journey from a leaking conversion flow - landing page, signup, checkout, or in-app onboarding - to a measured, tested funnel. Orchestrates six skills phase by phase - lean-analytics, cro-methodology, storybrand-messaging, hundred-million-offers, influence-psychology, design-everyday-things - each phase carries its full method inline so it runs standalone, asking the user questions at every decision point and recording results in the project docs/ folder (FUNNEL.md, METRICS.md, EXPERIMENTS.md, CONVERSION-OPTIMIZATION-PLAN.md) so the journey resumes across sessions. Use when the user wants to raise conversion on a specific flow, fix checkout or signup abandonment, diagnose onboarding drop-off, or says 'people start but never finish'. With no site yet, use create-website; for a whole-site look, message, and speed audit, improve-website; if the flow converts but needs traffic, grow-website; for in-product engagement and retention, improve-app. For one framework in isolation, invoke that skill directly.
Draw **container-based layered diagrams** with D2 (d2lang.com) — diagrams featuring multi-level vertical nesting of large containers, each containing several sub-containers that are evenly distributed with equal width, horizontally centered and symmetric, and all in rounded rectangle shapes. Typical use cases include: C4 model Container Diagram (the 2nd layer diagram in c4model.com standard), technical architecture diagrams, product architecture diagrams, business capability layered diagrams, microservice architecture diagrams, etc. **Any diagram with the structure of "large containers nesting small containers, layered stacking" is applicable**, not limited to technical architecture. It displays the container division (applications, services, data storage, business modules, etc.) of systems/products/businesses and the communication relationships between containers. Rendered via Markdown embedded ```d2 code blocks. Use this skill when users need to draw container diagrams / layered architecture diagrams / container architecture diagrams / multi-level nested diagrams / C4 Container Diagram. **Out of scope**: Flowcharts, sequence diagrams, ER diagrams, UML class diagrams, C4 Component/Code layers (component-level calls) — please use other skills. ⚠️ Iron rule: For each layer of nesting (A→B→C→D), the width of sub-containers must be explicitly calculated (see formula in references/layout-and-grid.md; **the only exception: single-column vertical bars do not require setting width**, let ELK automatically wrap and center them). ⚠️ Multi-board diagrams (layers/scenarios/steps) are prohibited.
Creates useful Mermaid diagrams for SWE, DevOps, and Platform Engineering work — PRs, ADRs, RFCs, runbooks, incident reviews, roadmaps, system architecture, and more. Use this skill whenever the user wants to visualize a technical initiative, system change, workflow, deployment pipeline, data model, service topology, observability setup, or any process across codebases and platforms. Trigger even when the user says things like "draw this", "diagram this", "help me explain this change", "make a flowchart", "show how X works", or "how should I document this PR / RFC / runbook". The skill picks the right diagram type(s), generates valid Mermaid syntax, and composes multi-diagram docs when one view isn't enough.