Loading...
Loading...
Found 6,994 Skills
Embedded CAN/CAN-FD debugging tool for interface scanning, message monitoring, test frame transmission, log recording, database file decoding, and bus statistics. Automatically triggered when users mention CAN, CAN-FD, DBC decoding, bus packet capture, USB-CAN joint debugging, message transmission, bus statistics, PCAN, Vector, slcan, CAN interface scanning, CAN ID filtering, ASC logs, BLF files. Also compatible with explicit invocation via /can. Even if users only say "check CAN messages", "send a test frame" or "decode DBC", this skill should be triggered as long as the context involves CAN bus communication.
Runs Visual Regression Testing (VRT) locally to prevent disqualification in Web Speed Hackathon. Captures screenshots, compares against baselines, updates snapshots, and validates visual integrity after performance optimizations. Use when optimizing WSH apps, running VRT checks, updating VRT baselines, or investigating VRT failures.
Phase 1 of the Issue Workflow - Translate the user's problem into a reproducible, traceable {slug}-report.md through conversation. The AI only asks "what you saw, how to reproduce it, what should happen" here, and does not guess the root cause for the user (that's Phase 2's responsibility). This phase is also the only official decision point for determining whether to take the fast track or the standard path: first read the relevant code based on the user's description, and if the root cause can be identified at a glance and the changes required are minor, directly inform the user to take the fast track. Trigger scenarios: The user says "file an issue", "log this bug", "I found a problem". This is the starting point of the issue workflow with no pre-requisites.
Solve CAPTCHAs in automated browser sessions using third-party solving services. Use this skill whenever you need to: bypass a CAPTCHA while automating a website, integrate CAPTCHA solving into a Playwright or Puppeteer script, solve reCAPTCHA v2 or v3, hCaptcha, Cloudflare Turnstile, or image-based CAPTCHAs, automate a login or form submission that's blocked by a CAPTCHA, test a page that has CAPTCHA challenges, or write a script that needs to pass a CAPTCHA programmatically. Also triggers for: "recaptcha", "hcaptcha", "turnstile", "captcha solving", "bypass captcha", "solve captcha", "pass captcha challenge", "automate past captcha", "get past robot check", "bot verification". Always use this skill for any CAPTCHA-related automation — even simple cases benefit from correct token injection patterns.
Design brainstorming and structural divergence engine. Generates 8-10 radically different product/design concepts using creative provocation techniques, persona lenses, and axis-based divergence. Concepts differ in mechanism, not styling. Outputs an interactive React prototype with a concept picker and per-concept DialKit tuning controls. Triggers on "diverge", "explore directions", "brainstorm directions", "conceptual range", "radically different concepts", "product directions", "divergent prototypes", "explode the solution space", "give me range".
Audit a codebase for maintenance and modernization. Challenges scope, reviews architecture/quality/tests/performance/dependencies, files deferred work via bd. Language-specific addendums for iOS/Swift, Go, and Web/JS/CSS activate automatically based on what's in the repo. Supports monorepos with mixed stacks.
Create ShinkaEvolve task scaffolds from a target directory and task description, producing `evaluate.py` and `initial.<ext>` (multi-language). Use when asked to set up new ShinkaEvolve tasks, evaluation harnesses, or baseline programs for ShinkaEvolve.
Cubox CLI is a callable personal reading memory system that enables you to search, read, and use saved content, perform semantic (RAG-based) queries, access articles, highlights, and metadata, save URLs, update content states, and retrieve annotations and structure such as folders and tags. Use this tool when a task depends on the user’s reading history or requires context from their Cubox library.
Persistent research knowledge base that accumulates papers, ideas, experiments, claims, and their relationships across the entire research lifecycle. Inspired by Karpathy's LLM Wiki pattern. Use when user says "知识库", "research wiki", "add paper", "wiki query", "查知识库", or wants to build/query a persistent field map.
Use this skill when generating higher-level synthesis notes such as literature reviews, comparison matrices, project summaries, or other cross-note summaries inside the project knowledge base.
Draft or update requirement documents under `codestable/requirements/` for the project — use **user stories + plain language** to describe a capability's "reason for existence, solution approach, and boundaries", so non-technical readers can quickly understand the highlights of the system. Layered with architecture: requirement is the "problem space" (why this capability is needed), while architecture is the "solution space" (what structure is used to implement it). Two modes: new (draft a new requirement doc from scratch), update (refresh an existing doc based on new materials or implementation changes). Single-target rule — only modify one document at a time. Trigger scenarios: the user says "fill in a requirement doc", "write down the requirements for this capability", "update the requirements directory", or during the feature-design phase, it is found that there is no corresponding requirement for the capability to be implemented this time.
Patch, extend, or explain DatoCMS front-end integration code inside an existing web project (Next.js App Router, Nuxt, SvelteKit, Astro, plus React/Vue/Svelte component usage). Use for targeted, per-concern work — adding a draft mode endpoint, wiring Preview Links / Visual Editing flows, fixing Content Link overlays, tuning real-time preview updates/subscriptions, setting up cache-tag invalidation/revalidation flows (Next.js revalidateTag or CDN purge by tags), adding robots/sitemap wiring, or hooking up crawler-safe search integration. Also the go-to skill for framework component/hook wiring with react-datocms, vue-datocms, @datocms/svelte, and @datocms/astro: Image/SRCImage/datocms-image, StructuredText, VideoPlayer (React/Vue/Svelte), SEO/meta helpers (renderMetaTags/toHead/Seo), QuerySubscription/QueryListener realtime patterns, ContentLink components, and Site Search (React/Vue). Prefer this skill whenever the user is modifying a live codebase one concern at a time, asking a framework-specific API question, or mixing several front-end concerns in the same patch.