Loading...
Loading...
Found 5,029 Skills
Use when optimizing content for Xiaohongshu discovery, understanding why posts succeed or fail in reach, trying to increase content exposure, or troubleshooting low view counts
Create, read, update, and manage all Google Workspace documents and services via REST APIs. Use when working with Google Docs, Google Sheets, Google Slides, Google Drive, Gmail, Google Calendar, Google Chat, Google Forms, Google Meet, Admin SDK, or Apps Script. Triggers on: "Google Doc", "Google Sheet", "spreadsheet", "Google Slides", "presentation", "Google Drive", "Drive folder", "Gmail", "send email", "Google Calendar", "calendar event", "schedule meeting", "Google Chat", "Google Forms", "survey form", "Google Meet", "Workspace user", "Apps Script", "구글 문서", "구글 시트", "스프레드시트", "구글 슬라이드", "프레젠테이션", "구글 드라이브", "지메일", "이메일 보내기", "구글 캘린더", "일정 추가", "회의 예약", "구글 챗", "구글 폼", "설문지", "워크스페이스 사용자".
Set up Goldsky CLI authentication and project configuration. Use this skill when the user needs to: install the goldsky CLI (what's the official install command?), run goldsky login (including when the browser opens but 'authentication failed'), run goldsky project list and see 'not logged in' or 'unauthorized', switch between Goldsky projects, check which project they're currently authenticated to, or fix 'unauthorized' errors when running goldsky turbo commands. Also use for 'walk me through setting up goldsky CLI from scratch for the first time'. If any other Goldsky skill hits an auth error, redirect here first.
Go function design patterns including multiple return values, file organization, signature formatting, and Printf conventions. Use when writing functions, organizing Go source files, or formatting function signatures.
Apply Go style guide conventions to code
This skill should be used when the user asks to "write Go unit tests", "add tests to a Go package", "use the testing package", "write table-driven tests in Go", or needs guidance on Go test patterns, subtests, benchmarks, and test helpers.
Use when writing ANY Mongoose query (.find, .findOne, .findById, .aggregate, .populate), adding database operations to services or controllers, wiring data between services, building endpoints that read or write to MongoDB, or reviewing code that chains service calls. TRIGGER especially when about to write a new findById or pass an ID where a document could be passed instead.
Go programming language. Covers goroutines, channels, interfaces, error handling, and modules. Use for building concurrent, high-performance backend services. USE WHEN: user mentions "go", "golang", "goroutines", "channels", asks about "concurrency", "select statement", "interfaces", "error handling", "go modules" DO NOT USE FOR: Gin/Fiber/Echo frameworks - use framework-specific skills DO NOT USE FOR: GORM - use ORM-specific skill DO NOT USE FOR: gRPC - use API design skills
Use when executing or continuing a spec plan interactively. Triggers on: "spec go", "execute plan", "run plan", "continue plan", "work on plan", "start plan", "run the spec". Runs tasks with configurable breakpoints for review. Pass --bg for fully autonomous background execution.
Google Calendar integration. Manage communication data, records, and workflows. Use when the user wants to interact with Google Calendar data.
Go error handling patterns: wrapping with context, sentinel errors, custom error types, errors.Is/As chains, and HTTP error mapping. Use when implementing error returns, defining package-level errors, creating custom error types, wrapping errors with fmt.Errorf, or checking errors with errors.Is/As. Use for "error handling", "fmt.Errorf", "errors.Is", "errors.As", "sentinel error", "custom error", or "%w". Do NOT use for general Go development, debugging runtime panics, or logging strategy.
Go-specific code review with 6-phase methodology: Context, Automated Checks, Quality Analysis, Specific Analysis, Line-by-Line, Documentation. Use when reviewing Go code, PRs, or auditing Go codebases for quality and best practices. Use for "review Go", "Go PR", "check Go code", "Go quality", "review .go". Do NOT use for writing new Go code, debugging Go bugs, or refactoring -- use golang-general-engineer, systematic-debugging, or systematic-refactoring for those tasks.