Loading...
Loading...
Found 621 Skills
Audits docs/en/specifications/, docs/en/issue/, and docs/en/policy/ for English documents that are missing a Korean translation in docs/ko/, or where the Korean version appears out of date compared to the English source, then creates or updates those translations. Use this to keep docs/ko/ in sync. Triggered by "sync docs", "번역 동기화", "update translations", "sync translations", or "mirror docs".
Validate Claude Code skills against the agentskills specification. Catches structural, semantic, and naming issues before users do.
WeChat Sticker Maker. Automatically crop and convert original images in 6-grid, 9-grid, or 12-grid layouts into formats that comply with WeChat sticker specifications (main sticker image 240x240, chat page icon 50x50).
AIWorkflowOrchestratorの正本仕様を `references/` から検索・参照・更新するスキル。 resource-map / quick-reference / topic-map / keywords を起点に、必要最小限の文書だけを段階的に読む。 用途: 要件確認、設計/API/IPC契約確認、UI/状態管理/セキュリティ判断、task-workflow・lessons-learned・未タスク同期。 特に safeInvoke timeout、settings bypass、skill lifecycle、global nav、Skill Center / Workspace / Agent / Skill Creator の導線再編を扱う。 Anchors: • Specification-Driven Development / 適用: 正本仕様同期 / 目的: 実装-仕様整合の維持 • Progressive Disclosure / 適用: resource-map起点読込 / 目的: 必要最小限参照で漏れ防止 Trigger: 仕様確認, 仕様更新, task-workflow同期, lessons-learned同期, UI仕様反映, API/IPC契約確認, セキュリティ要件確認, safeInvoke, timeout, settings bypass, skill lifecycle, Skill Center, Workspace, Agent, Skill Creator, navContract, GlobalNavStrip, MobileNavBar, SkillManagementPanel, line budget reform, spec splitting, family split, generated index sharding
This skill MUST be loaded on every git commit without exception. It should also be used when the user asks to "write a conventional commit", "format a commit message", "follow conventional commits spec", "create a semantic commit", "make a commit", "commit changes", or "git commit". Every commit message produced in this project MUST conform to this specification.
Create an icon system specification covering grid, sizing, naming, categories, and implementation guidance.
Craft elegant technical specifications with ASCII artistry, flow diagrams, and the Grove voice. The swan glides with purpose—vision first, then form, then perfection. Use when creating specs, reviewing documents, or transforming technical plans into storybook entries.
Uses Microsoft RESTler to perform stateful REST API fuzzing by automatically generating and executing test sequences that exercise API endpoints, discover producer-consumer dependencies between requests, and find security and reliability bugs. The tester compiles an OpenAPI specification into a RESTler fuzzing grammar, configures authentication, runs test/fuzz-lean/fuzz modes, and analyzes results for 500 errors, authentication bypasses, resource leaks, and payload injection vulnerabilities. Activates for requests involving API fuzzing, RESTler testing, stateful API testing, or automated API security scanning.
Conducts comprehensive backend design reviews covering API design quality, database architecture validation, microservices patterns assessment, integration strategies evaluation, security design review, and scalability analysis. Evaluates API specifications (REST, GraphQL, gRPC), database schemas, service boundaries, authentication/authorization flows, caching strategies, message queues, and deployment architectures. Identifies design flaws, security vulnerabilities, performance bottlenecks, and scalability issues. Produces detailed design review reports with severity-rated findings, architecture diagrams, and implementation recommendations. Use when reviewing backend system designs, validating API specifications, assessing database schemas, evaluating microservices architectures, reviewing integration patterns, or when users mention backend design review, API design validation, database design review, microservices assessment, or backend architecture evaluation.
Create git commits following Conventional Commits specification with project-specific branch naming rules. Use for commit message generation, changelog, and versioning.
Trigger Scenarios: (1) Explicit memory requests – remember, record, don't forget, pay attention next time, form rules, generate summaries/record documents; (2) Correction and modification – note, incorrect, wrong, it should be, change to, replace with, don't, also need, missing; (3) Preference expression – I prefer, in the future, it's better, suggest, my habit, I usually; (4) Global specifications – unified, all, every, any, each, every time, all, uniformly; (5) Conversation end settlement – when the conversation ends naturally or the topic switches. Convert users' corrections, preferences and rules into structured memory files to improve the output quality of subsequent conversations.
Create agent company packages conforming to the Agent Companies specification (agentcompanies/v1). Use when a user wants to create a new agent company from scratch, build a company around an existing git repo or skills collection, or scaffold a team/department of agents. Triggers on: "create a company", "make me a company", "build a company from this repo", "set up an agent company", "create a team of agents", "hire some agents", or when given a repo URL and asked to turn it into a company. Do NOT use for importing an existing company package (use the CLI import command instead) or for modifying a company that is already running in Paperclip.