スキルレーダー · GITHUB
実際に使われている Agent Skills。
公開リポジトリの検証済み Skills を比較し、機能、内容、導入状況、出典を確認してから追加できます。
- 掲載範囲
- 検証済み
- Skills
- 1,033
- リポジトリ
- 142
- 最終同期
- 2026/08/31
googleworkspacegws-gmail-triage
Gmail: Show unread inbox summary (sender, subject, date).
- 導入数
- 4.1万
- GitHub Stars
- 3.1万
- 更新日
- 8月25日
googleworkspacegws-sheets-append
Google Sheets: Append a row to a spreadsheet.
- 導入数
- 4万
- GitHub Stars
- 3.1万
- 更新日
- 8月25日
pexoaipexo-agent
AI video generation skill with auto model selection across Seedance 2, Kling 3.0, HappyHorse, and 10+ models. Produces finished multi-shot videos (5–120s) from text, images, URLs, scripts, or audio — including AI music, lip sync, and multi-shot sequencing. Calls Pexo's external API, manages project status and billing confirmations, and transfers only user-approved briefs and assets. Runs setup diagnostics, stores generated downloads locally, and requires shell, outbound HTTPS, and local file access. Authenticated requests are locked to https://pexo.ai. No prompts to write, no models to choose. USE FOR: video production, AI video, make a video, product video, brand video, promotional clip, explainer video, short video, TikTok video, Instagram Reel, YouTube Short, product ad, text-to-video, image-to-video, video generation, AI video agent.
- 導入数
- 4万
- GitHub Stars
- 776
- 更新日
- 8月20日
tencentweread-skills
微信读书助手 — 搜索书籍、管理书架、查看笔记划线、浏览书评、阅读统计、发现推荐好书
- 導入数
- 4万
- GitHub Stars
- 198
- 更新日
- 7月1日
sambergolang-code-style
Golang code style conventions — line length and breaking, variable declarations, control flow clarity, when comments help vs hurt. Use when writing or reviewing Go code, asking about style or clarity, or establishing project coding standards. Not for naming conventions (→ See samber/cc-skills-golang@golang-naming skill), linter configuration (→ See samber/cc-skills-golang@golang-lint skill), or doc comments (→ See samber/cc-skills-golang@golang-documentation skill).
- 導入数
- 3.9万
- GitHub Stars
- 3116
- 更新日
- 8月26日
2dmuralireview-loop
- Iterative worker-reviewer cycle that spawns a critic subagent to score work 1-10 and provide actionable feedback, then revises until a quality gate is met. Use when implementing features, writing specs, reviewing existing code, or completing any task where quality matters more than speed. Trigger phrases: "use review-loop", "polish this", "iterate on this", "/review-loop", "review with feedback loop".
- 導入数
- 3.9万
- GitHub Stars
- 2
- 更新日
- 5月8日
clerkclerk-setup
Add Clerk authentication to any project by following the official quickstart guides.
- 導入数
- 3.9万
- GitHub Stars
- 69
- 更新日
- 8月31日
mastra-aimastra
Comprehensive Mastra framework guide for building agents, workflows, tools, memory, workspaces, and storage with current APIs. Use for documentation lookup, API verification, TypeScript setup, common errors, migrations, and mastra api CLI tasks: inspect or call resources on local, Mastra platform, Trace Intelligence, or remote servers.
- 導入数
- 3.9万
- GitHub Stars
- 75
- 更新日
- 7月30日
sambergolang-error-handling
Idiomatic Golang error handling — creation, wrapping with %w, errors.Is/As, errors.Join, custom error types, sentinel errors, panic/recover, the single handling rule, structured logging with slog, HTTP request logging middleware, and samber/oops for production errors. Built to make logs usable at scale with log aggregation 3rd-party tools. Apply when creating, wrapping, inspecting, or logging errors in Go code. For samber/oops specifics → See samber/cc-skills-golang@golang-samber-oops skill; for slog handler ecosystem → See samber/cc-skills-golang@golang-samber-slog skill.
- 導入数
- 3.9万
- GitHub Stars
- 3116
- 更新日
- 8月26日
sambergolang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI, or debugging flaky/slow tests. For testify-specific APIs see samber/cc-skills-golang@golang-stretchr-testify; for measurement methodology see samber/cc-skills-golang@golang-benchmark.
- 導入数
- 3.9万
- GitHub Stars
- 3116
- 更新日
- 8月26日
googleworkspacegws-tasks
Google Tasks: Manage task lists and tasks.
- 導入数
- 3.9万
- GitHub Stars
- 3.1万
- 更新日
- 8月25日
google-labs-coderemotion
Generate walkthrough videos from Stitch projects using Remotion with smooth transitions, zooming, and text overlays
- 導入数
- 3.8万
- GitHub Stars
- 8224
- 更新日
- 8月17日
clerkclerk-nextjs-patterns
Advanced Next.js patterns - middleware, Server Actions, caching with Clerk.
- 導入数
- 3.8万
- GitHub Stars
- 69
- 更新日
- 8月31日
sambergolang-design-patterns
Idiomatic Golang design patterns — functional options, constructors, error flow and cascading, resource management and lifecycle, graceful shutdown, resilience, architecture, dependency injection, data handling, streaming, and more. Apply when explicitly choosing between architectural patterns, implementing functional options, designing constructor APIs, setting up graceful shutdown, applying resilience patterns, or asking which idiomatic Go pattern fits a specific problem.
- 導入数
- 3.8万
- GitHub Stars
- 3116
- 更新日
- 8月26日
sambergolang-performance
Golang performance optimization patterns and methodology - if X bottleneck, then apply Y. Covers allocation reduction, CPU efficiency, memory layout, GC tuning, pooling, caching, and hot-path optimization. Use when profiling or benchmarks have identified a bottleneck and you need the right optimization pattern to fix it. Also use when performing performance code review to suggest improvements or benchmarks that could help identify quick performance gains. Not for measurement methodology (→ See samber/cc-skills-golang@golang-benchmark skill) or debugging workflow (→ See samber/cc-skills-golang@golang-troubleshooting skill).
- 導入数
- 3.8万
- GitHub Stars
- 3116
- 更新日
- 8月26日
shadcn-uishadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".
- 導入数
- 3.8万
- GitHub Stars
- 12.3万
- 更新日
- 8月31日
sambergolang-security
Security best practices and vulnerability prevention for Golang. Covers injection (SQL, command, XSS), cryptography, filesystem safety, network security, cookies, secrets management, memory safety, and logging. Apply when writing, reviewing, or auditing Go code for security, or when working on any risky code involving crypto, I/O, secrets management, user input handling, or authentication. Includes configuration of security tools.
- 導入数
- 3.8万
- GitHub Stars
- 3116
- 更新日
- 8月26日
clerkclerk-custom-ui
Custom authentication flows and component appearance - hooks (useSignIn, useSignUp), themes, colors, fonts, CSS. Use for custom sign-in/sign-up flows, appearance styling, visual customization, branding.
- 導入数
- 3.8万
- GitHub Stars
- 69
- 更新日
- 8月31日
insforgeinsforge
- Use this skill when writing app code with InsForge or @insforge/sdk: database CRUD, auth, storage uploads/storage RLS, functions, OpenRouter AI, realtime, emails, Stripe or Razorpay payments, or pointing S3-compatible tooling (aws CLI, AWS SDKs, rclone, Terraform, boto3) at InsForge Storage. Trigger on requests like add auth, fetch data, upload files, make a bucket public, add checkout, sell subscriptions, or send email. For infrastructure, SQL migrations, CLI commands, or payment provider setup, use insforge-cli instead.
- 導入数
- 3.8万
- GitHub Stars
- 36
- 更新日
- 8月29日
insforgeinsforge-cli
- Use this skill whenever someone needs a backend, or a task touches InsForge backend or cloud infrastructure through the InsForge CLI: projects, SQL, migrations, RLS policies, functions, storage, backups, deployments, compute, secrets, config, schedules, logs, diagnostics, advisor scans and suppressions, import/export, AI/OpenRouter setup and usage overview, Stripe/Razorpay payments, Apify web scraping / data sources, PostHog product analytics, backend branches, organization membership (invite, leave, delete), agent memory (remember/recall project facts and decisions), reporting InsForge-side bugs or doc discrepancies (feedback), or CLI docs. For app code with InsForge or @insforge/sdk, use the insforge app-integration skill instead.
- 導入数
- 3.8万
- GitHub Stars
- 36
- 更新日
- 8月29日
vuejs-aivue-best-practices
MUST be used for Vue.js tasks. Strongly recommends Composition API with and TypeScript as the standard approach. Covers Vue 3, SSR, Volar, vue-tsc. Load for any Vue, .vue files, Vue Router, Pinia, or Vite with Vue work. ALWAYS use Composition API unless the project explicitly requires Options API.
- 導入数
- 3.8万
- GitHub Stars
- 2815
- 更新日
- 5月30日
sambergolang-concurrency
Golang concurrency patterns. Use when writing or reviewing concurrent Go code involving goroutines, channels, select, locks, sync primitives, errgroup, singleflight, worker pools, or fan-out/fan-in pipelines. Also triggers when you detect goroutine leaks, race conditions, channel ownership issues, or need to choose between channels and mutexes.
- 導入数
- 3.8万
- GitHub Stars
- 3116
- 更新日
- 8月26日
wshobsonbrand-landingpage
Brand-first landing page designer — runs a brand-identity interview (colors, typography, shape language), then generates and iterates on a polished landing page via Stitch with deployment-ready HTML. Use when the user asks to create, design, or build a landing page, homepage, or marketing page and has no established visual direction. Skip when they have a design mockup, need a dashboard or app UI, are working at component level, building a multi-page app, or restyling with known design tokens — use frontend-design instead.
- 導入数
- 3.7万
- GitHub Stars
- 3.9万
- 更新日
- 8月31日
sambergolang-naming
Go (Golang) naming conventions — covers packages, constructors, structs, interfaces, constants, enums, errors, booleans, receivers, getters/setters, functional options, acronyms, test functions, and subtest names. Use this skill when writing new Go code, reviewing or refactoring, choosing between naming alternatives (New vs NewTypeName, isConnected vs connected, ErrNotFound vs NotFoundError, StatusReady vs StatusUnknown at iota 0), debating Go package names (utils/helpers anti-patterns), or asking about Go naming best practices. Also trigger when the user mentions MixedCaps vs snakecase, ALLCAPS constants, Get-prefix on getters, or error string casing. Do NOT use for general Go implementation questions that don't involve naming decisions.
- 導入数
- 3.7万
- GitHub Stars
- 3116
- 更新日
- 8月26日