255건 · 관련도순
Guide team Git work with consistent commit messages, branch naming, and review practices. Follow concrete steps for everyday development, urgent fixes, releases, merge conflicts, and version tags, including guidance on when to use merge or rebase.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Co-write proposals, technical specifications, and decision documents through context gathering, section-by-section drafting, and revision. A fresh AI reader then tests the document to reveal unclear explanations, missing context, and contradictions before it is shared.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Extract statistical values from research PDFs for meta-analysis, which combines results across studies. Track each value’s source and confidence, prioritize review, and manage human corrections and final approval in a shared data structure.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Coordinate collaborative academic and policy writing, from author roles and timelines to draft revision, reviewer responses, and submission materials. Improve clarity and reproducibility while preserving authorial voice and flagging changes to claims or interpretations.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Organize research code, datasets, and outputs with consistent folders and script names. Provides Python and Stata templates, processing stage numbers, and guidance for paths, logs, and documentation so collaborators can follow the workflow.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Coordinate research, drafting, citation and data verification, AI review, revision, and final formatting through connected skills. Start from a research topic, an existing manuscript, or reviewer comments, with progress tracking and user checkpoints.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create proposals for sponsored content or collaborations with brands and creators. Combine reference-based price ranges, content ideas, schedules, and estimated results, or define shared content, responsibilities, and cross-promotion plans in a Markdown document.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Coordinates a named team of Codex workers with concrete responsibilities and shared progress records. It selects available collaboration tools, manages communication and separate working copies when needed, and handles integration, team archival, and cleanup after the work ends.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create structured Claude skill packages, validate their files and metadata, and bundle them as ZIP archives. Share the new skill’s description and file links in a Slack channel through Rube so teammates can discover it.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Automate Box file uploads, downloads, searches, folder organization, and sharing permissions through an AI agent. Find documents using metadata, the attributes attached to files, and review or cancel existing Box Sign requests.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Delegate work or request information from another CCB-managed agent using ask. Use when the user asks Grok to ask, delegate to, hand off to, consult, or send work to a named CCB agent, or when project memory requires CCB collaboration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design the team's operating rhythm — task management, collaboration rituals, and tooling. Use when the day-to-day cadence needs structure. For a time-boxed sprint, use `design-sprint-plan`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Troubleshoots and debugs AWS Clean Rooms collaboration issues related to IAM roles, S3 bucket policies, KMS keys, Lake Formation permissions, and CloudWatch logging for custom ML model training and inference jobs. Use when a customer reports permission failures, access errors, or log publishing issues in Clean Rooms.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Start and scale networked products using Andrew Chen's "The Cold Start Problem" framework for network effects. Use when the user mentions "network effects", "chicken and egg", "cold start", "two-sided marketplace", "atomic network", "hard side", "liquidity", "critical mass", "invite-only launch", "how do I get my first users", or "the marketplace has no buyers or sellers". Also trigger when launching a marketplace, social, or collaboration product that is worthless without other users, deciding launch sequencing and seeding tactics, or diagnosing stalled network growth at scale. Covers the five stages: cold start, tipping point, escape velocity, hitting the ceiling, and the moat. For word-of-mouth virality, see contagious. For habit-driven retention, see hooked-ux.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply lean thinking to UX: hypothesis-driven design, collaborative sketching, and rapid experiments instead of heavy deliverables. Use when the user mentions "Lean UX", "design hypothesis", "outcome over output", "design studio method", "assumption mapping", "lightweight research", "too much design documentation", or "get the team designing together". Also trigger when reducing design-documentation overhead, getting cross-functional teams to co-design, or running fast usability experiments. Covers hypothesis statements, MVPs for UX, and cross-functional collaboration. For Build-Measure-Learn, see lean-startup. For usability audits, see ux-heuristics.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Administers the email, chat, meeting and file-sharing platform the organization runs on — tenant and domain configuration, mail authentication and routing, phishing and spam controls, shared mailboxes and distribution groups, external sharing and guest access, permission sprawl in file storage, and retention and legal hold. Use this to configure a tenant, tighten sharing, investigate a mail delivery or phishing problem, or work out who can see a file and why.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Designs a realistic, execution-aware biomedical study version under explicit constraints of samples, time, budget, data access, lab capacity, team skill, and validation resources. Always use this skill when the user has a real study idea, a candidate route, or a partially framed project but cannot assume ideal conditions. If critical feasibility inputs are missing, first clarify what resources are currently available, what resources may be obtainable, and what resources are realistically unavailable. Do not invent access, capabilities, collaborations, or validation resources. Focus first on feasibility-constrained study framing, route narrowing, dependency control, and minimum viable study design.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
You are an expert team communication specialist focused on async-first standup practices, AI-assisted note generation from commit history, and effective remote team coordination patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide changes through code checks, testing, commits, and pull request preparation. Use when coordinating a complete Git workflow and verifying readiness for collaboration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manages work transitions between team members or agents by creating structured handoff documents, summarizing project status, documenting key decisions, blockers, and open questions, and generating onboarding briefs. Use when someone needs to hand off, hand over, or transition a project; pass work to another person or agent; brief a colleague taking over; prepare a shift change summary; or onboard someone mid-task. Produces ready-to-use handoff documents covering current status, next steps, known issues, technical context, and communication templates for both planned and unplanned transfers.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Coordinates parallel investigation threads to simultaneously explore multiple hypotheses or root causes across different system areas. Use when debugging production incidents, slow API performance, multi-system integration failures, or complex bugs where the root cause is unclear and multiple plausible theories exist; when serial troubleshooting is too slow; or when multiple investigators can divide root-cause analysis work. Provides structured phases for problem decomposition, thread assignment, sync points with Continue/Pivot/Converge decisions, and final report synthesis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Performs a structured five-stage code review covering requirements compliance, correctness, code quality, testing, and security/performance. Each stage uses targeted checklists and categorized feedback (Blocker/Major/Minor/Nit) with actionable suggestions and rationale. Use when the user asks for code review, PR feedback, pull request review, or wants their code checked for bugs, style issues, or vulnerabilities — triggered by phrases like "review my code", "check this PR", "review my changes", "pull request review", or "code feedback".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write warm, direct collaboration comments. Trigger: PR feedback, issue replies, reviews, Slack messages, or GitHub comments.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
TikTok Shop product differentiation strategy tool. Analyze viral product trends, competitor affiliate strategies, content performance, and identify differentiation opportunities. Includes TikTok-specific metrics like engagement rate, viral potential, and creator collaboration insights. No API key required.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.