Loading...
Loading...
Found 40 Skills
CRITICAL: Use for makepad-skills self-evolution and contribution. Triggers on: evolve, evolution, contribute, contribution, self-improve, self-improvement, add pattern, new pattern, capture learning, document solution, hooks, hook system, auto-trigger, skill routing, template, pattern template, shader template, troubleshooting template, 演进, 贡献, 自我改进, 添加模式, 记录学习, 文档化解决方案
Load plugin context from handoff files to resume work. Invoked by /continue command, 'resume [PluginName]', 'continue working on [PluginName]', 'pick up where I left off with [PluginName]', or 'show me where [PluginName] is at'. Locates handoff across 2 locations, parses state, presents summary, and routes to appropriate continuation skill.
Global Agent rules, including language, response style, debugging priority, engineering quality baseline, mandatory code metric limits, security baseline, test verification standards and Skills routing table. Applicable to all programming tasks.
Primary router skill for broad .NET work. Classify the repo by app model and cross-cutting concern first, then switch to the narrowest matching .NET skill instead of staying at a generic layer.
GitLab automation hub. Routes requests to specialized skills. ALWAYS use this skill when: (1) any GitLab operation, (2) unsure which skill to use, (3) multi-step GitLab workflows. Start here for any gitlab task.
Use this skill when the user says "/li", or when the request is related to content creation but the intent is ambiguous and the user is unsure which tool to use. As the main entry point of the li Toolkit, it judges the intent and routes to the corresponding specialized skill. Do NOT trigger: When the user's request clearly matches a specific li-* skill (e.g., "write a script" → li-writer, "deepen a topic" → li-topic), directly trigger the corresponding skill instead of this entry. DO NOT trigger for non-content-creation tasks. Use when the user says "/li" or the intent is ambiguous across multiple li-* tools.
Self-report agent issues by logging user corrections for later review, then resume with the correct skill. Use when a user says "don’t do that", "stop doing X", "always do Y", or requests self-correction.
Architectural reference for WorkOS AuthKit integrations. Fetch README first for implementation details.
Galaxy project development conventions and skill routing guide. ALWAYS load this skill when working in a Galaxy codebase. Routes to appropriate skills: use /galaxy-db-migration for database/Alembic/schema changes, /galaxy-api-endpoint for creating REST API endpoints/FastAPI routers, /galaxy-testing for running or writing tests, /galaxy-linting for code formatting/linting/type checking. Use galaxy-explorer agent for codebase architecture questions.
CRITICAL: Use for ALL Rust questions including errors, design, and coding. HIGHEST PRIORITY for: 比较, 对比, compare, vs, versus, 区别, difference, 最佳实践, best practice, tokio vs, async-std vs, 比较 tokio, 比较 async, Triggers on: Rust, cargo, rustc, crate, Cargo.toml, 意图分析, 问题分析, 语义分析, analyze intent, question analysis, compile error, borrow error, lifetime error, ownership error, type error, trait error, value moved, cannot borrow, does not live long enough, mismatched types, not satisfied, E0382, E0597, E0277, E0308, E0499, E0502, E0596, async, await, Send, Sync, tokio, concurrency, error handling, 编译错误, compile error, 所有权, ownership, 借用, borrow, 生命周期, lifetime, 类型错误, type error, 异步, async, 并发, concurrency, 错误处理, error handling, 问题, problem, question, 怎么用, how to use, 如何, how to, 为什么, why, 什么是, what is, 帮我写, help me write, 实现, implement, 解释, explain
This skill should be used when the user asks to "create a workflow", "run a workflow", "design a task pipeline", "execute a workflow", "resume a workflow", or "plan a multi-step automation". Creates and executes custom, repeatable workflows with multiple steps that can each use different AI models and run in parallel waves. Triggers on: 'create workflow', 'run workflow', 'execute workflow', 'workflow plan', 'workflow run', 'resume workflow', 'multi-step workflow', 'task pipeline', 'automation'.
Use whenever a beo session is starting, resuming, recovering from interruption, checking status, deciding what to do next, or when the correct beo skill is not obvious. This is the default bootstrap and routing entry point for the beo pipeline. Use first for prompts like "continue", "resume", "what's next?", "status?", "pick this back up", "where are we?", or any new feature request where the current phase is unclear.