Loading...
Loading...
Found 2,894 Skills
Write READMEs for software projects. The skill should be used when writing or revising a README or README.md file.
Upload PDF slides to CDN and configure chapter README with slides metadata. This skill should be used when adding teaching presentation slides to a chapter. Handles: PDF upload, part/chapter resolution, README frontmatter update, Teaching Aid heading.
Guide for creating or updating simple, standalone skills with a single SKILL.md file
Управление сотрудниками и тегами (группами). Создание, обновление, удаление, поиск сотрудников. Онбординг и offboarding. Создание и управление тегами. Используй когда нужно: найти сотрудника, создать пользователя, онбординг/offboarding, управлять тегами. НЕ используй для: собственного профиля (→ pachca-profile).
Minimal TTS smoke test for Model Studio Qwen TTS.
Create time-boxed technical spike documents for researching and resolving critical development decisions before implementation.
Help users organize weekly reports, presenting work value and boundaries in a complete logical manner. Triggered when users say "write weekly report", "weekly report", "organize weekly report", or "sort out work".
Create, improve, and test skills for the z-schema JSON Schema validator library. Use this skill whenever the user wants to create a new skill from scratch, turn a workflow into a reusable skill, update or refine an existing skill, write test cases for a skill, or organize reference material for a skill. Also use when someone mentions "skill", "SKILL.md", or wants to document a z-schema workflow for reuse by humans or AI agents.
세션 종료 전 HANDOFF.md 작업 인계 문서 생성. "인계", "handoff", "세션 정리" 키워드에 활성화.
Generate technical design documents using a standard template and save them to a group Yuque knowledge base. For group use — stores designs in group repos with review workflow. Requires group Token.
Produces comprehensive system architecture plans for features and products including component breakdown, data flow diagrams, system boundaries, API contracts, and scaling considerations. Use for "system design", "architecture planning", "feature design", or "technical specs".
Use when you need to generate "page list → function points → business processes → business rules" with evidence from frontend code, and the project has non-unique routing entries, complex dynamic routes/permissions/backend menus, and the team is prone to making assumptions or missing evidence chains.