398건 · 관련도순
Set up a task list, workplace memory files, and a dashboard. Use existing todos to clarify nicknames, abbreviations, and project names, then save that context for future conversations with the agent.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review open employee leave cases for legal deadlines and required decisions. Identify cases needing action around leave designation, certification, or entitlement exhaustion, explain why they need attention, and summarize cases without issues briefly.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Deploy and operate Vercel projects from the command line. Manage environment variables and domains, investigate build failures with logs and metrics, and handle platform settings while checking which project and team each operation targets.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build and update Convex backend code, including schemas, queries, authentication, storage, and scheduled jobs. Apply input and output validation, indexed data access, and deployment checks to verify the implementation.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Maintain data retention in ClawHub's Convex tables by classifying each table, defining expiration fields, and bounding cleanup jobs. Guide changes to temporary data and expired authentication records, with focused tests and runtime verification.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Route Convex development and operations requests to the relevant specialist skills and current procedures, covering app setup, backend features, code reviews, authorization checks, production monitoring, data migrations, and cost analysis.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Add capabilities to an existing Convex app by consulting an online catalog for matching procedures. If no procedure is available, it falls back to hosting setup or a component search, then installs and connects the selected component.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Map a website’s exposed services by collecting subdomains, active hosts, and current or historical URLs. Inspect JavaScript and exposed files, prioritize areas for security testing, and monitor new subdomains and GitHub commits.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create bash scripts for routine Linux administration, including backups, resource monitoring, user management, and log analysis. Templates also cover scheduled tasks, file cleanup, encryption, and network checks, providing starting points for automating recurring maintenance.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Deploy serverless browser automation as cloud functions using Browserbase. Use when the user wants to deploy browser automation to run on a schedule or cron, create a webhook endpoint for browser tasks, run automation in the cloud instead of locally, or asks about Browserbase Functions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when administering, operating, or debugging a GoClaw gateway through the GoClaw CLI/runtime package. It covers CLI discovery, safe command inspection, gateway health/config diagnostics, agents, skills, MCP/tools, runtime packages, credentials, traces, sessions, channels, providers, cron/jobs, and troubleshooting. Always inspect the live `goclaw --help` output first because command availability is version-dependent.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Backend and infra for a project via Cohesivity (cohesivity.ai). Provisions Postgres, hosting and deploys, auth and social login, realtime websockets, an agent-native email inbox, object and vector storage, Redis, cron, and AI model APIs (OpenAI, Anthropic, Deepgram, Exa) through one HTTP API. Use when a valid .cohesivity file exists, a Cohesivity MCP is available, the user names Cohesivity, or the project needs a backend or any of these services and no competing provider was chosen.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design and generate .envelope.json AI agent team definitions — the open standard for multi-agent teams with hierarchy, access policies, human-in-the-loop gates, and cron schedules.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run or configure the daily wiki maintenance cycle: check source freshness, refresh the index and hot.md, and manage its scheduled 9 AM launchd/systemd/cron reminder. Use for daily or morning wiki refresh or scheduler setup and verification.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reactive streams and event-driven programming in Golang using samber/ro — ReactiveX implementation with 150+ type-safe operators, cold/hot observables, 5 subject types (Publish, Behavior, Replay, Async, Unicast), declarative pipelines via Pipe, 40+ plugins (HTTP, cron, fsnotify, JSON, logging), automatic backpressure, error propagation, and Go context integration. Apply when using or adopting samber/ro, when the codebase imports github.com/samber/ro, or when building asynchronous event-driven pipelines, real-time data processing, streams, or reactive architectures in Go. Not for finite slice transforms (→ See `samber/cc-skills-golang@golang-samber-lo` skill).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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 snake_case, ALL_CAPS constants, Get-prefix on getters, or error string casing. Do NOT use for general Go implementation questions that don't involve naming decisions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5] [--notify-channel -1002381931352]
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide for upgrading Grails applications from Grails 7.x to Grails 8, covering Java 21, Groovy 5 name resolution and static compilation, Spring Boot 4.1, Spring Framework 7, dependency management, Micronaut, Jackson 3, Hibernate 7, TagLibs, testing, content negotiation, asset pipeline wildcard paths, and validation behavior changes
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Routes serverless requests to a compute form factor and the skill that owns it. Applies first to Lambda, API Gateway, EventBridge, Step Functions and event-driven work while the compute, orchestration or integration choice is open — API backends, webhooks, jobs, cron, queue/stream consumers, durable workflows, event routing, Step Functions vs Durable Functions, and Pipes vs native event source mappings for queues and streams. Decides Event Functions on-demand vs Managed Instances, Web Functions, MicroVMs, EventBridge rules/Scheduler/Pipes/bus, HTTP vs REST API. Owns shared Lambda references (cold starts, SnapStart, concurrency, event sources, function URLs, throttling, troubleshooting). Defers to the specialized skill once a request commits to one form factor or service, or describes its defining feature, even unnamed (durable checkpointing and automatic step retries, Firecracker sandbox, managed instances, Node.js server). Not for EC2, ECS/EKS/Fargate or Amplify hosting.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pg_cron, pgmq), vector/semantic search (pgvector), and restoring dumps (pg_restore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turns one-shot external recon into a continuous monitoring program. Covers the scheduled re-scan-and-diff loop (baseline snapshot -> interval sleep -> re-scan -> asset/finding delta -> threshold-gated webhook alert), the scan-to-scan diff engine (new/removed/changed assets by a tracked-attribute table, new/resolved findings by a stable cross-scan fingerprint), adversary CTI / chatter monitoring across six public feeds (ransomwatch, ransomware.live, HackerNews Algolia search, Reddit security-subreddit RSS, GitHub Gist code-search, public Telegram channel scraping) with a source-kind-aware severity engine (leak-site/forum/telegram/paste tiers, CRITICAL through INFO), literal/glob/regex watchlist pattern matching, full-corpus capture with retroactive rescan on new watchlist entries, infrastructure-tracking-over-time discipline (certificate-transparency, passive-DNS, port/service, and typosquat re-enumeration cadence, and what a genuine 'perimeter drift' event looks like in the diff output), a five-state finding-lifecycle state machine (open/triaged/risk_accepted/resolved/false_positive) with per-severity SLA and fingerprint-based cross-scan dedup and auto-resolve/reopen rules, the alert-fatigue trap where a lifecycle-unaware rule re-fires on an already-accepted finding, a durable retry/backoff alert-outbox pattern ('queued is not delivered'), and copy-paste bash-cron plus PowerShell-Scheduled-Task recipes for a re-scan+diff loop with the Slack-compatible webhook payload shape. Passive OSINT and analysis only -- no new active-intrusion technique. Use when setting up ongoing monitoring for a retainer or MSSP engagement, tuning alert thresholds to avoid fatigue, triaging a finding's lifecycle status, investigating adversary chatter about a brand, building a 'what changed on the perimeter since last week' report, or deciding whether a persisting finding should re-alert.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Linux privilege escalation playbook. Use when you have low-privilege shell access and need to escalate to root via SUID/SGID binaries, capabilities, cron abuse, kernel exploits, misconfigurations, or credential harvesting on Linux systems.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Schedule reminders and recurring tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when developing WordPress plugins: architecture and hooks, activation/deactivation/uninstall, admin UI and Settings API, data storage, cron/tasks, security (nonces/capabilities/sanitization/escaping), and release packaging.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.