Review focus and context switching over a chosen period without inventing productivity scores.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
이메일, 캘린더, 할 일 관리, 자동화 (7.9천건)
Review focus and context switching over a chosen period without inventing productivity scores.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Gate for any outbound message before it leaves: pull request or issue comment, DM, invite, post, email. Use before sending to check facts, tone, platform rules, registry status and AI-slop, and to block text that fails.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Check, search or digest Gmail across several mailboxes over the owner's own OAuth connector, with no browser and near-zero tokens for the raw pull. Read-only by default: drafting and sending go through the outbound approval gate. Triggers: "/gmail", "check mail", "any important emails", "find the email about <X>".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Default to Firefox for browser automation and decide when Chrome is truly required. Use before any task that needs a browser: fetching a page, grabbing cookies, headless runs, logging into a site. Includes a matrix of which tasks must stay on Chromium and why. Triggers: /firefox, /ff, via firefox, need a browser, headless browser, which browser to use, browser automation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
- Craft advanced search-engine queries and Google dorks to surface hidden files, documents and mentions. Use when building a Google dork, hunting a leaked document, or searching paste sites and document repositories for a name, email or selector
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Pull fresh meetings from Granola (summaries, transcripts, participants) into an Obsidian vault over the official API. Incremental and idempotent by note id and updated_at, so re-runs make no duplicates. Triggers: "/granola-sync", "pull granola", "refresh meetings".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Show the operator's day: today's calendar plus what needs them personally (leads due, people awaiting a reply, deadlines), pulled from Calendar and Telegram and ranked. Read-only: sends and commits nothing. Triggers: "/agenda", "what's on today", "my agenda".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write a bold, value-adding follow-up when your own outbound message got silence: check the thread, pick a second channel, add new value instead of a bare bump. Use when an email, DM or PR comment went unanswered. Triggers: /bold-followup, /bump, follow up on silence, second channel.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
ЧИП ТОЛЬКО ПО ПРЯМОМУ ЗАПРОСУ ЮЗЕРА (anton 14.08): сделать ЧИПЫ (spawn_task), которые юзер нажмёт сам.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Drive the current task to a verified result instead of stopping at a plausible report. Use when the user says /continue, keep going, not done yet, push further, or is unhappy with the result. Rebuilds requirements from the conversation, re-checks real state, fixes root causes, verifies from the consumer side, offloads side quests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Publishes HTML or Markdown as display.dev URLs with public, company, or private access. Supports signup, claiming, sharing, browsing, bounded reads, exact edits, and comment iteration. Use when the user asks to "publish this", "share this", "share with the org", "post this online", "make a private link", "share with [email]", "publish a report", "list my artifacts", "find an artifact", "publish a large file", "publish this generated HTML file", "read this artifact", "search inside this artifact", "change this passage", "make a copy of this artifact", "duplicate version", "create a display.dev account", "claim this publish", "add a company email domain", "transfer an email domain", "change the email domains add-on", "watch comments on this artifact", "respond to comments", or "resolve this comment thread". Use whenever a request contains a display.dev artifact URL (`*.dsp.so/*`). Anonymous publishing returns a 30-day preview and browser claim URL.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply an explicit, current-turn-only concise response mode without changing task rules, verification, or technical payload.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when executing implementation plans with independent tasks — dispatches fresh subagents per task with two-stage review (spec compliance, then code quality)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Save session state before context gets full or before ending. Writes current task state, branch, and loaded docs to claude/tasks/todo.md so the next session can resume cleanly.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate a parallel workstream plan for multi-agent Claude Code work. Decomposes a feature into independent workstreams, each ownable by a separate Claude Code instance. Saves to claude/tasks/ACTION_PLAN.md.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create a ticket/issue description with evidence-backed proof sections. Reads claude/templates.md for the template format. Saves to claude/tasks/ticket-<slug>.md.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Resume a previous session from claude/tasks/todo.md. Use at the start of a new session to restore context and continue where you left off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan a non-trivial task before implementing. Use when the task requires 3+ steps, multiple files, or an architectural decision. Writes a checkable plan to claude/tasks/todo.md.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to create bug reports, feature requests, or task issues, update existing issues, add labels/assignees/milestones, manage repository labels, set issue fields (dates, priority, custom fields), set issue types, manage issue workflows, link issues, add dependencies, or track blocked-by/blocking relationships. Triggers on requests like "create an issue", "file a bug", "request a feature", "update issue X", "set the priority", "set the start date", "create a label", "rename a label", "list repo labels", "link issues", "add dependency", "blocked by", "blocking", or any GitHub issue management task.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Triages GitHub issues and PRs into maintainer-facing cards: what each is, why it matters, author trust, risk, test and CI state, blockers, and next action. Use when the user says triage inside a repository or needs to work through an issue or PR queue.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Iterate on a PR until actionable CI passes and high/medium review feedback is addressed. Use for PR CI failures, review feedback, or green-check loops; do not wait for human approval, draft status, or merge gates.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
All changes to code must follow the guidance documented in the repository. Before any issue is filed, branch is made, commits generated, or pull request (or PR) created, a search must be done to ensure the right steps are followed. Whenever asked to create an issue, commit messages, to push code, or create a PR, use this skill so everything is done correctly.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Microsoft Store Developer CLI (msstore) for publishing Windows applications to the Microsoft Store. Use when asked to configure Store credentials, list Store apps, check submission status, publish submissions, manage package flights, set up CI/CD for Store publishing, or integrate with Partner Center. Supports Windows App SDK/WinUI, UWP, .NET MAUI, Flutter, Electron, React Native, and PWA applications.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.