Loading...
Loading...
Found 335 Skills
AI-native tutor and onboarding workflow for the MCPA (Model Context Protocol Associate) certification in AI Engineering from Scratch. Use when a learner wants to prepare for the MCPA, resume their certification path, learn the next lesson interactively, run and verify practical labs, take the diagnostic or a full mock, or remediate weak exam domains from GitHub with Claude Code, Codex, ChatGPT, Cursor, or another agent.
Read-only audit of performance and reliability — event-loop discipline, streaming and backpressure, memory and CPU diagnostics, shutdown/timeout/job habits, resilience topology (circuit breakers, retry budgets, queue bounds), and frontend delivery (Core Web Vitals, bundle size, hydration) — with evidence per finding and a SHIP / FIX / BLOCK verdict. Use when a service or page is slow, memory climbs, tail latency is bad, a worker OOMs, before a load event, or 'почему тормозит'. Measures and reports; rewrites no hot paths. Do not use for retry/idempotency contracts (awesome-error-standards) or render style rules (awesome-code-standards).
Diagnose why an application deployed by qianwenai-deploy to the Aliyun China site (aliyun.com) is unavailable or significantly slower, and perform a safe recovery only after the user explicitly confirms it. Read the .qianwenai-deploy state file in the project directory to identify ECS (and optionally RDS MySQL) resources, begin with minimal read-only diagnostics, and then propose only one recovery action at a time (starting the ECS instance, restarting the application service, or reloading Nginx), explaining the impact and obtaining confirmation before each action. Use cases: the user says the application will not open / returns 502 / cannot connect to the database, or requests a restart and confirmation that the application has recovered. Do not use: there is no .qianwenai-deploy state file; the target is the Aliyun International site (use qwencloud-operate); or the user only wants a status/cost overview (use qianwenai-observe).
Use when a Scenario user wants to report a bug or request a change, on the public tracker at github.com/scenario-labs/skills or by email to support@scenario.com: turning a failed generation, MCP tool error, or unclear skill into a reproducible report, collecting trace ids with diagnostics_run, stripping keys, signed asset URLs, and personal data, asking before sharing a team or project id, or building a prefilled issue URL. Keywords: file an issue, feature request, feedback.
Apply and diagnose Rust style, rustfmt, Clippy, compiler diagnostics, Edition migrations, lint policy, idiomatic control flow, error handling, allocation behavior, production Rust conventions, and the Rust API Guidelines ↔ Clippy lint mapping. Use when users ask to format or lint Rust, fix warning or error codes, migrate editions, review unwrap or clone usage, improve idioms, map a C-* API guideline rule to the enforcing Clippy lint, or establish CI quality gates. Route API shape decisions (naming conventions, type/trait design, module layout, full C-* guideline review) to the rust-api-design skill.
Create Earth2Studio prognostic (time-stepping forecast) model wrappers. Do NOT use for diagnostic models, data sources, or installation.
Review failed Nx Cloud CI pipeline executions and group recurring, evidence-based failure patterns. Use this skill whenever a user asks about failed CI pipelines, recurring task failures, failed CIPEs, a CI failure review, or a last-24-hours CI report. Use the nx-cloud-api skill for every Nx Cloud read. This read-only skill separates task, workflow, agent, timeout, cancellation, and unknown cases. It suggests diagnostic next steps without changing systems.
Make Chalk Python resolvers statically accelerable. Use when the user asks to accelerate resolvers, fix static-acceleration diagnostics, check why a resolver "can't be accelerated", or speed up Python feature pipelines in a Chalk project (a repo with chalk.yaml/chalk.yml).
Your team has high autonomy — and standups are vague, weekly meetings drift into status reports, and 1:1s produce nothing but "I'm fine." This playbook fixes all three layers at once. What's inside: • Daily Standup system — 3-field format, good sample, 4 COO principles to keep it honest • Weekly Meeting — strict 25-min agenda, Scrum Master rotation, 0–10 pulse check • 1:1 Framework — 9-dimension quantified pulse, 5-group deep question bank, bilateral feedback structure • Diagnostic layer — "stuck-at" detection: info / authority / collaboration / capability / direction • FAQ for 4 common failure modes (dead standups, status-report meetings, "I'm fine" 1:1s, scaling beyond 10 people) 🇨🇳 Your team has high autonomy — but standups are getting vague, weekly meetings turn into status reports, and you can't get honest answers in 1:1s. This three-layer Motivation playbook solves exactly this problem: standups are the information layer, weekly meetings are the alignment layer, and 1:1s are the individual layer. When these three things are done right, motivation isn't managed—it grows naturally. 🇯🇵 Your team has high autonomy, yet standups are vague, weekly meetings turn into progress reports, and you only get "I'm fine" in 1on1s — this playbook solves all three layers at once. 🇰🇷 Your team has high autonomy, but standups are vague, weekly meetings turn into progress reports, and you can't get honest feedback in 1:1s — this playbook solves all three layers simultaneously. Triggers: "team motivation" | "no one writes standups" | "weekly meetings turn into status reports" | "can't get honest answers in 1:1s" | "high-autonomy team management" | "how COOs manage teams" | "team motivation" | "standup best practices" | "1on1 framework" | "weekly meeting template" | "team motivation" | "team motivation" | "AI startup team ops" | "remote team alignment" | "engagement decline"
Interactive quiz tutor for Obsidian StudyVault learning. Use when the user wants to: (1) Take a diagnostic assessment of their knowledge, (2) Study or review specific sections/topics, (3) Drill weak areas identified in previous sessions, (4) Check their learning progress or dashboard, or says things like "quiz me", "test me", "let's study", "/tutor", "학습", "퀴즈", "평가".
Test, debug, or profile Roblox experiences. Use for Studio debugging, TestEZ, logging, connection cleanup, memory or network diagnostics, MicroProfiler, Scene Analysis, and Script Profiler.
Explain concepts, formulas, mechanisms, and principles until readers can recognize them, follow the derivation, and transfer them: use plain language to connect concrete situations, diagnostic criteria, operating processes, and conditions of validity. USE WHEN the user invokes ljg-explain, says “explain this in plain language,” “explain this concept or formula thoroughly,” “Feynman explanation,” or “ELI5,” or wants to understand a topic from scratch and apply it in new situations. NOT FOR simple polishing or translation, providing a read-along explanation of an entire work, interpreting a whole book or paper, or requests limited to a formal proof or procedural steps.