Loading...
Loading...
Found 10,506 Skills
Shows a structured progress dashboard for an album with percentage complete per phase, blocking items, and status breakdown. Use for a quick visual overview of album progress.
Update dependencies safely — check changelogs, run tests, create PR
SSH into host `h100_sglang`, enter Docker container `sglang_bbuf`, work in `/sgl-workspace/sglang`, and use the ready H100 remote environment for SGLang development and validation. Use when a task needs remote CUDA work, GPU-backed smoke tests, diffusion checks, or a safe remote copy instead of local-only execution.
All-in-one WeCom CLI Suite covering 6 core business domains: Contacts, Messages, Documents (including three types: Document, Smart Sheet, Smart Document (formerly Smart Homepage)), Schedules, Meetings, and Tasks. It supports searching contacts by name/alias, sending and receiving messages (text/image/file/voice/video), creating/reading/editing documents in Markdown format, managing Smart Sheet structures and records, creating Smart Documents and exporting their content as Markdown, creating/modifying/canceling schedules and checking availability, booking/managing meetings, and creating/tracking/assigning tasks. This skill should be triggered even if users do not explicitly mention 'WeCom' as long as scenarios involving messages, schedules, tasks, etc., are involved.
Follow this sub-process for code optimization — handle tasks where 'behavior remains unchanged but structure changes' (structure / performance / readability). Shift single-module internal optimization from 'AI random refactoring' to 'first scan to generate a checklist, confirm each item with the user, execute step by step according to the method library, and obtain manual approval for each step'. Trigger scenarios: When the user mentions phrases like 'optimize / refactor / rewrite / split / poor performance / too long code' without any accompanying behavior changes. Do not handle new requirements (route to feature), bugs (route to issue), or cross-module architecture restructuring (route to architecture + decisions).
One-stop skill for the project architecture center — draft new architecture documents, refresh existing architecture documents, or conduct an architecture health check. Automatically determine the mode based on user input: `new` (draft)/ `update` (refresh to the latest code status)/ `check` (view only, generate issue list). The `check` mode has three sub-goals: consistency within a single feature design, alignment between design and code, and consistency among multiple documents under `easysdd/architecture/`. Single-target rule — only modify one document or check one target at a time. Trigger scenarios: User says "fill in an architecture doc", "draft an architecture document", "refresh the architecture directory", "write down the structure of this module", "conduct an architecture check", "is the design internally consistent?", "does the plan match the code?", "are there conflicts among several documents in the architecture folder?", or when it is found in the feature-design / feature-acceptance / implement phase that an architecture action needs to be performed first before proceeding.
8x8 integration. Manage Persons, Organizations, Deals, Leads, Activities, Notes and more. Use when the user wants to interact with 8x8 data.
When developing new features, follow this sub-process — take the vague idea of "add X capability" through to the acceptance closure, with solution documents archived so that both AI and users can later check the original thinking and decision rationale. Trigger scenarios are focused on adding new capabilities ("develop new feature", "add X", "implement XX"), and do not handle bugs in existing code. This skill only acts as a router, deciding which sub-skill to trigger next among brainstorm / design / fastforward / implement / acceptance based on existing artifacts.
Conduct a targeted code exploration of the repository, and document the process of "Ask Questions → Read Code → Draw Conclusions" as searchable evidence for direct reuse when similar questions arise next time. There are three types: question (investigate code around a specific question and provide conclusions), module-overview (sort out the structure, boundaries, entry points, and dependencies of a module), and spike (conduct lightweight technical exploration of multiple possible directions without making final decisions). Trigger scenarios: Users say "Let's explore first", "How is X implemented in this repository", "Quickly get familiar with this module", "Archive the exploration results". Refer to `codestable/reference/system-overview.md` for how to distinguish it from learning / tricks / decisions.
Radar integration. Manage Organizations. Use when the user wants to interact with Radar data.
CircleCI integration. Manage Projects, Users, Organizations. Use when the user wants to interact with CircleCI data.
Use when acting as Grunk - reads specs from beads, plans, implements, commits, tags pr-ready. Merged TL+Engineer. Works in loop mode or interactive mode.