458건 · 관련도순
This skill should be used when the user asks to "create AGENTS.md", "update AGENTS.md", "maintain agent docs", "set up CLAUDE.md", or needs to keep agent instructions concise. Enforces research-backed best practices for minimal, high-signal agent documentation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a user asks for a concise Solana token research snapshot with market, trade, and security context
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Periodic repository health check — install, full validation, unused-code scan, outdated/vulnerable dependencies, and docs drift — ending in a concise report and, when there are safe fixes, a single PR. Designed to run unattended from a scheduled routine; also usable on demand.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turns one meeting transcript, recording recap or set of raw notes into concise DRAFT minutes returned in the chat as a single Markdown document: header metadata, attendance and apologies, agenda items each with a short neutral summary and outcome, numbered decisions with an owner, numbered action items with owner and due date, open questions, carried-over actions and the next-meeting line, every entry backed by a short verbatim source fragment and every missing fact marked UNKNOWN. Use when the user asks to "write the minutes", "draft minutes from this transcript", "turn these notes into meeting minutes", "produce the minutes of meeting for today's call", "tidy my rough minutes into the standard format" or "prepare the minutes for circulation". Do not use for extracting action items, task lists or per-owner follow-up emails alone, use transcript-to-actions instead. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Capture decisions and commitments after a meeting and draft a concise follow-up.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user explicitly invokes the `if` skill or asks for a concise, laconic, no-fluff, or to-the-point answer. Do not trigger on the ordinary word or programming keyword `if`. Detailed, step-by-step, exhaustive, educational, or fixed-length requests activate only when they also include an explicit invocation or brevity request.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Keep decision maps as concise routers from decisions to canonical documents and validation guardrails.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review someone else's PR through an architectural/strategic lens — does it shift design, raise complexity, or quietly change precedent? Drives a brief reflective discussion with the user, then posts a concise review comment via `gh`. Defers line-level and bug-hunting concerns to AI review bots and the PR author.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn an approved meme idea, image, or short source into a concise humorous video draft with a clear hook, caption plan, and platform variants.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Recast a supplied everyday photo as a witty illustrated product instruction sheet with a large Chinese title and concise English annotations. Use for 日常说明书、宠物使用说明、生活物品冷幽默说明图 or a fictional everyday object manual poster.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Extract bounded, source-linked context from large files or many inputs. Use when context is too large, files are oversized, or a task needs concise excerpts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write B2B cold outreach and follow-up sequences grounded in relevance, evidence, concise value, compliant sending practices and clear calls to action.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Multi-source research synthesizer. Takes a question, runs 3-5 parallel web searches with varied phrasings, deduplicates, and returns a cited, concise answer. For Hebrew questions, searches in both Hebrew and English. Output is always under ~400 words.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats/abuse paths, or perform AppSec threat modeling. Do not trigger for general architecture summaries, code review, or non-security design work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Refresh a safe, concise map of this GCI World 2026 workspace before deeper course, assignment, or dataset work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate a concise and structured PR description from commit history with minimal token usage
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze yesterday's prompts to surface one technical concept worth understanding, delivered as a concise morning lesson with everyday analogy + engineer vocabulary. Use when "morning lesson", "prompt mirror", "today's learning", "what should I learn", or via scheduled automation each morning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user asks to "create AGENTS.md", "update AGENTS.md", "maintain agent docs", "set up CLAUDE.md", or needs to keep agent instructions concise. Enforces research-backed best practices for minimal, high-signal agent documentation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Help the user understand the current topic visually with concise diagrams, code-shape sketches, and focused HTML artifacts. Use when the user asks to show / diagram / visualize / sketch / illustrate what is going on, asks "what does this look like", "how does this flow", "show me the structure", or in Japanese 図で見せて / 図解して / 図にして / 構造を見せて / フローを見せて / 全体像を見せて / どうつながってるか見せて. Also use it proactively when an explanation is running long and a call tree, file tree, component tree, diff, Mermaid diagram, or a small HTML artifact would land faster than prose.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.