Loading...
Loading...
Found 23 Skills
Core standards for all GitHub workflow agents. Covers authentication, smart defaults, repository discovery, dual MD+HTML output, screen-reader-compliant HTML accessibility standards, safety rules, progress announcements, parallel execution, and output quality. Apply when building any GitHub workflow agent - issues, PRs, briefings, analytics, community reports, team management.
Clarify scope through dialogue, surface key decisions and open questions. Use before planning.
An intelligent assistant designed for long-form online novel creation, supporting full-process management from setting generation to main text writing, including intelligent quality control and state synchronization. (Yunshu Optimized)
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.
Enter this sub-process when conducting code optimization — handle tasks where 'behavior remains unchanged, 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 require manual approval for each step'. Trigger scenarios: Users mention phrases like 'optimize it / refactor / rewrite / split it / poor performance / code is too long' 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).
Use when you need to create new skills or update existing ones, integrate and package domain knowledge, workflows, scripts and tools into reusable Skills; the newly generated skills must be written in Chinese. Trigger words: create new skill, update skill, create new skill package, expand AI capabilities.
Conduct targeted code exploration on a repository, and document the process of "Asking Questions → Reading Code → Reaching Conclusions" as searchable evidence for direct reuse when similar questions arise next time. There are three types: question (investigate code around a specific problem and provide conclusions), module-overview (organize the structure, boundaries, entry points, and dependencies of a module), spike (conduct lightweight technical exploration of multiple possible directions without making final decisions). Trigger scenarios: When users say "Let's explore first", "How is X implemented in this repository", "Quickly get familiar with this module", "Archive the exploration results". For the distinction from learning / tricks / decisions, refer to the root skill `easysdd`.
Standardize the article editing process to ensure clear modification scope, trackable progress, and documented changes. Use this skill when the user says "edit article", "revise article", "adjust content", or "modify this piece".
Generate project-level AGENTS.md guides that capture conventions, workflows, and required follow-up tasks. Use when a repository needs clear agent onboarding covering structure, tooling, testing, task flow, README expectations, and conventional commit summaries.
驗證規格檔案的完整性與一致性，確保所有必要的規格元素都已定義且符合標準格式。
When writing complex features or significant refactors or user ask explicitly, use an ExecPlan from design to implementation.
Directory convention, numbering system, and workflow for multi-session implementation plans. Follow when creating phased feature plans that span multiple sessions.